{"id":192,"date":"2026-08-22T18:37:47","date_gmt":"2026-08-22T18:37:47","guid":{"rendered":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/?p=192"},"modified":"2026-08-22T18:37:48","modified_gmt":"2026-08-22T18:37:48","slug":"spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp","status":"publish","type":"post","link":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/","title":{"rendered":"Spec vs. Drawing Discrepancies: Finding What’s Missing Before GMP"},"content":{"rendered":"\n

Once a Guaranteed Maximum Price is signed, every gap between what the specs say and what the drawings show becomes someone’s problem to pay for. Here’s how to find those gaps while they’re still cheap to fix.<\/em><\/p>\n\n\n\n

A Guaranteed Maximum Price is exactly what it sounds like: a number both the owner and the general contractor agree the project won’t exceed, barring approved changes. That agreement only holds up if the number actually reflects everything the contract documents require. When a requirement exists in the specification manual but never made it onto a drawing \u2014 or the reverse, something shown on a drawing with no corresponding specification \u2014 that requirement either got priced by accident, priced by nobody, or priced twice. None of those outcomes is good, and all three become considerably harder to fix once the GMP is signed.<\/p>\n\n\n\n

This is the specific risk a spec-versus-drawing discrepancy review exists to catch. It’s a distinct exercise from general scope gap analysis, because it’s not asking “did we assign this to the right trade” \u2014 it’s asking a more basic question first: “do the two documents that are both supposed to describe this requirement actually agree with each other?” A surprising number of real disputes trace back to exactly this kind of mismatch, hiding in plain sight across two document types that get reviewed separately far more often than they get reviewed together.<\/p>\n\n\n\n

\u2605 Key Takeaway<\/strong>
A GMP is a promise that the price reflects the full scope of work. That promise is only as good as the assumption that the specs and drawings agree with each other \u2014 an assumption that’s rarely tested directly and, when tested, often doesn’t fully hold.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

This article covers how spec-versus-drawing discrepancies actually happen, why they survive typical pre-GMP review, and how a systematic, technology-supported audit closes this specific risk before the price gets locked in.<\/p>\n\n\n\n

Key Definitions<\/strong><\/strong><\/h2>\n\n\n\n
Term<\/strong><\/strong><\/strong><\/th>Working Definition<\/strong><\/strong><\/strong><\/th><\/tr><\/thead>
Guaranteed Maximum Price (GMP)<\/td>A contract price the GC guarantees the actual project cost will not exceed, typically established once design is sufficiently developed to price with confidence.<\/td><\/tr>
Spec-Only Requirement<\/td>A requirement described in the specification manual with no corresponding reference or detail shown on the drawings.<\/td><\/tr>
Drawing-Only Requirement<\/td>A requirement shown on a drawing with no corresponding specification section addressing installation, material, or performance standards.<\/td><\/tr>
Conflicting Instruction<\/td>A case where the specifications and drawings both address the same requirement but describe it inconsistently.<\/td><\/tr>
Discrepancy Audit<\/td>A systematic review comparing specification content against drawing content to identify gaps or conflicts between the two.<\/td><\/tr>
Pre-GMP Confidence Report<\/td>A summary quantifying how completely the specifications and drawings align, used to inform the decision to finalize a GMP.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Objectives<\/strong><\/strong><\/h2>\n\n\n\n
    \n
  • Identify every requirement that exists in the specification manual but has no corresponding reference on the drawings, before pricing is finalized.<\/li>\n\n\n\n
  • Identify every requirement shown on drawings with no corresponding specification detail, particularly for material and performance standards.<\/li>\n\n\n\n
  • Catch cases where the two document types describe the same requirement in conflicting or inconsistent terms.<\/li>\n\n\n\n
  • Quantify the scope of remaining discrepancy risk so a GMP decision can be made with full information, not assumed completeness.<\/li>\n\n\n\n
  • Resolve genuine ambiguity through a design clarification before it’s priced, rather than pricing around a guess.<\/li>\n<\/ul>\n\n\n\n

    Importance<\/strong><\/strong><\/h2>\n\n\n\n

    The GMP moment is a specific point of no return in a project’s financial structure. Before it, a discovered discrepancy is a pricing adjustment \u2014 inconvenient, but routine. After it, the same discrepancy becomes a change order request, and change order requests after GMP carry a very different conversation: was this discrepancy something the GC should have caught during pricing, or is it a legitimate scope addition the owner should pay for? That conversation is rarely pleasant, and it’s entirely avoidable if the discrepancy gets caught before the price is locked.<\/p>\n\n\n\n

    There’s a reason this specific risk survives typical review processes even on well-run projects. Specifications and drawings are usually reviewed by different people, on different schedules, sometimes even by different firms within a design team. An architect’s specification writer and the mechanical engineer producing drawings rarely cross-check their work against each other directly \u2014 each assumes the other’s document is internally consistent with theirs, and that assumption is often simply never verified by anyone until a GC’s precon team goes looking, if they go looking at all.<\/p>\n\n\n\n

    \u25c6 Industry Insight<\/strong>
    Dedicated spec-versus-drawing discrepancy audits performed before GMP finalization typically surface a handful of genuine gaps even on well-documented projects \u2014 not because the design team was careless, but because nobody’s normal workflow includes directly comparing every specification section against every corresponding drawing reference.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    It’s worth being precise about what this implies for how a GC frames the audit internally and with the design team. Finding discrepancies isn’t a criticism of the design work \u2014 it’s the expected, normal result of checking two documents that were never designed to be cross-verified against each other as a standard part of their production. Framing it that way, rather than as catching design mistakes, tends to produce a more collaborative resolution process, since the design team isn’t being asked to defend an error so much as help close a gap that the document production process itself makes almost inevitable.<\/p>\n\n\n\n

    Stakeholders<\/strong><\/strong><\/h2>\n\n\n\n
    Role<\/strong><\/strong><\/strong><\/th>Interest in Spec-vs-Drawing Discrepancy Review<\/strong><\/strong><\/strong><\/th><\/tr><\/thead>
    Preconstruction Manager<\/td>Owns the completeness and accuracy of the GMP pricing basis before it’s presented for approval.<\/td><\/tr>
    Estimator<\/td>Needs assurance that pricing reflects the full, consistent scope described across both document types.<\/td><\/tr>
    Owner \/ Owner’s Rep<\/td>Bears the financial consequence of any discrepancy discovered after GMP, typically through a change order negotiation.<\/td><\/tr>
    Architect \/ Engineer of Record<\/td>Wants discrepancies resolved against actual design intent, ideally before pricing rather than through a post-award dispute.<\/td><\/tr>
    Project Executive<\/td>Carries responsibility for defending the GMP’s completeness if a discrepancy surfaces during construction.<\/td><\/tr>
    Legal \/ Risk Management<\/td>Needs a documented record showing discrepancy review was performed, supporting the company’s position in any later dispute.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Construction Workflow<\/strong><\/strong><\/h2>\n\n\n\n

    The Three Discrepancy Patterns<\/strong><\/strong><\/h3>\n\n\n\n

    Spec-versus-drawing discrepancies tend to fall into three recognizable patterns, and knowing the difference helps a reviewer know what to look for and how to resolve what they find.<\/p>\n\n\n\n

    Pattern<\/strong><\/strong><\/strong><\/th>Description<\/strong><\/strong><\/strong><\/th>Typical Resolution<\/strong><\/strong><\/strong><\/th><\/tr><\/thead>
    Spec-Only<\/td>A requirement described in the specification manual with no corresponding drawing reference or detail.<\/td>Add a drawing reference, or confirm the spec language alone is sufficient for pricing and installation.<\/td><\/tr>
    Drawing-Only<\/td>A requirement shown on a drawing with no corresponding specification addressing material or performance standards.<\/td>Add a specification reference, or confirm the drawing detail alone fully defines the requirement.<\/td><\/tr>
    Conflicting<\/td>Both documents address the same requirement, but describe it with different, inconsistent specifics.<\/td>A design clarification resolving which version governs, documented in writing before pricing.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    A Structured Discrepancy Audit Sequence<\/strong><\/strong><\/h3>\n\n\n\n
      \n
    • Extract every requirement from the full specification manual into a structured, searchable format, organized by CSI division.<\/li>\n\n\n\n
    • Extract every note and callout from the full drawing set, tagged in the same structure for direct comparison.<\/li>\n\n\n\n
    • Cross-reference the two datasets to identify items appearing in one but not the other.<\/li>\n\n\n\n
    • Flag items appearing in both with meaningfully different specifics for direct comparison and resolution.<\/li>\n\n\n\n
    • Compile findings into a discrepancy report, categorized by severity, for review before GMP finalization.<\/li>\n<\/ul>\n\n\n\n
      \u25a3 Field Reality<\/strong>
      Spec-only requirements tend to cluster in categories that don’t get drawn as a matter of convention \u2014 grounding requirements, testing procedures, and certain code-driven administrative requirements are described in specs and simply assumed to apply without a drawing callout.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      This clustering pattern is worth building into a review checklist rather than rediscovering project by project. A team that tracks which specification divisions have historically produced spec-only findings \u2014 commonly electrical grounding and bonding, commissioning and testing procedures, and certain fire protection administrative requirements \u2014 can weight its review attention accordingly, checking those divisions with extra care rather than distributing equal scrutiny across the entire specification manual regardless of where problems actually tend to concentrate.<\/p>\n\n\n\n

      Required Documentation<\/strong><\/strong><\/h2>\n\n\n\n
        \n
      • The complete, current specification manual, organized by CSI division, at the latest issued revision.<\/li>\n\n\n\n
      • The complete, current drawing set across every discipline, including all issued addenda.<\/li>\n\n\n\n
      • Any RFI responses that may have clarified a discrepancy already, to avoid re-flagging an item that’s genuinely resolved.<\/li>\n\n\n\n
      • Prior discrepancy audit results from similar project types, useful for anticipating which categories are most likely to need attention.<\/li>\n\n\n\n
      • A record of the GMP pricing basis itself, to confirm which specific documents the price was actually built against.<\/li>\n<\/ul>\n\n\n\n

        Technology Integration<\/strong><\/strong><\/h2>\n\n\n\n

        Manually cross-referencing a full specification manual against a full drawing set is a genuinely large undertaking \u2014 hundreds of specification sections need to be checked against a document set that might run several hundred sheets, looking for a match, a conflict, or an absence for each one. Doing this thoroughly by hand, on a tight pre-GMP schedule, is precisely the kind of task that tends to get compressed into a partial spot-check rather than the exhaustive review it needs to be.<\/p>\n\n\n\n

        What Automated Cross-Referencing Adds<\/strong><\/strong><\/h3>\n\n\n\n
          \n
        • Systematic comparison of every specification section against the full drawing set, rather than a sampled or discipline-limited review.<\/li>\n\n\n\n
        • Automatic flagging of spec-only and drawing-only items, sorted by CSI division and severity, so review time focuses where it matters most.<\/li>\n\n\n\n
        • Semantic comparison of overlapping requirements, catching conflicts even when the two documents use different terminology to describe the same thing.<\/li>\n\n\n\n
        • A quantified discrepancy count and severity breakdown that supports a clear go\/no-go decision on GMP finalization.<\/li>\n<\/ul>\n\n\n\n
          \u270e Expert Tip<\/strong>
          When reviewing an automated discrepancy report, spend disproportionate attention on the “conflicting” category rather than the “missing” categories. A missing cross-reference is usually a documentation gap; a genuine conflict between two documents both intended to govern the same requirement is a design ambiguity that needs resolution, not just administrative cleanup.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

          AI-Assisted Opportunities<\/strong><\/strong><\/h2>\n\n\n\n

          This is a strong application for AI assistance because the underlying comparison task benefits enormously from semantic understanding rather than simple text matching. A specification describing “provide continuous vapor barrier at all wall-to-roof transitions” and a drawing note describing “seal per manufacturer’s guide at parapet condition” might be describing the exact same requirement in different language \u2014 catching that connection requires understanding meaning, not just matching keywords.<\/p>\n\n\n\n

          Semantic Cross-Referencing at Scale<\/strong><\/strong><\/h3>\n\n\n\n

          An AI-assisted comparison engine can identify that two differently worded passages likely describe the same underlying requirement, flagging them for a human reviewer to confirm rather than requiring the reviewer to manually notice the connection across two large, separately organized documents. This is precisely the kind of exhaustive, consistent pattern-matching that benefits from automation while still needing human judgment for the final call.<\/p>\n\n\n\n

          On-Demand Discrepancy Queries<\/strong><\/strong><\/h3>\n\n\n\n

          A conversational layer on top of the cross-referenced dataset lets a reviewer ask direct questions \u2014 “what’s in the specs but not shown in the drawings for Division 23?” \u2014 and get an immediate, structured answer rather than waiting for a scheduled comprehensive report. This makes it realistic to check specific areas of concern as they come up during pre-GMP review, not just once at the very end.<\/p>\n\n\n\n

          \u25cf Important<\/strong>
          Automated discrepancy detection surfaces candidates for review \u2014 it doesn’t independently resolve which document should govern when there’s a genuine conflict. That decision belongs to the design team and should be documented as a formal clarification, not decided unilaterally by the reviewing GC.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

          There’s a practical reason this boundary matters beyond fairness to the design team. A GC that unilaterally decides which of two conflicting documents governs, without design team confirmation, is making a design decision it isn’t necessarily qualified or authorized to make \u2014 and if that decision turns out to conflict with what the architect or engineer actually intended, the GC has effectively created a new dispute while trying to resolve an old one. Routing genuine conflicts back to the design team for a documented answer costs a short delay; skipping that step risks a decision nobody with design authority ever actually approved.<\/p>\n\n\n\n

          Implementation<\/strong><\/strong><\/h2>\n\n\n\n
          Phase<\/strong><\/strong><\/strong><\/th>Activities<\/strong><\/strong><\/strong><\/th>Owner<\/strong><\/strong><\/strong><\/th><\/tr><\/thead>
          Pilot<\/td>Run a discrepancy audit on a project already through GMP and compare findings against known issues from that project.<\/td>Preconstruction Manager<\/td><\/tr>
          Severity Calibration<\/td>Establish what qualifies as a high-severity discrepancy warranting a mandatory resolution before GMP.<\/td>Estimating Lead<\/td><\/tr>
          Resolution Protocol<\/td>Define the process for routing conflicting-instruction items to the design team for clarification.<\/td>Contracts Administrator<\/td><\/tr>
          Schedule Integration<\/td>Build the audit into the standard pre-GMP timeline with enough lead time to resolve findings.<\/td>Preconstruction Team<\/td><\/tr>
          Outcome Tracking<\/td>Track which discrepancies, if any, still generate change orders despite the audit, to refine the process.<\/td>Estimating Lead<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

          Best Practices<\/strong><\/strong><\/h2>\n\n\n\n
          Practice<\/strong><\/strong><\/strong><\/th>Why It Matters<\/strong><\/strong><\/strong><\/th><\/tr><\/thead>
          Run the audit early enough to leave time for design clarification<\/td>A discrepancy found the day GMP is due to be signed leaves no room for a proper resolution.<\/td><\/tr>
          Treat conflicting instructions as design ambiguity, not administrative cleanup<\/td>These require a documented decision from the design team, not a GC-side guess about which version to price.<\/td><\/tr>
          Quantify the audit’s findings, not just narrate them<\/td>A specific count and severity breakdown supports a clearer, better-informed GMP decision than a qualitative summary.<\/td><\/tr>
          Document every resolution in writing before pricing is finalized<\/td>A verbal understanding about which document governs doesn’t protect either party if a dispute arises later.<\/td><\/tr>
          Re-run the audit after any late design revision before GMP<\/td>A late change can introduce a new discrepancy that wasn’t present when the audit was first performed.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
          \u2713 Best Practice<\/strong>
          Present the discrepancy audit findings to the owner’s representative directly as part of the GMP proposal package, rather than only using it internally. Transparency about what was checked and resolved builds trust and reduces the likelihood of a dispute over whether appropriate diligence was performed.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

          Common Mistakes<\/strong><\/strong><\/h2>\n\n\n\n
          Mistake<\/strong><\/strong><\/strong><\/th>Consequence<\/strong><\/strong><\/strong><\/th><\/tr><\/thead>
          Reviewing specs and drawings as separate, unconnected tasks<\/td>This is precisely the gap where discrepancies hide \u2014 each document type gets reviewed on its own terms, and the comparison itself never happens.<\/td><\/tr>
          Treating a spec-only requirement as automatically low-risk<\/td>Some spec-only requirements \u2014 grounding, life-safety testing \u2014 carry real cost and liability even without a drawing reference.<\/td><\/tr>
          Resolving a conflicting instruction internally without design team confirmation<\/td>A GC-side guess about which document governs can be challenged later if it turns out to contradict actual design intent.<\/td><\/tr>
          Running the audit too late in the pre-GMP schedule to allow resolution time<\/td>Discovering a discrepancy without time to resolve it just shifts the same problem to a rushed decision under deadline pressure.<\/td><\/tr>
          Treating the audit as a one-time check with no re-verification after late changes<\/td>A late design revision can introduce a new discrepancy that a single, earlier audit wouldn’t have caught.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
          \u2715 Common Mistake<\/strong>
          “The specs and drawings were both reviewed” is not the same claim as “the specs and drawings were reviewed against each other.” Two thorough, separate reviews can each miss a discrepancy that only becomes visible through direct comparison.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

          Industry Examples<\/strong><\/strong><\/h2>\n\n\n\n

          Commercial Office Tower Core and Shell<\/strong><\/strong><\/h3>\n\n\n\n

          A discrepancy audit found that specification section 07 92 00 described a specific sealant requirement at curtain wall joints with no corresponding drawing detail, prompting a design clarification that added the missing detail before GMP rather than leaving the requirement to be interpreted during construction.<\/p>\n\n\n\n

          Healthcare Surgical Suite Expansion<\/strong><\/strong><\/h3>\n\n\n\n

          An audit identified that medical gas piping testing requirements described in the specifications used a more stringent pressure testing standard than what was referenced in a mechanical drawing note \u2014 a conflict resolved through a design clarification confirming the specification’s stricter standard governed, avoiding a costly retest dispute during commissioning.<\/p>\n\n\n\n

          Industrial Chemical Processing Facility<\/strong><\/strong><\/h3>\n\n\n\n

          A drawing-only discrepancy surfaced when a piping isometric showed a specific alloy requirement with no corresponding specification section defining material certification requirements \u2014 an oversight that, caught before GMP, allowed the specification to be properly completed rather than leaving certification ambiguous during procurement.<\/p>\n\n\n\n

          Data Center Redundant Power Infrastructure<\/strong><\/strong><\/h3>\n\n\n\n

          A discrepancy audit caught that grounding requirements described in specification section 26 05 26 had no corresponding drawing reference anywhere in the electrical set \u2014 a spec-only gap that, left unresolved, could have led to a significant change order once grounding installation began without clear drawing guidance.<\/p>\n\n\n\n

          Residential High-Rise Podium Construction<\/strong><\/strong><\/h3>\n\n\n\n

          An audit found that waterproofing installation requirements in the specifications referenced a manufacturer’s guide with specific application temperature requirements that conflicted with a general note on the architectural drawings describing a different, less restrictive application window \u2014 a conflict resolved before GMP through direct confirmation with the manufacturer and the design team.<\/p>\n\n\n\n

          Institutional University Research Laboratory<\/strong><\/strong><\/h3>\n\n\n\n

          A spec-versus-drawing audit on a laboratory renovation caught that fume hood exhaust performance requirements described in the specifications had no corresponding drawing callout confirming duct sizing met that performance standard, prompting a design clarification before the mechanical package was priced.<\/p>\n\n\n\n

          Infrastructure \u2014 Municipal Water Treatment Upgrade<\/strong><\/strong><\/h3>\n\n\n\n

          A discrepancy audit found that a specification section describing corrosion-resistant coating requirements for buried piping had no corresponding drawing note at several pipe runs shown on the civil drawings, an omission that, caught before GMP, prevented a significant coating scope from being priced incorrectly as standard, uncoated piping.<\/p>\n\n\n\n

          Manufacturing Facility \u2014 Food Processing Expansion<\/strong><\/strong><\/h3>\n\n\n\n

          An audit identified a conflict between specification language requiring stainless steel fasteners throughout a wash-down area and a structural drawing detail specifying standard galvanized hardware at one connection type, a discrepancy resolved through direct confirmation with the structural engineer before pricing locked in the wrong material.<\/p>\n\n\n\n

          FAQs<\/strong><\/strong><\/h2>\n\n\n\n

          Q: What’s the difference between this audit and a general scope gap review?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>A scope gap review asks whether every requirement has a clear trade assignment. A spec-versus-drawing discrepancy audit asks a more fundamental question first: do the specifications and drawings actually agree with each other about what’s required, regardless of who’s assigned to do it.<\/p>\n\n\n\n

          Q: How common are genuine spec-versus-drawing discrepancies on a typical project?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>More common than most teams assume, precisely because specifications and drawings are usually produced and reviewed by different people on different schedules, with no standard step that directly compares the two against each other.<\/p>\n\n\n\n

          Q: Should every discrepancy delay GMP finalization?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>Not necessarily \u2014 low-severity items with minimal cost or schedule impact can sometimes be resolved after GMP through routine documentation. High-severity discrepancies, particularly life-safety or significant cost items, warrant resolution before the price is locked.<\/p>\n\n\n\n

          Q: Who should resolve a conflicting-instruction discrepancy?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>The design team \u2014 the architect or engineer of record \u2014 should confirm which version governs, since this is fundamentally a design intent question, not a preconstruction judgment call.<\/p>\n\n\n\n

          Q: Can this audit be performed on a compressed schedule right before GMP is due?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>It can be attempted, but a compressed schedule leaves little room to actually resolve anything found, which defeats much of the audit’s purpose. Building in adequate lead time is part of doing this well.<\/p>\n\n\n\n

          Q: Does this audit apply the same way to design-build projects?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>The principle applies, but design-build teams have more ability to resolve discrepancies during ongoing design development rather than treating it as a discrete pre-GMP checkpoint, since design and construction documentation evolve together.<\/p>\n\n\n\n

          Q: What happens if a discrepancy is discovered after GMP despite the audit?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>It follows the standard change order process, but a documented pre-GMP audit strengthens the GC’s position by showing reasonable diligence was performed \u2014 the discrepancy either wasn’t discoverable at the time, or falls into a category the audit appropriately classified as lower risk.<\/p>\n\n\n\n

          Q: How does this audit interact with value engineering during preconstruction?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>Value engineering changes can introduce new discrepancies if a substitution or design change isn’t reflected consistently across both the specifications and drawings, making a follow-up audit pass after major VE decisions a reasonable practice.<\/p>\n\n\n\n

          Q: Is this audit useful even on projects with a strong, experienced design team?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>Yes \u2014 discrepancies aren’t primarily a sign of poor design work. They’re a structural byproduct of specifications and drawings being produced through largely separate workflows, which happens even on well-run projects with experienced teams.<\/p>\n\n\n\n

          Q: How should severity be determined for a given discrepancy?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>By weighing potential cost exposure, schedule sensitivity, and life-safety or code-compliance implications together, similarly to how multi-trade overlap severity gets assessed elsewhere in preconstruction scope review \u2014 the goal is directing limited resolution time toward what actually matters most financially and functionally.<\/p>\n\n\n\n

          Q: Can this audit reasonably be performed in-house, or does it require a specialized third party?<\/strong><\/strong><\/h3>\n\n\n\n

          A: <\/strong>It can be performed in-house with the right structured extraction tools and a disciplined process; the key requirement is genuinely comparing the two document types against each other systematically, not which organization happens to run the comparison.<\/p>\n\n\n\n

          Expert Recommendations<\/strong><\/strong><\/h2>\n\n\n\n
            \n
          • Build a dedicated spec-versus-drawing discrepancy audit into the standard pre-GMP workflow, distinct from general scope gap review.<\/li>\n\n\n\n
          • Schedule the audit with enough lead time to actually resolve findings, not just discover them right before the price is due.<\/li>\n\n\n\n
          • Route conflicting-instruction items to the design team for a documented resolution rather than deciding unilaterally which document governs.<\/li>\n\n\n\n
          • Share audit findings transparently with the owner as part of the GMP proposal, building trust in the diligence performed.<\/li>\n\n\n\n
          • Re-run the audit after any significant late design change or value engineering decision affecting the GMP scope.<\/li>\n<\/ul>\n\n\n\n

            Professional Conclusion<\/strong><\/strong><\/h2>\n\n\n\n

            A Guaranteed Maximum Price is only as reliable as the documents it’s built from, and those documents’ internal consistency is an assumption almost nobody directly tests as part of a normal design or review process. Specifications and drawings get produced by different people, reviewed on different schedules, and checked against different standards \u2014 the assumption that they agree with each other is exactly that: an assumption, not a verified fact.<\/p>\n\n\n\n

            A dedicated discrepancy audit tests that assumption directly, and it does so at exactly the point in the project where the finding still matters most \u2014 before the price gets locked and every gap becomes someone’s change order fight instead of a routine correction. Teams that build this specific check into their standard pre-GMP process consistently protect both their own margin and their relationship with the owner, because the number that gets signed actually reflects what the documents, taken together, require.<\/p>\n\n\n\n

            The underlying lesson extends beyond any single GMP decision. Every project carries some baseline level of discrepancy between its specifications and drawings, simply as a function of how those two document types get produced. The question isn’t whether that risk exists \u2014 it does, on nearly every project of meaningful complexity \u2014 but whether it gets found and resolved while it’s still cheap, or discovered later, after the price is fixed, when resolving it costs considerably more and damages trust in the process along the way.<\/p>\n\n\n\n

            <\/p>\n","protected":false},"excerpt":{"rendered":"

            Once a Guaranteed Maximum Price is signed, every gap between what the specs say and what the drawings show becomes someone’s problem to pay for. Here’s how to find those gaps while they’re still cheap to fix. A Guaranteed Maximum Price is exactly what it sounds like: a number both the owner and the general […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-192","post","type-post","status-publish","format-standard","hentry","category-construction-drawings-specifications"],"yoast_head":"\nSpec vs Drawing Discrepancies | iFieldSmart AI<\/title>\n<meta name=\"description\" content=\"Compare specifications and drawings to find spec-only, drawing-only, and conflicting requirements before the GMP is finalized.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Spec vs Drawing Discrepancies | iFieldSmart AI\" \/>\n<meta property=\"og:description\" content=\"Compare specifications and drawings to find spec-only, drawing-only, and conflicting requirements before the GMP is finalized.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/\" \/>\n<meta property=\"og:site_name\" content=\"knowledge-center\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-22T18:37:47+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-22T18:37:48+00:00\" \/>\n<meta name=\"author\" content=\"ifieldsmart.ai\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"ifieldsmart.ai\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"17 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/construction-drawings-specifications\\\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/construction-drawings-specifications\\\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\\\/\"},\"author\":{\"name\":\"ifieldsmart.ai\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/51f5e238c4ca5a90257a3a2a63299411\"},\"headline\":\"Spec vs. Drawing Discrepancies: Finding What’s Missing Before GMP\",\"datePublished\":\"2026-08-22T18:37:47+00:00\",\"dateModified\":\"2026-08-22T18:37:48+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/construction-drawings-specifications\\\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\\\/\"},\"wordCount\":3724,\"commentCount\":0,\"articleSection\":[\"Construction Drawings & Specifications\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/construction-drawings-specifications\\\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/construction-drawings-specifications\\\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\\\/\",\"url\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/construction-drawings-specifications\\\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\\\/\",\"name\":\"Spec vs Drawing Discrepancies | iFieldSmart AI\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#website\"},\"datePublished\":\"2026-08-22T18:37:47+00:00\",\"dateModified\":\"2026-08-22T18:37:48+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/51f5e238c4ca5a90257a3a2a63299411\"},\"description\":\"Compare specifications and drawings to find spec-only, drawing-only, and conflicting requirements before the GMP is finalized.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/construction-drawings-specifications\\\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/construction-drawings-specifications\\\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/construction-drawings-specifications\\\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Spec vs. Drawing Discrepancies: Finding What’s Missing Before GMP\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#website\",\"url\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/\",\"name\":\"knowledge-center\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/51f5e238c4ca5a90257a3a2a63299411\",\"name\":\"ifieldsmart.ai\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g\",\"caption\":\"ifieldsmart.ai\"},\"sameAs\":[\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\"],\"url\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/author\\\/ifieldsmart-ai\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Spec vs Drawing Discrepancies | iFieldSmart AI","description":"Compare specifications and drawings to find spec-only, drawing-only, and conflicting requirements before the GMP is finalized.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/","og_locale":"en_US","og_type":"article","og_title":"Spec vs Drawing Discrepancies | iFieldSmart AI","og_description":"Compare specifications and drawings to find spec-only, drawing-only, and conflicting requirements before the GMP is finalized.","og_url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/","og_site_name":"knowledge-center","article_published_time":"2026-08-22T18:37:47+00:00","article_modified_time":"2026-08-22T18:37:48+00:00","author":"ifieldsmart.ai","twitter_card":"summary_large_image","twitter_misc":{"Written by":"ifieldsmart.ai","Est. reading time":"17 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/#article","isPartOf":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/"},"author":{"name":"ifieldsmart.ai","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#\/schema\/person\/51f5e238c4ca5a90257a3a2a63299411"},"headline":"Spec vs. Drawing Discrepancies: Finding What’s Missing Before GMP","datePublished":"2026-08-22T18:37:47+00:00","dateModified":"2026-08-22T18:37:48+00:00","mainEntityOfPage":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/"},"wordCount":3724,"commentCount":0,"articleSection":["Construction Drawings & Specifications"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/","url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/","name":"Spec vs Drawing Discrepancies | iFieldSmart AI","isPartOf":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#website"},"datePublished":"2026-08-22T18:37:47+00:00","dateModified":"2026-08-22T18:37:48+00:00","author":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#\/schema\/person\/51f5e238c4ca5a90257a3a2a63299411"},"description":"Compare specifications and drawings to find spec-only, drawing-only, and conflicting requirements before the GMP is finalized.","breadcrumb":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/construction-drawings-specifications\/spec-vs-drawing-discrepancies-finding-whats-missing-before-gmp\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/"},{"@type":"ListItem","position":2,"name":"Spec vs. Drawing Discrepancies: Finding What’s Missing Before GMP"}]},{"@type":"WebSite","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#website","url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/","name":"knowledge-center","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#\/schema\/person\/51f5e238c4ca5a90257a3a2a63299411","name":"ifieldsmart.ai","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g","caption":"ifieldsmart.ai"},"sameAs":["https:\/\/www.ifieldsmart.ai\/knowledge-center"],"url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/author\/ifieldsmart-ai\/"}]}},"_links":{"self":[{"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts\/192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/comments?post=192"}],"version-history":[{"count":1,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts\/192\/revisions"}],"predecessor-version":[{"id":193,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts\/192\/revisions\/193"}],"wp:attachment":[{"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/media?parent=192"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/categories?post=192"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/tags?post=192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}