Field Conditions Affect Scope Reality

Why the Drawing and the Field Are Never the Same Thing

Architectural drawings are produced before construction begins. They represent a design intent based on the information available at the time they were drawn. By the time finish trades mobilize, the project has been under construction for weeks or months. Conditions in the field reflect every decision made during that period, including decisions that were not communicated to the trade contractor.

Framing adjustments, MEP reroutes, structural modifications, and design changes issued mid-construction all alter the field conditions the finish trade will encounter. Some of those alterations are reflected in revised drawings. Many are not. The finish contractor working from the original drawing set is working from a document that no longer fully describes the site.

Recognizing this as a structural condition of construction, rather than an exceptional problem, is what separates a trade partner with an effective scope management process from one who discovers conditions on the first day of installation.

Where Undefined Scope Accumulates

Undefined scope accumulates in the areas where field conditions and drawing intent diverge most visibly: framing that is out of tolerance at door openings and built-in locations, MEP components that occupy space the drawing assumed would be clear, and surfaces that require additional preparation before finish work can begin.

Each of these areas represents a decision point. The finish contractor encountering them on site must either proceed on their own interpretation, stop work and contact the GC, or absorb the additional scope without documentation. Each option has a cost. The first option creates an undocumented scope assumption. The second option interrupts production. The third option creates an unpaid scope addition.

Pre-mobilization identification of these areas through a site visit or a direct coordination conversation with the GC eliminates all three of those outcomes. The decision is made before production begins, the documentation exists before work proceeds, and the scope reflects the field rather than the drawing.

Documenting the Gap Before Work Proceeds

The documentation required to manage field conditions against scope reality does not need to be formal or extensive. It needs to exist before work proceeds and be agreed upon by both the GC and the trade contractor. A written note confirming that a specific condition was reviewed and that the scope was adjusted accordingly is sufficient to protect both parties.

What is not sufficient is a verbal agreement made on site, a photograph without a corresponding written description, or a general understanding that both parties remember differently when billing questions arise. Written records are the only records that hold weight when conditions or costs are disputed.

At D'Matos, field conditions that diverge from the scope document are flagged before work proceeds, not after. The GC receives a written description of the condition and the proposed resolution. Work continues once the resolution is confirmed. That process adds minutes to the pre-execution phase and removes days from the closeout process.

The Project Compression Problem

Project compression at closeout is frequently caused by accumulated undefined scope that was never formally addressed during execution. Each undocumented decision adds a small, invisible cost to the project. At closeout, those costs become visible simultaneously, and neither party has a complete record of the decisions that generated them.

The GC's position at that point is that the original scope covered the work. The trade contractor's position is that field conditions required additional scope. Both positions are defensible in the absence of documentation and irresolvable without it. The dispute is not about the facts. It is about the absence of a record of the facts.

Early documentation of field conditions is the most effective tool available to prevent project compression at closeout. It is also the most consistently underused, because it requires discipline during execution when production pressure is highest and documentation pressure is lowest.

---