Safeguarding Signal DeskRESTRICTED CASEFILE CONTROL
SIGNAL / 01

Scope a Safeguarding Casefile

Identify sensitive documents, exclusions, versions and the people who require access for charity safeguarding leads

Hands sorting restricted safeguarding records into scope groups
Original adult-only faceless photograph matched to this safeguarding decision; no service-user data is shown.

Keep the live case-management record, restricted evidence copy, referral decision, recipient authority, encrypted retained copy and recovery copy distinct. Encryption must never delay an urgent safeguarding response or a required statutory report.

01 / DECISION

Protect the safeguarding casefile without hiding ownership

A safeguarding casefile archive should preserve the decisions needed for safeguarding governance without becoming an uncontrolled collection of incident and service-user data. Define the case purpose, incident chronology, referral evidence, restricted attachments and named roles that genuinely need access. Exclude credentials, unrestricted personal data and unrelated working material.

Safeguarding team scenario

A safeguarding lead freezes a restricted case stage for authorized safeguarding review. The team first proves the workflow with fictional training casefiles, documents each authorized role and preserves the working source separately.

02 / PROCEDURE

Run the control sequence

  1. 01

    Name the case purpose, lawful basis and accountable safeguarding lead.

  2. 02

    List approved incident chronology, referral decision and authorized handoff evidence.

  3. 03

    Map creators, reviewers, recipients and legitimate access duration.

  4. 04

    Exclude secrets, redundant exports and data held in a better system.

  5. 05

    Freeze a scope manifest and review it before every casefile handoff.

03 / RECORD

Preserve decision evidence

Record archive ID, case stage, included record classes, exclusions, owner, contributors, reviewers, recipient roles, sensitivity, dependency systems and next scope review.

Stop when

  • No accountable owner can approve the archive.
  • Credentials or production secrets appear in the folder.
  • Access is granted to an unverified shared mailbox instead of named roles.

The record should show the approved case stage, tested environment, responsible people and known limitations without storing passwords or unnecessary safeguarding casefile content.

04 / BOUNDARY

Separate the surrounding controls

Does not replace case-platform permissions, safeguarding authority, statutory reporting, guaranteed backup or password recovery. Encryption does not authorize safeguarding access, determine or report risk, preserve every backup or remove plaintext working copies automatically.

05 / QUESTIONS

Safeguarding casefile archive questions

Should the archive become the live case-management record?

No. Keep active case management, statutory reporting and referrals in approved systems; retain only the authorized evidence copy.

Does resetting a password recover an existing archive?

Do not assume so. Document the product-specific recovery boundary and test a separate recovery copy.

06 / SOURCES

Primary references

References support specific boundaries and do not imply endorsement.