Client reporting: what to send, how often, and what it costs you

Client reporting rarely appears as a line in the contract's cost model, but somebody spends hours on it every month. It is worth understanding what the client is actually using it for, because that determines what is worth automating.

What clients are actually checking

• –Was the site covered as contracted, and if not, what happened
• –What incidents occurred, and were they handled
• –Are there patterns — the same problem, the same time, the same entrance
• –Is anything outstanding from last month

Notice that all four are answerable from records your team already creates. The manual effort goes into assembling them, not producing them.

The re-keying tax

When reporting is assembled by hand, three things follow: it is expensive, it is late, and it occasionally disagrees with the operational record — because someone re-typed a number. The third is the serious one, since a discrepancy the client spots costs more trust than the report ever earned.

Reporting as a by-product

The goal is for the report to be a view of existing records rather than a document someone builds. If attendance is recorded against the rostered shift, and incidents are logged on shift, then cover and incident reporting already exist — they only need presenting.

The report that answers the question before it is asked

Most client reporting is retrospective: hours worked, incidents logged, patrols completed. It confirms what happened and rarely tells the client anything they could act on. The reports that change a relationship tend to include something forward-looking — a pattern in incidents, a recurring access issue, a recommendation — because that positions the contractor as noticing rather than recording.

The same applies to problems. A contractor who raises an issue on their own contract before the client finds it is treated very differently from one who reports only what is asked for.

Compliance position, proactively

Security clients increasingly ask about licensing and screening status across their account, often prompted by their own audit. Including a short, accurate compliance statement in routine reporting removes that as an event: the client already has the position, and the contractor is not scrambling to compile it under time pressure.

Common mistakes

• –Reporting only activity, with nothing the client can act on
• –Volume of detail that obscures anything significant
• –Waiting for the client to ask about compliance position
• –No trend, so a deteriorating pattern looks like isolated events
• –Reporting incidents without what was done about them
• –Different formats per client with no underlying consistency

What separates a report that gets read

Reports that change a client relationship share a structure: a short statement of position at the top, anything the client needs to act on next, and detail below for those who want it. Reports that get filed unread invert that — pages of activity data with anything significant buried inside it.

The other consistent feature is regularity. A report that arrives on the same day every month becomes something the client expects and notices the absence of. One that arrives when there is something to say trains the client to read it as a signal that something is wrong.

One more thing: agree the format once, then keep it

Clients rarely ask for a reporting format at mobilisation, so contractors invent one — and then vary it as different people produce it. A report whose shape changes month to month is hard to read comparatively, which quietly removes most of its value even when the content is good.

• –Agree the format at mobilisation rather than inventing it monthly
• –Keep the same structure so months can be compared at a glance
• –Send it on a fixed date, so its absence is noticeable

One practical test: ask the client what they read

Ask your main client contact which part of your monthly report they actually read, and what they would want that is not in it.

The answers are usually short and slightly deflating — a position at the top, anything needing their decision, and considerably less activity data than is being sent. It is a five-minute conversation that almost no contractor has, and it reliably improves the report more than any redesign.

• –Lead with position and anything needing action, not activity
• –Send on a fixed date so its absence is noticeable
• –Include something the client has not already raised
• –Keep the format stable so months can be compared
• –Include the compliance position before it is asked for