How security's daily records become intelligence for property decisions
FLSDs file records of the work they already do. The Oversight tool consolidates and reads them, the Security Director reviews them, and property management decides what to act on. No new data collection was required.
Fire Life Safety Directors run the Fire Command Center around the clock in three 8-hour tours: Day 0700–1500, Afternoon 1500–2300 and Night 2300–0700. Every report they file records work they already do. More than 340 End-of-Shift reports have been filed since April 2026.
| Input | Who files it | When | What it captures |
|---|---|---|---|
| End-of-Shift report | Every FLSD on duty | End of each tour, before relief | Pass-down briefing, fire panel status and bypasses, post coverage, work orders, log book, CCTV, elevator status car by car, building events, open items handed to the next tour |
| Elevator report | FLSD | As it happens | Car out of service or entrapment: car, bank, times, ticket number, restoration |
| Incident report | FLSD | As it happens | Alarms, leaks and other incidents: location, times, actions, notifications |
| Resolver report | Lead FLSD or Security Director | Within 24 hours | The official incident record: times, status and narrative, closed within 10 business days |
| Emails and photos | FLSDs and vendors | As received | Detail the forms miss, reviewed by the Security Director before filing |
| Meeting notes | Security Director | After each Friday meeting | Action items requested by property management |
End-of-Shift, elevator and incident reports. Each submission is synced, timestamped, attributed by name and locked against later edits.
Resolver entries, emails, photos and meeting notes. Each item is filed under the area it belongs to, such as elevator or alarm.
The tool brings every record into one database, then reads, counts and tracks it. The Security Director reviews everything before any report leaves.
A weekly report for action and a monthly bulletin for trends, both built from the same reviewed record.
| Output | How often | Who receives it | What it contains |
|---|---|---|---|
| Directors Report Client | Weekly, before the Friday 9 AM meeting | CBRE property management | Events since last Friday, month at a glance against last month and the average, each event with date and source, Resolver reports, repeats by car and floor |
| Directors Report Full | Weekly | Security Director | Everything in the client version, plus open building conditions |
| Oversight Insight Bulletin | Monthly | Property management and leadership | Monthly event counts and accumulation, trends and repeat locations, facts only |
| Action-item record | Weekly | Property management | What the meeting asked for and how each item was addressed |
| Period reports Planned | Quarterly, semi-annual, annual | Property management and ownership | Built from the stored record without starting over |
After the first monthly bulletin, CBRE's Senior Property Manager asked that the format stay as it is.
Security's records become business intelligence when they answer questions owned by someone other than security. The reports supply the facts; property management draws the conclusions and makes the decisions.
| Question the record answers | Data that answers it | Who acts on it |
|---|---|---|
| Is a building condition getting better or worse? | Monthly counts by event type | Property management |
| Which car, device or floor keeps failing? | Repeats by location | Property management, engineering, elevator vendor |
| Was the fix made, and did it hold? | Open conditions tracked to verified closure | Property management, engineering |
| Did the weekly asks get done? | Action-item record | Property management |
| What will the next quarter or year look like? | Stored record across periods | Property management, ownership |
The record today is built from officer reports. Three steps would strengthen it.