Bridging the Gap Between Written Policy and Daily Operations

Winter, EnableUs Community

Hey everyone, welcome back to The EnableUs Community Podcast. It’s Winter here, and today we’re talking about something I see all the time with small NDIS providers – you’ve got these gorgeous policy documents, they tick every box, but then you walk onto a shift and what’s actually happening… looks nothing like what’s written down.

Will, EnableUs Community

Yeah, totally. Hey folks, it’s Will. I’ve literally sat with providers who proudly show me this super polished Incident Management Policy, then in the next breath admit that half their support workers have never actually read it, and everyone does documentation a bit differently depending on who trained them on day one.

Winter, EnableUs Community

And if you’re listening to this going, yep, that’s us, you are so not alone. This gap between what the policy says and what happens on an ordinary Tuesday afternoon is everywhere, not just in NDIS. Research keeps showing the same pattern: policies don’t usually fail because they’re badly written; they fail because they never turn into changed behaviour.

Will, EnableUs Community

Exactly. I like how the article we’re drawing from puts it – that beautiful policy manual in the filing cabinet means nothing if staff don’t reference it, don’t understand it, and don’t follow it when they’re actually delivering supports. And for small providers, you feel this really sharply because you don’t have ten layers of middle management smoothing it out.

Winter, EnableUs Community

Let’s paint a picture for a second. You’ve got policies for Incident Management, Privacy and Confidentiality, Complaints Handling, Risk Management – all the big hitters, maybe from a template pack or a consultant. On paper, you’re like, we’re sorted, bring on the audit. But then, you look at real practice: support workers handle a complaint in the moment, but never record it as a complaint, or incidents get mentioned in a handover chat and never make it into the incident system.

Will, EnableUs Community

Or documentation is super inconsistent. One worker writes detailed, clear notes, another writes two lines and forgets key elements your Documentation Policy actually requires. Suddenly there’s a big gap between what you say you do and what you can prove you do, which is where compliance risk starts to creep in.

Winter, EnableUs Community

So why does this happen? One big reason is how policies are created. A lot of small providers either write them in isolation – just the director at home on a Sunday with a coffee and the NDIS Practice Standards – or they buy a set that’s written in quite technical, legal language. It might impress an auditor, but it doesn’t speak to the support worker who’s on shift at 7 pm dealing with a real issue.

Will, EnableUs Community

Yeah, if your Incident Management Policy reads like it was written by lawyers for lawyers, support workers are gonna struggle to translate that into “what do I actually do right now?” The article really stresses plain language – policies that talk directly to the people who have to use them. If staff can’t see themselves in the policy, they just won’t reach for it.

Winter, EnableUs Community

Another thing we see is the assumption that emailing out the policy is the same as implementing it. You know that move: “We updated the Complaints Policy, we sent it to everyone, so job done.” But no one’s actually explained why it matters, what’s changed, or what staff are expected to do differently tomorrow when a participant says, hey, I’m not happy with this.

Will, EnableUs Community

I was working with a small provider who had a really solid Complaints Handling Policy. It literally said all the right things about fairness, prompt responses, escalation, all that. But when we looked at practice, most complaints were just… disappearing. Staff were trying to fix things on the spot, which is great, but nothing was being documented. There was no clear process in their heads beyond “keep the participant happy.”

Winter, EnableUs Community

And the staff weren’t being dodgy – they just hadn’t had that bridge built between the words in the policy and what that means moment-to-moment. They didn’t know who exactly receives a complaint, how to record it, what the timeframes are. The policy existed, but the process in people’s brains was fuzzy.

Will, EnableUs Community

So that’s the core problem we’re unpacking in this episode: closing that gap. How do you go from lovely written documents to staff actually referencing them, understanding them, and following them when they’re with participants? And the good news is, especially for small providers, you can make big improvements with some very practical tweaks.

Winter, EnableUs Community

Yeah, we’re gonna stay really grounded. No theory for theory’s sake. We’ll talk about making policies practical and staff-friendly, then about baking them into your training, your systems, and your supervision so compliance becomes the easy default, not an extra chore.

Will, EnableUs Community

Alright, let’s get into the first big lever: making policies actually usable. The article talks about constantly asking, can frontline staff realistically implement what you’re proposing? And I love that question, because it forces you out of your office and into the real world.

Winter, EnableUs Community

Yeah, like, picture your newest support worker on a busy shift. If they grabbed your Complaints Handling Policy right now, could they work out what to do, or would they just feel overwhelmed? One of the key ideas from the article is breaking big policies into smaller, very concrete procedures and tools.

Will, EnableUs Community

So you might have an overarching Complaints Policy that sets out your values – fairness, prompt response, learning from feedback. But then you pair that with a Complaints Handling Procedure that literally walks through the steps: who receives complaints, where to record it, what’s the timeframe for acknowledging it, and when to escalate.

Winter, EnableUs Community

And then you go one step further again and turn that into a simple checklist or flowchart that sits where staff can see it – like “What to do when someone complains.” Step one: listen and acknowledge. Step two: record it in this form. Step three: notify this person. When you do that, staff aren’t trying to remember a big policy; they’re following a clear, small process.

Will, EnableUs Community

Another big point from the article is involving frontline staff and team leaders when you develop or review policies. Don’t do it all in isolation. Your support workers know exactly where things get clunky. They’ll say, that step is impossible on a sleepover shift, or we don’t actually have that form on site.

Winter, EnableUs Community

I remember a service where the Risk Management Policy said risk assessments had to be reviewed monthly. Great in theory, but the roster and systems weren’t set up for that, so workers just did it whenever they remembered. When we sat down with the team leaders, they came up with a really workable process – tying reviews to a particular week of the month and using a quick checklist. That came from listening to the people doing the work.

Will, EnableUs Community

And language really matters. The article is quite blunt about this: if your policy sounds like it was written by lawyers, staff will struggle. So swap out dense, bureaucratic phrasing for clear, direct sentences. Instead of “staff shall ensure the timely and appropriate documentation of incidents,” just say, “After every incident, you must complete the incident form before the end of your shift.”

Winter, EnableUs Community

Yeah, I love that. Talk to staff, not at them. Another massive piece is how you train. The article is really clear that just handing out documents is not training. When you introduce a new or updated policy, you want implementation training – time set aside to explain why it matters, and what staff need to do differently now compared to before.

Will, EnableUs Community

And make it real. Instead of reading the Medication Management Policy line by line – which, honestly, will lose people in about two minutes – use scenarios. The article gives good examples: what if a participant refuses prescribed medication? What if the tablets look different today than they usually do? Work through those together and show exactly how the policy guides the response.

Winter, EnableUs Community

I’ve seen role plays be so powerful here, especially for things like complaints or tricky conversations. I know people groan when you say “role play,” but once they get into it, they actually start to feel more confident. The article calls this out as a way to build competence before they’re in a real, emotionally charged situation where getting it wrong has serious consequences.

Will, EnableUs Community

Yeah, like practicing how to respond when a family member is really upset about something. If your staff have had a safe space to try that out, they’re much more likely to apply the policy calmly in real life. And from a compliance point of view, you’re not just hoping they’ll figure it out – you’re actively building the skill.

Winter, EnableUs Community

So, if you’re a small provider listening, a really practical takeaway from this chapter is: take one key policy – maybe Complaints, maybe Incidents – and ask three questions. One: is it written in language my support workers actually use? Two: have I got a clear, simple procedure or checklist that sits under it? And three: have I done real training with scenarios, not just emailed the PDF?

Will, EnableUs Community

If the answer is no to any of those, that’s your starting point. You don’t have to fix every policy at once. Pick the one that matters most for participant safety or risk right now, and make that one truly practical and staff-friendly. Then keep going from there.

Winter, EnableUs Community

Alright, so we’ve talked about making policies clearer and training people properly. The next step the article really emphasises is building those policies into the systems and routines your staff use every day. Because if following a policy relies purely on memory, it’s going to fall over.

Will, EnableUs Community

Yeah, the line that stuck with me was that policies become part of practice when you embed them into the tools staff use daily. So if your policy requires certain documentation, your forms and digital systems need to prompt for that information. Otherwise, you’re expecting staff to remember 20 different requirements while juggling real-life support.

Winter, EnableUs Community

A simple example is risk assessments. If your Risk Assessment Policy says you’ll review participant risks monthly, don’t leave that as a nice sentence in a document. Build reminders into your calendar or rostering system. Maybe you set up a repeating task for the case manager, or a checklist that sits alongside the shift planner for that week.

Will, EnableUs Community

The article also talks about checklists that walk staff through required elements. So for documentation, you might have a quick “before you finish your shift note, have you…” list that mirrors your Documentation Policy. Things like: did you record what support was provided, any changes in the participant’s condition, any incidents or complaints, and any follow-up actions?

Winter, EnableUs Community

And don’t forget the physical environment. I thought that was a really practical point in the article. If your Infection Control Policy requires handwashing at certain times, but the sink is miles away or there’s no soap, guess what – compliance will suffer. If your Privacy Policy says no discussing participant info in public, but your only handover space is the noisy café downstairs, staff are set up to fail.

Will, EnableUs Community

So part of closing the gap is removing those environmental barriers. Ask yourself: does our setup make it easy or hard to follow the policy? Sometimes a simple change like adding a wall-mounted hand sanitiser near the front door, or designating a private corner for handovers, makes compliance much more realistic.

Winter, EnableUs Community

Then there’s supervision. The article is clear that regular supervision is a key place to reinforce policy and catch gaps. It suggests supervisors routinely talk with staff about how they’re applying policies, where they’re unsure, and then coach them when practice doesn’t quite align.

Will, EnableUs Community

I really like the idea of using documentation reviews as teaching moments. So if a supervisor looks at shift notes and sees they consistently miss elements your policy requires, instead of just saying “do better,” you sit down and unpack why those elements matter, and help the staff member build new habits for future notes.

Winter, EnableUs Community

And it shouldn’t just be informal. Performance management systems can and should include policy compliance as part of how you assess performance. The article points out that when staff know adherence to policies affects their reviews and progression, they take it more seriously – as long as you balance that with support.

Will, EnableUs Community

Yeah, because if you punish people for honest mistakes or where the policy was genuinely unclear, you create fear and secrecy, not improvement. The focus needs to be on learning. That flows into the last big theme – monitoring the policy-practice gap and adapting policies based on what you find.

Winter, EnableUs Community

The article suggests some really doable monitoring strategies: spot checks of documentation, observing service delivery to see if safety procedures are actually being followed, audits of participant files to check assessments and plans are up to date, and even anonymous staff surveys about barriers to compliance.

Will, EnableUs Community

And when you do find gaps, the key message is: don’t jump straight to blaming staff. First ask why. Is the policy unclear? Is it impractical in the real environment? Did staff actually get enough training? Are there system or resource barriers? Once you know the root cause, you can choose the right fix – clearer wording, better tools, more training, or a system tweak.

Winter, EnableUs Community

I also liked that the article encourages looking for patterns over time. If multiple staff have the same issue with the same requirement, it’s probably not “a bad worker”; it’s a policy or implementation problem. That’s your cue to review that part of the policy or the way you’re training it.

Will, EnableUs Community

And that’s where the relationship between policy and practice becomes two-way. Policies guide practice, but practice feeds back into policy. Frontline staff need clear ways to say, hey, this bit doesn’t work, or this step creates a barrier. That might be in team meetings, through a suggestion box, or in regular policy review sessions.

Winter, EnableUs Community

So if we boil this down for small NDIS providers, I’d say your first three steps could be: one, pick a critical policy and make it truly practical – plain English, clear procedure, simple tools. Two, embed that policy into your systems – forms, reminders, environment – so following it is the easiest path. And three, use supervision and simple monitoring to see how it’s working in real life and adjust based on what you find.

Will, EnableUs Community

Yeah, and remember you don’t have to overhaul everything overnight. Start small, learn from what happens, and keep that feedback loop open. That’s actually how you build a culture where policies aren’t just documents, they’re how you do things every day.

Winter, EnableUs Community

Alright, we’ll wrap it there. Thanks for hanging out with us on Using Compliance Documents. I hope this has given you some really concrete ideas to start closing that gap between what’s on paper and what’s happening with your team on the floor.

Will, EnableUs Community

Yeah, thanks for listening. Have a think about which policy you want to tackle first, maybe chat it through with your team leaders, and just take that first practical step.

Winter, EnableUs Community

We’ll be back with more bite-sized episodes on using your compliance documents in a way that actually helps your staff and your participants, not just your audits. I’m Winter…

Will, EnableUs Community

And I’m Will. Take care, and we’ll catch you in the next one.