The Report That Landed on the Board's Desk Last Tuesday
Picture this: a property manager walks into a board meeting carrying 48 hours of incident logs from their current security provider. It is a three-page PDF. The columns read: Date, Time, Type, Notes. Under "Notes," the entry for a 2am access dispute says: "Male subject attempted entry. Asked to leave. Left."
That is it. No unit number. No description of the subject. No record of whether fob access was revoked. No note about whether residents were notified. No indication of whether this was the same person who tried three weeks ago.
The board votes on whether to renew the security contract with that company. They are holding the wrong document to make that decision.
We write reports differently. This is what the difference actually looks like.
Why Most Security Reports Fail Boards
Standard guard-company reporting was designed to document that something happened — not to explain what it meant or what should happen next. A log is a record of events in sequence. A board-ready report is an instrument of governance.
The distinction matters for three reasons:
Legal exposure. When an incident leads to a claim — a resident injury, a theft, a harassment complaint — the quality of your documentation determines how defensible your position is. Vague entries like "incident resolved" are not resolution records. They are liability gaps.
Operational insight. A board cannot improve what it cannot measure. If the report tells you there were 14 incidents last month but gives no context about severity, recurrence, or resolution, you have data without intelligence.
Vendor accountability. A report that contains no targets, no benchmarks, and no comparisons to the agreed scope makes it impossible to evaluate whether the vendor is actually delivering.
What We Mean by "Board-Ready"
Board-ready is not a design preference. It is a functional standard. A report built for the boardroom answers four questions without the board having to ask:
- What happened, and how serious was it?
- How does this period compare to the last one?
- What are we watching going forward?
- Are we delivering what we promised?
Before and After: A Real Comparison
The Standard Guard Report Entry
Date: April 14, 2026 Time: 02:17 Type: Unauthorized Access Attempt Notes: Resident claimed guest was expected. Guest did not have access. Incident resolved.
A Chromium Guard Incident Entry
Date: April 14, 2026 · 02:17 Location: Main lobby entrance Type: Unauthorized Access Attempt — Severity: 2 (Moderate) Parties: Unregistered visitor (male, approx. 30s) claiming guest of Unit 1204. Unit 1204 resident contacted via intercom — confirmed guest was unexpected and declined entry. Action Taken: Visitor declined entry. Access log noted. Incident photographed (lobby CCTV, timestamp 02:17–02:22). Visitor departed without incident at 02:22. Supervisor notified at 02:25. Follow-Up Required: Unit 1204 contacted following morning re: visitor safety protocol. Building manager notified by 07:00 with full entry. Status: Closed — no further action required unless pattern recurs. Note: Third unregistered late-night access attempt in the past 60 days. See Forward Indicator section for recommended protocol review.
The difference is not just detail. The Chromium entry is legally defensible. The standard entry is not.
The Five Sections Every Monthly Report Should Contain
1. Severity-Weighted Incident Index
Not just how many incidents — what they cost the building. We assign a severity tier (1–4) to every incident. A low-count month with a Tier-3 event (physical confrontation, fire panel activation, theft) is more significant than a high-count month of Tier-1 entries (noise complaints, package inquiries). The board reads this as a score, not a list.
2. Forward Indicators
What we are watching next month. If we recorded three after-hours access attempts in the past 30 days, that pattern gets flagged here with a recommended response — whether that is a protocol change, a resident communication, or an increase in patrol frequency. The board sees the curve before it becomes an incident.
3. Resident Communications Snapshot
Themes raised by residents during the reporting period. Not names, not unit numbers — themes. "Package handling process" appearing three times in one month is a signal the board should see, not suppress. Sentiment is a leading indicator.
4. Target vs. Achieved
Every scope agreement we sign specifies patrol counts, coverage hours, and response targets. This section reports actuals against those targets. If a patrol was missed, it is in here — with a reason. No surprises at audit.
5. Written Narrative Opener
Two paragraphs written in plain language that summarise the period. Not for the security professionals on the call — for the board member reading this on the subway at 7am before the meeting starts.
The Legal Consideration Boards Often Miss
Incident reports are legal documents. Under the Ontario Condominium Act, condo corporations are required to maintain records — and when a complaint, insurance claim, or legal action arises, the question is not just what happened, but what you knew and when you knew it.
Inadequate records are read by courts as a failure of due diligence. A security vendor whose reporting creates liability gaps is not providing a service. They are creating exposure.
Chromium Guard's incident documentation is designed to survive an audit. Every entry is timestamped, named, and action-tracked. Records are retained for a minimum of 24 months. If your board is ever asked to produce records in support of an insurance claim or legal review, the file should answer every question before the first question is asked.
Request a Sample Report
Before you sign any security contract, ask the vendor for a redacted sample of a real monthly report from an active site. If what comes back looks like a spreadsheet with no narrative, no severity weighting, and no forward-looking section — you know exactly what the board will be reading for the next 12 months.
To request a sample Chromium Guard report and see the standard firsthand, reach out at chromiumguard.com/contact or call us at (437) 734-2345.