Not Just Another Number: How We Actually Get to Know Every Participant We Support

Before he came to us, a participant we'll call David (details changed here to protect his privacy, as they are throughout this post) told us the thing he dreaded most about support work had nothing to do with his disability. It was Mondays. Specifically, it was the small dread of not knowing who'd be knocking on his door, whether they'd read his notes, and whether he'd have to explain, again, why he needed his morning routine done in a particular order, or what it meant when he went quiet instead of asking for help.

He'd come from a larger provider where the roster changed often enough that consistency wasn't really on offer. Support workers were capable and well-meaning, but they were reading a file, not a person. Every new face meant starting from zero. That's not a complaint about any individual worker. It's what happens when a system is built around filling shifts rather than understanding people.

We hear a version of David's worry constantly, from participants and from the families and support coordinators who refer them to us. It's rarely "will I get support." It's "will the support actually understand me." That's a fair thing to worry about, and it's not solved by a mission statement. It's solved by a process, so that's what we built.

When someone joins CDC, the first thing we do isn't roster them. It's sit down with them (and family or a support coordinator, if they want that) and build an actual profile of how they operate day to day. Not just the funded supports listed in the plan, but the practical detail underneath it: how they communicate, what a good day looks like versus a bad one, what routines matter and why, what's never worked with past providers and what has. That profile is what a worker reads before they ever meet the participant, not after.

Then we deliberately keep the roster small and consistent for that person, instead of pulling from whoever's free that week. New workers are introduced gradually, usually shadowing an existing worker first, so the handover happens face to face and the participant isn't the one doing the explaining. It's slower to set up than just filling a shift. It's also the difference between a support worker who knows to give David quiet time in the mornings, and one who's meeting him for the first time and reading it as disengagement.

None of this makes us immune to the ordinary logistics of running a roster: people get sick, go on leave, move on. What it changes is what happens when that happens. A backup worker who's already met the participant and read their profile, not a stranger starting from a blank page. And because our participant numbers are kept deliberately small, if something isn't working, it gets back to the team directly, not lost in a call queue and rediscovered three shifts later.

David's been with us for a while now, and that Monday dread is gone. He knows who's coming, and they know him. That was the actual problem we set out to fix, and it stayed fixed. What we didn't promise, and what no provider honestly can, is that support work makes every day easy. He still has hard days. The difference is that whoever's there on a hard day already knows what helps, instead of him having to teach a stranger in the middle of it.

If you're currently with a provider and this sounds familiar (the re-explaining, the rotating faces, the sense of being a shift rather than a person), that's exactly the gap we built this process to close. We're happy to talk through what switching would actually look like for your situation.