Safeguarding escalation note for lead review

Nothing here is clinical advice, and nothing here should touch identifiable patient information.

Use this process to turn scattered observations, contact attempts and recorded concerns into one factual note for a qualified safeguarding lead. It is for care coordinators, practice managers and safeguarding administrators who need a clear record without adding interpretation.

This is administrative drafting, not clinical or safeguarding advice. Do not enter identifiable patient information into the model. Keep names, dates of birth, addresses, contact details, record numbers, appointment details and any combination of facts that could identify a person in your approved case system.

1. Prepare a de-identified source sheet

Before you open the model, make a short source sheet from approved records. Use neutral labels such as Person A, Staff member 1 and Contact 2. Replace exact dates and times with relative markers only where your local process permits, such as Day 1, morning or later that week.

Keep the source sheet in the minimum structure below:

Field	Record	Do not add
Source	The document or system entry type	A claim that the source proves something
Sequence	The order of recorded events	Missing dates guessed from context
Observation	What was seen, heard or recorded	Motive, diagnosis or cause
Contact	Attempted or completed contact and outcome	An assumption about why contact failed
Existing action	The action already documented	A promise that a new action will happen
Review question	What the lead needs to decide	Your own safeguarding threshold decision

For example, write Day 2: staff record says Person A did not attend arranged contact. One telephone attempt is documented, with no answer. Do not write Person A was avoiding services.

Separate direct observations from reports made by someone else. A record saying that a family member expressed concern is not the same as a staff member observing the matter directly.

2. Set the note structure before drafting

Use the same headings each time. A fixed structure reduces the chance that a busy reviewer misses a contact attempt, a source or an unresolved point.

1. Purpose of escalation: one sentence stating why the note is being sent for review.
2. Recorded information: dated or sequenced facts, with the source beside each point.
3. Contact and actions recorded: attempts, outcomes and actions already logged.
4. Gaps or uncertainties: what the records do not establish.
5. Request to safeguarding lead: the decision, direction or review required.
6. Record controls: case reference in the approved system, author, date prepared and location of supporting records. Do not put these identifiers into the model.

This structure prevents a common failure: a long narrative where the actual request appears only in the final line.

3. Ask the model to organise, not decide

Paste only your de-identified source sheet. Tell the model that it must preserve uncertainty, avoid conclusions and label each statement as a recorded fact, reported concern or unresolved question.

Use this prompt:

Create a factual safeguarding escalation note using the headings below.

Rules:
- Use only the supplied information.
- Do not infer motive, risk level, diagnosis, cause or legal threshold.
- Keep direct observations separate from third-party reports.
- State uncertainty plainly.
- Do not recommend a safeguarding or clinical decision.
- End with a concise request for review by a qualified safeguarding lead.
- Use Person A and the supplied relative time markers only.

Headings:
Purpose of escalation
Recorded information
Contact and actions recorded
Gaps or uncertainties
Request to safeguarding lead

Source sheet:
[PASTE DE-IDENTIFIED SOURCE SHEET]

If your organisation permits use of the model for this purpose, check its current handling and product information before you begin. Availability and controls can vary, so use the current guidance in the xAI documentation overview alongside your local information-governance rules.

4. Check every sentence against the source sheet

Do not send the first draft on. Read it beside the de-identified source sheet, then make corrections in your approved system.

Check these points in order:

1. Match every event to a source-sheet line. Delete any sentence with no matching line.
2. Check sequence. The draft must not place a contact attempt before the concern that prompted it unless the source sheet says so.
3. Check attribution. Phrases such as it was reported that must name the role or source type, not turn a report into fact.
4. Check language. Replace words such as refused, unsafe, neglect, deteriorated or failed to engage unless they are direct quotations already recorded and necessary for the lead to see.
5. Check the final request. It should ask for review or direction, not tell the lead what conclusion to reach.
6. Add the correct identifiers, exact chronology and links to source records only inside the approved case-management system.

5. Recognise when the output is wrong

The most dangerous draft is one that sounds calm and complete while adding a conclusion not present in the records. Treat it as wrong if it does any of the following:

If you see this	Why it is wrong	What to do
This indicates or This shows	It converts records into an interpretation	Replace with the recorded observation or report
A precise date or time you did not supply	It may have been invented or inferred	Remove it and verify in the approved record
A statement about risk, capacity, diagnosis or intent	It goes beyond administrative organisation	Delete it and ask the qualified lead to review the facts
A missing contact attempt or source	The chronology is incomplete	Return to the source sheet and add the documented item
A recommendation presented as a decision	The draft has crossed the reviewer’s role	Change it to a request for direction

Quotations need the same care. Use only short, necessary quotations already present in the approved record. Do not ask the model to reconstruct wording from memory.

When the draft does not work

If the output is muddled, do not keep refining a large block of text. Go back to the source sheet and split it into three lists: observations, reported concerns, and contact or action records. Then run the prompt again with only those labelled items.

If the records conflict, keep both accounts, attribute each one and place the conflict under Gaps or uncertainties. Do not ask the model to choose which account is true.

If you cannot safely de-identify the material, do not use the model. Draft within your approved system or ask your safeguarding lead which local process to follow. Escalate through the established route where the records themselves require prompt review.