Child Missing Protocol
A standing template for known information that may be needed if a child goes missing.
Platform module
Missing episode records connected to the child profile.
ResiNotes supports missing-from-care workflows while keeping each episode connected to the wider care record.
ResiNotes separates the standing child protocol from the live missing episode. The protocol holds known information; the live episode records what is happening now.
Careful workflow design
Standing information and live risk need different records.
The module supports practice, not replacement for professional judgement or local policy.
Live missing episode
The priority record for what is happening now, including category, risk level and immediate circumstances.
Description from profile
Description information can be pulled from the child profile as a starting snapshot for the episode.
Last seen details
Last physically seen time, last known location and immediate circumstances sit in the live record.
Risk level
Risk information is designed to be visible without losing the wider context of the child profile.
Police details
Police references and contact details can be recorded as the workflow develops.
Professional notifications
Notification evidence for relevant professionals can sit with the episode record.
Timeline and updates
Episode updates build a timeline so follow-up is clearer for managers and authorised staff.
Return, closure and review
Return, closure, manager review and archive concepts sit inside the workflow shape.
Protected triggers
Hashtags support trigger visibility.
Protected hashtags can begin, update or end missing episode review without asking staff to duplicate the same information in multiple places.
- #beginmissing, #updatemissing and #endmissing are protected workflow tags.
- Standing protocol for known child information.
- Live episode record for the current event.
- Timeline updates, closure and review.