What is on the project scope template
- Deliverables
- The tangible things the project hands over: a website, a report, a trained team, an installed system. Not activities.
- Acceptance criteria
- For each deliverable, the checks that prove it is finished, written so both sides would agree whether they are met.
- Exclusions
- What the project will not do. A clear list here prevents most scope arguments later.
- WBS numbers and work packages
- Deliverables broken down into numbered pieces of work (1, 1.1, 1.2) small enough to estimate and assign, usually between a few hours and a couple of weeks.
- Hours, rate and cost
- Estimated effort for each work package; Excel multiplies by the rate and totals the project.
Writing a scope statement that holds
Start from the objective: one or two sentences on what the project will achieve and by when. Then list the deliverables, each as a thing, not a task, and write acceptance criteria for each that both sides could check: numbers, browsers, page counts, rounds of revisions, response times. The exclusions list is where you prevent future disputes; write down everything a reasonable client might assume is included but isn't. Record assumptions (what you're relying on the client or others to do) and constraints (fixed budget, deadline, platform). Have the sponsor or client sign, and from then on any change goes through the change request form.
Building a work breakdown structure
The WBS takes each deliverable and breaks it into work packages: chunks of work small enough that someone can estimate and own them. Number them so they can be referred to (2.1, 2.2), add an owner and the estimated hours, and Excel turns them into a cost. Add project management as its own line, typically about 10% of the effort, because it's real work. The totals feed the budget in the project plan or the price in an estimate, and the "depends on" column gives the order of work for the timeline. In the sample, 87 hours at mixed rates comes to $7,095 of effort against a $6,800 fixed fee, an early warning that the price or the scope needs another look.
Getting deliverables accepted
When a deliverable is ready, go through its acceptance criteria with the client or sponsor and record the result for each one. Most deliverables are accepted with a few small fixes; list them with a date and record that decision rather than waiting for perfection. If a criterion isn't met, the form makes clear exactly what is missing. Signed acceptance forms are the natural trigger for milestone invoices on client projects and the evidence that the work was delivered as agreed.
Editing the files
The PDFs are fillable, and the Word versions can carry your own terms and logo for client projects. The Excel WBS calculates cost per work package and totals; add or remove rows and levels as needed. Use heading rows (like "2 DESIGN") without hours to group work packages.
Questions
What is a project scope statement?
A document that defines what a project will deliver, how each deliverable will be accepted, what is excluded, and the assumptions and constraints, signed by the sponsor or client.
What is a work breakdown structure?
A breakdown of the project's deliverables into numbered work packages small enough to estimate, assign and schedule.
How do I prevent scope creep?
Write clear deliverables, acceptance criteria and exclusions, get sign-off, and route every change through a change request with its effect on cost and schedule.
What are acceptance criteria?
Specific, checkable conditions a deliverable must meet to be considered complete.
Does the WBS calculate cost?
Yes. The Excel version multiplies hours by rate for each work package and totals hours and cost.
Comments and questions
Have a question about this template, or an idea to make it better? Leave a comment.
Leave a comment