A week's visits waiting to become certificates
Your engineers complete a dozen fire alarm services this week. Each one produces notes: devices tested, zones, faults found, battery readings, any variations, the logbook entry made on site. Some engineers write on a paper template, some type into their phone's notes app, one emails photos of scrap paper. On Friday the office administrator starts turning them into certificates in Word, copying last year's certificate for each site and changing the details.
By Wednesday the certificates go out. One has last year's date in a footer. Another lists a zone that was removed during refurbishment. A customer rings on Monday asking for their certificate because their insurer has asked for it, and it is not ready.
The certificate is written twice
The information on a service certificate is gathered once on site and then written again in the office. Every rewrite is a chance to lose or change something, and it adds days between the visit and the paperwork.
- Engineers record visits in whatever format suits them on the day.
- Certificates are produced by editing last year's copy for that site.
- Site details such as zones and device counts are copied forward even if they changed.
- Variations and defects written on site are paraphrased in the office.
- Certificates wait in a queue behind everything else the office does.
The content of your certificates, and what they must include, is for your competent people and the schemes you work under to set. What we deal with is how the information gets from the engineer to the finished document.
What the delay and rework cost
Office staff spend a large part of the week retyping. Errors that slip through reach customers and sometimes their insurers or auditors, which reflects poorly on the engineer who did careful work on site. Customers who need their certificate for a renewal or an inspection chase you. Invoices, which often go out with the certificate, are delayed too.
Capture once on site, produce the certificate from it
We build an on-site capture form for your engineers that mirrors the structure of your certificate, connected to a certificate generator that produces the finished document for review.
- Before the visit, the engineer's phone is loaded with the site's current system details: panel, zones, device list and last visit's notes.
- The engineer works through the visit on the form, confirming or updating zones and devices, recording test results, battery readings and any variations, with photos where useful.
- Changes to the system, such as a zone added or devices removed, update the site record after office review, so next time starts from the truth.
- Defects are recorded as separate items, so they also feed your remedial quoting.
- When the engineer finishes, a draft certificate is generated from the visit record in your certificate layout, with the engineer's details and signature.
- The office reviews the draft, approves it, and it is emailed to the customer or placed in their portal, with a copy filed against the site.
| Step | Today | With on-site capture |
|---|---|---|
| Recording the visit | Notes in many formats | Structured form on the phone |
| Site details | Copied from last year | Confirmed or updated on site |
| Producing the certificate | Typed in the office | Generated from the visit record |
| Checking | Proofreading retyped text | Reviewing a generated draft |
| Sending | When the office catches up | After review, from the system |
If you already use certificate software, we look at whether engineers can complete it on site before building anything new. Often the gap is in how it is used, not what it can do.
The week after the change
The engineer finishes a service at eleven and the draft certificate is in the office queue before they reach their van. The administrator checks it against the visit record, spots nothing unusual, and approves it. The customer has it that afternoon. On Friday there is no pile. The administrator's time goes on scheduling, quotes and customer calls instead.
Engineers find they are asked fewer questions about their notes. Customers see certificates arriving promptly and consistently. When an insurer asks for a copy, it is on the site record already.
Recognise this?
- Certificates are typed in the office from engineers' notes.
- Certificates are made by editing last year's version.
- Customers chase you for certificates after the visit.
- Errors in certificates are found by customers.
- Invoices wait for certificates to be finished.