Define the Field Condition

The Foundation of Field Decisions

Defining the field condition is where the rubber meets the road on any job site. It isn't just a matter of saying 'something is wrong'; it is about capturing the exact delta between the contract documents and the physical reality. When you walk into a space and realize the existing plumbing lines are six inches lower than the MEP drawings indicated, you've found a condition. But if you haven't defined it—captured its dimensions, its impact on the surrounding framing, and its specific location—you haven't really started the decision process. Most site disputes aren't about the solution; they're about a failure to agree on what the problem was in the first place.

Observation vs. Documentation

Precision in this phase saves weeks of back-and-forth RFI cycles. We often see teams rushing through the 'what' to get to the 'how much,' but without a solid definition, those cost estimates are just guesses. A well-defined condition includes not just the physical anomaly, but the environment around it. Answering critical questions early creates a shared set of facts that all stakeholders can work from, reducing the friction of ownership transfers later in the project.

• Cross-reference the observed condition with the most recent submittals and shop drawings to confirm it is truly a deviation.
• Document the 'area of influence'—exactly how far this condition ripples into other trades' work zones.
• Use a standardized naming convention so the field crew, the project manager, and the architect are all talking about the same thing.