Assignment instructions that officers actually use

Assignment instructions are the document that translates a contract into what an officer actually does on a shift. They are also, in a great many contractors, written at mobilisation for the client's benefit and never read again by anybody on the site.

Written for the reader who has never been there

The test of assignment instructions is whether an officer covering the site for the first time, at short notice, at two in the morning, can work the shift from them. That is not a hypothetical reader — it is the most likely reader, because established officers work from habit and cover officers work from the document.

Which means the things that get omitted as obvious are exactly the things that matter: where the keys are, which door the alarm panel is behind, who to ring when something happens, what the client's own staff are and are not allowed to do, and which of the site's quirks have caught people out before.

They go stale faster than anybody updates them

Sites change. A door is sealed, a camera is added, the client's out-of-hours contact leaves, a wing is mothballed, the fire assembly point moves for building works. None of those generate a prompt to revisit the document, so instructions drift from reality in a way that is invisible until somebody relies on them.

A short review on a cycle, and a rule that any change to the site is a trigger, is what keeps them usable. Asking a cover officer what they could not find is the cheapest audit available and reliably produces a list.

Escalation is the part most often vague

The section officers most need under pressure is usually the weakest: who to call, in what order, after how long, and what to do if nobody answers. Escalation arrangements written as a principle rather than as names and numbers fail exactly when they are needed.

In practice: the cover shift that could not find the panel

An officer covers an unfamiliar site at short notice. The alarm activates at 3am. The instructions describe the response procedure in detail and do not say where the panel is, because whoever wrote them knew and everybody who normally works the site knows.

The procedure was correct. It was unusable by the one category of reader most likely to need it, and the omission was invisible to every person who had reviewed it.

Common mistakes

• –Written for the client rather than for the officer on shift
• –Omitting what is obvious to anyone who knows the site
• –No review cycle, and no trigger when the site changes
• –Escalation written as a principle rather than names and numbers
• –Held only at the site, so a cover officer cannot read them beforehand
• –Never asking a cover officer what they could not find

One practical test: send a stranger

Have an officer who has never worked a site cover a shift there using only the assignment instructions, and ask them afterwards what they could not find.

The list is always longer than expected and always consists of things obvious to everyone who knows the site. That is precisely the category the document exists to cover, and the only way to find it is to ask somebody who did not already know.

• –Write for a cover officer at short notice, not a regular
• –Ask cover officers what they could not find
• –Review when the site changes, not on a calendar alone
• –Give escalation names, numbers, timeframes and a no-answer path
• –Make them readable before arrival, not only on site

Worth adding: make them readable before arrival

Instructions held only at the site are unavailable to the one reader who most needs them — an officer travelling to cover a shift they have never worked. Being able to read them beforehand turns an unfamiliar site into a briefed one, at no cost.

It also gives the officer somewhere to raise a question before they are standing at a gate at 10pm unable to find the keys.