Safeguarding Log Template: What Every Entry Must Record
Knowing how to make a safeguarding referral is only half the requirement. The other half is a confidential internal register that shows every concern was logged, tracked, and followed through — whether or not it was ever escalated.
A safeguarding log is a different document from a safeguarding referral. The referral is what gets sent to the local authority once a concern meets the threshold for a Section 42 enquiry under the Care Act 2014. The log is the internal register that records every concern raised in your service — including the ones that, after review, didn’t need external escalation. Both matter, but it’s the log that inspectors ask for first, because it’s the only record that shows the full picture rather than just the cases that were referred out.
What Every Entry Needs to Record
| Field | Why it matters |
|---|---|
| Date and time concern was raised | Establishes the timeline — critical if the concern later becomes part of a Section 42 enquiry |
| Who raised it and who it concerns | Names both the reporter and the person(s) affected, kept confidential and access-restricted |
| Nature of the concern | Factual description — what was observed or reported, not conclusions drawn at the time |
| Immediate actions taken | What was done at the point of disclosure — separating the person from a risk, informing a senior, etc. |
| Referral decision and rationale | Whether it was escalated to the local authority, and why or why not — this is the line inspectors scrutinise most |
| CQC notification status | Whether the concern triggered a statutory notification to CQC, and the date it was sent |
| Outcome and closure date | How the concern was ultimately resolved, and when the record was closed |
The Decision Not to Refer Needs Recording Too
Many providers log concerns that were escalated and leave out the ones that weren’t — usually because a manager judged, correctly, that the threshold for a Section 42 enquiry wasn’t met. That judgement itself needs to be on record. An inspector reviewing a thin log with only referred cases has no way to tell whether concerns are genuinely rare, or whether they’re being screened out informally before they reach the register at all.
✗ Referral-only record
Only concerns that were escalated to the local authority appear in the file. Concerns judged not to meet the threshold leave no trace — including the reasoning behind that judgement.
✓ Complete confidential register
Every concern is logged the moment it’s raised, with the referral decision and rationale recorded alongside it — whether the outcome was escalation or a documented decision not to.
Access control matters as much as content
A safeguarding log contains some of the most sensitive information your service holds. It should be restricted to those with a genuine need to know, with access itself logged — not stored on a shared drive every staff member can open, and not discussed outside the people directly managing the concern.
Reviewing the Log for Patterns
A log that’s only ever read one entry at a time misses what a governance review is meant to catch: whether concerns cluster around a particular shift, a particular member of staff, or a particular type of incident. Reviewing the whole log periodically — not just individual entries as they arise — is what turns a safeguarding record from a compliance formality into an actual early-warning system.
A confidential register built for Section 42 tracking
CQCLogic’s Safeguarding Log is a confidential register for safeguarding concerns and allegations, with Section 42 enquiry tracking and notification status to CQC and the local authority built in — so nothing depends on remembering which concerns were referred and which were logged only. See the full feature or view a sample plan.
Summary: What a Complete Safeguarding Log Must Include
- Every concern raised, not only the ones escalated to the local authority
- Date, time, and a factual description separate from conclusions drawn later
- The referral decision and rationale recorded explicitly, including decisions not to escalate
- CQC notification status and date, tracked separately from the underlying concern
- Restricted access, logged and reviewed periodically
- An outcome and closure date for every entry
- Regular pattern review across the whole log, not just entry-by-entry handling
Frequently Asked Questions
What is the difference between a safeguarding log and a referral?
The safeguarding log is the internal register recording every concern raised, whether or not it was escalated externally. A referral is the formal notification sent to the local authority once a concern meets the threshold for a Section 42 enquiry. Not every logged concern becomes a referral, but every referral should trace back to a logged concern.
How long should safeguarding records be kept?
Safeguarding records should generally be retained for a minimum of the statutory retention period your local authority and CQC guidance specify — commonly several years beyond the person’s time using the service — because historical patterns can become relevant to a later safeguarding enquiry, inspection, or legal process.
Who should have access to the safeguarding log?
Access should be restricted to those with a genuine need to know — typically the registered manager, deputy, and any staff directly involved in managing a specific concern. It is a confidential record, not a general team communication tool, and access should be logged and reviewed periodically.
Does every safeguarding concern need to be notified to CQC?
Not automatically, but many do. CQC must be notified of allegations of abuse and certain safeguarding-related incidents under the notification regulations, and a well-run safeguarding log should flag which entries triggered a CQC notification and when, so this can be evidenced separately from the underlying concern record.
What happens if a safeguarding concern isn’t logged?
An unlogged concern can’t be tracked, can’t be reviewed for patterns, and can’t be evidenced to an inspector — even if it was handled appropriately at the time. Inspectors treat gaps in the log as seriously as gaps in the response, since an undocumented concern looks, from the outside, indistinguishable from one that was ignored.