A scope of work is the document that decides who owes what. Not the drawings, not the specifications, not the schedule. When a subcontractor and a general contractor disagree in month seven about whether something was included, the argument gets settled by reading the scope of work attached to the subcontract, usually called Exhibit B.
Which makes it strange how casually most of them get written. I have read hundreds of trade scope exhibits over the years and a large share of them are three pages of boilerplate, a bullet list lifted from the specification table of contents, and a closing sentence saying the subcontractor shall provide all work necessary for a complete and operational installation. That last sentence is doing an enormous amount of load-bearing work and it will not hold.
A well-built scope of work has a definite anatomy. Sixteen components, each solving a specific problem, each traceable to a class of dispute that occurs when it is absent. Some are legal, most are technical, and the technical ones are where general contractors lose money.
This article walks the anatomy. What each component is, what it prevents, how to write it, and what it looks like when it is done badly. If you are building a scope of work template for your office, or auditing the one you inherited, this is the parts list.
What a Scope of Work Actually Is
A construction scope of work is the contractual document that defines the work a specific party must perform, the work that party is not performing, the interfaces where its work meets others, and the standards, deliverables, and conditions attached to that performance.
Notice the four elements. Work included. Work excluded. Interfaces. Conditions. A document that only does the first is not a scope of work, it is a wish list, and it is the most common form of the document in commercial construction.
Two more distinctions are worth fixing early, because the terms get used loosely.
Table 1. Scope of Work Compared With Related Documents
| Document | What It Establishes | Governs | Typical Length | Who Writes It |
|---|---|---|---|---|
| Scope of work (Exhibit B) | What this party performs and does not perform | The subcontract relationship | 6 to 25 pages per trade | Contractor, preconstruction and contracts |
| Specification section | Products, standards, execution quality | All parties performing that work | 8 to 40 pages per section | Design team |
| Drawings | Geometry, location, quantity, configuration | All parties | Full set | Design team |
| Statement of work (owner side) | Services and deliverables the contractor owes the owner | The prime contract | 10 to 60 pages | Owner or program manager |
| Work breakdown structure | Decomposition of work for planning and cost control | Internal management | Variable | Contractor, project controls |
| Bid package | The invitation and its attachments, of which the scope of work is one | The bidding process | Package | Contractor, preconstruction |
A specification tells a subcontractor how to install a fire damper correctly. A scope of work tells him whether he is installing it, whether he furnishes the access panel that serves it, who cuts the opening, and who is present for the inspection. Those are different questions and specifications are not written to answer them.
Core Terminology
Inclusion. An affirmative statement that specified work is within this party’s scope.
Exclusion. An affirmative statement that specified work is outside this party’s scope. Exclusions are not the absence of an inclusion. Silence is not exclusion, and treating it as such is how disputes start.
Interface. A single work item that two or more parties touch, decomposed into who furnishes, who installs, who coordinates, and who verifies.
Incorporation by reference. Language pulling other documents into the subcontract without reproducing them. “Work shall conform to Specification Section 23 05 29” incorporates that section. Done carelessly, incorporation pulls in obligations nobody priced.
Order of precedence. The stated rule for which document governs when two conflict. Without it, conflicts get resolved by negotiation or by a judge.
Delegated design. Scope where the documents define performance and expect the trade to engineer a solution. Creates three obligations: the engineering, the deferred submittal, and the special inspection.
Allowance. A stated sum carried in the subcontract price for work not yet fully defined, with the basis and exclusions stated.
Unit price. A pre-agreed rate for work of uncertain quantity, so that quantity variation is priced rather than negotiated.
| KEY TAKEAWAY The single most consequential idea in scope drafting is that silence is not exclusion. If your scope of work does not say a subcontractor is excluded from something, and a reasonable reading of the incorporated documents suggests the work belongs to his trade, he owes it. That cuts both ways, which is why both the inclusion and the exclusion sections have to be deliberate. |
Objectives of a Well-Built Scope of Work
- Eliminate reasonable disagreement. Not all disagreement. A subcontractor determined to argue will argue. The target is removing every reading a reasonable person could defend.
- Price accurately. A specific scope gets a tighter number, because the bidder is not pricing uncertainty. Vague scope is always priced defensively, and you pay for the defense.
- Establish interfaces before the field discovers them. Interfaces are where sequence-critical disputes happen, and they happen at the worst moment.
- Make change orders provable. A change is a departure from a defined baseline. Without a defined baseline you cannot demonstrate a change, and neither can the subcontractor, which produces a negotiation instead of an entitlement determination.
- Survive personnel turnover. The estimator who bought the job may not be running it. The scope of work is what transfers the deal.
- Support the prime contract. Every obligation the owner imposed on you must be assigned to somebody. Scope of work documents in aggregate should account for the whole prime contract.
Why the Components Matter More Than the Length
There is a persistent belief that a longer scope of work is a stronger one. It is not. A twenty-page exhibit built from three pages of substance and seventeen pages of boilerplate is weaker than a nine-page exhibit that covers all sixteen components. Boilerplate creates internal contradictions a bidder can use to their advantage.
The failure mode is specific and worth naming. Most scope of work templates in circulation are strong on components 1, 2, 3, and 16, which are the legal ones: identification, incorporation, precedence, and changes. They are weak or silent on components 7 through 12, which are the technical ones: interfaces, deliverables, quantities, sequencing, coordination, and verification. Legal completeness with technical emptiness is the standard commercial construction scope exhibit, and it is why so many disputes are technical arguments conducted with legal documents that have nothing useful to say about them.
| INDUSTRY INSIGHT Ask to read a competitor’s Exhibit B sometime, or your own from five years ago. Count how many of the sixteen components below are actually present. In my experience the honest answer for most contractors is seven or eight, and the missing ones are always the same missing ones. |
Component 1: Identification and Parties
What it establishes. Who is bound, to what project, under which prime contract, for which trade package.
Why it exists. Sounds trivial. It is not, on projects with multiple phases, multiple buildings, or an owner entity that differs from the entity named in the notice to proceed. A scope of work that identifies “the Project” without defining its physical limits creates an argument about whether Building C was included.
How to write it. Name the project, the physical limits by building, level, and area, the phase if phased, the prime contract by date, the trade package by number and title, and the CSI divisions and sections the package addresses. State whether the package covers the whole project or defined areas.
Component 2: Contract Documents and Incorporation
What it establishes. Exactly which documents are part of this subcontract.
Why it exists. This is where the most expensive drafting errors live. Two opposite failures both occur constantly. The first is under-incorporation: the exhibit references the drawings but not the specifications, and the subcontractor later declines an obligation that appears only in the spec. The second, more common, is over-incorporation by blanket reference: “all contract documents” pulls the entire project manual into every trade’s subcontract, including Division 01 obligations the trade never priced and would not have priced.
How to write it. List documents specifically, with dates and revision numbers. Drawings by sheet number or by discipline series with the issue date. Specifications by section number. Addenda by number. Then state what is incorporated for information versus what is incorporated as an obligation. A subcontractor should have the structural drawings for information and be obligated to the structural drawings only where his work attaches to structure.
Table 2. Incorporation Approaches and Their Consequences
| Approach | Language Pattern | Effect | Risk |
|---|---|---|---|
| Blanket incorporation | “All contract documents apply” | Everything is arguably in scope | Subcontractor prices defensively or disputes later; Division 01 obligations unpriced |
| Specific enumeration | Named sheets, sections, addenda with dates | Clear obligation boundary | Omission of a document leaves a genuine gap |
| Enumeration plus catch-all | Named documents, then “and all other documents to the extent applicable” | Appears safe, is ambiguous | The catch-all defeats the enumeration; worst of both |
| Two-tier | Named obligation documents plus named information documents | Obligation boundary clear, context provided | Requires drafting discipline per package |
The two-tier approach is the one that holds up. It takes an extra thirty minutes per package and it removes the entire category of argument about whether a document was in or out.
Component 3: Order of Precedence
What it establishes. Which document wins when two conflict.
Why it exists. Conflicts are inevitable on a commercial set. A detail shows a two-hour rated assembly, the schedule shows one hour, and the specification references a third standard. Without a precedence clause, resolution is a negotiation in which the party with more time and more lawyers does better.
How to write it. State a hierarchy. A conventional one runs: modifications and addenda, then the agreement, then the general and supplementary conditions, then the specifications, then the drawings, with large-scale details governing over small-scale and schedules governing over plans. Then add the sentence that actually does the work: where a conflict is discovered, the subcontractor shall notify the contractor before proceeding and shall be entitled to no additional compensation for work performed after discovery without notice.
That second sentence converts precedence from a dispute-resolution rule into a behavior rule. It gets conflicts surfaced during construction instead of after.
Component 4: Scope Summary
What it establishes. A plain-language statement of what this trade is doing, in a paragraph.
Why it exists. Every reader of the document, including a field superintendent two years later and a claims consultant three years after that, needs an orienting statement before the detail. It also functions as an internal check: if you cannot describe the package in a paragraph, the package boundary is probably wrong.
How to write it. Three to six sentences. What system, what building areas, what the trade furnishes and installs at a high level, and the notable exclusions. Do not put obligations here that appear nowhere else. The summary should be a summary.
Component 5: Detailed Work Description by Division and System
What it establishes. The substantive inclusions, organized so a reader can find things.
Why it exists. This is the body of the document and where most of the technical content lives.
How to write it. Organize by CSI division and then by system, not by drawing sheet and not by construction sequence. Divisions are how specifications are organized and how estimators think, and CSI organization is what makes the document searchable and comparable across trades. Within each division, group by system or assembly.
Write inclusions as complete obligations. “Furnish and install ductwork” is not an obligation. “Furnish and install all supply, return, exhaust, and outside air ductwork, including hangers, supports, seismic restraints, dampers, turning vanes, flexible connections, and access provisions, from the air handling unit discharge to the terminal device connection, throughout Levels 1 through 6” is an obligation. It states verbs, components, limits, and areas.
Table 3. Anatomy of a Well-Written Inclusion
| Element | Function | Weak Example | Strong Example |
|---|---|---|---|
| Verb set | States which of furnish, install, coordinate, verify, test apply | “Provide” | “Furnish, install, connect, and test” |
| Object with components | Names the assembly and its parts | “Ductwork” | “Ductwork including hangers, supports, restraints, dampers, and access provisions” |
| Physical limits | Where the obligation starts and stops | Silent | “From AHU discharge to terminal device connection” |
| Area limits | Which parts of the project | Silent | “Levels 1 through 6, Building A only” |
| Standard reference | The governing quality basis | Silent | “Per Section 23 31 13 and SMACNA” |
| Quantity basis | Where quantity comes from | Silent | “As shown on M-201 through M-260” |
The word “provide” deserves special mention. In most standard general conditions it is defined to mean furnish and install. Many subcontractors read it as furnish only. If your general conditions define it, cite the definition in the scope of work. If they do not, stop using the word and write both verbs.
| FIELD REALITY The single highest-value editing pass on any scope of work is to search for every instance of “provide” and replace it with the actual verb set. It takes twenty minutes and it removes one of the two most common sources of scope argument in commercial construction. The other is silence about interfaces. |
Component 6: Exclusions
What it establishes. Work specifically not in this party’s scope.
Why it exists. Because silence is not exclusion, and because an exclusion in your document is a directive while an exclusion in the subcontractor’s proposal is a negotiating position. Whoever writes the exclusions controls the boundary.
How to write it. Two categories, stated separately.
The first is scope excluded and assigned elsewhere. “Concrete housekeeping pads are excluded from this scope and are included in the Concrete package.” Note that this tells the subcontractor both that he is not doing it and that somebody is, which prevents him from carrying it defensively.
The second is scope excluded and not assigned, meaning the contractor holds it. Say so explicitly. A subcontractor reading an unqualified exclusion may reasonably assume the work will be done by someone before he needs it, and sequence around that assumption.
What not to do: adopt the subcontractor’s exclusion list wholesale into the executed subcontract. This happens constantly during buyout, usually as an attachment titled “Subcontractor’s Clarifications,” and it silently transfers the boundary to the party with the most to gain. Every proposed exclusion should be either accepted and written into your language, rejected in writing, or resolved by reassignment.
Table 4. Exclusion Drafting Patterns
| Pattern | Example | Effect |
|---|---|---|
| Excluded and assigned | “Access panels excluded; included in Division 09 package” | Clean; subcontractor does not price it and knows who does |
| Excluded and contractor-held | “Temporary heat excluded; performed by Contractor” | Clean; sequencing expectation set |
| Excluded, unassigned | “Access panels excluded” | Incomplete; work may belong to nobody |
| Excluded by silence | No mention of access panels anywhere | Dangerous; obligation may attach by incorporation |
| Excluded by adopting subcontractor’s list | “See Subcontractor’s Clarification Letter dated…” | Boundary set by the counterparty |
| Excluded with condition | “Rock excavation excluded above 50 CY; unit price per Attachment C” | Strong; quantity risk priced rather than argued |
Component 7: Interface and Responsibility Matrix
What it establishes. For every work item involving more than one party, who furnishes, who installs, who coordinates, and who verifies.
Why it exists. This is the component most often missing and the one that prevents the most field disputes. Naming two trades on an item resolves nothing. Both know they are involved. Neither knows what they are doing.
How to write it. A table, one row per interface item, four columns plus a location or system column. Attach it to every affected package, identically. The same matrix in both the mechanical and drywall exhibits, with both parties seeing both sides, is worth more than any amount of narrative.
Table 5. Interface Matrix, Representative Rows
| Interface Item | Furnish | Install | Coordinate | Verify |
|---|---|---|---|---|
| Access panel at fire damper | Mechanical | Drywall | Mechanical provides locations | Superintendent, then AHJ |
| Housekeeping pad at pump | Concrete | Concrete | Plumbing provides layout and anchor template | Contractor before pour |
| Sleeve through rated wall | Penetrating trade | Penetrating trade | Contractor | Firestop subcontractor and AHJ |
| Firestopping at penetration | Firestop subcontractor | Firestop subcontractor | Contractor | Third-party inspector |
| Final connection to owner-furnished equipment | Owner | Named trade per system | Contractor | Commissioning agent |
| Ceiling grid at sprinkler head | Each own component | Each own component | Ceilings subcontractor | Superintendent |
| Roof curb for rooftop unit | Mechanical | Roofing installs flashing | Contractor | Roofing warranty inspector |
| Low-voltage backbox and pathway | Electrical | Electrical | Low-voltage trade provides locations | Commissioning agent |
| Blocking at wall-mounted equipment | Carpentry | Carpentry | Mounting trade provides locations | Superintendent |
| Seismic restraint at duct | Delegated engineer and fabricator | Mechanical | Structural engineer reviews | Special inspector |
Fill every cell. A blank cell in an executed subcontract is an unpriced obligation belonging to whoever loses the argument.
Component 8: Deliverables and Submittals
What it establishes. The documents, samples, and data the subcontractor owes, and when.
Why it exists. Submittal obligations are real cost and real schedule, and they are routinely underpriced because they are treated as administrative. Delegated design engineering, coordination drawings, and as-built documentation are the three that carry meaningful money.
How to write it. A table with the deliverable, the quantity or format, the due date expressed relative to a schedule milestone rather than a calendar date, and the review duration.
Table 6. Deliverables Matrix, Representative Structure
| Deliverable | Format | Due | Review Duration | Notes |
|---|---|---|---|---|
| Product data and shop drawings | Electronic, per Section 01 33 00 | Within 21 days of subcontract execution | 10 working days | Sequential resubmittals do not extend the schedule |
| Delegated design calculations and drawings, sealed | Sealed PDF plus one wet-signed set | Within 35 days of execution | 15 working days | Engineer licensed in project jurisdiction |
| Coordination model contribution | Native plus IFC, per BIM execution plan | Per coordination schedule | Rolling | Participation in weekly coordination required |
| Samples and mockups | Physical, quantity per specification | Before fabrication release | 10 working days | Mockup remains until approved |
| Certified test reports | Electronic | Within 10 days of test | 5 working days | Third-party where specified |
| Operation and maintenance data | Electronic plus two bound sets | 30 days before substantial completion | 15 working days | Condition of final payment |
| Training and demonstration | Recorded sessions plus attendance record | Before substantial completion | Acceptance by owner | Owner personnel scheduling by Contractor |
| As-built documentation | Marked-up set plus model where required | 15 days before substantial completion | 10 working days | Condition of retention release |
| Warranty documentation | Executed warranties | At substantial completion | 5 working days | Manufacturer plus workmanship |
| Attic stock and spare parts | Delivered and inventoried | Before substantial completion | Receipt acknowledged | Storage location by Contractor |
Two drafting notes. Express due dates relative to milestones, because calendar dates go stale the first time the schedule moves. And state the review duration, because a subcontractor cannot be responsible for a delay caused by a review that took six weeks against a stated ten days.
Component 9: Quality Standards and Acceptance Criteria
What it establishes. The basis on which work is accepted or rejected.
Why it exists. A standard referenced without an acceptance criterion is not enforceable in any practical sense. “Install per manufacturer’s recommendations” is a common clause and it is nearly meaningless, because manufacturers publish recommendations at several levels of stringency and the subcontractor will pick one.
How to write it. Reference the governing specification section. State the tolerance where the specification does not. State who inspects, at what stage, and what constitutes acceptance. Where a mockup governs, say the mockup governs and state what happens to it.
Component 10: Quantities, Allowances, and Unit Prices
What it establishes. How quantity risk is allocated.
Why it exists. Some quantities are unknown at buyout and no amount of drafting makes them known. Rock excavation, unforeseen conditions on renovation work, firestop penetration counts, and blocking quantities are the recurring examples. Pretending they are known produces either an inflated bid or a claim.
How to write it. Three mechanisms, used deliberately.
A defined quantity states the number and the basis. “Firestopping at 340 penetrations as scheduled on A-901.” Variation is a change.
An allowance states a sum, what it covers, what it excludes, and how it is reconciled. An allowance without stated exclusions is a fund the subcontractor will spend on whatever he likes.
A unit price states a rate for work of uncertain quantity, with the measurement method and any threshold. Unit prices are the strongest of the three because they price the risk instead of allocating it, and they remove the argument entirely.
Table 7. Quantity Risk Mechanisms
| Mechanism | Use When | Must State | Common Drafting Failure |
|---|---|---|---|
| Defined quantity | Quantity is knowable from documents | Number, source document, that variation is a change | Quantity stated with no source |
| Allowance | Scope known, extent not | Sum, inclusions, exclusions, reconciliation method, markup treatment | No exclusions stated |
| Unit price | Quantity uncertain and measurable | Rate, unit of measure, measurement method, threshold, validity period | Unit of measure undefined or measurement method absent |
| Contingency held by contractor | Scope may not occur at all | That it is not subcontractor’s to draw | Confused with allowance |
| Cost-plus carve-out | Scope undefinable at buyout | Labor rates, markup, approval procedure, documentation required | No approval procedure |
| EXPERT TIP Establish unit prices at buyout for the four or five items most likely to vary in quantity on your project type. It costs nothing while you have competitive leverage, and it converts what would be a field negotiation into an arithmetic exercise. On renovation work this single practice is worth more than any other scope drafting improvement. |
Component 11: Schedule and Sequencing Obligations
What it establishes. What the subcontractor owes in terms of time, manpower, and sequence.
Why it exists. Because a scope of work that is silent on schedule creates a subcontractor who is contractually free to perform his work in any order, at any pace, with any crew size, so long as he finishes. Delay claims and acceleration disputes both trace back here.
How to write it. Reference the project schedule by name and date and state that the subcontractor’s work is bound to it. State the milestones this trade must meet. State the manpower and shift obligations. State the obligation to sequence around other trades, to work in areas as released rather than continuously, and to remobilize as required at no additional cost within a stated number of mobilizations. That last item is worth naming explicitly, because multiple mobilization is a real cost and the argument about who owns it is common on phased and occupied projects.
Component 12: Coordination and Site Obligations
What it establishes. The non-installation obligations that come with being on the project.
Why it exists. These are the obligations subcontractors most often argue were not in their number, largely because they usually were not written down.
How to write it. Enumerate. Attendance at coordination meetings and required frequency. Participation in model coordination and the deliverable that entails. Layout and survey responsibility. Hoisting and material handling, including who provides the crane, when, and for how long. Cutting and patching. Protection of adjacent work. Housekeeping, including the standard and frequency. Temporary facilities usage. Waste separation. Site access, parking, and laydown limits. Safety program obligations. Substance testing and badging where required.
Every one of these items has a cost. Whichever ones you do not state, you own.
Component 13: Safety and Regulatory Obligations
What it establishes. The safety program, permitting, and inspection obligations attaching to this trade.
How to write it. Reference the project safety plan. State the trade-specific requirements: fall protection, hot work permitting, confined space, lockout and tagout, silica and lead procedures, crane and rigging plans. Assign permit responsibility item by item, because permits split unpredictably between trades and the contractor. Assign special inspection coordination, and state who pays for reinspection when the first one fails.
Component 14: Delegated Design Obligations
What it establishes. Which engineering the subcontractor owes, and the two obligations that travel with it.
Why it exists. A delegated design requirement reads as one thing and is three: the engineering, the deferred submittal, and the special inspection. Trades price the first, absorb the second, and are unaware of the third. Special inspection is frequently a condition of occupancy, which makes it the one that hurts.
How to write it. A table, one row per delegated system, with three columns. Name the engineer’s licensing jurisdiction. State who submits the deferred submittal package to the authority having jurisdiction and who pays the associated fee. State who engages and pays the special inspector, and whether reinspection after a failure is at the subcontractor’s cost.
Table 8. Delegated Design Obligation Table, Representative Rows
| System | Engineering | Deferred Submittal | Special Inspection | Reinspection Cost |
|---|---|---|---|---|
| Cold-formed framing over height limit | Subcontractor’s licensed engineer | Subcontractor submits, Contractor pays fee | Contractor engages | Subcontractor if failure is workmanship |
| Mechanical seismic restraint and supports | Subcontractor’s licensed engineer | Subcontractor submits and pays fee | Contractor engages | Subcontractor if failure is workmanship |
| Fire sprinkler hydraulic design | Subcontractor | Subcontractor submits and pays fee | AHJ plus special inspector | Subcontractor |
| Curtain wall and storefront | Manufacturer’s engineer | Subcontractor submits | Structural observation by design team | Subcontractor |
| Handrails and guardrails | Fabricator’s engineer | Subcontractor submits | Load testing where specified | Subcontractor |
| Anchorage of owner-furnished equipment | To be assigned; frequently unassigned | To be assigned | To be assigned | To be assigned |
That last row is deliberately written as unresolved, because on most projects it is. Anchorage engineering for owner-furnished equipment sits in a gap between the owner who bought the equipment, the vendor who will not engineer the attachment, and the trades who did not buy it. Decide it during scope drafting or discover it during inspection.
Component 15: Closeout, Commissioning, and Warranty
What it establishes. What the subcontractor owes at the end.
Why it exists. Closeout obligations are chronically underpriced because they occur after the work looks finished and after the subcontractor’s crew has largely demobilized. Commissioning participation in particular is real labor over a long period, and trades bid it as a nominal number when they bid it at all.
How to write it. State the commissioning role by phase, referencing the commissioning plan: pre-functional checklists, functional performance testing, seasonal testing, and the labor obligation for each. State punch list procedure and response duration. State the training obligation with duration and audience. State warranty duration, start date, and whether it starts at substantial completion or at first beneficial use, which matters on phased projects. State the emergency response obligation during the warranty period, including response time.
Component 16: Changes, Claims, and Notice
What it establishes. The procedure for departing from this scope.
How to write it. State the notice period for a claimed change and that it is a condition precedent, if your general conditions support that. State the pricing basis and the markup limits. State the documentation required. State what constitutes authorization to proceed and, importantly, that verbal direction is not authorization. State the schedule impact procedure separately from the cost procedure, because a change with no cost impact can still have a time impact and trades routinely waive one while claiming the other.
Stakeholders and Ownership of Components
Table 9. Component Ownership RACI
| Component Group | Preconstruction | Estimating | Contracts | Project Manager | Superintendent | Project Executive |
|---|---|---|---|---|---|---|
| 1 to 3, Identification, incorporation, precedence | C | I | A | R | I | C |
| 4 to 5, Summary and detailed inclusions | A | R | C | R | C | I |
| 6, Exclusions | A | R | C | R | C | C |
| 7, Interface matrix | R | C | I | R | A | I |
| 8, Deliverables | C | I | R | A | I | I |
| 9, Quality and acceptance | C | C | C | A | R | I |
| 10, Quantities, allowances, unit prices | R | A | C | R | C | C |
| 11 to 12, Schedule, sequencing, coordination | C | I | C | R | A | I |
| 13, Safety and regulatory | I | I | C | R | A | I |
| 14, Delegated design | R | C | C | A | I | I |
| 15, Closeout and commissioning | C | I | C | A | R | I |
| 16, Changes and notice | I | I | A | R | I | C |
R responsible, A accountable, C consulted, I informed.
The superintendent being accountable for the interface matrix is deliberate and it is the assignment most offices get wrong. Interfaces are questions about how work sequences and who physically shows up. The office answers them incorrectly when the office answers them alone.
Required Source Documentation
Table 10. Documents Needed to Draft a Complete Scope of Work
| Source Document | Components It Feeds | Consequence If Missing |
|---|---|---|
| Prime contract and general conditions | 2, 3, 11, 16 | Flow-down obligations unassigned; precedence undefined |
| Division 01 General Requirements | 8, 11, 12, 13, 15 | Coordination, closeout, and temporary obligations unpriced |
| Full drawing set with revision index | 5, 7, 10 | Inclusions without quantity basis |
| Complete project manual | 5, 9, 14 | Delegated design and acceptance criteria missing |
| Addenda and bulletins | 2, 5 | Scope described that no longer exists |
| Bid package definitions | 1, 5, 6 | Boundaries undefined; overlaps between exhibits |
| Interface matrix from scope analysis | 7 | The highest-value component absent |
| Project schedule | 11 | No time obligation |
| Commissioning plan | 15 | Commissioning labor unpriced |
| Safety plan | 13 | Trade-specific safety obligations unstated |
| OFCI equipment schedule | 7, 14 | Split responsibility and anchorage unassigned |
| Work letter or tenant criteria, if applicable | 1, 5, 6 | Base building boundary undefined |
| Subcontractor proposals and exclusions | 6 | Boundary ceded to the counterparty |
Technology Integration
Scope of work drafting is document assembly from distributed sources, which is exactly the kind of task where tooling helps and where most contractors are still working manually.
Table 11. Drafting Approach Comparison
| Approach | Time per Package | Consistency Across Packages | Traceability to Source | Typical Component Coverage |
|---|---|---|---|---|
| Word template, manual editing | 4 to 12 hours | Poor; drift within one project | None | 7 to 9 of 16 |
| Template plus clause library | 3 to 6 hours | Good on boilerplate, poor on technical content | Weak | 9 to 11 of 16 |
| Contract lifecycle management platform | 2 to 5 hours | Strong on legal components | Version history only | 9 to 12 of 16 |
| Structured scope register plus generation | 1 to 3 hours | Strong | Per obligation | 13 to 16 of 16 |
| AI scope extraction and document generation | Under 1 hour to draft | Strong | Per obligation, linked to sheet | 13 to 16 of 16 |
The interesting column is the last one. Component coverage is what determines whether the document works, and it improves with tooling not because software writes better clauses but because the technical components require pulling obligations from every sheet in the set. That is a volume problem, and volume problems are the ones that get solved.
AI-Assisted Opportunities
The hard part of a scope of work is not the boilerplate. It is Component 5 and Component 7: knowing every obligation in the documents that belongs to this trade, including the ones described on other disciplines’ drawings, and knowing which of them involve more than one party.
That is where preconstruction AI has changed the work. Platforms including iFieldSmart AI extract every note from every sheet, assign trade responsibility and CSI division per item, keep a link from each item back to its exact location on the drawing, and generate trade-specific scope documentation in Word directly from the assigned register. A user selects a trade, and the export contains that trade’s obligations from every drawing in the set, not only from that discipline’s sheets.
Table 12. AI Use Case Matrix for Scope of Work Drafting
| Component | AI Contribution | Human Contribution |
|---|---|---|
| 2, Incorporation | Sheet and section enumeration with revision dates | Deciding obligation versus information tier |
| 5, Detailed inclusions | Trade obligations pulled from all disciplines, CSI organized | Verb sets, physical limits, editorial judgment |
| 6, Exclusions | Flags obligations assigned elsewhere that this trade might assume | Deciding what to exclude and how to say it |
| 7, Interface matrix | Identifies multi-trade obligations as candidates | All four responsibility answers |
| 8, Deliverables | Extracts submittal requirements from specifications | Milestone-relative dates and review durations |
| 10, Quantities | Counts scheduled items for defined quantity statements | Allowance and unit price strategy |
| 14, Delegated design | Detects delegated design triggers across the project manual | Assigning engineering, submittal, inspection, reinspection |
| 15, Closeout | Extracts commissioning and closeout obligations per trade | Labor estimate and acceptance terms |
| All | Generates the draft document in editable Word format | Legal review and commercial negotiation |
| IMPORTANT Generation is the least valuable part of this. Producing a Word document was never the bottleneck. Knowing what belongs in it was. A team that adopts automated generation without fixing component coverage will produce badly incomplete scope exhibits faster than before. |
Implementation
- Audit your current template against the sixteen components. Mark each present, partial, or absent. Most offices find seven to nine present, and the absences cluster in components 7, 8, 10, 12, and 14.
- Build Component 7 first. The interface matrix is the highest-value addition and it does not require rewriting anything. Draft it once for your most common project type, with a superintendent, and attach it to every affected package.
- Fix the verb problem. Search for “provide” throughout your template and replace with explicit verb sets. Add a defined-terms section if you do not have one.
- Convert incorporation to two-tier. Named obligation documents, named information documents, no catch-all.
- Add Component 10 mechanisms. Pick the four or five quantity-variable items on your project type and establish unit prices at buyout as standard practice.
- Write Component 12 as an enumerated list. Everything you do not state, you own.
- Reconcile across packages before issuing. Every exhibit in a project should be checked against its neighbors for overlaps and for obligations excluded by all.
- Close the loop. When a scope dispute occurs, identify which component would have prevented it and amend the template.
Table 13. Implementation Roadmap
| Phase | Duration | Activities | Deliverable |
|---|---|---|---|
| Audit | Weeks 1 to 2 | Score current template against sixteen components; pull last five scope disputes and map to components | Component gap report |
| Build core | Weeks 3 to 6 | Draft interface matrix, deliverables matrix, delegated design table; fix verbs and incorporation | Template version 2 |
| Pilot | Weeks 7 to 12 | Apply to one live project, all packages; log bidder questions by component | Pilot exhibits plus question log |
| Reconcile | Weeks 10 to 14 | Cross-package overlap and universal-exclusion check as a standing gate | Reconciliation procedure |
| Standardize | Weeks 14 to 20 | Roll to all projects; train precon, contracts, and field staff | Standard template plus training record |
| Improve | Ongoing | Amend template from dispute retrospectives | Annual template revision |
Best Practices
Table 14. Scope of Work Drafting Best Practices
| Practice | Why It Works |
|---|---|
| Organize inclusions by CSI division, never by drawing sheet | Matches how specifications and estimators are organized; makes packages comparable |
| Write explicit verb sets instead of “provide” | Removes the most common single source of scope argument |
| State physical and area limits on every inclusion | Converts an obligation into a bounded obligation |
| Use two-tier incorporation | Clear obligation boundary with context preserved |
| Exclude affirmatively and say who has it instead | Prevents defensive pricing and sequencing assumptions |
| Attach the identical interface matrix to every affected package | Both parties read both sides of the same row |
| Express deliverable dates relative to milestones | Survives schedule revision |
| State review durations alongside submittal durations | Prevents delay claims founded on your own review time |
| Establish unit prices at buyout while leverage exists | Prices quantity risk instead of arguing it |
| Enumerate coordination and site obligations | Unstated obligations default to the contractor |
| Reconcile exhibits across packages before issuing | Catches overlaps and universal exclusions |
| Never adopt a subcontractor’s exclusion list by reference | The boundary belongs to whoever drafts it |
Common Mistakes
Table 15. Common Scope of Work Drafting Failures
| Mistake | What Goes Wrong | Correction |
|---|---|---|
| “Complete and operational” as the substantive scope | Everything and nothing is included; unenforceable in practice | Enumerate obligations; keep the catch-all as a backstop only |
| Blanket incorporation of all contract documents | Division 01 obligations unpriced; defensive bidding | Two-tier incorporation with named documents |
| “Provide” used throughout | Furnish-only readings on install obligations | Explicit verb sets |
| No exclusions section | Silence read as inclusion by you, as exclusion by them | Affirmative exclusions with assignment stated |
| Interfaces named but not decomposed | Both parties assume the other performs | Four responsibility columns, no blank cells |
| Inclusions organized by drawing sheet | Cross-discipline obligations dropped; not comparable | CSI division organization |
| Deliverables treated as administrative | Delegated engineering and commissioning labor unpriced | Deliverables matrix with dates and durations |
| Allowance with no stated exclusions | Fund spent on unrelated work | State inclusions, exclusions, and reconciliation |
| Silent on schedule and mobilizations | Remobilization and acceleration disputes | State milestones, manpower, and mobilization count |
| Delegated design engineering assigned, inspection ignored | Occupancy-gating surprise near completion | Three columns per delegated system |
| Subcontractor’s clarification letter attached and incorporated | Boundary ceded to the counterparty | Accept, reject, or reassign each item in your own words |
| Exhibits not reconciled across packages | Overlaps paid twice; universal exclusions belong to nobody | Cross-package reconciliation gate before issue |
How the Components Play Out on Real Projects
Class A office core and shell, 340,000 square feet. Component 1 carried the project. The base building and tenant improvement boundary was defined in a work letter that contradicted the drawings on ceiling grid extent and base-building sprinkler head count. Writing the physical and scope limits explicitly into the identification and inclusion sections of each affected exhibit, and cross-referencing the work letter as an obligation document, settled three arguments before they happened. On core and shell work that boundary is the most consequential line in the project.
Acute care hospital, 240 beds. Component 14 and Component 15 together. Medical gas required a certified installer, third-party verification, and certification documentation, and the equipment schedule listed outlets as owner-furnished. The exhibit named a party for piping, outlets, alarms, certification, third-party verification, and the reinspection cost if verification failed. On healthcare work these obligations are licensing conditions, not cost items, and an unassigned verification obligation delays occupancy rather than payment.
Hyperscale data center, 60 MW. Component 10 drove the value. Equipment count on a project of that density makes housekeeping pads, firestop penetrations, and equipment anchorage genuinely quantity-variable at buyout. The team established unit prices for pads by size class, penetrations by rating and diameter, and anchorage by equipment weight class. Field variation became arithmetic. Commissioning participation under Component 15 was written with stated labor hours per phase, because commissioning on data center work is a substantial and long-duration obligation that trades habitually underbid.
Food grade manufacturing plant. Component 7 and Component 10. Process equipment vendor documents were seven weeks behind buyout, which was planned rather than a failure. The exhibits carried a named allowance for equipment support, hygienic panel interfaces, and process piping attachment, with exclusions stated and a reconciliation method defined. When the vendor package landed the reconciliation was a budget draw rather than a claim.
University laboratory building, 11 floors. Component 5 and Component 7 on casework. Lab casework, fume hood connections, exhaust, controls, and utility rough-in split across five packages. Rather than describing each package narratively, the team built one interface matrix covering every casework and hood connection point and attached it identically to all five exhibits. Eleven interface items, nine resolved by assignment, two by RFI before award.
Multifamily podium, 240 units. Component 10 again, applied to blocking. Blocking and backing on repetitive residential work is the classic quantity-variable item, and framers price only what is detailed. The exhibit carried a blocking schedule by unit type with defined counts, which converted an unknown into a quantity. The priced number came in below the allowance the team had been carrying.
Highway interchange, design-bid-build. Component 12 and Component 13. On infrastructure work the coordination and permitting obligations dominate. Among the exhibits is traffic control, lane closure permitting, utility notification, restoration and erosion control maintenance. These are some of the obligations that will be divided among the earthwork contractor, the electrical subcontractor, and the prime.
Historic warehouse renovation to hotel, 140 keys. Component 10 in its renovation form. Unforeseen conditions dominate adaptive reuse, and the exhibits carried unit prices for selective demolition by assembly type, abatement by material and quantity, and structural remediation by condition class, along with a stated procedure for pricing discovered conditions. Without that structure every discovery becomes a negotiation, and on a 140-key conversion there are hundreds of discoveries.
Frequently Asked Questions
How long should a trade scope of work be?
Component coverage matters, not page count. A well-built exhibit for a major mechanical or electrical package on a mid-size commercial project typically runs 15 to 25 pages including matrices. A minor trade might be 6 to 10. If yours is 40 pages, check how much is boilerplate creating internal contradictions, and if it is 4 pages, check which of the sixteen components are missing.
Is the scope of work the same as Exhibit B?
Functionally yes, in common usage. Exhibit B is simply the conventional exhibit letter for the scope attachment in many subcontract forms, with Exhibit A commonly being the contract documents list and Exhibit C the schedule of values or unit prices. The letters vary by office. What matters is that the scope attachment does the sixteen jobs described here regardless of what it is labeled.
Who should write the scope of work, preconstruction or contracts?
Split it. Preconstruction owns the technical components, meaning inclusions, exclusions, interfaces, and quantities, because those require knowing what is in the documents. Contracts owns the legal components, meaning incorporation, precedence, notice, and changes. Blurring the line produces documents that are legally tidy and technically empty, which is the most common failure mode in the industry.
Should the interface matrix be identical in every affected exhibit?
Yes, identical, and this is one of the few places I would call a practice mandatory. If the mechanical exhibit and the drywall exhibit contain different versions of the access panel row, you have created the dispute rather than prevented it. One matrix, one version, attached to every package it touches.
How do we handle a subcontractor who submits his own scope clarifications?
Treat each item as a proposal requiring a decision, and never incorporate the letter by reference. Accept the item and write it into your language, reject it in writing with a reason, or resolve it by reassigning the work to another package. An attached clarification letter transfers the boundary to the counterparty and it is signed by you, which makes it very hard to argue with later.
What is the difference between an allowance and a contingency in a scope of work?
An allowance is the subcontractor’s to spend on defined work of undefined extent, reconciled against actual cost. A contingency is the contractor’s, held for work that may not occur at all, and the subcontractor has no entitlement to it. Confusing them is common, and the confusion always runs one direction: the subcontractor treats a contractor contingency as an allowance he can draw.
Do we need a scope of work if the specifications are thorough?
Yes, because they answer different questions. Specifications describe how work is performed correctly and apply to whoever performs it. A scope of work states who performs it, where the obligation starts and stops, what happens at interfaces, and what the party owes in deliverables, time, and closeout. No specification addresses any of that, and no specification is written to.
How should the scope of work handle work shown on other disciplines’ drawings?
State it explicitly as an inclusion with the source cited. Electrical obligations appearing on mechanical sheets are the single most common category of disputed scope in commercial construction, and the reason is that exhibits get assembled by drawing discipline. Assemble by assigned trade across the whole set, and cite the sheet, so the bidder cannot claim surprise.
When should the scope of work be drafted relative to bidding?
Draft it before the bid package is issued and issue it with the package. A scope of work written after bids are received is not a scope document, it is a negotiation position, and you have already lost the pricing benefit of specificity. On negotiated work, drafting can begin at design development and refine through each design issue.
How do we keep exhibits consistent across twenty or thirty packages?
Structure and reconciliation. A shared clause library handles the legal components. A structured scope register, where every obligation carries a trade assignment and a CSI division, handles the technical components, since each exhibit is then a filtered view of one dataset rather than a separately authored document. Then run a cross-package reconciliation before issuing, checking for obligations assigned twice and obligations excluded by everyone.
What happens to the scope of work after execution?
It stays live. Addenda, change orders, and design revisions all modify scope, and an exhibit that is never amended stops describing the deal within weeks. Maintain an amendment log tied to the original component structure, so that when a dispute arises the current scope can be reconstructed rather than argued about.
Which single component would you add first to a weak template?
Component 7, the interface matrix. It requires no rewriting of existing language, it can be drafted once per project type, and it addresses the category of dispute that most damages field relationships and schedule. Second would be Component 12, the enumerated coordination and site obligations, because every item you leave unstated becomes yours by default.
Expert Recommendations
For the preconstruction manager: build the interface matrix with a superintendent, once, for your most common project type. Reuse it. It will be the most-referenced page in every buyout package you issue.
For the estimator: refuse to price a package whose scope exhibit is silent on Component 12. Coordination, hoisting, cutting and patching, and housekeeping are real costs, and if the exhibit does not state them your number is wrong in a direction you will not discover until the field.
For the contracts group: convert incorporation to two tiers this quarter. It is a small drafting change and it removes an entire category of argument about whether a document applied.
For the project manager: maintain the amendment log. An executed exhibit that has absorbed nine change orders and two addenda without being updated cannot be relied on, and reconstructing it during a dispute costs far more than maintaining it did.
For the superintendent: read Component 7 and Component 11 before each trade mobilizes. Interfaces and sequencing obligations are what you will be enforcing, and if a row is blank you want to know before the crew is on site.
For the project executive: audit one competitor’s or one legacy exhibit against the sixteen components at your next leadership meeting. The exercise takes twenty minutes and it usually changes how the organization thinks about scope documentation.
For the owner or owner’s representative: ask to see a trade scope exhibit at buyout, not the summary. Whether it contains an interface matrix and a deliverables matrix tells you more about your project’s cost certainty than the schedule of values does.
Bringing the Components Together
A scope of work is a parts assembly. Sixteen components, each answering a question that will otherwise be answered by whoever argues better in month seven. The legal components are usually present because lawyers wrote the template. The technical components are usually absent because nobody owned them, and they are the ones that decide whether the project loses money.
None of this requires new software or new headcount. It requires deciding that the scope exhibit is a technical document with legal sections rather than a legal document with a technical appendix, and staffing it accordingly.
Start with the audit. Score your current template against the sixteen, and pull your last five scope disputes to see which absent component would have prevented each one. The correlation is usually uncomfortable and always instructive.
