Welcome to the show. Winter, the sharpest line in this whole topic is this: your policies can look immaculate on paper, but the audit interview is where an auditor finds out whether anyone in the organisation can actually LIVE them. And that word "live" is the bit that bites, hey. Because a Stage 2 audit interview is not the auditor admiring your incident policy in a PDF. It's them asking a support worker, in real time, "What do you do if an incident happens?" And if the answer is, "Uh... I'm not sure," that one "not sure" tells them more than ten polished documents. Exactly. Documents tell the auditor what your systems ARE. Interviews reveal whether your people understand those systems and use them properly. That's why providers who prep their people as carefully as their paperwork usually do better, especially on the certification pathway in 2026. I think some providers still underestimate that. They sort of act like the interview is a side chat. It's not. The auditor isn't randomly having a yarn with one worker and one participant just for colour. The sample is set using a formula tied to organisation size, participant numbers, and the number of sites you operate from. And that formula point matters. Because you won't know in advance exactly who gets picked. Leadership, coordinators, support workers, carers, participants -- any of those people may be in scope. So if your prep strategy is, "We'll just coach the management team and hope for the best," you've already missed it. "Hope for the best" is doing a lot of work there. Because if you've got, say, multiple sites, more participants, more staff, the sample broadens. The implication is organisation-wide readiness, not a little performance from your three most confident people. Right. And participant interviews are probably the most revealing part. Auditors use them to hear directly how the service actually feels to the person receiving it. Do they feel safe? Do they know how to complain? Were they involved in their support plan? Do staff listen to what they want? That list -- "safe," "complain," "support plan" -- that's basically the NDIS Practice Standards made human. Rights and responsibilities. Choice and control. Person-centred support. If your policies say all the right words but the participant says, "No one explained my rights," or "I don't know who to talk to if something's wrong," that's a massive gap. Yes. And auditors know the difference between values that are embedded and values that are decorative. A policy can say "person-centred" twelve times. But if a participant can't recognise that in their day-to-day support, then it's rhetorical, not real. Decorative compliance. That's rough, but fair. And it's why participant interviews carry so much weight. They're not a box-ticking exercise. They're the closest thing an auditor has to a live customer reality check. There's also a tension here providers need to hear: the more polished and scripted your interview answers sound, the less credible they can become. Auditors are experienced. If everyone sounds like they're reading the same script, that can raise MORE questions, not fewer. Especially with participants. Coaching a participant on what to say is both ethically wrong and, honestly, strategically clumsy. If a participant sounds rehearsed, the auditor's thinking, "Why was this person prepared like a witness?" That's the opposite of trust. And trust is really the currency here. Honest, natural answers -- even imperfectly worded ones -- are usually stronger evidence than a perfect line delivered like a school speech. So what does good prep actually look like? First, with participants: consent comes BEFORE anything else. Participation is opt-out, but the provider still has to ask whether the participant wants to be involved, explain what the interview means, and document it if they don't want to take part. And that documentation piece is not admin fluff. If a participant declines, record the reason and let the auditor know. That's important because getting participant evidence is part of the audit process, and overlooking consent or opt-outs can leave the auditor without evidence they were expecting. I want to slow that down. "Document the reason" sounds tiny, but it's one of those tiny things that can save confusion later. Without it, an auditor may wonder whether the participant was never offered the choice, whether communication needs were missed, whether the provider just... forgot. Exactly. And when you explain the interview to participants, keep it simple. Tell them an auditor may ask about their experience with your service. Tell them there are no right or wrong answers. Tell them their responses won't affect their support in any way. That phrase -- "no right or wrong answers" -- I reckon providers should almost memorise that one. Not for the participant to repeat, but for the provider to say. Because it lowers pressure. It tells the participant, this is about YOUR experience, not passing a test. And if the participant has complex communication needs, think ahead about adjustments. Maybe the auditor needs to adapt the way they ask questions. Maybe extra time is needed. Maybe a different communication approach helps. Discuss that with the auditor in advance. But don't cross the line into coaching. Don't feed answers. Don't rehearse stories. You're preparing the environment, not manufacturing evidence. Now staff. Good preparation here is short, practical, and repeated. Run brief sessions before the audit where workers can talk through common questions: What do you do if a participant makes a complaint? How do you report an incident? What does person-centred support mean in your actual work? What training have you completed, and when? And if someone answers, "Person-centred support means... providing quality care," that's your cue to keep going. Because that's too vague. A stronger answer is concrete: "I ask the participant what matters to them, I follow their support plan, I respect their choices, and if they want something changed, I escalate that through the right process." Perfect example. Auditors are listening for real-world understanding. Same with incidents. A strong answer isn't "We follow policy." It's "We log the incident in this platform, notify this role, document what happened, and follow the next steps under our process." That platform detail -- "this platform" -- that's what makes an answer believable. You're describing the actual machine room, not the brochure. Leadership needs the same discipline. Key personnel should be able to explain qualifications and training checks, risk management, complaints and feedback, service agreement review, participant rights, and quality monitoring in plain language. Not by reading a document. Not by hiding behind jargon. This is where senior people can get caught, weirdly enough. Because they know TOO much jargon. If the person responsible for governance can't explain the risk management framework in a ten-minute conversation a normal human can follow, the auditor may think the system exists more on paper than in practice. And in 2026, there's even more focus on proactive risk and continuous improvement. Auditors want to see not just that you responded to problems, but that you learned from them. Internal audits, self-assessments, improvement plans, actions from previous audit findings -- those all matter. Let me try to explain that back. It's not enough to say, "We fixed the complaint." You also need to show, "We reviewed why it happened, changed the process, monitored the change, and used that learning to improve service quality." Is that basically it? That's it. Almost exactly. The interview is about proving your systems are active, not static. That they adapt as the organisation grows and learns. And during the interview itself, the safest answer is the honest one. If you know, say it clearly. If you don't know, say you don't know and offer to find out. Auditors don't punish uncertainty the way they punish guessing, inaccuracy, or evasiveness. Honesty builds credibility. Guessing burns it. Same with idealised answers -- don't describe how the service should work in a perfect world. Describe how it ACTUALLY works in your organisation, with your real people, your real process, your real records. So if an auditor raises a concern in the interview, don't get defensive. Treat it like useful intelligence. It's a signal about what they may explore next in the documentation review. Yeah. The interview isn't theatre. It's evidence. And the providers who do well are usually the ones whose people can speak plainly, specifically, and truthfully about the service they're already delivering. Which is maybe the cleanest test of all: if your team can't explain your systems in their own words, do they really own them? Thanks for listening.
Audio Coursesby Jellypod