The Policy Document

A lone worker policy is short, or it is not read. Most of them are long and describe a product.

When the policy document also depends on reliable work records, the platform overview can support time, attendance and workload review without being treated as the emergency response itself. Compare any workflow with ISO standards catalogue and keep alarm ownership, escalation and dispatch responsibilities explicit.

What it should contain

Scope: which situations, defined by circumstance rather than job title.

The assessment requirement and who carries it out.

The check-in arrangement and who receives them.

The escalation tree, or a reference to where a current version is held.

The withdrawal right, stated unambiguously.

Equipment: what is issued, to whom, and what is expected about carrying it.

Reporting: what to report, how, and what happens next.

And the tasks that are not to be done alone.

Eight sections, a few pages.

The sentences that must be unambiguous

"You may leave any situation you judge to be unsafe. You do not need permission, and there will be no consequence."

"If the system fails, you are not expected to continue without it."

"These tasks are not to be carried out by one person in any circumstances."

Each is frequently written with a qualifier that removes its meaning — "wherever reasonably practicable", "subject to operational requirements" — and the qualifier is what the workforce reads.

Write them flat, or do not write them.

Where policies go wrong

Written to describe a product, so they become obsolete when the supplier changes.

Written by somebody who has not done the work, producing instructions that cannot be followed at a doorstep.

Covering job titles rather than situations, which leaves the intermittent cases uncovered.

And silent on the two questions everybody has: is it tracking me, and will it be used against me.

The parts that belong elsewhere

The escalation tree, which changes too often to sit in a governance document.

Device instructions, which belong on one page with pictures.

Site-specific arrangements.

Keep the policy stable and the operational detail in documents that can be changed without a committee, because a policy requiring board approval to update a phone number will contain the wrong phone number.

Consultation and sign-off

Safety representatives involved in drafting rather than shown the result, which is a requirement in many jurisdictions and improves the document everywhere.

Signed by somebody senior enough that the withdrawal sentence carries weight.

And issued to everybody it covers, individually, with a record — because in an investigation the question is whether the person was told.

Review and version

Annually, and after any incident or significant change.

Dated, versioned, with the review date on the front page.

And a change log, because the question later is what the policy said at the time rather than what it says now.

Making it real

A policy is evidence of intent and nothing more.

What makes it real is the testing, the recording, and the first time somebody withdraws and nothing happens to them.

Which is the argument for keeping it short: the effort belongs in the arrangement rather than in the drafting.

An organisation with a thirty-page policy and an untested escalation tree has spent its effort in exactly the wrong place, and that combination is common enough to be worth naming.

Who the policy is actually for

Three audiences, and they need different things from the same document.

The worker wants to know what happens if something goes wrong, and whether they are being tracked.

The manager wants to know what they must do and what they may decide.

And the inspector wants to see that the arrangement was designed rather than assembled.

Write the first two into the document and let the third follow, which is the opposite of how most are drafted.

The supporting documents

A one-page worker guide: how to check in, how to raise an alarm, how to cancel, what happens next.

A one-page responder guide: the tree, the timings, the authority.

A current escalation tree, held where it can be updated.

And the test log, which is the evidence that any of it works.

Four documents beside the policy, none longer than a page, and together they are more useful than any policy can be alone.