System overview
Panels, cameras, readers, sensors, zones and key locations presented in a simple project structure.
For fire, security and access-control contractors
A fire and security example is in preparation.
A fire and security example is on the way. In the meantime, have a look at what a handover manual holds.
Why it hurts
The client needs the details after you leave site.
Fire and security handovers carry a lot of small but important information. If it is buried in email attachments, the client will come back to you for answers.
- Zone charts, panel manuals, device lists, certificates and maintenance contacts are easy to separate during close-out.
- Facilities teams need the right document fast when an alarm, fault or access issue appears.
- A generic file dump makes the finished system look less professional than the installation work behind it.
- Future maintenance visits are slower when the current asset list and document history are not in one place.
What goes inside
A handover pack built around systems, devices and evidence.
Give the client a practical record of what was installed, where to find it, and which documents support it.
Certificates and test records
Completion certificates, commissioning sheets, inspection records and manufacturer documents grouped by system.
Support and maintenance
Service contacts, warranty notes, maintenance intervals and user guides available from one QR code.
How it works
Make close-out repeatable across every installation.
Use the same simple workflow for a small access-control job, a CCTV upgrade or a mixed fire and security package.
Create the project
Add the site, client and package scope, then upload drawings, certs, photos, manuals and spreadsheets.
Build the record
Group information by system, zone, device and document type so a non-technical client can navigate it.
Publish the handover
Share the manual link, print the QR code, and keep a PDF copy for formal project records.