As-Built or Out of Date
July 6, 2026 · 2 min read · SiteOps Command
The as-built is usually a PDF someone exported once, three remodels ago — and the person who knew the rest of the story has since left. It is not a document anyone trusts, which means it is not a document anyone reads.
Redrawn versus generated
A redrawn as-built is a fresh act of drafting after the fact, assembled from field notes and memory at closeout. It is stale the moment anything moves. A generated as-built is produced from the live model of what was actually placed and verified — so it is not a snapshot that starts decaying on delivery; it is the current state, queried when you need it.
The field closes the loop
The gap between the design and the install is where as-builts go wrong. Photo verification in the field — the camera is where the drawing said, the cable took the route it should have — feeds the record, so the as-built reflects what was installed, not what was intended. The loop from design to install to record closes instead of drifting.
Sites and floors as records, not folders
When each site and floor is a living record rather than a folder of drawings, the as-built does not have to be reassembled from scratch every time someone asks. The renewal, the expansion, and the next technician all read the same current state — the same record that keeps the renewal honest a year later.
Why it pays
An out-of-date as-built is not a paperwork problem. It is the technician tracing a cable that was moved, the renewal quoted from fiction, the expansion designed against a plan that is wrong. Every one of those costs more than keeping the record true would have.
A short checklist
- Generate the as-built from the model; do not redraw it from memory.
- Verify installs against the design with field photos.
- Keep sites and floors as records, not folders of PDFs.
- Quote renewals and expansions from the live state, not an archive.
An as-built nobody trusts is an as-built nobody reads. See the field operations and project lifecycle pages, why your BOM is the design, or the integrator workflow; or book a demo on your own project.
Frequently asked
- What is an as-built?
- A record of what was actually installed, as opposed to the original design. It matters because the install rarely matches the plan exactly, and everything downstream — service, renewal, expansion — depends on the record being true.
- Why do as-builts go out of date?
- Because they are usually redrawn once at closeout and never updated. The moment a device moves or a cable is rerouted, a static PDF is wrong, and the people who knew the difference move on.
- How do you keep an as-built current?
- Generate it from a live model of what was placed and verified, rather than redrawing it from memory, and verify installs against the design in the field so the record reflects reality.