Security Project Acceptance and Handover Workbook
Use this workbook to agree what a completed commercial security project must demonstrate. It focuses on customer acceptance and records, not equipment programming. Complete the test plan with the provider before work begins, and assign an authorized customer representative to witness results.
1. Create an acceptance register
Use one row per requirement: requirement ID; location or device; expected result; test conditions; responsible person; witness; result; evidence reference; outstanding issue; retest date. Keep detailed drawings and security records in restricted storage. A general meeting document should reference evidence rather than include passwords, access codes or sensitive footage.
Example: D-07, employee entrance. An authorized day-shift credential permits entry during its schedule; an expired test credential is rejected; the door closes and latches; the correct event is recorded. Specify the actual approved behavior rather than copying this example into every opening.
2. Agree representative operating scenarios
- Video: demonstrate the required detail at the agreed location under representative light and movement. Retrieve a specified event, confirm timestamps, and export it for an authorized reviewer. Confirm actual retention after sufficient operating time.
- Access: demonstrate allowed and denied entry, schedules, credential revocation, door status, administrator roles and the approved emergency behavior for each opening.
- Intrusion: have the responsible qualified personnel coordinate controlled testing with the monitoring provider. Record signal identity, notification and restoration results. Do not trigger unscheduled tests or assume a general test mode covers every function.
- Integration: demonstrate a real agreed workflow, such as finding the relevant camera recording from a door event. A product logo in a proposal is not acceptance evidence.
- Continuity: agree safe, authorized tests of power or communications interruption, local operation, fault notification and recovery. Plan operational safeguards before any interruption.
Fire-alarm and other regulated acceptance procedures must follow the applicable design, requirements and qualified parties. This customer workbook does not replace required inspections or testing.
3. Separate defects from scope changes
A defect fails an agreed requirement. A scope change introduces a new requirement or alters an approved one. Record which applies, who decides, the proposed correction, any operational workaround and the retest criteria. Do not close an item solely because a technician visited.
Use clear statuses: not tested, passed, failed, blocked, or accepted with a documented exception. An exception needs an owner, limitation, deadline and written customer decision; it should not disappear into an email chain.
4. Collect the handover package
- Final equipment inventory with model, serial number, location and supported software version.
- As-built drawings, labeled device names, door and zone schedules, network responsibilities and relevant interfaces.
- Customer account ownership, authorized administrators, recovery process and secure credential transfer.
- Configuration backups or export capabilities where supported, plus restoration responsibilities.
- License terms, subscription renewals, warranty information, support contacts and escalation procedures.
- Completed test records, open exceptions, maintenance instructions and training attendance.
5. Have staff perform the work
Ask authorized staff to add and remove a test user, find an event, export an allowed record, recognize a fault and request support. Record any task that still depends on the installer. Training is complete when the intended operators can perform their assigned tasks, not merely when a demonstration ends.
6. Schedule the first operational review
After the agreed settling-in period, review missed events, nuisance alerts, permission errors, storage results and unclear procedures. Assign corrective actions and retain the original acceptance baseline so later changes can be compared with it.
Begin with the project brief and choose relevant tests from the property scenarios. For terminology, use the planning glossary.