Run a monitoring service review using real records
Prepared 22 October 2026 by NightMarshal

Review monitoring using traceable incident, fault and change records. Distinguish workload, service performance and business outcomes; a lower alert count alone does not prove reduced risk or a better service.

Instructions
1. Agree counts, denominators and reporting windows.
2. Review evidence for exceptions and coverage gaps.
3. Assign corrective actions with verification.

Open the blank CSV in a spreadsheet app; add one row per item. Use Pending for unknowns and N/A only where a field truly does not apply. Review the separate example CSV; all example values are fictional. Keep completed sheets private. Do not include passwords, access codes, personal contacts, footage links or camera stream URLs. No input is collected by these downloads.

Fields
Review item
Counting unit
Evidence source
Known limitation
Action owner
Verification

Fictional example
Fictional review: alert count falls after a zone change. The buyer also checks positive tests and missed-event reports before accepting that the tuning improved the workflow.

Limits
This is a measurement framework, not evidence of NightMarshal performance, savings or customer outcomes.