Drawings and records
Every contractor in fire, security, electrical and data runs the same two documents on every job. A drawing set, issued as PDF. And a device schedule, living in a spreadsheet. They are supposed to describe the same building.
They never do. Not by the end.
It starts on day one and nobody notices. A detector will not go where it is drawn because there is a duct in the way, so the engineer puts it two metres along. A door gets reversed, so the reader moves inside. Three outlets get added in a room that changed use during the fit-out. A camera comes off the schedule entirely because the client decided that corridor did not need covering.
Each of those is a five-second decision made by a competent person standing in the right place, and every one of them is correct. The problem is not the decision. The problem is that it now needs recording in two separate places by two different people, and one of those places is a spreadsheet on somebody’s laptop that nobody else has open.
So the drawing gets marked up, badly, in biro, and photographed. Or the schedule gets updated and the drawing does not. By second fix you have two documents that disagree, and no reliable way of knowing which one is right.
This is not a tidiness problem. It shows up as money in four specific places.
Commissioning takes longer than it should. The engineer works down the schedule and finds devices that are not where the schedule says, and devices on site that are not on the schedule at all. Every mismatch is a phone call, and every phone call is two people standing still.
The as-built is fiction. You hand over a drawing that does not match the building. Nobody checks it on the day. It gets found eighteen months later by a maintenance engineer who cannot locate a device, and the call comes back to you.
Variations go unrecovered. Those three extra outlets were real work with real material and real labour. If the only record of them is a marked-up print in a van, they are not going on an application. You did the work for nothing.
The handover pack takes a week. Somebody has to reconcile the two documents before anything can be issued, and that reconciliation is entirely avoidable work that no client will ever pay you for.
Most firms have tried at least two of these.
Stricter version control. Naming conventions, a shared drive, REV A through REV F. This slows the divergence down; it does not stop it, because the underlying problem is that there are still two documents.
One person owns the schedule. Works until that person is on another job, on holiday, or leaves. Single points of failure always eventually fail, and this one takes the project record with it.
Everyone photographs their markups into the WhatsApp group. Genuinely better than nothing, and completely unsearchable by the time there are four hundred messages in it.
All three share the same flaw. They are attempts to keep two records in sync, when the actual answer is to stop having two records.
The alternative is to stop treating the drawing as a picture and start treating it as the thing the data lives on.
A device is not a row in a spreadsheet that happens to reference a location. A device is a point on a sheet, and everything else about it — address, loop, zone, circuit, model, test result, photo, who fitted it and when — hangs off that point.
Move the device on site and you move the pin. There is no second document to update, because the pin is the record. The as-built is not something you produce at the end of the job; it is what you have been looking at the whole way through.
This sounds like a small distinction. In practice it removes an entire category of work from your projects.
An engineer opens the drawing for the floor they are on. They can filter it down to their trade, or their loop, or just the tasks assigned to them. They fit a device, take a photo, mark it complete. If it went somewhere different to where it was drawn, they drag the pin.
The project manager, in the office, sees the completion count move. Not a percentage somebody estimated in a meeting, but a real figure calculated from real devices that are really in.
At handover, the device schedule already exists, because it was never a separate thing. It is just an export of what is on the drawing.
The test of any field management tool is whether an engineer standing in a riser with cold hands will actually open it. If the answer is no, the drawing and the schedule will keep drifting apart no matter what the office does.
You do not need to change how the whole business works to find out whether this helps. Take one live job, upload the drawing set, and pin one floor or one loop. It takes an afternoon, and by the end of it you will know whether it fits how your engineers actually work.
If it does, the next job starts with the schedule and the drawing already being the same object, and stays that way to handover.
Graftix is built for exactly this. Have a look at the plan viewer, or see how it plays out for fire, security, electrical and data 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