Construction Scope of Work: How to Write One (With Template)

SheetIntel Team ·

A weak scope of work is how GCs lose money on projects they should have won. Scope gaps — work nobody explicitly owns — end up costing the GC who built an incomplete picture of the job.

This guide covers what belongs in a construction scope of work, the most dangerous things to leave ambiguous, and a section-by-section template you can adapt for commercial projects.

What Is a Construction Scope of Work?

A construction scope of work is a written definition of exactly what work is included in a contract or bid — and what isn't. It answers three questions:

  • 1.What work will be performed?
  • 2.Who is responsible for each item?
  • 3.What is explicitly excluded?

The scope of work is not the same as the project specifications. Specs define quality standards and materials. The scope defines what work your contract covers. Both are necessary. Neither replaces the other.

Why Scope Gaps Happen

Scope gaps don't come from laziness — they come from ambiguity in the drawings that nobody resolved before bidding. Three common sources:

Interface work between trades

Where one trade's work ends and another's begins is often not shown on drawings. The blocking behind a TV mount — is that GC framing scope or AV sub scope? The connection between the HVAC condensate line and the plumbing waste — who owns that tie-in? If your scope doesn't name it, expect a dispute.

Owner-furnished / contractor-installed (OFCI)

Equipment the owner purchases but the contractor installs. If the scope doesn't call out OFCI items, a sub will price the equipment they're only supposed to install — or they'll skip both. Always identify what's OFCI in the scope.

Drawings that don't match specs

The drawings show one material, the spec book calls out another. The scope needs to clarify which governs — or send an RFI before bidding. A scope written off drawings only may miss spec requirements that add cost.

Construction Scope of Work Template

The sections below apply to commercial GC scope of work documents. Adapt the items to match your trade package and project type.

Section 1: Project Description

Brief description of project type, size, and location. Establishes context for everything that follows.

  • • Project name, address, and owner
  • • Building type and gross square footage
  • • Applicable building code (IBC year, jurisdiction amendments)
  • • Contract type (lump sum, GMP, T&M)
  • • Basis of design documents (drawing set date, addenda incorporated)

Section 2: Work Included

Positive statement of every scope item covered under this contract. Be specific — vague language creates dispute surface.

  • • List each work area or system (by CSI division if helpful)
  • • Identify material standards and allowable substitutions
  • • Name all trade packages included (self-perform vs. sub)
  • • Note OFCI items and what "install only" means for each
  • • Specify temporary facilities scope (job site trailer, dumpsters, portable toilets)
  • • Define cleanup and debris removal scope

Section 3: Work Excluded (Clarifications)

This section protects you more than any other. Explicit exclusions remove scope gap risk and align expectations before contract execution.

  • • Trades or systems handled by owner's separate contracts
  • • Permit fees (if by owner)
  • • Testing and inspection fees (if by owner)
  • • Utility connection fees
  • • Hazmat / abatement (if not scoped)
  • • Anything shown on drawings but not included in your bid
  • • Any work contingent on conditions not visible at bid time

Section 4: Allowances and Alternates

Items priced as separate line items from the base bid — either because the scope isn't fully defined (allowance) or because the owner may or may not want them (alternate).

  • • List each allowance with dollar amount and what it covers
  • • List each alternate with add/deduct amount
  • • Note that allowances are not profit-bearing — document your markup separately if applicable

Section 5: Schedule Assumptions

Documents the time-based conditions your price is contingent on. Scope changes that affect schedule are change order territory.

  • • Assumed start date and substantial completion date
  • • Key milestones (site available, long-lead deliveries, owner move-in)
  • • Assumed work hours (single shift, overtime, weekend)
  • • Owner-caused delay language (price is based on uninterrupted access)

Section 6: Open Issues / Pending RFIs

Documents drawing conflicts and ambiguities you identified during plan review that are not yet resolved. Creates a paper trail.

  • • List each open RFI by number with a one-line description
  • • State your bid assumption for each (what you priced, pending resolution)
  • • Flag items where your price is contingent on a specific answer

This section converts plan review findings into contract protection. An undisclosed scope gap is your liability. A disclosed one with a pricing assumption is the owner's problem to clarify or the architect's to resolve.

The Most Dangerous Items to Leave Vague

Based on common scope dispute patterns, these are the items most likely to generate change orders or claims when not addressed explicitly:

Item The Dispute
Existing condition demolition How much demo is in scope? If existing conditions are unknown, price as an allowance or note that demo scope is based on visible conditions only
Underground utilities What happens when you hit an undisclosed utility? State that scope is based on as-built drawings provided by owner; conflicts are owner's responsibility
Final cleaning Is that "broom clean" or "white glove"? Define the cleaning standard explicitly
Punch list labor How many rounds of punch list are included? After 3 walks, are additional mobilizations a change order?
As-built drawings Are as-builts required? In what format? Who compiles them? If required by spec, confirm your price includes the time
Commissioning support MEP subs: does scope include attending commissioning? How many days? Who pays for re-commissioning after punch list items?

How Plan Review Feeds Your Scope

The quality of your scope of work is directly proportional to the quality of your plan review. A thorough pre-bid plan review produces:

  • A complete list of scope items (nothing missed from drawings)
  • Identified trade interface conflicts for Section 2 and Section 6
  • Missing spec callouts to exclude or price as allowances
  • Drawing conflicts to document as open RFIs before bid submission

GCs who review plans thoroughly write tighter scopes. Tighter scopes produce fewer change orders. Fewer change orders mean less exposure on margin.

Know your scope before you write it

SheetIntel analyzes your plan set and produces a trade-by-trade scope summary — finding the conflicts, gaps, and interface issues that belong in your scope exclusions before you submit. First review is free.

Try SheetIntel Free →