How to Conduct a Smooth and Professional Intake Session

Will, EnableUs Community

So, I- I- I was actually looking through some old NDIS audit preparation files last week, and- and it hit me how incredibly dry we've made the intake process. It- it- it's usually just a checklist, right? Name, date of birth, NDIS plan number, funding categories, tick, tick, tick. But if you actually look at how the NDIA wants us to do this, the entire foundation is supposed to be about, um, what they call the dignity of risk. The idea that people with disability have the right to make choices, even if those choices involve, you know, taking reasonable risks to pursue their goals.

Winter, EnableUs Community

Right, dignity of risk. But- but how does that actually translate to an intake form? Because usually, when a provider sees the word "risk," they immediately think, oh, liability. We need to cover ourselves. How do we stop them doing anything slightly dangerous?

Will, EnableUs Community

Exactly! That's the admin trap. We build these risk assessments that are basically designed to put the participant in bubble wrap so the organization doesn't get sued. But the NDIA guidelines literally state that people learn through trial and error. They learn from mistakes just like everyone else. So if your intake risk assessment is just a list of things the participant is *not* allowed to do, you've- you've completely failed the dignity of risk test before the service even starts.

Winter, EnableUs Community

Yeah, it- it becomes a gatekeeping exercise rather than a support planning exercise. I mean, if I'm a participant and I walk into an intake session, and the first forty-five minutes is just you asking for my NDIS number and then telling me what I can't do because of "health and safety"... I- I'm not going to feel very empowered, am I? I'm going to feel like a folder on a shelf.

Will, EnableUs Community

Exactly, you're a transaction. So, to avoid that, you have to flip the structure. You don't start with the NDIS plan number or the budget. You start with the person. You- you literally ask them, "What does a good day look like for you?" Or, "What's worked well with previous providers, and what made you want to scream?" You get their goals in *their* own words first. Once you have that foundation of who they actually are, then—and only then—do you pull out the administrative paperwork to see how the funding can actually make those things happen.

Winter, EnableUs Community

Hmm. I- I like that. It- it shifts the dynamic completely. It's like, instead of saying, "Here is our service, how do you fit into it?" we're saying, "Here is your life, how do we support it?" But wait, how do you do a risk assessment collaboratively then? If they want to do something that *is* actually quite risky, how do you document that without the auditor losing their mind?

Will, EnableUs Community

Well, that's where the collaborative partnership comes in. Instead of you, the provider, writing down "Participant cannot do X because of risk Y," you sit down together and say, "Okay, you want to learn to catch the public bus by yourself. That's fantastic. Let's talk about what might go wrong, and what safeguards *you* want to put in place to manage that." Maybe they suggest carrying a fully charged phone with a tracking app, or having a written plan of what to do if they miss their stop. You're- you're documenting *their* strategies. That way, the risk assessment isn't a barrier—it's actually a roadmap to independence. And guess what? Auditors absolutely love seeing that because it proves choice and control are actually happening in practice, not just on a policy document.

Winter, EnableUs Community

Yes! It- it shows the actual process of decision-making, not just a signed piece of paper. Which, actually, brings up consent. Because when we talk about NDIS audits, consent is always the big stumbling block, isn't it? It's- it's usually just a single tick box on the back of a ten-page service agreement that someone signed three years ago and everyone forgot about.

Will, EnableUs Community

Oh, look, the "ticked-once-and-never-revisited" consent form is- is the bane of an auditor's existence. If an auditor looks at a file and just sees a signature on a standard form, they're going to dig. They want to know *how* that consent was obtained. Did the person actually understand what they were signing, or did someone just point to the dotted line and say "sign here to get your services"?

Winter, EnableUs Community

Right, so we need to prove the *how*. Like, did we offer an Easy Read version? Was there an interpreter there? Or maybe an advocate? We need to document that whole conversation, not just the signature.

Will, EnableUs Community

Precisely. Your intake notes should explicitly state, um, "Easy Read consent form was provided and discussed. Participant confirmed they understood we would share their support plan with their speech therapist, but specifically requested we do not share details with their uncle." You need that level of detail. It proves genuine, informed, and- and specific consent. And it has to be dated! You'd be amazed how many undated consent forms we see in audits. If there's no date, as far as an auditor is concerned, it didn't happen.

Winter, EnableUs Community

And that ties back to keeping the risk assessment dynamic too, right? Because a participant's life changes. If they have a health crisis, or their living situation changes, that intake risk assessment from two years ago is completely useless.

Will, EnableUs Community

Completely useless! If an incident occurs, and the auditor goes back to the file and sees the risk assessment hasn't been touched since the day they signed up... that's a massive non-conformance. You need triggers in your system. If there's a hospital admission, or a change in behaviors, or even a change in support staff, that should automatically trigger a review of the risk assessment. It has to be a living document, not something you do once to tick a compliance box and then hide in a digital drawer.

Winter, EnableUs Community

Which means the intake session isn't a one-off event, really. It's the launchpad for an ongoing conversation. And- and that includes things like culture and communication. I hate it when you see an intake form where "cultural needs" is just a tiny tick box at the very end, like an afterthought.

Will, EnableUs Community

Yeah, "Are you from a culturally diverse background? Yes or No." It's- it's terrible. Cultural and communication needs shape the *entire* way you conduct the intake session itself. You don't ask about language preferences at the end of the meeting—you need to know that *before* you book the meeting so you can have the interpreter there from minute one. If family involvement is central to how they make decisions, you- you need to invite the family to the intake, not just send them the completed paperwork afterwards. It's about respecting their environment and their way of communicating right from the very first hello.

Winter, EnableUs Community

Yeah, it's about shifting from a system-first mindset to a person-first mindset. If you get those foundations right at intake—the dignity of risk, the genuine consent, the cultural safety—then the compliance and the audit stuff, it- it actually just falls into place naturally because your documentation reflects real life.

Will, EnableUs Community

Exactly. It's not about writing things down just for the auditor; it's about documenting the real, respectful relationship you're building with the participant. If you do that, the audit takes care of itself. Anyway, that's probably a good place to wrap this one up. Good chatting, talk soon!

Winter, EnableUs Community

Catch you later.