Stop silent hour creep by enforcing post orders, shift schedules, overtime approvals, and invoice-to-schedule reconciliation.
Security spend leaks when there is no measurable schedule to reconcile against.
This playbook installs:
Post orders define:
You cannot audit hours without a schedule.
Overtime should be the exception, not the default.
If you wait until the month-end invoice, recovery is harder.
Copyable template (TEXT)
Security Post Orders Site: Post name: Primary responsibilities: - Responsibility 1 - Responsibility 2 Patrol expectations: - Route: - Frequency: - Checkpoints: Required logs: - Start of shift log - Incident log - Visitor log Escalation triggers: - Trigger: - Who to contact:
Copyable template (TEXT)
Shift Schedule and Roster | Site | Post | Day | Shift start | Shift end | Scheduled hours | Assigned guard | | ---- | ---- | --- | ----------: | --------: | --------------: | ------------- |
Copyable template (TEXT)
Overtime Approval Request Site: Post: Date: Requested overtime hours: Reason: Approver: Decision:
Copyable template (TEXT)
Weekly Reconciliation Week ending: | Vendor | Site | Scheduled hours | Billed hours | Variance | Reason | Action | | ------ | ---- | --------------: | ----------: | -------: | ------ | ------ |
Copyable template (TEXT)
Subject: Security invoice discrepancy Hi [Name], We reviewed billed hours for [site] and found a variance versus the approved schedule. Variance details: - Scheduled hours: - Billed hours: - Difference: Please provide supporting evidence or issue a corrected invoice. Thank you, [Name]
v1.0 (2026-01): Latest release