One loop, repeated for every placement.
Deterministic, explainable and fast enough to complete before the bell.
- 1
The SEND Lead records the support profile
Mandatory fields cover the child reference, setting, year group, communication method, known triggers, support strategies, whether critical information exists and the named contact. Everything else is optional and additive.
- 2
An assignment is named
One worker, one child, one setting context, one role, one period. One worker can hold several assignments and one child can have several workers; readiness is always calculated per assignment row.
- 3
The engine generates requirements
Rules read the current profile version and produce a checklist tagged worker foundation, setting readiness or child-specific — with the field that triggered each item.
- 4
The worker completes micro-briefings
Two minutes each, written for the shift rather than the policy folder.
- 5
A knowledge check confirms understanding
Questions are tied to the exact fields the briefings covered, so a pass means something.
- 6
A supervisor approves where it matters
Always for temporary and agency workers, for critical children and after material changes.
- 7
Access opens
The practical action view unlocks with the fields this role is permitted to see on this assignment. Nothing more.
- 8
Evidence builds as work happens
Strategy outcomes, concerns and escalations are recorded in seconds and roll up into the setting's trend view.
- 9
Material change triggers re-readiness
Change a trigger, a strategy, critical information or the safeguarding route and affected assignments reopen exactly those steps. Cosmetic edits do not.