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.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
Two more distinctions are worth fixing early, because the terms get used loosely.<\/p>\n\n\n\n
Table 1. Scope of Work Compared <\/strong>With<\/strong> Related Documents<\/strong><\/p>\n\n\n\n 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.<\/p>\n\n\n\n Inclusion.<\/strong> An affirmative statement that specified work is within this party’s scope.<\/p>\n\n\n\n Exclusion.<\/strong> 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.<\/p>\n\n\n\n Interface.<\/strong> A single work item that two or more parties touch, decomposed into who furnishes, who installs, who coordinates, and who verifies.<\/p>\n\n\n\n Incorporation by reference.<\/strong> 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.<\/p>\n\n\n\n Order of precedence.<\/strong> The stated rule for which document governs when two conflict. Without it, conflicts get resolved by negotiation or by a judge.<\/p>\n\n\n\n Delegated design.<\/strong> 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.<\/p>\n\n\n\n Allowance.<\/strong> A stated sum carried in the subcontract price for work not yet fully defined, with the basis and exclusions stated.<\/p>\n\n\n\n Unit price.<\/strong> A pre-agreed rate for work of uncertain quantity, so that quantity variation is priced rather than negotiated.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n What it establishes.<\/strong> Who is bound, to what project, under which prime contract, for which trade package.<\/p>\n\n\n\n Why it exists.<\/strong> 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.<\/p>\n\n\n\n How to write it.<\/strong> 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.<\/p>\n\n\n\n What it establishes.<\/strong> Exactly which documents are part of this subcontract.<\/p>\n\n\n\n Why it exists.<\/strong> 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.<\/p>\n\n\n\n How to write it.<\/strong> 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.<\/p>\n\n\n\n Table 2. Incorporation Approaches and Their Consequences<\/strong><\/p>\n\n\n\n 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.<\/p>\n\n\n\n What it establishes.<\/strong> Which document wins when two conflict.<\/p>\n\n\n\n Why it exists.<\/strong> 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.<\/p>\n\n\n\n How to write it.<\/strong> 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.<\/p>\n\n\n\n That second sentence converts precedence from a dispute-resolution rule into a behavior rule. It gets conflicts surfaced during construction instead of after.<\/p>\n\n\n\n What it establishes.<\/strong> A plain-language statement of what this trade is doing, in a paragraph.<\/p>\n\n\n\n Why it exists.<\/strong> 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.<\/p>\n\n\n\n How to write it.<\/strong> 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.<\/p>\n\n\n\n What it establishes.<\/strong> The substantive inclusions, organized so a reader can find things.<\/p>\n\n\n\n Why it exists.<\/strong> This is the body of the document and where most of the technical content lives.<\/p>\n\n\n\n How to write it.<\/strong> 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n Table 3. Anatomy of a Well-Written Inclusion<\/strong><\/p>\n\n\n\n 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.<\/p>\n\n\n\n What it establishes.<\/strong> Work specifically not in this party’s scope.<\/p>\n\n\n\n Why it exists.<\/strong> 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.<\/p>\n\n\n\n How to write it.<\/strong> Two categories, stated separately.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n Table 4. Exclusion Drafting Patterns<\/strong><\/p>\n\n\n\n What it establishes.<\/strong> For every work item involving more than one party, who furnishes, who installs, who coordinates, and who verifies.<\/p>\n\n\n\n Why it exists.<\/strong> 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.<\/p>\n\n\n\n How to write it.<\/strong> 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.<\/p>\n\n\n\n Table 5. Interface Matrix, Representative Rows<\/strong><\/p>\n\n\n\nDocument<\/strong><\/th> What It Establishes<\/strong><\/th> Governs<\/strong><\/th> Typical Length<\/strong><\/th> Who Writes It<\/strong><\/th><\/tr><\/thead> Scope of work (Exhibit B)<\/strong><\/td> What this party performs and does not perform<\/td> The subcontract relationship<\/td> 6 to 25 pages per trade<\/td> Contractor, preconstruction and contracts<\/td><\/tr> Specification section<\/strong><\/td> Products, standards, execution quality<\/td> All parties performing that work<\/td> 8 to 40 pages per section<\/td> Design team<\/td><\/tr> Drawings<\/strong><\/td> Geometry, location, quantity, configuration<\/td> All parties<\/td> Full set<\/td> Design team<\/td><\/tr> Statement of work (owner side)<\/strong><\/td> Services and deliverables the contractor owes the owner<\/td> The prime contract<\/td> 10 to 60 pages<\/td> Owner or program manager<\/td><\/tr> Work breakdown structure<\/strong><\/td> Decomposition of work for planning and cost control<\/td> Internal management<\/td> Variable<\/td> Contractor, project controls<\/td><\/tr> Bid package<\/strong><\/td> The invitation and its attachments, of which the scope of work is one<\/td> The bidding process<\/td> Package<\/td> Contractor, preconstruction<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Core Terminology<\/strong><\/h3>\n\n\n\n
KEY TAKEAWAY<\/strong>
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.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nObjectives of a Well-Built Scope of Work<\/strong><\/h2>\n\n\n\n
\n
Why the Components Matter More Than the Length<\/strong><\/h2>\n\n\n\n
INDUSTRY INSIGHT<\/strong>
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.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nComponent 1: Identification and Parties<\/strong><\/h2>\n\n\n\n
Component 2: Contract Documents and Incorporation<\/strong><\/h2>\n\n\n\n
Approach<\/strong><\/th> Language Pattern<\/strong><\/th> Effect<\/strong><\/th> Risk<\/strong><\/th><\/tr><\/thead> Blanket incorporation<\/strong><\/td> “All contract documents apply”<\/td> Everything is arguably in scope<\/td> Subcontractor prices defensively or disputes later; Division 01 obligations unpriced<\/td><\/tr> Specific enumeration<\/strong><\/td> Named sheets, sections, addenda with dates<\/td> Clear obligation boundary<\/td> Omission of a document leaves a genuine gap<\/td><\/tr> Enumeration plus catch-all<\/strong><\/td> Named documents, then “and all other documents to the extent applicable”<\/td> Appears safe, is ambiguous<\/td> The catch-all defeats the enumeration; worst of both<\/td><\/tr> Two-tier<\/strong><\/td> Named obligation documents plus named information documents<\/td> Obligation boundary clear, context provided<\/td> Requires drafting discipline per package<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Component 3: Order of Precedence<\/strong><\/h2>\n\n\n\n
Component 4: Scope Summary<\/strong><\/h2>\n\n\n\n
Component 5: Detailed Work Description by Division and System<\/strong><\/h2>\n\n\n\n
Element<\/strong><\/th> Function<\/strong><\/th> Weak Example<\/strong><\/th> Strong Example<\/strong><\/th><\/tr><\/thead> Verb set<\/strong><\/td> States which of furnish, install, coordinate, verify, test apply<\/td> “Provide”<\/td> “Furnish, install, connect, and test”<\/td><\/tr> Object with components<\/strong><\/td> Names the assembly and its parts<\/td> “Ductwork”<\/td> “Ductwork including hangers, supports, restraints, dampers, and access provisions”<\/td><\/tr> Physical limits<\/strong><\/td> Where the obligation starts and stops<\/td> Silent<\/td> “From AHU discharge to terminal device connection”<\/td><\/tr> Area limits<\/strong><\/td> Which parts of the project<\/td> Silent<\/td> “Levels 1 through 6, Building A only”<\/td><\/tr> Standard reference<\/strong><\/td> The governing quality basis<\/td> Silent<\/td> “Per Section 23 31 13 and SMACNA”<\/td><\/tr> Quantity basis<\/strong><\/td> Where quantity comes from<\/td> Silent<\/td> “As shown on M-201 through M-260”<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n FIELD REALITY<\/strong>
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.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nComponent 6: Exclusions<\/strong><\/h2>\n\n\n\n
Pattern<\/strong><\/th> Example<\/strong><\/th> Effect<\/strong><\/th><\/tr><\/thead> Excluded and assigned<\/strong><\/td> “Access panels excluded; included in Division 09 package”<\/td> Clean; subcontractor does not price it and knows who does<\/td><\/tr> Excluded and contractor-held<\/strong><\/td> “Temporary heat excluded; performed by Contractor”<\/td> Clean; sequencing expectation set<\/td><\/tr> Excluded, unassigned<\/strong><\/td> “Access panels excluded”<\/td> Incomplete; work may belong to nobody<\/td><\/tr> Excluded by silence<\/strong><\/td> No mention of access panels anywhere<\/td> Dangerous; obligation may attach by incorporation<\/td><\/tr> Excluded by adopting subcontractor’s list<\/strong><\/td> “See Subcontractor’s Clarification Letter dated…”<\/td> Boundary set by the counterparty<\/td><\/tr> Excluded with condition<\/strong><\/td> “Rock excavation excluded above 50 CY; unit price per Attachment C”<\/td> Strong; quantity risk priced rather than argued<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Component 7: Interface and Responsibility Matrix<\/strong><\/h2>\n\n\n\n
Interface Item<\/strong><\/th>