TacDesk
All articles

Assignment Instructions Guards Actually Follow: A Practical Guide

Most assignment instructions are too long, out of date, and stuck in a folder nobody reads. Here is how to write site instructions your guards will actually use — and how to keep them current.

By Michael Bryce · 5 August 2026 · 5 min read

Every security company has them. Assignment instructions — the site-specific document that tells a guard what to do, where to go, who to call, and how to handle the things that go wrong. Every ACS assessor asks for them. Every client assumes they exist.

And yet, on most sites, the assignment instructions are a fifteen-page Word document, printed once, stuffed in a plastic wallet in the gatehouse, and last updated when the site opened. The guard on shift has never read them. The version in the office does not match the version on-site. When something happens at 3am, nobody can find the emergency contact.

Assignment instructions are one of the most important operational documents you produce — and one of the most neglected. This guide covers how to write them so they get used, and how to keep them from going stale.

What Assignment Instructions Are For

At their heart, assignment instructions exist to answer one question: if I were a competent guard who had never been to this site before, would I know exactly what to do?

That covers the routine and the exceptional:

  • Where the site is, how to get in, and where to sign on
  • What the patrol routine is, and what to check
  • Who the client contacts are, and who to escalate to
  • What "normal" looks like, so the guard can spot what isn't
  • Emergency procedures — fire, intruder, medical, lockdown, evacuation
  • Reporting expectations — what to log, and how

They are also a compliance artefact. Under ACS and BS 7499, you are expected to have documented, site-specific instructions and to be able to show that guards have been briefed on them. "We told them verbally" does not hold up.

Why Most Assignment Instructions Fail

Before fixing them, it helps to be honest about why they don't work.

They are too long

A guard on a night shift is not going to read fifteen pages. The critical information — the fire assembly point, the escalation number, the lockdown trigger — is buried on page nine between the history of the building and a copy-pasted health and safety policy.

They are out of date

The client changed their duty manager six months ago. The alarm code changed. A new fire exit was added during a refurbishment. None of it made it into the document, because updating a printed folder means someone has to physically go to site.

They are hard to access

The one copy lives on-site. If a guard is deployed at short notice to cover a shift, they may arrive having never seen the instructions at all. The office cannot check what the on-site version actually says without driving over.

They are generic

A template with the site name changed at the top is not a site-specific instruction. Guards learn quickly that the document does not reflect reality, and they stop trusting it.

How to Write Instructions Guards Will Actually Use

Lead with what matters at 3am

Put the emergency procedures and key contacts first, not last. The first page should answer: who do I call, where do I go, and what do I do if the worst happens. Everything else is reference material that follows.

Be specific and concrete

"Conduct regular patrols" tells a guard nothing. "Patrol the perimeter every hour, checking gates A, B, and C are locked, and scan the checkpoint at the loading bay" tells them exactly what good looks like — and gives you something to verify against.

Write for the reader, not the auditor

It is tempting to pad instructions with policy language to impress an assessor. Resist it. A clear, usable document that guards actually follow is far more defensible than an exhaustive one nobody reads. Keep the policy in your management system; keep the site instructions operational.

Use a consistent structure

When every site follows the same layout — access, patrols, contacts, emergencies, reporting — a guard moving between sites always knows where to look. Consistency is what turns a document into a habit.

Make emergency contacts unmissable

Names, roles, and numbers, in priority order, on the first page. When a guard needs them, they need them immediately, not after flipping through a laminated folder.

The Real Fix: Get Them Off Paper

Even the best-written instructions fail if they live in a plastic wallet in the gatehouse. The single biggest improvement you can make is to move assignment instructions off paper and into a system your guards carry with them.

This is where TacDesk changes the picture. Site-specific assignment instructions live in the app, attached to the site:

  • Every guard sees the current version. When you update the escalation contact or the lockdown procedure once, in the office, every guard deployed to that site has the new version instantly. No reprinting, no site visit, no mismatched copies.
  • They are available before the shift starts. A guard covering a last-minute shift can read the instructions on their phone on the way to site, not discover them on arrival.
  • They sit alongside the work. Because patrols, clock-ins, and incident reports run through the same app, the instructions are right there next to the job the guard is doing — not in a separate document they have to remember to consult.
  • You can prove they were available. When an ACS assessor or a client asks how guards are briefed, you can show that current, site-specific instructions are delivered to every guard on every shift, digitally and on the record.

That last point matters. Paper instructions prove that a document existed. Digital instructions delivered through the platform your guards clock in on prove that the document was actually in front of the people doing the work.

Keep Them Alive

Assignment instructions are not a "write once" document. Build a simple review habit:

  1. Review after every incident. If something went wrong and the instructions did not cover it, fix them.
  2. Review when the site changes. New manager, new alarm code, new layout — update the same day.
  3. Review on a schedule. At least quarterly, even if nothing has obviously changed. Things drift.
  4. Ask your guards. The people on-site know where the instructions are wrong. Give them an easy way to flag it.

Good assignment instructions are not about having the thickest folder. They are about a guard on shift, at the worst moment of the night, knowing exactly what to do — and being able to prove, afterwards, that they were set up to succeed.

See how TacDesk puts current, site-specific assignment instructions in every guard's pocket — start a free trial at tacdesk.co.uk. No setup fees, no contracts, cancel any time.

MB

Michael Bryce

Founder of TacDesk. Writes about SIA compliance, operations, and running a UK security company — from someone who actually works the shifts.

Connect on LinkedIn →

See TacDesk in action

Win contracts, pass SIA audits, and run your whole operation from one place. Book a free 30-minute demo.

Book a Free Demo

Get Field Notes

The ACS traps, licensing changes and ops shortcuts we write about — one straight email every week or two, from someone still doing the shifts, not a marketing team. Unsubscribe anytime.