The five-part instruction: trigger, owner, action, proof, escalation

01

Why the usual document does not survive contact

I would test the instruction with the person who uses it during ordinary work. Ask them to find the next action without coaching. Record the pauses, workarounds and missing information, then revise the document with its authorised owner.

That gap is the whole problem. It is not a compliance problem and it is not a training problem. It is a drafting problem, and it is fixable at the desk.

Use short, direct instructions and put the next action where the reader expects to find it. Keep background explanation available separately. The test is whether the instruction can be used accurately in context, not whether it meets an arbitrary sentence-length rule.

02

The five parts

Trigger. What starts this instruction. A time, an event, a state. "At the start of every session." "When the patient arrives for the second review." "If the room temperature reading is outside range." An instruction with no trigger sits in the document waiting for someone to remember it, which is another way of saying it will not happen.

Owner. A named role, never a department and never a plural. Not "the clinical team", not "staff", not "we". One role, singular, that a person can point at on a rota. The moment you write a plural you have created a step that three people assume the other two are doing.

Action. One verb, one outcome. If you need the word "and" in the middle of the action, you have two instructions and you should split them. This is where most SOPs quietly bloat, because a writer compresses six real actions into one elegant sentence and the reader has to decompress it while wearing gloves.

Proof. What is left behind afterwards that shows this happened. A time and initials, a photograph, a batch number, a signed page, a system entry. The proof must be smaller than the action. If recording takes longer than doing, it will be back-filled from memory once the last patient has gone, and a back-filled record is worse than no record because it looks like evidence.

Escalation. What the owner does when they cannot complete the action. Who they call, what they say, and what happens to the patient in the meantime. This is the part that gets cut, and it is the part that decides whether a bad day becomes a serious incident.

03

Escalation is a permission, not a phone number

An escalation instruction must cover both recognising the trigger and reaching the authorised person. I would rehearse an unanswered call and an absent supervisor. The team should know the next route without having to negotiate permission during the incident.

You cannot fix that with a phone number. You fix it by writing the escalation line so that it removes the judgement call from the junior person. Not "escalate if concerned" but "call the on-call clinician if any of these three readings appear, regardless of how the patient looks". Then add the sentence that does the real work: no one will be questioned for making this call.

An escalation route that requires courage to use is not a route, it is a trap with a phone number written on it.

04

Proof is the part people cut first, and it is the part that pays

A recorded check should show that the required step happened and identify who completed it. The clinical lead determines the clinical requirements. Operations should make the evidence easy to capture and review without treating a ticked box as proof of a clinical outcome.

That is what proof does. It converts a private intention into a public fact.

05

A Monday morning pass through your worst SOP

Take the procedure you already suspect is being ignored. Do not rewrite it yet. Do this instead.

1. Number every sentence that tells someone to do something. Ignore everything else. 2. For each numbered sentence, write five letters in the margin: T, O, A, P, E. Cross out the ones the sentence does not answer. 3. Count the crossings. In my experience O and P are missing from more than half of the instructions in any document over two years old. 4. Take the three instructions with the most crossings and fix only those. Not the whole document. 5. Walk the fixed version with the person who runs it, standing where they stand, on a normal busy day. Not in a meeting room. 6. Ask one question at the end: what would you have done differently if I were not here. The answer is your real procedure. 7. Date it, version it, and put the operating steps within arm's reach of the work rather than in a folder on a server.

Seven steps, one morning, one document. You will not fix your manual this way. You will fix the three instructions that were going to hurt someone.

06

What you actually control

You do not control whether your staff are busy. They will be. You do not control the day a regulator changes what has to be recorded, or the day two people call in sick and the rota is thin, or whether a patient behaves the way the procedure assumed. Those arrive on their own schedule and no amount of drafting keeps them out.