Project Charter: [project]
The authorization document – scope, authority, and constraints
agreed before work starts. PMBOK-style.
| Field | Value |
|---|
| Project | [name] |
| Sponsor | @name |
| Project manager | @name |
| Date | YYYY-MM-DD |
| Status | Draft / Approved |
Purpose & justification
Why this project exists and the business case in two sentences:
Objectives & success criteria
| Objective | Measure | Target |
|---|
| [objective] | [metric] | [target] |
Scope
- In scope: [deliverables]
- Out of scope: [explicitly excluded – prevents 80% of disputes]
Key milestones
| Milestone | Date | Deliverable |
|---|
| Kickoff | YYYY-MM-DD | Charter signed |
| | |
Budget & resources
| Item | Estimate | Notes |
|---|
| People | N FTE | [roles] |
| Budget | $N | |
| Tools / vendors | $N | |
Stakeholders
| Stakeholder | Interest | Influence | Engagement |
|---|
| @name | [what they want] | High / Med / Low | Manage / Inform |
Assumptions & constraints
- Assumptions: [treated as true until disproven]
- Constraints: [budget, deadline, compliance, tech]
Risks (top)
Approval & authority
The sponsor authorizes the PM to [spend up to $N / assign people /
make scope calls below N]. Signature:
| Sponsor | Date |
|---|
| @name | YYYY-MM-DD |