Document Comparison
The charter defines boundaries. The scope statement details deliverables. The SOW creates a contractual agreement. Each serves a different audience and different purpose.
Updated 27 April 2026
A project charter authorises the project and defines its boundaries (what is in and out of scope, and who holds decision authority). A scope statement details the specific deliverables and their acceptance criteria within those boundaries. A statement of work (SOW) is the legally binding contract that commits an external vendor to those deliverables with payment terms attached. The charter comes first and sets the boundaries; the scope statement details the deliverables; the SOW makes them contractual.
Project Charter
Boundaries and authority. 1 to 5 pages. Written Week 0 to 2, approved by the sponsor. Internal governance document.
Scope Statement
Deliverables and acceptance criteria. 3 to 10 pages. Written Week 2 to 6 by the PM with team input. Internal planning document.
Statement of Work
Payment milestones, penalties, IP ownership. 5 to 20+ pages. Reviewed by legal before a vendor engagement. Legally binding contract.
Project Charter
Boundaries and authority
What the project covers and who decides
Scope Statement
Deliverables and acceptance
What the project produces and how to verify it
Statement of Work
Contractual agreement
What the vendor delivers and payment terms
| Dimension | Charter | Scope Statement | SOW |
|---|---|---|---|
| Purpose | Authorise the project and define boundaries | Detail deliverables and acceptance criteria | Contractual agreement between parties |
| Timing | Before team assembly (Week 0-2) | During planning (Week 2-6) | Before vendor engagement or contract signing |
| Author | PM (drafted), sponsor (approved) | PM with team input | PM or procurement, reviewed by legal |
| Audience | Sponsor, stakeholders | Project team, functional leads | Vendor, legal, procurement |
| Length | 1 to 5 pages | 3 to 10 pages | 5 to 20+ pages |
| Detail level | Boundary-level (in/out) | Deliverable-level (acceptance criteria) | Contractual-level (payment terms, penalties) |
| Binding nature | Internal governance document | Internal planning document | Legally binding contract |
| Change process | Formal charter revision (rare) | Scope change request process | Contract amendment (requires legal review) |
| Key sections | Problem, criteria, scope boundaries, authority | Deliverables, acceptance criteria, exclusions, WBS reference | Deliverables, payment milestones, penalties, IP ownership, warranty |
| Without it | No project authority, scope creep risk | Ambiguous deliverables, acceptance disputes | No contractual protection, payment disputes |
Internal project, small team
Scope lives in the charter's in/out table. No vendor, so no SOW needed. Scope statement detail goes into the project plan.
Internal project, enterprise PMO
PMO governance requires both. Charter for approval, scope statement for detailed deliverable tracking.
External vendor project
Charter authorises the project internally. SOW creates the contractual agreement with the vendor. Scope detail lives in the SOW.
Large enterprise with vendor
Charter for internal authorisation. Scope statement for detailed deliverable tracking. SOW for contractual protection with the vendor.
Agile / small project
Scope lives in the product backlog. No scope statement needed. SOW only if a vendor is involved.
A $150K website redesign project shown as charter scope, scope statement deliverables, and SOW extract.
In scope: Redesign homepage, 12 landing pages, pricing page, and signup flow.
Out of scope: Do not redesign blog, documentation, or help centre. Do not build native mobile app.
Deliverable 1: Homepage redesign. Acceptance: responsive (320px to 2560px), loads under 1.5s on 4G, achieves 90+ Lighthouse performance score.
Deliverable 2: 12 landing pages. Acceptance: unique above-fold content, A/B test framework integrated, UTM tracking functional.
Deliverable 3: Signup flow. Acceptance: 3-field form, email verification, OAuth options (Google, Microsoft), under 30s completion time.
Payment milestone 1: 30% upon design approval ($45K). Approval criteria: client signs off on high-fidelity mockups for homepage and 3 representative landing pages.
Payment milestone 2: 40% upon development completion ($60K). Criteria: all pages deployed to staging environment, all acceptance criteria met, UAT sign-off.
Payment milestone 3: 30% upon go-live ($45K). Criteria: production deployment, 5-day monitoring period with zero P1 issues, analytics tracking verified.
Change order process: Client-requested changes outside the deliverable list require written change order with cost and timeline impact assessment. Changes under $5K approved by PM. Changes over $5K require sponsor approval.
The project charter authorises the project and defines its boundaries: what is in and out of scope, and who holds decision authority. It is written first, before the team assembles. The scope statement comes later, during planning, and details the specific deliverables and their acceptance criteria within those boundaries. In short, the charter sets the boundaries and the scope statement details the deliverables those boundaries contain.
The charter. It is drafted before the team assembles (typically Week 0 to 2) and is approved by the sponsor. The scope statement is written during planning (typically Week 2 to 6) by the PM with team input, after the charter has authorised the project.
Not always. A small internal project can run on a charter alone, with scope held in the charter's in and out table. An enterprise PMO usually requires both: the charter for approval and the scope statement for detailed deliverable tracking. Add a statement of work only when an external vendor is involved.
No. A scope statement is an internal planning document that details deliverables and acceptance criteria. A statement of work is a legally binding contract between parties that adds payment milestones, penalties, IP ownership, and warranty terms.
The project charter is an internal governance document that authorises the project and defines its boundaries and decision authority; it binds no one contractually. A statement of work is a legally binding contract with an external vendor that adds payment milestones, penalties, IP ownership, and warranty terms. The charter is written first, at Week 0 to 2, by the PM and approved by the sponsor. The SOW is written before the vendor is engaged, by the PM or procurement, and reviewed by legal. In short: the charter authorises the project internally, the SOW commits a vendor to deliver against payment.
Updated 2 May 2026