Recording Information Sharing Decisions in Safeguarding: What Inspectors Look For

Safeguarding information sharing decisions must be clearly recorded to withstand scrutiny. In practice, many services do “the right thing” but cannot evidence it: the record lacks rationale, timing, who was told, and what happened next. This guide supports teams working within safeguarding information sharing and shows how good documentation changes depending on the types of abuse involved, because risk drives what must be captured.

What “good recording” means in safeguarding information sharing

Good recording is not long recording. It is complete recording. A defensible note allows an external reader (commissioner, safeguarding partner, inspector, auditor) to understand:

• What happened: the concern, facts observed, and immediate risks
• What you decided: share / don’t share / share later with consent
• Why you decided it: rationale linked to risk, capacity, and proportionality
• Who you told: names/roles/teams (and who you deliberately did not tell)
• What you shared: the minimum relevant information, not “everything we have”
• When: timestamps that show timeliness against local thresholds
• What happened next: confirmation of receipt, outcome, actions and follow-up

If any of these are missing, the decision can appear unsafe even when the underlying judgement was sound.

A simple structure staff can use every time

High-performing providers standardise the record. A practical approach is a short template embedded in the care record system:

1. Risk statement: “We believe X is at risk of Y because…”
2. Decision: “We shared / did not share / delayed sharing because…”
3. Proportionality: “We shared only A, B, C because…”
4. Lawful basis: “Shared to protect an adult at risk; rationale recorded.”
5. Recipients: “Shared with [role/team], not with [role/team] because…”
6. Timescales: “Shared at [time/date]; receipt confirmed at [time/date].”
7. Follow-up: “Next steps, review date, escalation route if no response.”

This is tender-ready as well: you can describe the pathway succinctly and evidence it via audits.

Commissioner expectation

Commissioner expectation: Providers can evidence timely referrals, accurate threshold understanding, and complete audit trails (including follow-up). Commissioners want proof that safeguarding information does not disappear into informal conversations or undocumented emails, and that actions are tracked to completion.

Regulator / Inspector expectation (CQC)

Regulator / Inspector expectation (CQC): Inspectors look for records that demonstrate staff understand when and how to share information to reduce risk, and that leaders provide oversight through audit and learning. They pay close attention to whether safeguarding concerns are documented consistently, escalated appropriately, and linked to governance (themes, learning, supervision).

Operational example 1: self-neglect with fluctuating engagement

Context: A person receiving domiciliary care refuses medication, declines personal care, and the home environment deteriorates. Staff observe significant weight loss and evidence of hoarding. The person sometimes agrees to help and later refuses again.

Support approach: The service completes a same-day risk update and manager review. Capacity is considered in relation to the specific decisions (care refusal, medication refusal). The safeguarding lead is consulted to confirm local thresholds for self-neglect and escalation routes.

Day-to-day delivery detail: Recording captures: the specific observations (dates, missed meds, refusal statements), what staff tried (motivational conversation approach, GP contact attempt, family contact attempt where appropriate), and the immediate protective steps (increased welfare checks, clinical advice request). The information shared externally is a factual summary focused on risk and immediate needs, not a full narrative history.

How effectiveness is evidenced: The file includes the referral timestamp, confirmation of receipt, the triage outcome, and a clear action log: who is doing what and by when (e.g., GP review, social worker visit, fire safety check). A review entry shows whether risk reduced and what changed operationally (visit schedule, care plan updates, escalation if no response).

Operational example 2: safeguarding meeting preparation and defensible sharing

Context: A provider is invited to a strategy meeting following repeated safeguarding concerns involving a tenant and allegations between peers. Historically, meetings have been difficult because staff arrive with either too little evidence or too much indiscriminate paperwork.

Support approach: The safeguarding lead prepares a structured “meeting pack” that is proportionate: timeline, key incidents, current risk controls, and specific questions for partner agencies. The pack is reviewed by the Registered Manager to ensure clarity and data minimisation.

Day-to-day delivery detail: The service records what was shared and why: the specific incidents relevant to the enquiry, the current protection measures, and the support plan controls. It also records what was not shared (irrelevant third-party details, unrelated historical notes) and the rationale for limiting disclosure.

How effectiveness is evidenced: Post-meeting notes capture actions allocated to each agency, deadlines, and how the provider will verify completion. A follow-up entry confirms actions completed and updates the person’s care plan and risk assessment. Governance minutes capture learning (e.g., training refresh on recording and meeting preparation).

Operational example 3: information sharing with families where there is conflict

Context: A family member requests detailed safeguarding information, claiming they are “next of kin,” while staff suspect family dynamics may be contributing to risk (coercion, financial pressure, or intimidation). The person expresses mixed views about what can be shared.

Support approach: The service separates involvement from disclosure. It checks consent and capacity for information sharing and considers whether sharing details could increase risk. The safeguarding lead reviews the request and agrees a safe communication plan.

Day-to-day delivery detail: The record shows: what the family asked for, what the person agreed (or did not agree) to share, what the service disclosed (often limited to process updates rather than sensitive details), and why. It documents any safeguarding advice received and sets a review date. Staff are guided to record factually and avoid subjective language about family members.

How effectiveness is evidenced: The audit trail demonstrates proportionality and protection: clear rationale, documented decisions, and any escalation if the family response increases risk. Supervision notes show staff were supported to manage the situation consistently.

Governance: making records inspection-ready

Recording quality improves when leaders treat it as a safety control. Practical governance mechanisms include:

• Monthly sampling: a small number of cases checked for completeness against a checklist
• Timeliness audit: referral times, receipt confirmation rates, and follow-up completion
• Decision consistency: whether different teams use the same structure and language
• Learning loops: themes reported, actions agreed, and re-audit to confirm improvement
• Supervision prompts: managers routinely review a safeguarding record with staff to build confidence

Where performance is weak, good providers do not just retrain; they simplify the workflow (templates, prompts, mandatory fields) so staff can succeed under pressure.

Common recording mistakes that reduce confidence

• Unclear rationale: “Shared due to safeguarding” with no explanation of why sharing was necessary.
• No audience clarity: records don’t say who received the information or whether receipt was confirmed.
• No proportionality: either no detail (making the referral unusable) or excessive detail (creating data risk).
• Missing follow-up: referral made, but no outcome recorded and no escalation when response stalls.
• Speculation: opinions presented as facts, which undermines credibility under scrutiny.

Strong safeguarding is visible in records. When your documentation shows risk, rationale, proportionality, recipients, timing and follow-up, you demonstrate a service that is safe, well-led and reliable in multi-agency systems — and you make it easy for commissioners and inspectors to have confidence in your practice.