{"id":36,"date":"2026-08-09T12:12:59","date_gmt":"2026-08-09T12:12:59","guid":{"rendered":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/?p=36"},"modified":"2026-08-09T12:34:47","modified_gmt":"2026-08-09T12:34:47","slug":"scope-gap-analysis-checklist","status":"publish","type":"post","link":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/","title":{"rendered":"Scope Gap Analysis Checklist"},"content":{"rendered":"\n

Ask ten preconstruction managers what they check for scope gaps and you will get ten answers, most of them good, none of them written down. The knowledge exists. It lives in the heads of people who have paid for the education, and it walks out the door when they take another job.<\/p>\n\n\n\n

A checklist fixes that. Not a generic one copied off a forum, but a specific list built around where scope actually goes missing on commercial building work: division boundaries, cross-discipline obligations, delegated design, and the twelve or fifteen recurring interfaces that generate a disproportionate share of change orders on every project in every market.<\/p>\n\n\n\n

This article is that list. It is organized by phase so you can use it in sequence, and by division so you can use it as a reference during buyout. Nothing here is theoretical. Every item on it exists because somebody discovered it in the field and paid for the correction.<\/p>\n\n\n\n

Print it, load it into your precon template, or turn it into query filters against your scope register. No matter how you employ it, use it consistently across all projects. Value is created from consistency.<\/p>\n\n\n\n

How to Use This Checklist<\/strong><\/h2>\n\n\n\n

Three rules before you start.<\/p>\n\n\n\n

First, a checklist is a floor, not a ceiling.<\/strong> It catches known patterns. Your organization has never encountered this type of gap, so you would be correct to say it belongs in a systematic analysis rather than a replacement thereof. If a checklist is all you do, you will see gaps that you are already accustomed to and miss the ones unique to this project.<\/p>\n\n\n\n

Second, every item needs a disposition, not a checkmark.<\/strong> “Checked” is not an answer. The answers are: assigned to a named package, assigned to a GC line with dollars, RFI issued, or carried as a priced allowance. A checkbox with a tick next to it six months later tells you nothing about what was decided.<\/p>\n\n\n\n

Third, work it with someone who has installed the work.<\/strong> Office staff read scope. Field staff know who shows up with the ladder. The single highest-yield thirty minutes in this whole exercise is walking the interface section with a superintendent.<\/p>\n\n\n\n

FIELD REALITY<\/strong>
Teams that adopt a checklist usually see results on the first project and then watch compliance decay by the third, because the list starts feeling like paperwork. The fix is not discipline. It is embedding the items as saved queries against your scope register so the check runs itself and the human only adjudicates findings.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Key Definitions Used in This Checklist<\/strong><\/h2>\n\n\n\n

Obligation.<\/strong> One discrete requirement someone must perform, furnish, coordinate, or verify. The unit this checklist operates on.<\/p>\n\n\n\n

Interface.<\/strong> A single obligation that two or more trades touch. Decomposed into four questions: who furnishes, who installs, who coordinates, who verifies. An interface with fewer than four answers is unresolved regardless of how many trades are named.<\/p>\n\n\n\n

Orphan division.<\/strong> A CSI division whose content spreads across many packages such that no single subcontractor feels ownership. Divisions 07, 09, 10, 12, and 31 are the usual suspects on commercial work.<\/p>\n\n\n\n

Delegated design trigger.<\/strong> Language that shifts engineering responsibility to a trade. The trigger creates three separate obligations that are frequently assigned to three different parties, or to none: the engineering itself, the deferred submittal, and the special inspection.<\/p>\n\n\n\n

By-others note.<\/strong> Any obligation whose responsible party is described rather than named. The highest-frequency source of scope disputes in commercial construction.<\/p>\n\n\n\n

Disposition.<\/strong> The recorded outcome for a checklist item. Assigned, GC-held with dollars, RFI issued, or allowance carried. Nothing else counts.<\/p>\n\n\n\n

Objectives of the Checklist<\/strong><\/h2>\n\n\n\n
    \n
  • Catch known recurring gaps without depending on which reviewer is available<\/li>\n\n\n\n
  • Cover division boundaries and interfaces, which is where gaps concentrate<\/li>\n\n\n\n
  • Produce a defensible record of what was examined and what was decided<\/li>\n\n\n\n
  • Compress the time from document receipt to buyout-ready scope documents<\/li>\n\n\n\n
  • Give new precon staff the pattern knowledge that otherwise takes a decade to acquire<\/li>\n\n\n\n
  • Feed closeout findings back so the list gets sharper every project<\/li>\n<\/ul>\n\n\n\n

    Phase 1: Document Intake Checklist<\/strong><\/h2>\n\n\n\n

    Nothing downstream is valid if the baseline is wrong. This section takes an hour and prevents the most expensive category of wasted effort, which is a thorough analysis of superseded documents.<\/p>\n\n\n\n

    Table 1. Document Intake and Baseline Checklist<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th>Why It Matters<\/strong><\/th>Disposition Required<\/strong><\/th><\/tr><\/thead>
    1.1<\/strong><\/td>Sheet index built and reconciled against the drawing list on G-001<\/td>Missing sheets are invisible without a reconciliation<\/td>Confirm complete or request missing sheets<\/td><\/tr>
    1.2<\/strong><\/td>Revision number and date recorded per sheet<\/td>Analyzing a superseded sheet invalidates every finding on it<\/td>Baseline version recorded and frozen<\/td><\/tr>
    1.3<\/strong><\/td>All addenda and bulletins logged, with affected sheets and sections identified<\/td>Addenda reassign scope silently<\/td>Each addendum mapped to affected obligations<\/td><\/tr>
    1.4<\/strong><\/td>Complete project manual received, Divisions 00 through 48<\/td>Spec-only obligations are the ones estimators miss<\/td>Confirm all sections present per table of contents<\/td><\/tr>
    1.5<\/strong><\/td>Division 01 read in full and obligations extracted<\/td>Temporary facilities, cleaning, hoisting, commissioning support<\/td>Division 01 obligations assigned<\/td><\/tr>
    1.6<\/strong><\/td>Prime contract and general conditions reviewed for GC-held scope<\/td>GC obligations get assigned to subs or to nobody<\/td>GC-held items listed separately<\/td><\/tr>
    1.7<\/strong><\/td>OFCI and owner-furnished equipment schedule obtained<\/td>Split-responsibility items have the highest gap rate of any category<\/td>Each OFCI item decomposed into four responsibilities<\/td><\/tr>
    1.8<\/strong><\/td>Work letter or tenant criteria obtained, if core and shell or retail<\/td>Base-building boundary usually lives here, not in the specs<\/td>Boundary matrix built<\/td><\/tr>
    1.9<\/strong><\/td>Geotechnical and environmental reports received<\/td>Division 02 and 31 obligations, unforeseen conditions basis<\/td>Site obligations extracted<\/td><\/tr>
    1.10<\/strong><\/td>Bid package boundaries defined in writing before assignment begins<\/td>Assignment has no destination without defined packages<\/td>Package list published to the team<\/td><\/tr>
    1.11<\/strong><\/td>Referenced details and sheets verified to exist in the set<\/td>Notes referencing nonexistent details are common and always a gap<\/td>Missing references logged as RFIs<\/td><\/tr>
    1.12<\/strong><\/td>Existing conditions documentation obtained, if renovation<\/td>Demolition limits and trade-performed removals overlap<\/td>Demolition limits matrix built<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    WARNING<\/strong>
    Item 1.10 is the one teams skip, and skipping it guarantees internal disagreement later. Most arguments inside a precon team about who owns an obligation are actually arguments about where the package boundary sits, and nobody wrote it down.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Phase 2: Language Screen Checklist<\/strong><\/h2>\n\n\n\n

    This is the fastest high-yield check in the entire process. It ignores subject matter and screens purely on wording. Run it before assignment so the team knows where to slow down.<\/p>\n\n\n\n

    Table 2. Ambiguous Language Screen<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Pattern to Search<\/strong><\/th>Why It Generates Gaps<\/strong><\/th>Typical Location<\/strong><\/th><\/tr><\/thead>
    2.1<\/strong><\/td>“By others” \/ “by other trades”<\/td>Responsible party described, not named<\/td>General notes, MEP plans, equipment schedules<\/td><\/tr>
    2.2<\/strong><\/td>“As required” \/ “as needed”<\/td>Quantity and responsibility both undefined<\/td>Architectural general notes, access provisions<\/td><\/tr>
    2.3<\/strong><\/td>“Coordinate with” used as an assignment<\/td>Coordination is not installation; both get assumed away<\/td>Structural and MEP interface notes<\/td><\/tr>
    2.4<\/strong><\/td>“Field verify” \/ “verify in field”<\/td>Shifts risk without shifting scope<\/td>Renovation drawings, existing condition ties<\/td><\/tr>
    2.5<\/strong><\/td>“By installing contractor”<\/td>Installer undetermined elsewhere in the documents<\/td>Equipment schedules, specialty items<\/td><\/tr>
    2.6<\/strong><\/td>“Provide for” \/ “make provisions for” \/ “allow for”<\/td>Obligation exists, extent does not<\/td>Electrical and mechanical capacity notes<\/td><\/tr>
    2.7<\/strong><\/td>“Typical” \/ “similar” applied to varying conditions<\/td>One detail assumed to cover conditions it does not<\/td>Details, wall types, unit plans<\/td><\/tr>
    2.8<\/strong><\/td>“Engineer” \/ “design-build” \/ “performance” \/ “deferred submittal”<\/td>Three obligations created: engineering, submittal, inspection<\/td>Divisions 05, 09, 13, 21, 23<\/td><\/tr>
    2.9<\/strong><\/td>“Shall be responsible for all work necessary”<\/td>Catch-all that expands or evaporates depending on who reads it<\/td>Division 01, front-end specs<\/td><\/tr>
    2.10<\/strong><\/td>Standards referenced without a stated compliance obligation<\/td>Standard cited, nobody assigned to meet it<\/td>Specification part 2 and 3<\/td><\/tr>
    2.11<\/strong><\/td>“Where shown” with no location shown<\/td>Obligation with no quantity basis<\/td>Firestopping, sealants, access panels<\/td><\/tr>
    2.12<\/strong><\/td>“Match existing”<\/td>Extent, standard, and testing all undefined<\/td>Renovation and adaptive reuse<\/td><\/tr>
    2.13<\/strong><\/td>“Rough-in only” or “final connection by others”<\/td>Boundary between rough-in and connection undefined<\/td>Plumbing and electrical equipment tie-ins<\/td><\/tr>
    2.14<\/strong><\/td>“Furnish only” or “install only” without the counterpart<\/td>Half an obligation is a whole gap<\/td>Equipment, specialties, owner-furnished items<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Note<\/strong>: Division references follow CSI MasterFormat. Examples: Division 01 \u2013 General Requirements, 05 \u2013 Metals, 09 \u2013 Finishes, 13 \u2013 Special Construction, 21 \u2013 Fire Suppression, and 23 \u2013 HVAC. Specification Part 2 covers Products, while Part 3 covers Execution and installation requirements.
    <\/p>\n\n\n\n

    Every hit gets logged, not just the ones that look expensive. Item 2.13 in particular tends to look harmless and reliably costs money on equipment-heavy projects.<\/p>\n\n\n\n

    Phase 3: Cross-Discipline Trace Checklist<\/strong><\/h2>\n\n\n\n

    Obligations that appear on one discipline’s drawings but belong to another discipline’s trade are the highest-frequency gap category on commercial building work. Manual review handles them worst, because estimators read by discipline.<\/p>\n\n\n\n

    Run each pair below as a deliberate pass and review the results as a batch.<\/p>\n\n\n\n

    Table 3. Cross-Discipline Trace Checklist<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Search On<\/strong><\/th>Looking For Obligations Belonging To<\/strong><\/th>Specific Items to Confirm<\/strong><\/th><\/tr><\/thead>
    3.1<\/strong><\/td>Mechanical drawings<\/td>Electrical<\/td>Power to VAVs, fan coils, unit heaters; thermostat and sensor wiring; disconnects; control panel feeds<\/td><\/tr>
    3.2<\/strong><\/td>Mechanical and plumbing drawings<\/td>Concrete<\/td>Housekeeping pads, equipment bases, pits, trench drains, thickened slabs<\/td><\/tr>
    3.3<\/strong><\/td>Architectural drawings<\/td>Electrical and low voltage<\/td>Device and plate locations, floor boxes, access panels, AV backboxes, pathway<\/td><\/tr>
    3.4<\/strong><\/td>Architectural drawings<\/td>Carpentry and blocking<\/td>Blocking at accessories, TV mounts, handrails, casework, grab bars, closet systems<\/td><\/tr>
    3.5<\/strong><\/td>Structural drawings<\/td>Mechanical, plumbing, electrical<\/td>Sleeves, embeds, slab and beam penetration limits, hanger attachment points<\/td><\/tr>
    3.6<\/strong><\/td>Architectural and mechanical drawings<\/td>Firestopping and joint sealants<\/td>Penetrations and joints in rated assemblies, head-of-wall conditions<\/td><\/tr>
    3.7<\/strong><\/td>Electrical drawings<\/td>Drywall and ceilings<\/td>Openings, backing, access provisions, grid coordination at devices<\/td><\/tr>
    3.8<\/strong><\/td>Civil drawings<\/td>Electrical and plumbing<\/td>Site lighting circuits, utility transitions at the five-foot line, irrigation power<\/td><\/tr>
    3.9<\/strong><\/td>Fire protection drawings<\/td>Structural and drywall<\/td>Attachment to structure, head coordination in rated ceilings, escutcheon fit<\/td><\/tr>
    3.10<\/strong><\/td>Landscape drawings<\/td>Plumbing and electrical<\/td>Irrigation supply and backflow, landscape lighting, planter drainage<\/td><\/tr>
    3.11<\/strong><\/td>Equipment schedules, all disciplines<\/td>Multiple<\/td>Furnish versus install split for every scheduled item<\/td><\/tr>
    3.12<\/strong><\/td>Roof plans<\/td>Steel, roofing, mechanical, electrical<\/td>Curbs, supports, anchors, walkway pads, tie-off and anchor points, lightning protection<\/td><\/tr>
    3.13<\/strong><\/td>Interiors and finish drawings<\/td>Multiple<\/td>Substrate preparation obligations that precede the finish<\/td><\/tr>
    3.14<\/strong><\/td>Vertical transportation drawings<\/td>Electrical, drywall, structural<\/td>Hoistway prep, sill angles, pit ladders, machine room power and cooling<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    EXPERT TIP<\/strong>
    Item 3.12 deserves special attention. Roofs concentrate obligations from five or six trades on one plane, the sequencing is unforgiving, and a missed obligation there frequently means opening a completed assembly. If you check nothing else in this table, check the roof.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Phase 4: Division-by-Division Checklist<\/strong><\/h2>\n\n\n\n

    This is the reference section. Work it during buyout, package by package. The items listed are the recurring gaps by division on commercial building work, not a complete scope description.<\/p>\n\n\n\n

    Table 4. Division-by-Division Recurring Gap Checklist, Divisions 02 to 14<\/strong><\/p>\n\n\n\n

    Division<\/strong><\/th>Recurring Gap Items to Confirm Assigned<\/strong><\/th><\/tr><\/thead>
    02 Existing Conditions<\/strong><\/td>Selective demolition limits versus trade-performed removals; abatement coordination; salvage obligations; temporary shoring; protection of adjacent construction<\/td><\/tr>
    03 Concrete<\/strong><\/td>Housekeeping pads and equipment bases; slab openings and infills; embeds furnished by whom; curbs; thickened slabs at equipment; topping slabs; sealer and hardener scope<\/td><\/tr>
    04 Masonry<\/strong><\/td>Lintels furnished by whom; embeds and anchors; cavity flashing termination; through-wall flashing overlap with roofing; cleaning and pointing<\/td><\/tr>
    05 Metals<\/strong><\/td>Supplementary framing for MEP support; embed plates; miscellaneous metals boundary with each trade; delegated connection design; galvanizing and touch-up; stair and rail interface with concrete<\/td><\/tr>
    06 Wood and Plastics<\/strong><\/td>Blocking and backing at all wall-mounted items; plywood backboards for electrical and low voltage; rough carpentry at roof curbs; casework installation versus fabrication; solid surface interface with plumbing<\/td><\/tr>
    07 Thermal and Moisture<\/strong><\/td>Penetration firestopping ownership by trade; roof curb flashing; through-wall flashing overlap with masonry; air and vapor barrier continuity at transitions; joint sealants at dissimilar materials; waterproofing tie-ins at slab edges<\/td><\/tr>
    08 Openings<\/strong><\/td>Hollow metal frame installation versus furnishing; hardware furnished by whom and installed by whom; access panel furnishing and installation; glazing at rated assemblies; door undercutting for airflow<\/td><\/tr>
    09 Finishes<\/strong><\/td>Access panels in ceilings and walls; substrate preparation; painting of exposed conduit, ductwork, and hangers; ceiling grid coordination at devices and sprinklers; delegated engineering for framing over height limits; touch-up after other trades<\/td><\/tr>
    10 Specialties<\/strong><\/td>Blocking and backing; installation versus furnishing for every specialty item; toilet accessory layout; fire extinguisher cabinets in rated walls; signage electrical connection<\/td><\/tr>
    11 Equipment<\/strong><\/td>Furnish versus install split; rough-in extent; final connection responsibility; startup and demonstration; equipment pads; anchorage and seismic restraint<\/td><\/tr>
    12 Furnishings<\/strong><\/td>Casework installation; countertop and plumbing interface; window treatment blocking and power; furniture power and data connection<\/td><\/tr>
    13 Special Construction<\/strong><\/td>Delegated design scope entirely; foundation and support interface; utility connections; controls integration; pre-engineered structure erection boundary<\/td><\/tr>
    14 Conveying Systems<\/strong><\/td>Hoistway rough opening and tolerance; pit and sump; sill angles; machine room power, lighting, cooling, and phone; fire alarm interface; temporary use and protection<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Table 5. Division-by-Division Recurring Gap Checklist, Divisions 21 to 48<\/strong><\/p>\n\n\n\n

    Division<\/strong><\/th>Recurring Gap Items to Confirm Assigned<\/strong><\/th><\/tr><\/thead>
    21 Fire Suppression<\/strong><\/td>Attachment to structure; escutcheon and trim at ceilings; head layout in coordinated ceilings; fire pump power, controls, and monitoring; standpipe interface with structural openings<\/td><\/tr>
    22 Plumbing<\/strong><\/td>Housekeeping pads; sleeves and penetration sealing; trap primers; final connection to owner-furnished fixtures and equipment; roof drain interface with roofing; backflow preventer power and drainage; medical gas certification and third-party verification<\/td><\/tr>
    23 HVAC<\/strong><\/td>Access panels for dampers, valves, and VAVs; seismic and hanger support engineering; power and control wiring boundary; roof curbs; test and balance scope; ductwork insulation split; commissioning support obligations<\/td><\/tr>
    25 Integrated Automation<\/strong><\/td>Network and pathway ownership; device power; integration responsibility across systems; commissioning participation<\/td><\/tr>
    26 Electrical<\/strong><\/td>Backboxes and pathway for low-voltage systems; equipment connections for owner-furnished items; temporary power extent and duration; grounding and bonding beyond code minimum; fire alarm interface with mechanical shutdown; panel schedule reconciliation with actual loads; painting of exposed raceway<\/td><\/tr>
    27 Communications<\/strong><\/td>Pathway versus cabling boundary; backboxes; grounding and bonding of racks; firestopping of communications penetrations; equipment room power and cooling<\/td><\/tr>
    28 Electronic Safety and Security<\/strong><\/td>Door hardware interface; power and pathway; integration with access control and fire alarm; camera backing and blocking; monitoring and programming scope<\/td><\/tr>
    31 Earthwork<\/strong><\/td>Excavation for utilities versus utility trade trenching; bedding and backfill; dewatering; shoring; import and export of soil; erosion control maintenance duration<\/td><\/tr>
    32 Exterior Improvements<\/strong><\/td>Site utility transitions; irrigation supply and power; site lighting bases and conduit; landscape drainage tie-in; pavement patching after utility work<\/td><\/tr>
    33 Utilities<\/strong><\/td>Point of connection responsibility; utility company work versus contractor work; permitting and inspection; service transitions at the building line<\/td><\/tr>
    40 Process Interconnections<\/strong><\/td>Vendor scope boundary; support and attachment; instrumentation and controls; commissioning and validation<\/td><\/tr>
    48 Electrical Power Generation<\/strong><\/td>Generator pad, fuel, exhaust, and cooling interface; transfer switch responsibility; load bank testing; permanent versus temporary connection<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    COMMON MISTAKE<\/strong>
    All the divisions, 07 and 09 have the highest incidence of commercial work related scope disputes. Unlike most divisions, Division 07 and 09 disputes are related to structure. Their content distributes across almost every package, so no single subcontractor sees the whole obligation. Firestopping and access panels alone account for a striking share of first-year change orders.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Phase 5: Interface Decomposition Checklist<\/strong><\/h2>\n\n\n\n

    Naming two trades on an obligation resolves nothing. Every multi-trade obligation needs four answers. This is the checklist that prevents most field disputes, and it is the one most teams do not run.<\/p>\n\n\n\n

    Table 6. Interface Decomposition, Recurring Commercial Interfaces<\/strong><\/p>\n\n\n\n

    Interface Item<\/strong><\/th>Furnish<\/strong><\/th>Install<\/strong><\/th>Coordinate<\/strong><\/th>Verify<\/strong><\/th><\/tr><\/thead>
    Access panels at concealed equipment<\/strong><\/td>Confirm assigned<\/td>Confirm assigned<\/td>Confirm assigned<\/td>Confirm assigned<\/td><\/tr>
    Housekeeping pads at MEP equipment<\/strong><\/td>Concrete typically<\/td>Concrete typically<\/td>Equipment trade provides layout and templates<\/td>GC or inspection<\/td><\/tr>
    Penetration firestopping in rated assemblies<\/strong><\/td>Firestop or penetrating trade<\/td>Confirm per penetration type<\/td>GC typically<\/td>Third-party or AHJ<\/td><\/tr>
    Blocking and backing at wall-mounted items<\/strong><\/td>Carpentry typically<\/td>Carpentry typically<\/td>Installing trade provides locations<\/td>Superintendent<\/td><\/tr>
    Sleeves and slab openings<\/strong><\/td>Confirm per system<\/td>Confirm per system<\/td>Structural and MEP jointly<\/td>GC before pour<\/td><\/tr>
    Equipment supports and seismic restraint<\/strong><\/td>Delegated engineer plus fabricator<\/td>Installing trade<\/td>Structural review<\/td>Special inspection<\/td><\/tr>
    Final connection to owner-furnished equipment<\/strong><\/td>Owner<\/td>Confirm assigned<\/td>GC<\/td>Startup and commissioning<\/td><\/tr>
    Ceiling grid coordination at devices, sprinklers, diffusers<\/strong><\/td>Each trade<\/td>Each trade<\/td>Ceilings or VDC<\/td>Superintendent<\/td><\/tr>
    Roof curbs and equipment supports<\/strong><\/td>Confirm per item<\/td>Confirm per item<\/td>Roofing, mechanical, steel<\/td>Roofing warranty inspection<\/td><\/tr>
    Fire alarm interface with mechanical shutdown<\/strong><\/td>Electrical and mechanical<\/td>Confirm split<\/td>GC<\/td>Commissioning and AHJ<\/td><\/tr>
    Low-voltage pathway and backboxes<\/strong><\/td>Electrical typically<\/td>Electrical typically<\/td>Low-voltage trades provide locations<\/td>Commissioning<\/td><\/tr>
    Trench, bedding, and backfill for site utilities<\/strong><\/td>Confirm per utility<\/td>Confirm per utility<\/td>Earthwork and utility trades<\/td>Inspection before backfill<\/td><\/tr>
    Substrate preparation before finishes<\/strong><\/td>Preceding trade<\/td>Preceding trade<\/td>Finish trade defines requirement<\/td>Finish trade acceptance<\/td><\/tr>
    Temporary power, lighting, and heat<\/strong><\/td>GC typically<\/td>Electrical typically<\/td>GC<\/td>Confirm duration and cost basis<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Fill in every cell. A blank cell is an open finding. “Typically” in this table means a common convention, not a contract term, which is exactly why each one has to be stated in the scope narrative if you are relying on it.<\/p>\n\n\n\n

    Phase 6: Delegated Design Checklist<\/strong><\/h2>\n\n\n\n

    Delegated design creates three obligations from one requirement, and the three routinely land on three different parties or on none. Check every trigger.<\/p>\n\n\n\n

    Table 7. Delegated Design Obligation Checklist<\/strong><\/p>\n\n\n\n

    System<\/strong><\/th>Engineering Assigned To<\/strong><\/th>Deferred Submittal Assigned To<\/strong><\/th>Special Inspection Assigned To<\/strong><\/th>Confirmed<\/strong><\/th><\/tr><\/thead>
    Cold-formed metal framing over height limit<\/td>Cold-formed framing subcontractor’s delegated engineer<\/td>Cold-formed framing subcontractor<\/td>Special Inspector \/ GC<\/td>\u2610<\/td><\/tr>
    Metal stud exterior backup and deflection<\/td>Framing subcontractor’s engineer<\/td>Framing subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Mechanical hangers, supports, seismic restraint<\/td>Mechanical subcontractor’s engineer<\/td>Mechanical subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Plumbing seismic restraint and supports<\/td>Plumbing subcontractor’s engineer<\/td>Plumbing subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Electrical equipment and raceway seismic bracing<\/td>Electrical subcontractor’s engineer<\/td>Electrical subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Fire sprinkler hydraulic layout and calculations<\/td>Fire Protection subcontractor<\/td>Fire Protection subcontractor<\/td>AHJ \/ Special Inspector<\/td>\u2610<\/td><\/tr>
    Precast and connection design<\/td>Precast manufacturer \/ delegated engineer<\/td>Precast subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Steel connection design where delegated<\/td>Structural steel connection engineer<\/td>Steel fabricator<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Curtain wall and storefront engineering<\/td>Curtain wall manufacturer<\/td>Curtain wall subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Canopies, awnings, and trellises<\/td>Specialty fabricator’s engineer<\/td>Specialty subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Handrail and guardrail load design<\/td>Metal fabricator’s engineer<\/td>Metal fabricator<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Elevator and hoisting equipment anchorage<\/td>Elevator manufacturer<\/td>Elevator subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Pre-engineered metal building components<\/td>PEMB manufacturer<\/td>PEMB supplier \/ erector<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Ceiling suspension in seismic zones<\/td>Ceiling subcontractor’s engineer<\/td>Ceiling subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr>
    Equipment anchorage for owner-furnished items<\/td>Equipment supplier’s engineer (or delegated engineer)<\/td>Installing subcontractor<\/td>Special Inspector<\/td>\u2610<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    IMPORTANT<\/strong>
    The special inspection column is where money hides. A delegated design obligation with engineering and submittal assigned but inspection unassigned is not resolved, because inspection is a cost, a schedule constraint, and frequently a condition of the certificate of occupancy.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Phase 7: Pre-Award Checklist<\/strong><\/h2>\n\n\n\n

    Run this per bid package, before the subcontract is executed. It is the last point at which you have competitive leverage.<\/p>\n\n\n\n

    Table 8. Pre-Award Scope Verification Checklist<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th>Disposition<\/strong><\/th><\/tr><\/thead>
    7.1<\/strong><\/td>Every obligation assigned to this package appears in the trade scope register, including obligations sourced from other disciplines’ drawings<\/td>Register issued to bidder<\/td><\/tr>
    7.2<\/strong><\/td>Exclusions from all bidders on this package compared side by side<\/td>Exclusion reconciliation sheet complete<\/td><\/tr>
    7.3<\/strong><\/td>Any item excluded by all bidders is assigned elsewhere or GC-held with dollars<\/td>No unclaimed exclusions remain<\/td><\/tr>
    7.4<\/strong><\/td>Interface schedule attached with all four responsibilities filled<\/td>No blank cells<\/td><\/tr>
    7.5<\/strong><\/td>Level C conventional assignments stated explicitly in the scope narrative<\/td>Narrative language reviewed<\/td><\/tr>
    7.6<\/strong><\/td>Delegated design engineering, submittal, and inspection assigned for this trade<\/td>All three confirmed<\/td><\/tr>
    7.7<\/strong><\/td>Allowances identified and quantified, with what is excluded stated in writing<\/td>Allowance schedule attached<\/td><\/tr>
    7.8<\/strong><\/td>Unit prices established for likely field-discovered work<\/td>Unit price schedule attached<\/td><\/tr>
    7.9<\/strong><\/td>Scope review call held with the bidder, interface schedule walked line by line<\/td>Call documented, assumptions logged<\/td><\/tr>
    7.10<\/strong><\/td>Addenda incorporated and acknowledged by bidder in writing<\/td>Acknowledgment received<\/td><\/tr>
    7.11<\/strong><\/td>Long-lead items identified with procurement responsibility assigned<\/td>Procurement log updated<\/td><\/tr>
    7.12<\/strong><\/td>Commissioning and closeout obligations for this trade stated<\/td>Closeout requirements attached<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    BEST PRACTICE<\/strong>
    Item 7.9 takes half an hour and returns more than anything else on this page. Walking the interface schedule with the bidder surfaces the assumptions inside his number while you can still do something about them. After award, the same conversation is a negotiation.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Phase 8: Handoff and Closeout Checklist<\/strong><\/h2>\n\n\n\n

    Table 9. Handoff and Retrospective Checklist<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th>Timing<\/strong><\/th><\/tr><\/thead>
    8.1<\/strong><\/td>Gap log transferred live to the project team with open items, allowances, and RFI threads<\/td>At award<\/td><\/tr>
    8.2<\/strong><\/td>Residual exposure figure stated and accepted by the project executive<\/td>At award<\/td><\/tr>
    8.3<\/strong><\/td>Open items reviewed at the first three OAC meetings<\/td>First 90 days<\/td><\/tr>
    8.4<\/strong><\/td>Interface schedule reviewed with each trade before mobilization<\/td>Per trade<\/td><\/tr>
    8.5<\/strong><\/td>Register reversioned on each addendum or bulletin<\/td>Ongoing<\/td><\/tr>
    8.6<\/strong><\/td>Field-discovered gaps logged with the reason they were not caught<\/td>Ongoing<\/td><\/tr>
    8.7<\/strong><\/td>Logged gaps marked materialized, avoided, or resolved without cost<\/td>At closeout<\/td><\/tr>
    8.8<\/strong><\/td>New patterns added to this checklist<\/td>At closeout<\/td><\/tr>
    8.9<\/strong><\/td>Scope-driven change orders categorized by gap type and reported<\/td>At closeout<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Item 8.6 is the one that makes the checklist better. A gap discovered in the field is a diagnostic. Either the pattern was not on the list, or it was and somebody skipped it. Both answers are actionable and only one of them is about discipline.<\/p>\n\n\n\n

    Importance: What the Checklist Is Actually Preventing<\/strong><\/h2>\n\n\n\n

    Rework on commercial building work generally runs in the range of four to six percent of contract value, and a meaningful share traces to scope and coordination failures rather than defective workmanship. Whatever figure your own history supports, the arithmetic is unforgiving. On a sixty million dollar project, one point of contract value is six hundred thousand dollars.<\/p>\n\n\n\n

    The subtler cost is behavioral. Ambiguous scope does not distribute risk evenly. It selects for the subcontractors most willing to price narrowly and recover later. Every project bought out on vague documents quietly filters your subcontractor pool toward the ones who read the documents adversarially, and away from the ones who price honestly and lose.<\/p>\n\n\n\n

    A checklist changes that dynamic because it changes what the sub receives. A specific, sourced, internally consistent scope document is priced tighter, because the bidder is not pricing uncertainty.<\/p>\n\n\n\n

    Stakeholders and Their Sections<\/strong><\/h2>\n\n\n\n
    Role<\/strong><\/th>Owns<\/strong><\/th>Contributes To<\/strong><\/th>Reviews<\/strong><\/th><\/tr><\/thead>
    Preconstruction manager<\/strong><\/td>Phases 1, 2, 3, and overall log<\/td>4, 6<\/td>5, 7<\/td><\/tr>
    Estimator<\/strong><\/td>Phase 7 exclusion reconciliation<\/td>3, 4<\/td>2<\/td><\/tr>
    Project manager<\/strong><\/td>Phase 8 handoff, dispositions<\/td>5, 7<\/td>All<\/td><\/tr>
    Superintendent<\/strong><\/td>Phase 5 interface decomposition<\/td>4, 8<\/td>3<\/td><\/tr>
    VDC or BIM manager<\/strong><\/td>Coordination-heavy zone identification<\/td>3, 5<\/td>6<\/td><\/tr>
    Contracts<\/strong><\/td>Scope narrative language<\/td>7<\/td>5<\/td><\/tr>
    Project executive<\/strong><\/td>Residual exposure acceptance<\/td><\/td>All<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Note:<\/strong> Phase numbers refer to the Scope Gap Analysis Checklist workflow: 1 = Document Intake, 2 = Language Screen, 3 = Cross-Discipline Trace, 4 = Division-by-Division Review, 5 = Interface Decomposition, 6 = Delegated Design, 7 = Pre-Award Scope Verification, and 8 = Handoff & Continuous Improvement. All indicates the role reviews every phase of the workflow.<\/p>\n\n\n\n

    Table 10. Who Runs Which Section<\/strong><\/p>\n\n\n\n

    The superintendent owning Phase 5 is deliberate. Interface decomposition is a question about how work gets built and sequenced, and the office consistently answers it wrong when it answers it alone.<\/p>\n\n\n\n

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

    You can run this checklist on paper. Most teams start there. What limits the paper version is not rigor but reach: Phases 3 and 4 require searching a full document set for specific obligation patterns, and searching four hundred sheets by hand is not something anyone does completely.<\/p>\n\n\n\n

    Table 11. Checklist Execution by Method<\/strong><\/p>\n\n\n\n

    Phase<\/strong><\/th>Manual Effort<\/strong><\/th>With a Searchable Scope Register<\/strong><\/th>With AI Extraction<\/strong><\/th><\/tr><\/thead>
    1, Intake<\/strong><\/td>1 to 2 hours<\/td>1 hour<\/td>30 minutes, index generated<\/td><\/tr>
    2, Language screen<\/strong><\/td>4 to 8 hours, partial coverage<\/td>1 hour, full text search<\/td>Minutes, every pattern, full set<\/td><\/tr>
    3, Cross-discipline trace<\/strong><\/td>2 to 5 days, heavily sampled<\/td>4 to 8 hours<\/td>Under an hour per pair, complete<\/td><\/tr>
    4, Division review<\/strong><\/td>2 to 3 days<\/td>1 day<\/td>Hours, coverage reportable<\/td><\/tr>
    5, Interface decomposition<\/strong><\/td>1 day, judgment-heavy<\/td>1 day<\/td>1 day, candidates pre-identified<\/td><\/tr>
    6, Delegated design<\/strong><\/td>4 hours<\/td>2 hours<\/td>Minutes to identify, hours to assign<\/td><\/tr>
    7, Pre-award<\/strong><\/td>2 to 4 hours per package<\/td>1 to 2 hours per package<\/td>Under an hour, register exports per trade<\/td><\/tr>
    8, Handoff and closeout<\/strong><\/td>4 hours<\/td>2 hours<\/td>2 hours<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Phases 5 and 8 barely move. That is the honest picture. Those are judgment and communication tasks, and no tool does them for you. What tooling changes is Phases 2, 3, and 4, which are search tasks performed at a volume humans cannot complete.<\/p>\n\n\n\n

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

    Scope extraction is the constraint. Every phase of this checklist depends on knowing what obligations exist in the documents, and building that register by hand across a full commercial set inside a bid window is not achievable.<\/p>\n\n\n\n

    Preconstruction AI platforms tackle that directly. For example, iFieldSmart AI analyzes an entire set of construction drawings and notes; captures construction drawings and notes; suggests a relevant trade and CSI division for each item; and registers each note and construction drawing in a searchable format. Users can click on an entry in the constructed register and the AI will display the construction drawing and note. This capability combined with other capabilities of the platform will make Phase 7 defensible, because subcontractors will have the source for every assignment given to them.<\/p>\n\n\n\n

    Table 12. Checklist Phases Mapped to AI Capability<\/strong><\/p>\n\n\n\n

    Checklist Phase<\/strong><\/th>AI Capability Applied<\/strong><\/th>What Still Requires You<\/strong><\/th><\/tr><\/thead>
    1, Intake<\/strong><\/td>Sheet indexing, revision differencing, missing reference detection<\/td>Confirming the set is what the owner issued<\/td><\/tr>
    2, Language screen<\/strong><\/td>Pattern matching across every note and spec paragraph<\/td>Deciding RFI versus reassignment versus allowance<\/td><\/tr>
    3, Cross-discipline trace<\/strong><\/td>Query by assigned trade across all source disciplines<\/td>Judging whether the item belongs in the package<\/td><\/tr>
    4, Division review<\/strong><\/td>CSI mapping and coverage reporting per division<\/td>Matching divisions to your package boundaries<\/td><\/tr>
    5, Interface decomposition<\/strong><\/td>Flagging multi-trade obligations as candidates<\/td>All four responsibility answers<\/td><\/tr>
    6, Delegated design<\/strong><\/td>Trigger detection across specifications<\/td>Assigning engineering, submittal, and inspection<\/td><\/tr>
    7, Pre-award<\/strong><\/td>Trade-specific register and scope narrative generation<\/td>Commercial judgment and the bidder conversation<\/td><\/tr>
    8, Closeout<\/strong><\/td>Categorizing scope change orders against logged gaps<\/td>Deciding what goes into the pattern library<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    LESSONS LEARNED<\/strong>
    The teams that get the most from automated extraction are the ones who had a checklist first. Tooling multiplies whatever discipline already exists. Applied to an undisciplined process it produces a very large register that nobody adjudicates, which is worse than a short list somebody actually worked.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Implementation<\/strong><\/h2>\n\n\n\n
      \n
    • Adopt Phases 1, 2, and 5 immediately. They require no tooling, they take under two days on a mid-size project, and they cover intake integrity, the highest-yield screen, and the interface decomposition that prevents field disputes.<\/li>\n\n\n\n
    • Customize Phase 4 to your market. Trade boundaries vary by region and by office. Go through Tables 4 and 5 with your two most experienced estimators and mark which items your packages normally carry. That editing session is where the checklist becomes yours.<\/li>\n\n\n\n
    • Add Phase 3 on the next project. Even sampled, cross-discipline trace pays for itself. Start with pairs 3.1, 3.2, 3.4, 3.6, and 3.12, which cover the majority of recurring findings.<\/li>\n\n\n\n
    • Instrument Phase 2 as saved searches. Whatever platform holds your documents, build the fourteen language patterns as stored queries so the check runs without anyone remembering to run it.<\/li>\n\n\n\n
    • Make Phase 7 a gate. No subcontract executes without the pre-award checklist complete. This is a policy decision, not a process improvement, and it needs executive backing.<\/li>\n\n\n\n
    • Run Phase 8 on your next two closeouts, even retroactively. Categorizing past scope change orders against this list tells you which sections matter most in your specific market.<\/li>\n\n\n\n
    • Review and revise annually. Items that never produce findings come off. Field-discovered gaps go on.<\/li>\n<\/ul>\n\n\n\n

      Best Practices<\/strong><\/h2>\n\n\n\n

      Table 13. Checklist Discipline Best Practices<\/strong><\/p>\n\n\n\n

      Practice<\/strong><\/th>Why<\/strong><\/th><\/tr><\/thead>
      Require a disposition, never a checkmark<\/strong><\/td>A tick records that someone looked, not what was decided<\/td><\/tr>
      Run the language screen before assignment<\/strong><\/td>Tells the team where to slow down while there is still time<\/td><\/tr>
      Work Phase 5 with a superintendent present<\/strong><\/td>Interfaces are a construction question, not a documents question<\/td><\/tr>
      Customize the division tables to your market<\/strong><\/td>Trade convention varies; a generic list produces false findings<\/td><\/tr>
      Instrument the searchable phases<\/strong><\/td>Compliance decays; saved queries do not<\/td><\/tr>
      Reconcile exclusions across all bidders per package<\/strong><\/td>An item excluded by everyone belongs to nobody<\/td><\/tr>
      State conventional assignments in the scope narrative<\/strong><\/td>Your convention is not in the contract documents<\/td><\/tr>
      Keep the log live after award<\/strong><\/td>Open items do not close themselves<\/td><\/tr>
      Add field-discovered gaps to the list at closeout<\/strong><\/td>The only mechanism by which the checklist improves<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      Common Mistakes<\/strong><\/h2>\n\n\n\n

      Table 14. Common Checklist Failures<\/strong><\/p>\n\n\n\n

      Mistake<\/strong><\/th>Consequence<\/strong><\/th>Fix<\/strong><\/th><\/tr><\/thead>
      Treating the checklist as the whole analysis<\/strong><\/td>Novel gap types missed entirely<\/td>Pair the checklist with systematic extraction<\/td><\/tr>
      Checkmarks instead of dispositions<\/strong><\/td>No record of decisions; log useless in a dispute<\/td>Four permitted dispositions, enforced<\/td><\/tr>
      Using a generic list without customization<\/strong><\/td>False findings erode trust; real gaps still missed<\/td>Edit Tables 4 and 5 with senior staff<\/td><\/tr>
      Skipping Phase 1 to save time<\/strong><\/td>Findings against superseded documents<\/td>Freeze the baseline first, always<\/td><\/tr>
      Running Phase 3 by discipline instead of by trade<\/strong><\/td>Cross-discipline obligations dropped<\/td>Query by assigned trade across all sources<\/td><\/tr>
      Interfaces named but cells left blank<\/strong><\/td>Both subs assume the other has it<\/td>Blank cell equals open finding<\/td><\/tr>
      Delegated design engineering assigned, inspection forgotten<\/strong><\/td>Inspection cost and schedule surprise near occupancy<\/td>All three columns required<\/td><\/tr>
      Pre-award checklist run after award<\/strong><\/td>Findings become negotiations<\/td>Make Phase 7 a gate<\/td><\/tr>
      Never revising the list<\/strong><\/td>Same gaps recur; checklist loses credibility<\/td>Annual review, driven by closeout data<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

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

      New construction of corporate campus office building of 280,000 square feet<\/strong>. Phase 2 flagged eleven “provide for” notes on the electrical drawings covering future tenant capacity. None had a defined extent. The team converted all eleven into a defined allowance with stated panel capacity and conduit stub counts. Without that screen, the ambiguity would have been priced narrowly by the bidder and expanded by the tenant.<\/p>\n\n\n\n

      Regional hospital expansion, 190 beds.<\/strong> Phase 6 caught the one that matters in healthcare. Mechanical seismic restraint engineering was assigned to the mechanical sub, the deferred submittal was assumed to be part of it, and special inspection was assigned to nobody. Special inspection on that scope is a condition of occupancy in the jurisdiction. Caught in precon it was a line item. Caught during inspection it would have been a schedule event.<\/p>\n\n\n\n

      Colocation data <\/strong>center<\/strong>, 24 MW.<\/strong> Phase 3, pair 3.2, produced 34 housekeeping pad obligations across mechanical, electrical, and structural sheets with three different implied owners. Resolution was one interface schedule row and one clarification to the concrete package. On equipment-dense projects that single pair is often the highest-value check on the list.<\/p>\n\n\n\n

      University residence hall, 480 beds.<\/strong> Phase 3, pair 3.4, produced 71 blocking obligations across four room types. The framing package had priced detailed blocking only. Presenting the findings in a room-type blocking schedule gave the framer a firm number instead of an estimation and the final number came in under the allowed estimate.<\/p>\n\n\n\n

      900,000 square feet distribution warehouse.<\/strong> Phase 4 on Division 31 found the recurring earthwork gap: trenching, bedding, and backfill for site utilities sat between the earthwork package and each utility trade. Resolution was to write trenching and backfill into earthwork with a joint hold point before backfill, and pipe and conduit into the respective trades.<\/p>\n\n\n\n

      Historic building conversion to hotel, 140 keys.<\/strong> Phase 1, item 1.12 drove everything. Without a demolition limits matrix, selective demolition and trade-performed removals overlapped in every area of the building. The matrix took a day to build and eliminated an entire category of dispute on a project type where that category usually dominates.<\/p>\n\n\n\n

      Precision manufacturing facility.<\/strong> Phase 5 on final connections to owner-furnished process equipment. Twelve pieces of equipment, each needing rough-in, final connection, startup, and validation. The furnish column was clear because the owner was furnishing. Every other column was blank. The most referred-to page in the buyout documents came from filling in the grid.<\/p>\n\n\n\n

      F<\/strong>AQ\u2019s<\/strong><\/h2>\n\n\n\n

      How many steps does the checklist have?<\/strong><\/p>\n\n\n\n

      On a mid-size commercial project with a searchable scope register, budget four to six working days spread across the bid period. Manually, on a large set, closer to two weeks with partial coverage on Phases 3 and 4. Phase 1 is an hour. Phase 2 is under a day if your documents are text-searchable. Phases 5 through 8 are judgment work and do not compress much regardless of tooling.<\/p>\n\n\n\n

      Which phases should we adopt first if we can only do some?<\/strong><\/h3>\n\n\n\n

      Phases 1, 2, and 5. Intake integrity, the language screen, and interface decomposition. Together they take under two days, require no software, and cover the failure modes with the worst cost-to-effort ratio. Phase 7 comes next, because it is where leverage exists.<\/p>\n\n\n\n

      Is this checklist appropriate for projects under ten million dollars?<\/strong><\/h3>\n\n\n\n

      Yes, and arguably it matters more, because small projects carry less margin to absorb surprises. Scale the effort rather than the rigor. On a small job, run Phase 1, the highest-frequency items from Phase 2, the roof and blocking pairs from Phase 3, and the full Phase 5 interface grid. That is perhaps a day and a half.<\/p>\n\n\n\n

      How do we adapt this for renovation work?<\/strong><\/h3>\n\n\n\n

      Add existing conditions throughout. Item 1.12 becomes mandatory and expands into a demolition limits matrix by area and system. Item 2.12, “match existing,” becomes one of the highest-frequency findings on the project. Division 02 in Table 4 moves from a reference item to the primary focus. Also add an unforeseen conditions methodology stating how discovered conditions get priced, because on renovation that document prevents more disputes than the rest of the checklist combined.<\/p>\n\n\n\n

      Should subcontractors see this checklist?<\/strong><\/h3>\n\n\n\n

      Share the interface schedule and the scope narrative, always. Share the relevant portions of Phases 3 and 4 for their trade, because it makes their bid more accurate. Keep the language screen findings and the residual exposure internal, since those reflect your risk position and your allowance strategy.<\/p>\n\n\n\n

      How is this different from a bid package checklist?<\/strong><\/h3>\n\n\n\n

      A bid package checklist confirms your package documents are complete: drawings issued, addenda included, schedule attached, insurance requirements stated. This checklist confirms the scope inside those packages is completely and unambiguously assigned. Both are necessary. Many teams have the first and assume it covers the second.<\/p>\n\n\n\n

      What if we find more items than we can resolve before the bid is due?<\/strong><\/h3>\n\n\n\n

      That is the normal outcome, not a failure. Rank by cost exposure multiplied by the likelihood the item stays unresolved, resolve the top of the list, and carry the rest as named, quantified allowances. A specific allowance tied to a specific open question is a management tool. Blanket contingency is not.<\/p>\n\n\n\n

      Who should hold the master copy?<\/strong><\/h3>\n\n\n\n

      Preconstruction, with a single named owner accountable for the annual revision. Distributed copies drift within one project cycle. If the list lives in a document management system with version control and the phases exist as saved queries, drift stops being a problem.<\/p>\n\n\n\n

      Does this replace a coordination or clash detection process?<\/strong><\/h3>\n\n\n\n

      No. Clash detection answers whether two systems physically conflict. This checklist answers who is contractually responsible. A model can show you a duct hitting a beam and tell you nothing about whether the supplementary steel that resolves it is in anyone’s package. Run both.<\/p>\n\n\n\n

      How do we prove the checklist is working?<\/strong><\/h3>\n\n\n\n

      Two metrics. Early-construction RFI volume, which drops fast and visibly, usually within the first sixty days of mobilization. And scope-driven change orders as a percentage of contract value, categorized by gap type, which needs two to four completed projects to trend. Both require a baseline from past projects, so pull that data before you start.<\/p>\n\n\n\n

      What is the single most commonly missed item across all commercial projects?<\/strong><\/h3>\n\n\n\n

      Penetration firestopping ownership in rated assemblies. It appears in Divisions 07, 21, 22, 23, 26, and 27, no single subcontractor sees the whole obligation, the drawings usually show a schedule without locations, and the inspection gates other work. If you check one item on this entire list, check that one.<\/p>\n\n\n\n

      Can we run this checklist against a model instead of drawings?<\/strong><\/h3>\n\n\n\n

      Partially. A federated model supports Phase 3 well and Phase 5 reasonably. It does not support Phase 2, Phase 4, or Phase 6 at all, because language patterns, division coverage, and delegated design triggers live in specification and note text rather than in geometry. Roughly half the checklist requires the documents.<\/p>\n\n\n\n

      Expert Recommendations<\/strong><\/h2>\n\n\n\n

      Customize the division tables before your next bid, not during it. An hour with your two most experienced estimators marking which items your packages carry converts a generic reference into your organization’s actual scope convention.<\/p>\n\n\n\n

      Make the pre-award checklist a gate with executive backing. Process improvements that depend on goodwill get skipped when the bid is due in three days. Gates do not.<\/p>\n\n\n\n

      Put the language screen into your document platform as saved searches this week. It is the cheapest action available and it removes the item most vulnerable to compliance decay.<\/p>\n\n\n\n

      Bring a superintendent to the interface decomposition session and let him lead it. The office fills that grid wrong when the office fills it alone.<\/p>\n\n\n\n

      Give the residual exposure figure to your project executive at award, in writing. It reads as command of the project rather than as exposure of weakness, and it changes how contingency conversations go for the rest of the job.<\/p>\n\n\n\n

      Log every field-discovered gap with the reason it was missed. That single field is what separates a checklist that improves from one that ossifies.<\/p>\n\n\n\n

      Review the whole list once a year against your own change order data. Items producing no findings come off. New patterns go on. A checklist nobody has revised in three years has stopped being a tool and become a ritual.<\/p>\n\n\n\n

      Using This <\/strong>From<\/strong> Here<\/strong><\/h2>\n\n\n\n

      A checklist is a modest thing. It does not require new software, new headcount, or a change management initiative. It requires deciding in advance what you are going to look at, and then looking at it the same way every time.<\/p>\n\n\n\n

      What makes it powerful in commercial construction is that scope gaps are not random. They cluster in the same divisions, the same interfaces, and the same fourteen phrases, project after project, market after market. That regularity is exactly what a checklist is for.<\/p>\n\n\n\n

      Take this one, edit it to match how your office divides work, run Phases 1, 2, and 5 on your next bid, and add whatever you find in the field to the bottom of it. Within three projects it will be better than anything you could have bought.<\/p>\n\n\n\n

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

      Ask ten preconstruction managers what they check for scope gaps and you will get ten answers, most of them good, none of them written down. The knowledge exists. It lives in the heads of people who have paid for the education, and it walks out the door when they take another job. A checklist fixes […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-36","post","type-post","status-publish","format-standard","hentry","category-scope-gap-analysis"],"yoast_head":"\nScope Gap Analysis Checklist | iFieldSmart AI<\/title>\n<meta name=\"description\" content=\"Download and use a practical scope gap analysis checklist to identify missing scope, improve coordination, and reduce construction project risks.\" \/>\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\/scope-gap-analysis\/scope-gap-analysis-checklist\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scope Gap Analysis Checklist | iFieldSmart AI\" \/>\n<meta property=\"og:description\" content=\"Download and use a practical scope gap analysis checklist to identify missing scope, improve coordination, and reduce construction project risks.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/\" \/>\n<meta property=\"og:site_name\" content=\"knowledge-center\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-09T12:12:59+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-09T12:34:47+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=\"29 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\\\/scope-gap-analysis\\\/scope-gap-analysis-checklist\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/scope-gap-analysis\\\/scope-gap-analysis-checklist\\\/\"},\"author\":{\"name\":\"ifieldsmart.ai\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/51f5e238c4ca5a90257a3a2a63299411\"},\"headline\":\"Scope Gap Analysis Checklist\",\"datePublished\":\"2026-08-09T12:12:59+00:00\",\"dateModified\":\"2026-08-09T12:34:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/scope-gap-analysis\\\/scope-gap-analysis-checklist\\\/\"},\"wordCount\":6080,\"commentCount\":0,\"articleSection\":[\"Scope Gap Analysis\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/scope-gap-analysis\\\/scope-gap-analysis-checklist\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/scope-gap-analysis\\\/scope-gap-analysis-checklist\\\/\",\"url\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/scope-gap-analysis\\\/scope-gap-analysis-checklist\\\/\",\"name\":\"Scope Gap Analysis Checklist | iFieldSmart AI\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#website\"},\"datePublished\":\"2026-08-09T12:12:59+00:00\",\"dateModified\":\"2026-08-09T12:34:47+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/51f5e238c4ca5a90257a3a2a63299411\"},\"description\":\"Download and use a practical scope gap analysis checklist to identify missing scope, improve coordination, and reduce construction project risks.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/scope-gap-analysis\\\/scope-gap-analysis-checklist\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/scope-gap-analysis\\\/scope-gap-analysis-checklist\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/scope-gap-analysis\\\/scope-gap-analysis-checklist\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scope Gap Analysis Checklist\"}]},{\"@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":"Scope Gap Analysis Checklist | iFieldSmart AI","description":"Download and use a practical scope gap analysis checklist to identify missing scope, improve coordination, and reduce construction project risks.","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\/scope-gap-analysis\/scope-gap-analysis-checklist\/","og_locale":"en_US","og_type":"article","og_title":"Scope Gap Analysis Checklist | iFieldSmart AI","og_description":"Download and use a practical scope gap analysis checklist to identify missing scope, improve coordination, and reduce construction project risks.","og_url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/","og_site_name":"knowledge-center","article_published_time":"2026-08-09T12:12:59+00:00","article_modified_time":"2026-08-09T12:34:47+00:00","author":"ifieldsmart.ai","twitter_card":"summary_large_image","twitter_misc":{"Written by":"ifieldsmart.ai","Est. reading time":"29 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/#article","isPartOf":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/"},"author":{"name":"ifieldsmart.ai","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#\/schema\/person\/51f5e238c4ca5a90257a3a2a63299411"},"headline":"Scope Gap Analysis Checklist","datePublished":"2026-08-09T12:12:59+00:00","dateModified":"2026-08-09T12:34:47+00:00","mainEntityOfPage":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/"},"wordCount":6080,"commentCount":0,"articleSection":["Scope Gap Analysis"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/","url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/","name":"Scope Gap Analysis Checklist | iFieldSmart AI","isPartOf":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#website"},"datePublished":"2026-08-09T12:12:59+00:00","dateModified":"2026-08-09T12:34:47+00:00","author":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#\/schema\/person\/51f5e238c4ca5a90257a3a2a63299411"},"description":"Download and use a practical scope gap analysis checklist to identify missing scope, improve coordination, and reduce construction project risks.","breadcrumb":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/scope-gap-analysis\/scope-gap-analysis-checklist\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/"},{"@type":"ListItem","position":2,"name":"Scope Gap Analysis Checklist"}]},{"@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\/36","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=36"}],"version-history":[{"count":5,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts\/36\/revisions"}],"predecessor-version":[{"id":41,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts\/36\/revisions\/41"}],"wp:attachment":[{"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/media?parent=36"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/categories?post=36"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/tags?post=36"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}