Document Precedence and Conflict Resolution: Governing Documents, Specification Language, and NIC/NIS

How construction contract documents relate to each other, which document governs when conflicts arise, and how specification language like NIC and NIS directs responsibility across the project team.

ARE · Project Development & Documentation

Overview

A construction project generates hundreds of pages of contract documents: the owner-contractor agreement, general conditions, supplementary conditions, drawings, specifications, addenda, and change orders. These documents are supposed to work together. But when they contradict each other, and they will, someone has to determine which document wins.

That determination comes down to document precedence. Under AIA A201-2017, the default position is that all contract documents are complementary. What one document requires is as binding as if all documents required it. But complementary does not mean conflict-free. Drawings might show a material that the specifications contradict. A change order might override language in the general conditions. When these clashes surface during construction, the architect steps in to interpret the documents and resolve the inconsistency.

For the PDD exam, you need to understand how this hierarchy operates, what specification terms like NIC (Not in Contract) and NIS (Not in Scope) signal to contractors, and how the architect's interpretive authority shapes the resolution process. Getting this wrong on a project means disputes, claims, and delays. Getting it wrong on the exam means lost points in a section that rewards careful reading of document relationships. When conflicts arise between documents during construction, the precedence hierarchy determines which document governs, and the architect must understand this hierarchy to respond correctly.

Essential

The Complementary Document Principle Under AIA A201-2017 Section 1.2.1, all contract documents are treated as complementary. The contractor is required to perform work to the extent consistent with the contract documents and reasonably inferable from them as being necessary to produce the indicated results. This is a significant concept: if the drawings show a fire-rated partition but the specifications do not mention it, the contractor is still expected to provide it. The documents read together, not in isolation. But "complementary" does not mean "identical." Conflicts between documents happen constantly. Drawings might indicate one product while the specifications name another. The general conditions might set one standard for payment applications while a supplementary condition modifies it. When that happens, you need a system for determining which document controls.

Professional

The Window Schedule Problem Consider a mixed-use project where the architectural drawings show aluminum-framed windows with a specific manufacturer on the elevation drawings. The window schedule in the drawings lists the same manufacturer with a particular thermal performance rating. But Division 08 of the specifications calls for a different manufacturer with a higher thermal performance rating, because the specification writer updated the energy analysis after the drawings were issued. The contractor submits for the less expensive product shown on the drawings. The architect rejects the submittal, pointing to the specification requirement. The contractor argues the drawings govern. Who is right? Under the standard AIA A201 framework, neither the drawings nor the specifications automatically take precedence. The architect must interpret the documents to reflect the design intent. In this case, the updated energy analysis drove the specification change, making the specification the more current expression of design intent.

TLDR

AIA A201-2017 treats all contract documents as complementary; what one requires is binding as if all required it
A201 does NOT establish a fixed order of precedence; the architect interprets conflicts based on design intent
A503 model precedence (top to bottom): Modifications, Agreement, Addenda, Supplementary Conditions, General Conditions, Division 01, Drawings + Divisions 02-49, Other documents
Drawings and technical specifications (Divisions 02-49) share the same priority level; neither automatically wins
NIC (Not in Contract) = work exists but is under a different contract; NIS (Not in Scope) = work is not addressed in this section
The architect must act impartially when interpreting document conflicts, favoring neither owner nor contractor
"Provide" = furnish and install; "Furnish" = deliver to site only (critical distinction in UFGS federal specs)
Change orders always sit at the top of the precedence hierarchy because they represent the most recent agreement
Do not repeat information across documents; every repetition creates an opportunity for inconsistency
Coordination before document issuance prevents conflicts; precedence clauses only resolve them after disputes arise

ELI5

Think of a construction project like a recipe written by a whole team of people. One person writes the ingredient list (specifications). Another draws pictures of what the final dish should look like (drawings). Someone else writes the rules for how the kitchen operates (general conditions). And the head chef writes the total agreement about what dish to make and how much it costs (the agreement). Now imagine the ingredient list says to use cheddar cheese, but the picture clearly shows mozzarella. Who is right? In construction, these kinds of mix-ups happen all the time. The solution comes in two parts. First, all the recipe pages are meant to work together. If the ingredient list mentions cheese but does not specify the type, and the picture shows mozzarella, you use mozzarella. The pages fill each other's gaps. This is called the complementary document principle.

AREProject Development & Documentation

Document Precedence and Conflict Resolution: Governing Documents, Specification Language, and NIC/NIS

How construction contract documents relate to each other, which document governs when conflicts arise, and how specification language like NIC and NIS directs responsibility across the project team.

2 min read214 words

Why Document Precedence Matters on Every Project

Want to track your progress and access more study tools?

Create a free account