How Security Contracts Are Structured: Hours, Minimums and Notice

Three elements do most of the work: hours, minimums and notice

Most disputes between a client and a security company trace back to one of these three being unclear at signing rather than to anything that happened on post. Reading them carefully before you sign is worth more than reading almost anything else in the document.

A security contract is built around more terms than these three, but hours, minimums and notice are the ones that decide what you actually pay and how much room you have to change the arrangement once it starts. Understanding how each is written protects against the two most common surprises: a bill that does not match what was expected, and a schedule that cannot flex when the property’s needs change.

Hours are written as a schedule, not a total

A standing post is not billed as a lump number of hours per month; it is written as a specific schedule, the days of the week and the time window the post runs, and the total hours fall out of that schedule rather than the other way around. This matters because a schedule can be read and checked against what actually happened, while a monthly total cannot. An event or a temporary post is written differently: as a stated date and time range, with setup and breakdown hours included explicitly rather than assumed. Reading the schedule as written, not just the total hours quoted, is how you catch a mismatch between what you asked for and what is on the contract before the first shift rather than after.

Minimums protect against a shift too short to staff economically

A minimum number of hours per shift or per call-out exists because assigning, briefing and transporting an officer to a site costs the same whether the shift is two hours or eight. A standing weekly post rarely runs into its minimum, since the schedule is already well above it, but a one-time request, a single evening, a short event, a single fire-watch round, is the case where the minimum applies and where it is worth confirming before you book rather than after the invoice arrives. The minimum is stated as a number of hours in the contract, not as a policy explained after the fact.

Notice runs in both directions

The contract states how much notice the client gives to change the schedule, add a post, or end coverage, and it should state the company’s own notice obligations as well, for a scheduled change on the company’s side or for ending the arrangement. Emergency and same-day starts are the exception built into most contracts specifically because they skip the normal notice period: an urgent request is priced and scheduled outside the standard notice terms, with the paperwork, the post orders and the formal notice period catching up around the start rather than blocking it. A contract that is silent on notice in either direction is one to raise before signing, not after a schedule change becomes a dispute.

Holiday and short-notice terms are set before they are needed

Rather than negotiating a holiday shift or an emergency call-out in the moment, a well-structured contract states those terms up front: which dates count as holidays, how a short-notice request is priced relative to a scheduled one, and how quickly a change can take effect once requested. Setting these terms at signing, when there is no pressure and no clock running, produces better terms for both sides than working them out during an actual emergency.

Billing runs on a period, and reports back it up

Alongside hours, minimums and notice, the contract states a billing period, typically weekly or monthly, and the invoice for that period should be traceable back to the daily reports for the same dates: the schedule the contract sets, the hours the reports show were actually worked, and the invoice should all agree. A client who reads the daily reports has an independent check on the invoice rather than having to take the billed hours on faith, and a discrepancy between what the reports show and what is billed is something to raise immediately rather than let compound over several billing periods. Payment terms, how long the client has to pay after an invoice is issued, and whether there is any mechanism for the rate to be revisited over a longer contract term are the remaining pieces, and both should be stated plainly enough that neither side is guessing at them partway through the agreement.

Comparing a standing post and a single event

	Standing weekly post	Single event or one-time post
Hours written as	A recurring schedule (days and window)	A stated date, start and end time
Minimum usually reached	Rarely	Often, especially for short bookings
Notice to change	Set period, usually days	Often booked with less lead time
Holiday terms	Apply to specific recurring dates	Apply if the event falls on one

Where these terms come from

Every one of these terms should trace back to the proposal, which is where hours, minimums and notice are first stated after the walk-through; the contract formalizes what the proposal already set out rather than introducing new terms at signing. The proposal article walks through what that document contains, and the before you sign article lists what to review once the contract itself is in front of you.