Handover
Ask ten contractors what an O and M pack is and you will get ten answers, all of them slightly defensive. It is the last thing on the job, it is nobody’s favourite week, and it is very often the reason a final payment sits unpaid for two months.
It does not have to work like that. But fixing it means understanding what the pack actually is, and being honest about why yours takes so long.
Strip away the variation between clients and specifications, and an operation and maintenance pack answers four questions about the system you have just installed.
What did you put in? Every device, its make and model, its serial where relevant, and where it physically is. This is the asset register, whether or not anyone calls it that.
How do I know it works? Commissioning records and test results, device by device or circuit by circuit, signed by somebody competent to sign them.
How do I know it is legal? Certification. Electrical certificates, fire commissioning certificates, whatever the discipline requires, issued by a person whose competence you can evidence.
How do I keep it working? Manufacturer documentation, maintenance requirements, recommended service intervals, and who to call.
Everything else in the pack — as-builts, RAMS, subcontractor details, warranty terms — sits underneath one of those four.
Here is the uncomfortable bit. The pack takes a week not because it is complicated, but because none of that information was captured in a usable form while the work was happening.
The device list is in a spreadsheet that stopped matching the drawing around second fix. The test results are on printed schedules in a folder in somebody’s van, some of them photographed, some not. The certificates were typed up at a kitchen table in the evening from those printed schedules. The as-builts are marked-up PDFs at various revisions. The product data sheets are in an email thread from eight months ago.
So the week is not spent producing anything. It is spent hunting, reconciling and retyping. It is pure recovery work, and no client has ever paid a penny for it.
Cash. Final accounts routinely hinge on the handover pack being accepted. A week late producing it, plus a round of comments, plus a re-issue, is easily a month on your payment. On a job of any size that is real money sitting still.
Rework. Reconciling records at the end always surfaces gaps. A device with no test result. A circuit with no certificate. Half the time the work was done and the record is missing, and you cannot prove which. So somebody goes back to site to re-test something that was almost certainly fine.
The next contract. Handover is the last thing the client experiences. Whatever they thought of your engineers, the pack is what they remember when the next tender goes out.
The pack is not a document you write. It is a by-product of records you already had to create.
Every one of those four questions is answered by something that existed during the job. The device list existed the moment you set out the drawing. The test results existed the moment the engineer tested. The certificate existed the moment somebody signed. The data sheets existed at procurement.
The only reason assembling them is hard is that they were captured on paper, in email, and in three different file formats, by people who were not thinking about handover at the time.
Capture them once, in one place, attached to the thing they describe, and the pack assembles itself.
Four changes, none of them dramatic.
Devices live on the drawing, not in a spreadsheet. The asset register is then just an export, and it cannot disagree with the as-built because they are the same object. This is the single biggest one.
Test sheets are completed on site, on the device. Not on paper to be retyped later. Digital forms in your own wording, filled in at the point of work, filed against the task automatically. Nothing to transcribe means nothing to transcribe wrongly.
Certificates are generated from data you already hold. If the project knows the circuits and the test results, the certificate is a rendering job, not a typing job.
Product documentation is held at organisation level. A data sheet approved on one job should be available on the next without being resubmitted. Most contractors install a fairly narrow range of kit; there is no reason to re-source the paperwork every time.
Graftix does not yet auto-compile a finished O and M pack at the push of a button. That is on the roadmap and we are not going to pretend otherwise.
What it does do today is hold every component of that pack — the asset register, the certificates, the eForm submissions, the RAMS, the as-built drawings, the technical submittals — against the project they belong to, captured at the point the work happened. Which means the week you currently spend hunting and reconciling becomes an afternoon spent assembling.
That is the bulk of the saving. The button is the easy part; having the records in one place is the hard part, and that is the part that is built.
Pick the form your engineers currently fill in twice — once on paper on site, once at a laptop that evening. Rebuild it once as a digital form and complete it where the work is. That single change usually pays for the subscription on its own, and it is the fastest way to see whether the rest holds up.
More on safety and compliance records and building your own forms, or see how it fits electrical and fire work.
Try it on a real job
Graftix puts every task on the actual drawing, then hangs the materials, certificates and sign-offs off that pin. Seven days, every feature, no card.
Read-only live environment · No sign-up required