Quality and Safeguards Commission audits now explicitly assess service accessibility. If you can't produce call records, response time data, or a documented phone protocol, that's a compliance gap. Learn what auditors are looking for and how to prepare.
The NDIS Quality and Safeguards Commission (QSC) audit framework focuses on 6 practice standards. Standard 1 (service delivery) and Standard 4 (communication) both touch on accessibility. The implicit question: How do you ensure participants can reach you when they need you?
Auditors don't just look at paper records (service plans, invoices, participant feedback). They increasingly ask operational questions: How long does it take to answer a phone? What happens to missed calls? Do you track incoming enquiries? Can you show me data on call response times?
If you don't have phone records, response time data, or a documented phone protocol, auditors will flag it as a potential accessibility gap.
This isn't bureaucratic nitpicking. The QSC's mandate is to protect participants. Poor accessibility—meaning participants can't reach you when they need help—is a safeguarding issue. An audit finding here can result in a compliance order or, in severe cases, deregistration.
When auditors assess Standard 1 (service delivery) and Standard 4 (communication), they're implicitly asking:
1. How accessible are you? Do participants have a direct phone line? Is there a documented protocol for how calls are handled? What's your average response time?
2. What happens to missed calls? If a participant calls and reaches voicemail, do you have a system for returning that call? By what time? Do you track missed calls?
3. Can you show evidence? Phone records, call logs, response time data, documentation of your phone protocol—these are now audit evidence. If you don't have them, you can't prove compliance.
4. Is accessibility equitable? Do all participants have equal access, or is there a gap? (E.g., participants calling after 3 PM can't reach anyone, so they're effectively locked out.) Equity gaps are compliance failures.
An auditor interviews a participant: "How do you contact your provider if you need something?" Participant: "I call, but usually it goes to voicemail. I've waited 3–4 hours for a callback." Auditor makes a note. Later, auditor asks the provider: "What's your protocol for returning calls?" Provider: "We try to get back to people within 24 hours." Auditor: "Do you track response times?" Provider: "No, not formally."
Result: An audit finding under Standard 4 (communication): The provider does not have documented evidence of how it ensures responsive, accessible communication with participants.
The finding isn't severe (not a risk to safety), but it's a compliance gap. The provider is given 30 days to implement a phone protocol, document response times, and submit evidence of compliance.
1. Documented phone protocol: A written policy that answers: What's our phone line number? Who answers? What's our target response time? What happens to voicemail? Is there an after-hours protocol?
2. Call tracking data: Phone records showing incoming calls, missed calls, call duration, and resolution. Even basic data (number of calls per month, average response time) is sufficient. The point is to show you're monitoring accessibility.
3. Participant feedback: Evidence that you ask participants about accessibility. E.g., "Can you easily reach us?" Include feedback from surveys, meetings, or complaint logs. If participants report difficulty reaching you, address it in your response to the audit.
4. Response time evidence: Logs or records showing how quickly you return calls. If your protocol says "same day," show examples of voicemails returned within 24 hours. If your protocol says "2 hours," show call logs with timestamps.
Pro tip: If you use a phone service that tracks calls automatically (e.g., an AI voicemail system, a call-tracking app), keep monthly reports. Send these to your auditor. They're evidence of accessibility monitoring.
Step 1: Document your protocol. Write a simple phone policy. Example:
"Incoming calls are answered during business hours (9 AM–5 PM, Monday–Friday). If the clinician is with a client, calls are answered by admin staff or go to voicemail. Voicemails are returned within 2 hours on the same day. After-hours calls go to an emergency protocol [describe]. We track all incoming calls and response times monthly."
Step 2: Implement call tracking. Use your existing phone system or add a simple tracking tool. Log: date, time, caller name, reason for call, outcome (answered/voicemail/transferred), response time.
Step 3: Generate monthly reports. By the 1st of each month, run a summary: total calls, average response time, number of missed calls, any patterns. Share this internally so staff know you're tracking.
Step 4: Gather participant feedback. In your quarterly or annual participant satisfaction survey, ask: "How easy is it to reach us by phone?" Collect feedback. If it's negative, it's an opportunity to improve. If it's positive, it's audit evidence.
Step 5: Keep audit-ready documentation. Folder structure: /Audit Readiness/Phone Protocol, /Call Logs (monthly), /Participant Feedback (accessibility questions), /Response Time Data. When the auditor arrives, you can hand over evidence immediately.
An audit finding on accessibility isn't the end of your NDIS journey, but it triggers a compliance order. You'll have 30–60 days to respond, implement changes, and submit evidence. The process is time-consuming and stressful.
Worse, audits can be triggered by participant complaints. If a participant files a complaint about difficulty reaching you, the QSC will investigate. Without documented phone records, you're in a weak position to defend yourself.
The alternative: Get ahead of it now. Implement a phone protocol, start tracking calls, gather feedback. By the time an auditor arrives, you can show accessibility monitoring already in place.
CallSorted's AI phone assistant answers incoming calls, logs every interaction, and tracks response times automatically. The result: detailed, audit-ready call records with zero manual effort. Each call is documented, every voicemail is logged, and response time data is generated monthly.
For an NDIS provider preparing for audit, this is invaluable evidence of accessibility and responsiveness. You can hand an auditor 12 months of call data proving your commitment to participant accessibility.
Your phone isn't just operational. It's now audit evidence. QSC audits assess accessibility, and accessibility means responsiveness. Document your phone protocol, track your calls, gather participant feedback, and be ready to show evidence. An audit-ready phone system is a competitive advantage and a safeguarding best practice.