Free Scope of Work Template

What is a scope of work?

A scope of work — sometimes abbreviated SOW or SoW — describes the work that one party is hiring another to perform. It defines the objectives, the activities the vendor will perform, what they will deliver, when, and how the client will confirm acceptance. It also names the items the vendor will not perform, which prevents scope creep at the source.

In federal contracting (US Department of Veterans Affairs and the FAR-based template canon), the Scope of Work is required to cover six elements: description of the work, location, period of performance, deliverable schedule, performance standards, and special requirements. Commercial engagements rarely need all six in that exact form, but every commercial SOW that holds up under stress covers the same ground in plain English.

Project-management bodies (PMI, ISO 21500) treat the Scope of Work as one input to a Project Charter or Statement of Work. In practice, for most consulting, software, construction, and services engagements, the SOW is the document the parties actually sign and reference when something goes sideways.

Scope of work vs. statement of work

The two terms collide because they share the same acronym (SOW), and most people use them interchangeably. There is a real distinction worth knowing.

• Statement of Work. The full contractual document. Includes the scope, deliverables, timeline, fees, change-order process, IP terms, governing law, and signatures. In US federal contracting (FAR Part 37 and DoD MIL-HDBK-245), the Statement of Work is the master artifact for service contracts.
• Scope of Work. The narrower section or standalone document focused on the work itself — what gets done, when, and how acceptance is judged. In federal contracting it lives inside the Statement of Work. In commercial work, especially construction and consulting, people often call the whole document a Scope of Work and skip the broader contract framing.

If you are working under an existing Master Services Agreement, this template can serve as the Scope of Work attached to a short Statement of Work cover page. If you have no MSA and want a standalone contract, our separate Statement of Work template adds the legal framing this template intentionally leaves out.

What to include in a scope of work

The template covers thirteen sections, in this order. The first six describe the work and the last seven govern how the work is run.

1. Project overview. Two to four sentences. Business context, the problem, the high-level outcome.
2. Objectives. Measurable outcomes, plain English. “Migrate three source systems into a single Snowflake warehouse with row-count drift below 0.1%.”
3. In-scope activities. The actual work the vendor will perform. The cardinal rule of SOW writing: if it isn’t listed, it isn’t in scope.
4. Out of scope. Items the vendor will not perform. Adding any of these requires a Change Order. Naming them here heads off most scope-creep arguments before they start.
5. Deliverables. Table format. Each deliverable: ID, name, description, due date, acceptance criteria.
6. Timeline and milestones. Table format. Each milestone: ID, name, target date, completion trigger.
7. Roles and responsibilities. What the client owes (access, decisions, reviews) and what the vendor owes (the work, status reporting, escalation).
8. Pricing and payment schedule. Fee model (fixed-fee, T&M, or hybrid), total fee, and a payment schedule tied to milestone acceptance.
9. Acceptance criteria. How the client confirms a deliverable is complete. The template defaults to a 10-business-day review window with silence treated as acceptance.
10. Assumptions. What the SOW depends on being true. Wrong assumptions trigger Change Orders rather than disputes.
11. Confidentiality and underlying agreement. Reference to an existing MSA or NDA. The SOW does not re-litigate confidentiality.
12. Change order process. How scope, timeline, or fee changes get agreed in writing before the vendor performs the changed work.
13. Authorization. Signature block for both parties’ authorized representatives.

Scope of work for construction

Construction SOWs are the heaviest variant. The activities section will reference CSI MasterFormat divisions (e.g., “Division 09 — Finishes per Project Manual Section 09 29 00”), include submittals, name the responsible party for site conditions and code compliance, and list as-built drawings as a final deliverable.

When adapting the template, the deliverables table grows: each major trade or phase usually gets its own deliverable row, and acceptance criteria reference building codes, inspection sign-offs, or punchlist completion. The milestone schedule typically aligns to phases (mobilization, foundations, framing, MEP rough-in, finish) rather than discrete dates.

Scope of work for consulting and software

Consulting and software SOWs are the most common commercial pattern and the one the filled example in the download walks through. Activities are described as a sequence of analysis, design, build, and validation; deliverables are typically design memos, working code, dashboards, runbooks, or written reports.

Two judgment calls drive the rest: the fee model and acceptance bar. Fixed-fee suits well-scoped, low-discovery work; time-and-materials suits open-ended discovery; a hybrid (fixed-fee per phase, T&M for Change Orders) is the common middle ground. Acceptance criteria are best stated as observable behaviors — “pipelines run cleanly for seven consecutive days,” “design memo approved by the Project Sponsor” — not subjective quality judgments.

Scope of work for cleaning and HVAC

Cleaning, janitorial, and HVAC SOWs are recurring-services scopes. The deliverables table is replaced or supplemented by a frequency matrix — task rows (vacuum, sanitize restrooms, replace filters) crossed with frequency columns (daily, weekly, monthly, quarterly). Acceptance criteria reference inspection scores or response-time SLAs.

When adapting the template for these engagements, leave the milestone schedule largely empty (recurring services don’t hit milestones in the project sense), and lean on the assumptions section to spell out access hours, holiday coverage, and product specifications. HVAC SOWs usually add an equipment list as a separate schedule.

How to write a scope of work

1. Start with the objective. Two sentences on what good looks like. If you can’t state the outcome plainly, the rest of the SOW will paper over the gap.
2. Write the in-scope list before anything else. List every activity the vendor will perform. Be specific. Vague activities (“support the migration”) are where scope creep enters.
3. Write the out-of-scope list immediately after. Anything plausibly adjacent that the vendor will not do. This list is doing more than its size suggests.
4. Name the deliverables. Each deliverable should be a specific artifact with a specific format — not an activity. “Written parity report (PDF) covering 90 days”, not “validate parity.”
5. Set acceptance criteria for each deliverable. How will the client confirm completion? The template defaults to a written acceptance procedure with a fixed review window and silence-equals-acceptance.
6. Tie payment to milestones. The default in the template is 30/40/30 across three milestones. Adjust as needed; the principle is that the vendor is paid as outcomes land, not as time passes.
7. Document assumptions. If wrong assumptions would change the scope or fee, list them. The Change Order process kicks in when an assumption breaks.

What is inside the template

The download is a zip containing two files:

• scope-of-work-blank.docx — the full template with [BRACKETED PLACEHOLDERS] for every field that varies: project name, parties, dates, objectives, in-scope and out-of-scope activities, deliverables, milestones, fee, and signatures.
• scope-of-work-example.docx — the same template filled with a realistic software-consulting example: Acme Corporation hires Widget Industries Inc. to migrate three legacy data systems into a Snowflake warehouse, with three milestones, four deliverables, a 200K USD fixed fee, and a 30/40/30 payment schedule.

Both files render in Cambria on US letter-size pages with Butterick-style 1.5-inch margins. They open cleanly in Microsoft Word, Google Docs, Apple Pages, and LibreOffice without reformatting. A short footer on every page repeats the disclaimer that this is a template, not legal advice.