Your as-built documentation is a work of fiction

Asset Integrity & Documentation

Your As-Built Documentation is a Work of Fiction

Why the gap between the blueprint and the copper is the most expensive distance in engineering.

You are standing in the dim, humming silence of a primary switchroom in an industrial park just outside of Dandenong. The air smells of ozone and the faint, sweet scent of warm dust. In your left hand, you hold a heavy, three-ring binder with a plastic sleeve that says “As-Built Documentation.” In your right hand, you hold a high-intensity torch.

You are looking for a specific sub-circuit, a 40-amp run that is supposed to feed the auxiliary cooling fans for a newly installed inverter bank. According to the crisp, CAD-plotted diagram on page 42, that cable should be housed in a 32mm orange conduit, running vertically along the northern structural column before diving into the floor slab.

You shine your light on the northern column. It is bare concrete. There is no conduit. There is no hole in the slab. You trace the wall back toward the main distribution board, and you find the cable-unlabeled, running in a galvanized tray along the southern ceiling, zig-zagging around a fire suppression pipe that wasn’t on the original architectural plans.

This is the silent crisis of the handover. For most facility managers and CFOs, the “as-built” package is the final box to be ticked before a project is considered closed and the final invoice is paid. It is treated as a historical record, a faithful map of the infrastructure you now own.

But in reality, the vast majority of as-built documentation is merely a reprint of the original design intent-a ghost of what was planned, rather than a record of what was actually built by hands on a hot tin roof in the middle of a Victorian summer.

R

The Discrepancy on the Western Wing

Roberta, a maintenance lead for a sprawling cold-storage facility, lived this discrepancy after a large-scale solar commissioning. When a communication fault crippled the monitoring on the western wing, she opened the as-built digital twin provided by the contractor.

The “as-built” showed a clean, linear daisy-chain of optimizers. It looked like a textbook example of electrical engineering. Confident, she sent a technician onto the roof with instructions to check “Inverter 4, String 2.”

The technician spent searching because the crew on the day of installation had found a previously undocumented HVAC condenser blocking the planned path. Instead of stopping the job to redraw the plans, they did what installers do: they adapted.

They rerouted the strings, jumped the cable across a different walkway, and buried the junction boxes under the shade of the panels to keep them cool. They solved the immediate problem, but they never told the CAD drafter back in the office. The drafter, tasked with “completing the as-builts,” simply changed the title block on the design drawings from “FOR CONSTRUCTION” to “AS-BUILT” and hit print.

Confessions of a Technical Debt Planter

I have to admit, I used to be part of the problem. Early in my career, I viewed documentation as a bureaucratic tax on real work. I once managed a project where we had to deviate significantly from the cable schedule because the specified tray was undersized for the thermal load once we accounted for the ambient heat of the roof space.

We fixed it in the field-we used heavier gauge copper and wider spacing. It was a better, safer build. But when it came time for the paperwork, I let the original design stand in the record. I told myself that as long as the system worked and the light turned green, the “map” didn’t really matter.

I was wrong. I was deeply, fundamentally wrong, because I wasn’t just saving time; I was planting a time bomb of technical debt for the person who would eventually have to maintain that system later.

Planned Repair Time

350%

Actual “Discovery” Time

When documentation is a lie, you aren’t just paying for a repair; you are paying for an archaeological expedition.

When the record departs from reality, the cost of ownership begins to climb. This is especially true in the world of high-performance commercial solar systems, where the complexity of the electrical integration is often invisible to the naked eye.

If an engineer in needs to troubleshoot a ground fault, they rely entirely on the accuracy of the schematics. If those schematics are a lie, the “search time”-the most expensive part of any maintenance call-doubles or triples.

The “Sacksian” reality of an electrical system is that it is a living organism, subject to the constraints of its environment. In a clinical sense, a true as-built document should record the “as-is” state with surgical precision.

It should note that the inverter was moved 200mm to the left to avoid a damp patch on the masonry. It should record the exact torque settings used on the mounting bolts and the specific serial number of every individual optimizer in the sequence.

When we look at the engineering-led approach, we see a refusal to accept the “print-to-as-built” shortcut. It requires a rigorous loop between the site foreman and the design office. It means “redlining”-the process of physically marking up paper drawings on-site with a red pen every time a screw is turned differently than planned-is treated as a sacred duty rather than a chore.

Surprises in Campbellfield and Braeside

In the Victorian context, where commercial and industrial sites often involve aging switchgear or complex structural realities in places like Campbellfield or Braeside, the design rarely survives first contact with the roof.

A warehouse built in the will have “surprises” hidden behind every distribution board cover. A design might call for a specific penetration point, only for the crew to find a structural beam that the original building plans (which were also likely inaccurate) failed to mention.

Projected ROI

15%

Clean “Fiction” Documentation

Actual ROI

9%

O&M spike due to “Discovery” phase

The danger of the “fiction” as-built is that it creates a false sense of security regarding the Levelized Cost of Energy (LCOE). When a CFO looks at a solar proposal, the LCOE is the North Star-it tells them the true cost of every kilowatt-hour produced over the life of the system.

But the LCOE calculation assumes the system can be maintained efficiently. If every service call requires a “discovery phase” because the drawings are wrong, the O&M (Operations and Maintenance) costs spike. Suddenly, that 15% ROI starts to look more like 9%. The documentation is, in effect, a financial instrument.

If you are a facility manager, you should treat the handover of the as-built documentation with the same scrutiny you would a financial audit. Do not accept a clean, perfect CAD drawing that shows no deviations from the design. No project in the history of construction has ever been built exactly to the millimeter of the original plan.

You want to see the “mess.” You want to see the notes that say “Rerouted via Column B due to unforeseen obstruction.” You want to see the photos of the open trenching before the concrete was poured, showing the actual depth and orientation of the conduits.

This level of detail is what separates a “sales-led” installation from an “engineering-led” one. In a sales-led model, the goal is the commissioning light. Once the panels are generating, the job is done. In an engineering-led model, the goal is the 20-year performance window.

“The engineers at Lumenaus understand that the system is not the panels on the roof; the system is the panels, plus the wire, plus the switchgear, plus the information required to keep it all running.”

The discrepancy between the plan and the reality is often where the most critical information lives. Why was that cable rerouted? Usually, it was for a very good reason-to avoid heat, to reduce voltage drop, or to protect the cable from mechanical damage.

If that reason isn’t recorded, the next person might “fix” the deviation by moving it back to the planned (and inferior) position, inadvertently introducing the very fault the original installers were trying to avoid.

Ultimately, we must recognize that documents lag the territory. The map is not the thing. The binder in the cabinet is a representation of a physical reality that is subject to the laws of thermodynamics, the vibrations of the building, and the expansion and contraction of metal under the Australian sun.

We have to stop viewing the as-built as a “final report” and start viewing it as a “first manual.” It is the foundation of the next of the building’s life. When Roberta finally found that cable in the southern tray, she didn’t just find a wire; she found the truth of her building.

She took out a red marker, crossed out the northern column on page 42, and drew the zig-zag path around the fire pipe. She was doing the work the installers should have done. She was reclaiming the map.

In the end, the integrity of a solar system-or any complex infrastructure-is only as strong as the integrity of the record. You cannot manage what you do not understand, and you cannot understand what you have not accurately recorded.

It is time to demand that our documentation reflects the beautiful, messy, adapted reality of the “as-built” world, rather than the sterilized, convenient fiction of the “as-planned” one. Only then can we truly own the assets we have spent so much to create.