Construction Spec Conflicts: 5 Fields Every Estimator Must Log
Construction Spec Conflicts: 5 Fields Every Estimator Must Log ! Construction specification conflict title card When specifications and drawings conflict, document the mismatch and submit an RFI, or state a clear, written assumption in your bid if you're still pre-award.
When specifications and drawings conflict, document the mismatch and submit an RFI, or state a clear, written assumption in your bid if you’re still pre-award. Before you touch anything, check who actually has authority to interpret the conflict: that answer usually sits buried in your contract’s order of precedence clause, and acting without it puts the cost and risk on you.
TL;DR:
- Most construction conflicts involve dimensional discrepancies, omitted items, material differences, or quantity mismatches, which can often be preempted with proper classification.
- Checking contract-specific precedence rules, such as AIA A201 or FAR, is crucial before making field decisions to avoid costly unilateral changes.
- Logging conflicts immediately with key details and pricing both interpretation options in bid preparation prevents rework and supports strong documentation for claims.
- Implementing structured cross-checks and version-controlled documents during bid and design stages reduces mismatch occurrences before they reach construction.
- Using automated tools integrated with existing platforms, like ArosBid, helps track conflicts and assumptions through the entire bid cycle, minimizing overlooked issues.
Table of Contents
- How to Spot and Catalogue Spec vs. Drawing Conflicts
- Who Decides: Contract Clauses, AIA A201 vs. Federal FAR Rules
- Step-by-Step Workflow for Resolving Spec vs. Drawing Conflicts
- Preventing Spec vs. Drawing Conflicts Before They Start
- An Estimator’s Conflict-Log Playbook
- Speed Versus a Defensible Bid
- A Practical Option for Tracking Conflicts and Assumptions
- FAQ
- Sources
- Primary Standards and Contract Clauses Referenced
How to Spot and Catalogue Spec vs. Drawing Conflicts
Most construction spec conflicts fall into a handful of repeatable categories. Catching them early means knowing what to look for before the mismatch becomes a change order.
The common mismatch types include:
- Dimensional conflicts: a drawing shows one measurement while the spec section states another.
- Omitted items: a product or assembly appears in the spec but is missing from the drawings, or the reverse.
- Material or performance differences: the drawing calls for one finish or rating, the spec calls for another.
- Quantity mismatches: the bill of quantities does not match what the spec actually describes.
Not every conflict deserves the same urgency. Triage by three factors: safety or structural impact first, cost exposure second, and frequency of occurrence third. A one-line dimensional discrepancy on a non-structural partition can wait for a routine RFI batch. A load rating mismatch on a structural member cannot.
Once you’ve spotted a conflict, log it immediately rather than relying on memory or a scattered email thread. A useful conflict log captures:
- A unique conflict ID for tracking.
- The date identified.
- The sheet reference and spec section in conflict.
- A short, plain-language description of the mismatch.
- An initial estimate of cost and schedule exposure.
This log becomes the backbone of everything that follows: your RFIs reference it, your bid assumptions cite it, and if a dispute ever reaches a claim, it’s the document that shows you flagged the issue instead of guessing.
Who Decides: Contract Clauses, AIA A201 vs. Federal FAR Rules
The contract form you’re working under changes who get to settle a conflict, and getting this wrong is one of the costliest mistakes an estimator can make.
Under AIA A201, the standard agreement used widely in private commercial work, drawings and specifications are treated as complementary documents, and the architect holds responsibility for interpreting conflicts between them. That means a contractor working under A201 generally cannot unilaterally decide which document wins; the interpretation runs through the architect.
Federal contracts work differently. FAR 52.236-21 states that, when drawings and specifications differ, the specifications govern, and it requires a prompt written determination from the Contracting Officer before work proceeds. A contractor who assumes the A201 precedence logic applies on a federal job, or vice versa, can end up building to the wrong standard entirely.
The practical takeaway is the same regardless of which form you’re under: always check the contract’s order of precedence clause before making a field decision, and always follow the written change order process rather than acting on a verbal direction. Many disputes start because an estimator assumes a precedence rule that only applies to a specific contract type. The safer habit, used across public and private work, is to flag the conflict during bid review, price both interpretations when the exposure is material, and then submit an RFI or record a written assumption rather than guess.
Unilateral field changes made before written direction arrives are made at the contractor’s own cost and risk. That single fact is worth repeating to every superintendent and project engineer on a job.
Step-by-Step Workflow for Resolving Spec vs. Drawing Conflicts
A repeatable workflow protects both time and money, whether the conflict surfaces during bid prep or mid-construction.
Pre-bid. Build the conflict log the moment a discrepancy turns up during takeoff. Price the exposure for each entry so you know what’s at stake if the worse-case interpretation wins. Then either submit an RFI to the design team or, if the bid deadline won’t allow for a response, record a clear written assumption directly in your bid documents stating which interpretation you priced.
During the RFI process. A well-written RFI does three things: it references both the drawing and the spec section in conflict, states your recommended interpretation, and quantifies the cost or schedule impact where you can. Closing with a direct request for written clarification, rather than a general question, speeds up the response and leaves a cleaner record. A subcontractor-focused guide to RFI workflow mistakes covers several of the most common missteps worth avoiding, including vague framing and missing cost context.
Shop drawings. Any deviation introduced at the shop drawing stage needs its own log entry and a written approval or contract modification before fabrication starts. Skipping this step is how a resolved RFI quietly becomes an unresolved field conflict again.
Post-award documentation. If a conflict eventually supports a change order or claim, the documentation that holds up is specific: the original conflict log entry, the RFI and its written response, any priced assumption from the bid, and the shop drawing approval trail. Preserve all of it in one place rather than scattered across email.
A minimal, defensible RFI needs just a few fields:
- The conflict ID from your log.
- Sheet and spec references.
- Your recommended interpretation.
- The cost and schedule impact, if known.
- A clear request for written direction by a stated date.
Pro Tip: Price every material conflict both ways before you submit the RFI. A written exposure range turns a vague question into a decision the design team can act on quickly.
Preventing Spec vs. Drawing Conflicts Before They Start
The cheapest conflict is the one that never makes it to a drawing set. Prevention starts with classification systems that keep specifications, drawings, and cost data aligned from the start.
MasterFormat 2026, maintained by the Construction Specifications Institute, increases classification granularity and helps keep specifications, drawings, and product data aligned across project phases. The 2026 update introduces 2,185 new listings and reorganizes 617 existing ones, which gives spec writers more precise categories to work with instead of forcing unrelated scopes into the same section. Used alongside UniFormat for early design phases, it reduces the chance that a scope described one way in the spec book gets drawn a different way on the sheets.
A few document control habits do most of the heavy lifting:
- Keep a single version-controlled master for both specs and drawings, with no parallel copies circulating.
- Use revision clouds and transmittal logs so every change has a visible trail.
- Cross-reference spec sections directly on the drawings where a scope overlaps.
- Run a dedicated spec-to-drawing cross-check before issuing for bid, not after.
Pre-bid coordination meetings and a QA/QC gate before issuance catch a surprising share of mismatches that a single reviewer misses. Pairing that human review with templated checklists and lightweight automated document checks tends to catch the rest, especially on larger spec books where manual review alone starts to miss things.
Pro Tip: Build your spec-to-drawing cross-check into the same QA/QC gate you already use for code compliance, instead of treating it as a separate review step.
An Estimator’s Conflict-Log Playbook
Experienced estimators assign a quick dollar range to each conflict the moment it’s logged, even before a formal takeoff, because that range decides whether the conflict gets priced into the bid or escalated immediately for design clarification. A conflict log that survives from bid to buyout also stops the same mismatch from getting re-discovered and re-argued on the next similar project.
A simple handoff checklist to procurement and field crews should include the conflict ID, the RFI number if one was filed, the approved interpretation, and any deviation sign-off from shop drawings. Teams using a structured bid platform, like the one ArosBid describes in a steel estimating post, have found that tracking assumptions in one place reduces how often the same mismatch resurfaces as an RFI later in the job.
Speed Versus a Defensible Bid
Skipping the conflict log to save an hour before a bid deadline is a false economy. That hour comes back tenfold the first time a claim depends on proving you flagged the issue instead of guessing your way through it.
The teams that actually reduce disputes aren’t the ones with the fanciest software. They’re the ones that make logging a conflict a mandatory step, not an optional one, and that run a short debrief after every bid to ask what got missed and why. Treating an RFI as a bureaucratic delay is the wrong frame. It’s a risk-reduction tool, and the contractors who file them early tend to spend far less time in claims meetings later.
— arosbid team
A Practical Option for Tracking Conflicts and Assumptions
Catching a spec conflict during takeoff is one thing. Keeping that catch documented, priced, and visible through buyout is another, and it’s where most conflict logs quietly fall apart under deadline pressure. We built ArosBid as a command center for the whole bid cycle, with automated document review that flags conflicting clauses, vendor quote leveling, and a running log of the assumptions you’ve made so nothing gets lost between the estimate and the signed contract.
The platform integrates with Excel and Outlook, so adopting a structured conflict log doesn’t mean replacing the tools your team already runs on. Compare plans and pricing or book a live demo to see how it fits your next bid.
FAQ
What are the three main types of construction specifications?
Construction specifications are commonly grouped into prescriptive, performance, and proprietary types. Prescriptive specs dictate exact materials and methods, performance specs define the required result and let the contractor choose the method, and proprietary specs name a specific product or manufacturer.
What are the current issues facing the construction industry?
Specification and drawing conflicts remain a persistent source of rework, delay, and disputed scope on projects of every size. Coordination gaps between design and field teams, inconsistent document control, and uneven adoption of classification standards like MasterFormat all contribute to the problem.
How do I resolve a conflict with a contractor over specifications?
Start by checking the contract’s order of precedence clause to confirm who has authority to interpret the conflict, since this differs between forms like AIA A201 and federal FAR contracts. Document the mismatch, submit a written RFI with your recommended interpretation, and avoid making field changes until you have written direction.
What are some common types of disputes in construction?
Common disputes trace back to unresolved spec-versus-drawing conflicts, unapproved scope changes, delayed RFI responses, and disagreements over which contract document governs. Most of these become harder to resolve when the originating conflict was never logged or documented in writing at the time it was discovered.
Does ArosBid help with specification conflicts during bidding?
ArosBid’s document review features are built to flag conflicting clauses and missed items before a bid goes out, pairing automated checks with human review. Pricing for the One Desk, The Department, and The Whole Year plans is available on the pricing page.
Sources
- A201-2017 (AIA) standard contract document (procurement copy)
- MasterFormat 2026 (Construction Specifications Institute)
Primary Standards and Contract Clauses Referenced
For contract verification and further reading, review the AIA A201 standard agreement and the MasterFormat 2026 overview from the Construction Specifications Institute. Federal projects should also check FAR 52.236-21 directly within the applicable procurement clauses.