MCS paperwork: build the handover file while the job is happening
Organise your MCS job records around the applicable scheme requirements, with named owners for design, commissioning, customer documents and unresolved questions.
Check the scheme documents your business is using
A checklist copied from an old job can carry old requirements into a new one. Before handing over the paperwork, identify your technology, the applicable scheme documents and the arrangements confirmed by your certification body.
NICEIC’s current transition guidance points installers to updated MCS requirements and technology-specific documents. It also describes changes to operating requirements and customer protection. Do not treat an older PDF as proof of what your business must do now.
Have your certification body confirm the standards and transition arrangements that apply to your business. This article gives an admin handover structure. It does not claim to reproduce the technology standards or provide a complete scheme compliance checklist.
Build the file from the start of the job
I would turn the confirmed requirements into a job checklist before the installation. Give each required record an owner and the point at which it should be collected. The desk can then flag the gap while somebody still has access to the site.
Use the categories below to organise the record, then adapt them to the actual technology and requirements. They are a working structure, not a complete MCS compliance checklist.
- Customer, property and agreed scope, including approved changes.
- Required customer information and evidence it was provided at the right stage.
- Design and equipment records approved by the responsible person.
- Installation and commissioning information supplied by the engineer.
- Required certificates, registrations and customer handover documents.
- Open questions, the person who can answer them and the next action.
Keep technical approval out of the typing task
The desk can assemble supplied records, enter confirmed details and compare the file with your approved checklist. It should put conflicting equipment details or missing commissioning information back to the responsible person.
Design decisions, commissioning judgements and scheme declarations remain with the people responsible for them. Agree who approves each document before it is submitted or sent to the customer.
Track the customer handover as its own task
Have somebody check which approved documents and instructions the customer should receive and which conversations or demonstrations need the engineer. Record the completed handover against the installation.
Keep any registration, notification and certificate statuses separate. A file containing a draft certificate does not show that registration is complete, and a sent email does not confirm every technical handover requirement was met.
A useful handover status
Use a short record with the actual job reference, the missing information and a named owner. The example below shows the structure; replace every placeholder with the checked job details.
Invented admin example Job: [reference] Missing record: commissioning information from the engineer Technical owner: [responsible person] Desk action: collect the record and prepare the customer pack for approval Sending rule: only the approved version can be released Customer handover: record documents sent and any engineer demonstration still outstanding
Use exceptions to improve the next job
Record why a document is missing rather than marking the whole job “paperwork”. If serial-number evidence repeatedly comes back unreadable, change the engineer’s collection checklist. If approvals wait for one person, agree a review point in the diary.
Use the Admin Handover Pack to write the desk’s preparation task and the approval boundary. Check your scheme and technology requirements with your certification body when those requirements are uncertain; the admin brief should follow that answer.