Using Field Reports to Verify Design Intent

Design-phase QA/QC catches issues on paper, before anything is built. It doesn't confirm that what actually gets built matches what was designed. That's a separate verification step, and field reports are the primary tool for closing that gap.

Why This Gap Exists Even With Strong Design-Phase Review

A drawing set can be thoroughly reviewed, fully coordinated, and code compliant, and installed work can still deviate from it. Field conditions differ from what was anticipated. Subcontractors interpret details differently than intended. Substitutions happen without always being fully documented or communicated back to the design team. None of this is necessarily a design error, it's a construction-phase verification problem, which is a different failure mode than a coordination conflict caught during plan review.

What Verification Against Design Intent Actually Looks Like

At its core, this means comparing what's documented in the field, photos, notes, inspection results, against what the drawings actually called for at that location. A field report that clearly ties its documentation to a specific drawing sheet or detail reference makes this comparison direct: pull up the relevant sheet, pull up the field documentation for that location, and check whether they agree.

This is most critical at points that become inaccessible once construction proceeds. Reinforcement and formwork before a concrete pour. Rough-in conditions before drywall closes a wall. Waterproofing details before they're covered by finish work. These are the moments where field documentation is the only record that will exist once the work is covered, which makes getting it right at the time non-negotiable, since there's no going back to check later without demolition.

Where This Connects Back to Design-Phase QA/QC

Strong design-phase review reduces how much verification burden falls on field documentation, since a well-coordinated, clearly detailed drawing set gives less room for field interpretation to drift from design intent in the first place. But it doesn't eliminate the need for field verification entirely. The two are complementary parts of a full QA/QC process: design-phase review reduces the chance of errors being designed in, field verification confirms what was designed is actually what got built.

Using This to Close the Loop When Discrepancies Are Found

When field documentation reveals installed work that doesn't match design intent, that discrepancy is worth tracing back to understand why. Sometimes it's a legitimate field-driven change that should have been documented as a change order but wasn't formally processed. Sometimes it's a genuine installation error. Sometimes it points to a detail that was actually ambiguous or difficult to execute as drawn, which is useful feedback for how similar details get drawn on future projects. Treating these discrepancies as information rather than just problems to close out tends to improve both future field documentation practices and future design detailing.

FAQ

How often should field documentation be checked against design intent, rather than just at project closeout? Ongoing, ideally, particularly at points that become inaccessible once construction proceeds. Waiting until closeout to compare field documentation against design intent means any discrepancies found are much harder and more expensive to address.

Does this replace formal inspections and QC testing? No. Formal inspections and testing, concrete testing, weld inspections, and similar, remain their own QC activities. Field report verification against design intent is complementary, capturing a broader record of installed conditions beyond what formal testing specifically covers.

What should happen when a discrepancy between field conditions and design intent is found? It's worth understanding the root cause, whether it's an undocumented field change, an installation error, or an ambiguous detail, both to resolve the immediate issue and to inform whether the underlying design or documentation practice needs adjustment going forward.