The Scope Package Looked Complete. The Building Didn’t Match.
Scope documents can look complete on paper and still not reflect what’s actually in the building, especially in buildings that have been modified over the years. Validating the scope of work against the drawings doesn’t take special software. A ladder, a flashlight, a look above the ceiling tiles, and a borescope for the spaces you can’t reach will show where the drawings and the building don’t match. When scope validation gets skipped and the documents are built from design-phase assumptions instead of field-verified conditions, any gap between the drawings and the field invites an increased risk of unnecessary change orders. The cost isn’t just the change order. It’s the project manager spending the first month of execution managing scope discrepancies instead of managing the work to the deliverable.
We’ve watched this play out on more than one project.
What Happens When Scope Documents Aren’t Validated Against the Field?
A capital improvement project was to replace an HVAC system in an occupied office space that was original to the building. It was antiquated, often needed repairs, and was unreliable in both summer and winter extremes. Over the years, the building had gone through multiple office space reconfigurations, and the ductwork reflected every one of them. Diffusers had been relocated, runs had been rerouted, and much of it no longer matched the original as-builts. The new system was a significant upgrade: energy-efficient equipment with air dampers for zoning, programmable thermostats, and modern controls.
The retrofit drawings and bid package were assembled from the original construction documents and pieced together with whatever record drawings existed from past reconfigurations. The documents were never validated against what was actually in the building, and there were reasons for that.
There are practical reasons that step gets skipped. The owner may believe their as-builts are accurate. They may not want to pay for someone to walk the existing space before they’ve committed to the project. The designer may be working remotely and building the drawings from available documents rather than traveling for a site visit. The office space may be occupied and access is limited. Sometimes it’s budget pressure, schedule pressure, and a project that looks straightforward enough that nobody thinks validation is necessary. The reasons are understandable. The risk they introduce doesn’t have to be part of the project.
The pre-construction meeting happened, the contractor mobilized, started demo, and within two weeks the gaps in the scope started surfacing. Duct routing above the ceiling didn’t match the drawings because runs had been moved during past reconfigurations and never documented. Penetrations through fire-rated walls existed where the drawings showed none, and a supplemental beam that had been added during a previous renovation sat exactly where the new trunk line was supposed to run.
The office had a drop ceiling. A short ladder, a flashlight, and a peek above the ceiling tiles would have shown the real conditions in a few minutes. For harder-to-reach spaces (above walls, tight chases, areas where you can’t get a head and shoulders through), a borescope would show what’s there without pulling anything apart. For larger concealed spaces, a remote-controlled robotic crawler could map conditions the drawings can’t account for. These aren’t specialty tools. They exist because as-builts go stale, especially in buildings that have been reconfigured more than once. The actual conditions could have been found, and the process just didn’t require anyone to go find them before the bid package went final.
Where Do the Change Orders Actually Come From?
That was one building and one HVAC system. But the types of scope discrepancies that surfaced on that project aren’t unique to it. They follow a pattern that shows up on renovations and retrofits across industries. The table below breaks that pattern down into what to look for, how to find it even when conditions aren’t ideal, and what it costs when it gets found during execution instead of during design.
| What to Check | How to Check It, Even With Constraints | What It Costs When You Don’t |
|---|---|---|
| Routing and clearances match actual conditions | Walk the space with drawings in hand. Lift ceiling tiles, check access panels. In occupied buildings, coordinate off-hours access or work section by section during low-traffic periods | Reroute design at field rates, emergency material procurement at premium pricing, idle crew costs during the approval cycle |
| Prior modifications are documented | Compare record drawings against field conditions. For concealed spaces, use a borescope or robotic crawler. When the designer is working remotely, maintenance staff familiar with the building can serve as a secondary source for known modifications | Unplanned demo and disposal, re-sequencing the installation, contractor change order markup on work that would have been cheaper in the original bid |
| Code compliance of existing conditions | Review current code requirements against what’s actually installed, not what’s on the drawings. For fire-rated assemblies and structural modifications from past renovations, visual confirmation of existing conditions is the only reliable check | Work stoppage on the critical path, remediation priced as a change order, potential re-inspection fees |
| Dimensional accuracy of the design | Field measurements compared to drawing dimensions at key connection points. Even a partial site visit to confirm critical dimensions reduces the risk of refabrication | Refabrication or material substitution at field cost, schedule slip while waiting on replacement materials |
This is what we call the Scope Validation Gate, the checkpoint during the design phase that confirms scope documents reflect actual field conditions before the bid package is assembled. It’s not a new process. It’s the discipline of making sure the step that should already happen actually gets assigned, executed, and documented.
When the Scope Validation Gate isn’t part of the process, it more than often doesn’t get done. The documents move forward with unchecked assumptions, and the crew becomes the validation step. By that point, the tools are down, the crew is standing by, and every hour spent sorting out what the documents should have shown is an hour billed at field rates with nothing to show for it. If you can’t point to when it triggers, how it fails, and what happens next, it’s not a gate. It’s a suggestion.
How Do You Close the Gap Between the Drawings and the Field Before It Costs You?
When scope documents aren’t validated against actual field conditions, the project carries risk that didn’t have to be there. The HVAC project made that visible, but the pattern applies to any renovation, retrofit, or capital improvement in an existing facility. Closing that gap is a process decision, not a technical one, and it starts with making validation part of how the project moves forward, not treating it as something that happens if there’s time:
- Assign the Scope Validation Gate to the project team as an explicit responsibility during the design phase. Not at the bid stage, not assumed, owned by name. If it’s not someone’s job, it doesn’t happen.
- Walk the project with the documents well before the bid package is assembled. Use site visits, borescopes, robotic crawlers, whatever the conditions require. This is the project team’s responsibility, not something to discover during a pre-bid meeting.
- Document every deviation between the drawings and the actual conditions and get them into the design documents so contractors are pricing what’s actually there, not what the as-builts assumed.
- Scope validation before bidding is a line item. Finding the gap during construction is a change order. Build it into the project budget accordingly.
The reasons this step gets skipped are rarely about negligence. They’re about budget, access, schedule, and a belief that the documents are close enough. But “close enough” is what generates change orders in the first month, and once the scope is in question, the schedule starts slipping right behind it. The scope documents are part of the plan, and if the plan hasn’t been pressure-tested against what’s actually in the field, the plan isn’t ready. If the plan isn’t ready, the project isn’t ready. Finding the gaps before they find your budget starts here.
Think first. Execute strong.
Why do renovation and retrofit projects generate unexpected change orders?
Change orders on renovation projects often trace back to scope documents that were never validated against actual field conditions. When drawings are built from original as-builts in buildings that have been reconfigured, the documents describe conditions that no longer exist. The crew discovers the gaps during execution, at field rates, instead of the project team catching them during the design phase when the fix is a drawing revision.
What is the Scope Validation Gate?
The Scope Validation Gate is a checkpoint during the design phase that confirms scope documents reflect actual field conditions before the bid package is assembled. It assigns validation as an explicit responsibility with a named owner, uses site visits and inspection tools to document deviations, and gets those deviations into the design documents so contractors price validated conditions, not assumptions.
What does it cost when scope documents aren’t validated against the field?
Scope gaps nobody validated result in reroute designs at field rates, emergency material procurement at premium pricing, idle crew costs during approval cycles, work stoppages on the critical path, contractor change order markup on work that would have been cheaper in the original bid, and refabrication or material substitution when dimensions don’t match. Every hour the crew spends sorting out what the documents should have shown is billed at field rates with nothing to show for it.
How do you validate scope documents against field conditions on existing buildings?
Walk the project with the documents during the design phase, well before the bid package is assembled. Use site visits to check accessible spaces like drop ceilings and access panels. Use a borescope for concealed spaces above walls and tight chases. Use a remote-controlled robotic crawler for larger concealed areas. Document every deviation and get it into the design documents so the bid package reflects what’s actually there.
Who is responsible for scope validation on a capital improvement project?
The project manager needs to ensure the validation step happens. On smaller projects, the project manager may conduct the validation directly. On larger projects, it may be assigned to a team member. The key is explicit ownership. When scope validation isn’t someone’s named responsibility during the design phase, it more than often doesn’t get done and the crew becomes the validation step during execution.
When drawings and the field disagree, change orders are not a documentation glitch. They are an owner-side control failure that shows up in cost and schedule. Owner’s representation and project control is how we pressure-test scope before award and keep the plan honest through build. More on how A. McBeth works.
