Setting Expectations: Response Times, Reports and Communication

Response time expectations belong in hours, not minutes

The single expectation most likely to cause disappointment later is response time, and it is worth setting honestly at the very first conversation rather than letting a manager assume something faster. For an unarmed post, dispatch generally works in a window of hours: enough time to confirm the address, assign an available officer and get that officer moving, not an emergency-service promise measured in minutes. Armed coverage can take a little longer to arrange since it depends on a commissioned officer’s availability, though emergency armed coverage exists for genuine emergencies. Fire watch, because it is so often triggered by a system going down without warning, is staffed on a similarly short timeline once the details of the impairment are known.

None of this is a weakness to apologize for; it is what an honest security company should say plainly, because a manager who understands the real window makes better decisions with it, whether that means calling earlier than they otherwise would or building a standing schedule instead of relying on same-day requests for a need that recurs.

Reports need a cadence and a named reader

A report that nobody reads is wasted regardless of how well it is written, and the failure mode is rarely a bad report, it is an unclear expectation about who is supposed to read it and when. Before coverage starts, the property should say plainly who receives the daily report, by what time they expect to see it, and what they intend to do with it: forward maintenance items, compare it to a prior week, simply confirm the post ran. A property with more than one manager benefits from naming a primary reader and a backup, so a report is never sitting unread because two people each assumed the other had it.

The same clarity matters for incident reports, which arrive separately and the same day as whatever they describe. A manager who expects to be told about an incident only through the next morning’s report, rather than by a phone call, should say so explicitly, since the default on anything serious is a same-day call as well as a written record, and a property that prefers otherwise for minor matters can say that too.

Communication needs a line drawn between “call now” and “it can wait”

Not every event on a property needs a phone call at eleven at night, and not every event should wait for the morning. The clearest way to avoid both extremes is to draw the line explicitly, in the post orders, rather than leaving it to an officer’s judgment about what a particular manager would want to be woken up for. Injuries, police or fire involvement, threats and anything that needs an immediate decision belong on the “call now” side. A logged visitor, a resolved disturbance, a routine finding on a round belong on the “written report” side. A manager who wants a different line, perhaps wanting a call for anything involving a specific resident, or wanting fewer calls overall and more trust placed in the written report, should say so at the start rather than after being surprised by a midnight call or a missed one.

Expectation	Reasonable	Not reasonable
Response time for a new unarmed post	Hours from the call to dispatch	A promise measured in minutes
Report delivery	A written report at the end of every shift, to a named reader	Reports that exist but nobody has agreed to actually read
What triggers a call	Injury, police or fire involvement, a threat, anything needing an immediate decision	A call for every minor, resolved event; or no call for anything serious
Escalation contact	A specific name or role reachable after hours, agreed in advance	“Someone from the office,” discovered for the first time during an actual emergency

Different properties reasonably draw the line differently

There is no single correct place to set these expectations, and two properties of the same type can reasonably land in different spots. A small commercial building with one manager who does not want to be woken for anything short of an emergency can ask for a narrow “call now” list and rely on the written report for everything else. A community with a board that expects to hear about anything involving a resident by name, even something minor, can ask for a wider list and a same-day summary beyond the standard report. Neither preference is wrong; what matters is that dispatch and the officers on the post actually know which one applies, because a preference that only exists in a manager’s head is not an expectation the post orders can follow.

Putting the answer in writing, in the post orders themselves rather than in a single conversation at the start, is what keeps the expectation intact when staff turn over on either side. A new officer reading the post orders should be able to tell, without asking anyone, who gets called about what and when the report is expected to land.

Set it once, then revisit it deliberately

Expectations set at the start of a contract are a beginning, not a permanent fixture. A property’s escalation contact changes when staff turn over; a manager who found the calls too frequent in month one might want fewer by month three, or the reverse. Revisiting these three expectations, response time, reporting and communication, at renewal or whenever the property’s own situation changes keeps the arrangement matched to what the manager actually needs rather than to what was assumed on the first call. The coverage planning worksheet is a useful place to write these preferences down before the first conversation with dispatch, so nothing has to be reconstructed from memory later.