Cover at 5am: what a roster needs to tell you in ninety seconds
Someone has called in. You have a site that must be manned, a list of people who might be available, and very little time to check anything.
30 July 2026 · 6 min readIncident reports that still make sense six months later
The report is written in ten minutes at the end of a shift. It may be read by a client, an insurer, or a court, long after everyone has forgotten the detail.
25 July 2026 · 5 min readSubcontracted cover: whose compliance problem is it?
When you subcontract a shift, you do not subcontract the client relationship — or, usually, the risk that comes with an unlicensed officer.
20 July 2026 · 5 min readClient reporting: what to send, how often, and what it costs you
Most reporting is assembled by hand on a Friday afternoon. That effort is invisible to the client and expensive to you.
7 July 2026 · 5 min readWho needs to know, and how fast: escalation after an incident
Writing a good incident report matters. Getting the right people told, in the right order, within the time a contract actually requires, is a separate and earlier problem.
28 May 2026 · 5 min readProving you met the SLA, not just meeting it
Hitting a coverage target is one thing. Being able to show, with evidence, that you hit it for the month in question is a different and separate capability.
2 April 2026 · 6 min readLone working in security: what good practice actually looks like
A single officer on a static site overnight is normal in this sector. Whether there is a working plan for what happens if something goes wrong is not always so normal.
5 February 2026 · 5 min readWhat your no-show pattern is actually telling you
A single no-show is a cover problem. The same shift falling through every few weeks is a rostering problem wearing a cover problem's clothes.