A participant's behaviour support plan, allied-health reports and incident history are
30–60 pages each — several hundred pages in total, and none of it written for the person standing in the
room at 11pm on a Tuesday. This is what those documents look like when they are replaced by two pages
of “this happens → do this”. Start on Plan, then switch to Caseload
to see how many of them are actually current.
Current and actioned
–
plan in date and read by every rostered worker
Past their review date
–
still the plan staff are working from
BSP but no current daily plan
–
the clinical plan exists; the usable one doesn't
Source documents out of date
–
expired, overdue, or newer than the plan built on them
The caseload
Every participant across the four SIL sites, the state of their daily
support plan, and whether the people on shift have actually read the current version.
How long since each plan was reviewed
Days since last review, against a six-month
review cycle. Bars past 180 days are shown in red and labelled overdue.
What the plans are built on
Each daily plan derives from clinical and allied-health source documents.
A plan can be in date while the document underneath it is not — or, worse, while the document has been
revised since and nobody rewrote the plan.
The second gap — “current” is not the same as “read”
A plan that nobody on the roster has opened is a document, not a control. Nothing in
the current process distinguishes the two, so the caseload report says the plan is in place.
Why this altitude matters
The individual view answers “what do I do with this person tonight”. This view answers a question no
one can currently ask:
across the whole caseload, how many people are being supported from a plan that is
current, complete, and actually in the hands of the workers on shift?