The Change Nobody Told the Crew About

You did not sell the job and you did not design it. You inherit both, and you are measured on whether it lands on the hours it was sold with.

Which is why the most expensive thing in your week is not a hard install. It is a decision somebody made three weeks ago that nobody told the crew about.

The change is cheap. The propagation is not.

A customer turns a training room into a lab. That is one sentence in an email. Downstream it is:

• device positions move
• cable lengths change, and so does the footage on the order
• the bill of materials no longer matches the drawing
• the labour estimate was built on the old count
• the install sequence shifts

In a normal toolchain each of those lives in a different document, updated by a different person, at a different time. The crew works from whichever copy reached them. That is not carelessness — it is what happens when five artefacts describe one building and nothing keeps them in step.

One object, not five documents

The BOM is auto-derived from the placed devices, with provenance reconciled across eight source types and sealed revisions with diffs. It is not a spreadsheet somebody maintains next to the drawing; it is a view of the drawing. Move the device, and the count moves.

The labour and cost estimate sits on the same footing — a ROM budget band grounded in BICSI TDMM and RS Means, carrying a reproducibility hash and versioned diffs. That last part is the one that matters on a Tuesday: you can see what the estimate was, what it is now, and what changed between them, rather than arguing from memory about what was in the original number.

And the change itself becomes a document rather than an email. The Change Order Report covers one or all change orders, scope by product type, full installation detail and a sign-off sheet — written to go to the customer for approval and to an installation partner to quote from, so the approval and the quote are the same piece of paper.

What you still do by hand, and it is the handoff

Two gaps, both on the part of your day closest to the crew.

There is no single named technician work package. The pieces exist — the scope of work, the work items, the installer plan — as separate artefacts. Assembling them into the one thing you hand a technician on Monday is still your job.

Procurement is not included. The platform does not generate vendor purchase orders or push estimates to a supplier. You get to a BOM and then re-key it into whatever actually orders.

If the thing you wanted was “the change updates the order automatically”, that is not built, and the honest version is that it updates the bill automatically and you place the order yourself.

The sequence view, precisely

There is a 4D build timeline that scrubs the install phase by phase — entities render as installed, ghosted ahead of their phase, or hidden. It requires the project to carry a phase plan. It will show a sequence; it will not author one for you.

The narrow claim

Every cost you own is a repeat: the second trip, the re-pull, the re-terminate, the re-survey because nobody wrote down what changed. Most of those trace to the same root — the drawing, the bill and the crew’s copy drifting apart between the sale and the install.

Making them one object does not remove change. It removes the part where change arrives silently.

See why the BOM is the design, what a stale as-built costs, or book a demo on a job you are running now.