Two formats. Eight filled examples. One interactive generator. Pick the charter structure that matches your project, fill it in, and get approval in one review cycle. No signup, no software, no paywall.
Updated 27 April 2026
1 page, 4 sections
Best for projects under $50K with small teams. Problem statement, success criteria, scope boundaries, and decision authority. Everything a sponsor needs to say "go" in 60 seconds.
3 to 5 pages, 12 sections
For enterprise projects with governance requirements. Includes business case summary, deliverables, milestones, budget breakdown, risk register, RACI matrix, and formal approval block.
Fill in the fields below to generate a formatted project charter. No signup required. Fields marked with * are required.
What business problem does this project solve? Include current metrics and cost of inaction. Aim for 50 to 150 words.
Each criterion should be Specific, Measurable, Achievable, Relevant, and Time-bound.
The out-of-scope column matters more than the in-scope column. Use verb phrases, not nouns.
Every charter, regardless of size or industry, needs these four sections. The lean format strips everything else away.
What business problem does this project solve? Include current metrics and cost of inaction.
50 to 150 words. One paragraph, no jargon.
3 to 5 measurable outcomes using the SMART framework.
Each criterion needs a number, a baseline, a target, and a deadline.
Deep-dive guide →What is in scope and, more importantly, what is explicitly out of scope.
Use verb phrases. Every in-scope item needs a corresponding boundary.
Deep-dive guide →Who can approve what. Sponsor authority, PM authority, and escalation path.
Name the person, not the role. Roles change, names create accountability.
For enterprise projects where governance requires comprehensive documentation. Each section links to a detailed writing guide.
| # | Section | What It Covers |
|---|---|---|
| 01 | Project Information | Name, ID, sponsor, PM, date, version |
| 02 | Background / Business Case | Why this project exists and what triggered it |
| 03 | Problem Statement | Current state with metrics and cost of inaction |
| 04 | Goals and Objectives | Strategic alignment and project-level goals |
| 05 | Success Criteria | 3 to 5 SMART outcomes with baselines and targets |
| 06 | Scope (In/Out) | Boundary table with verb phrases and reasons for exclusions |
| 07 | Deliverables | Tangible outputs with acceptance criteria |
| 08 | Milestones | Phase gates with dates, dependencies, and approval requirements |
| 09 | Budget | Capital, operational, contingency (typically 10 to 15%) |
| 10 | Risk Register | Top 3 to 5 risks with probability, impact, and charter-level response |
| 11 | Team and Roles | RACI matrix for key decisions and deliverables |
| 12 | Approval and Governance | Review cadence, change control process, signature block |
Use this decision framework instead of guessing. Match your project characteristics to the right charter format.
| Factor | Lean (1 page) | Full PMO (3-5 pages) |
|---|---|---|
| Budget | Under $50K | Over $50K |
| Duration | Under 3 months | 3+ months |
| Team size | 2 to 5 people | 6+ people or cross-department |
| Methodology | Agile, lean, startup | Waterfall, PRINCE2, enterprise PMO |
| Compliance | None or minimal | Regulatory, audit, or governance requirements |
| Stakeholders | 1 to 2 approvers | Steering committee or board review |
Mixed signals? Default to the lean format and add sections as your sponsor requests them. PMI data shows charters under 3 pages have 89% first-pass approval rates, compared to 61% for documents over 5 pages.
The same project scoped in different methodologies produces different charters. Pick the template that matches your context.
Product vision replaces problem statement. Definition of Done replaces success criteria. Sprint boundaries replace scope.
Sprint-based
Process metrics, sigma-level targets, VOC data, and SIPOC boundaries. Aligned to the Define phase.
Process improvement
Permit timelines, contractor scope delineation, payment milestones, and change order authority thresholds.
Permit-driven
System boundaries, data migration scope, downtime windows, rollback criteria, and vendor SLAs.
System cutover
Patient safety metrics, HIPAA scope, IRB dependencies, and clinical workflow boundaries.
Patient-safety scoped
By methodology
By industry / domain
Turn your charter milestones into assigned action items and structured meeting agendas.
Updated 2 May 2026