One-Page Project Charter Template: The Format Sponsors Actually Read (2026)

The 4-Quadrant Layout

Why, what, who, when. Four quadrants on one page (or one printed A4 / Letter sheet). Each quadrant holds the minimum content required by PMBOK's six required charter outputs, condensed.

Top-left: Why

Problem statement + 3 success criteria. Two short paragraphs. The reader should understand both the problem and what success looks like within 60 seconds.

Top-right: What

Scope in-table (3-5 bullets) + scope out-table (3-5 bullets). The most important quadrant because it bounds the project.

Bottom-left: Who

Named sponsor, named PM, 3-5 named stakeholders (with role). Decision authority for 2-3 key decision types.

Bottom-right: When and how much

5 milestones with target dates. Total budget envelope (one line). Top 3 risks (one line each).

ASCII Layout (Print-Ready)

The ASCII version is intentional. The format constraint forces clarity; if the content does not fit, the project is not yet thought through.


+--------------------------------------+--------------------------------------+
| WHY                                  | WHAT                                 |
| Problem: <50-100 words>              | In scope:                            |
| Success criteria:                    | - <verb phrase>                      |
| 1. <SMART criterion>                 | - <verb phrase>                      |
| 2. <SMART criterion>                 | - <verb phrase>                      |
| 3. <SMART criterion>                 | Out of scope:                        |
|                                      | - <verb phrase>                      |
|                                      | - <verb phrase>                      |
+--------------------------------------+--------------------------------------+
| WHO                                  | WHEN AND HOW MUCH                    |
| Sponsor: <name>                      | M1 <name>                  <date>    |
| PM: <name>                           | M2 <name>                  <date>    |
| Stakeholders:                        | M3 <name>                  <date>    |
| - <name>, <role>                     | M4 <name>                  <date>    |
| - <name>, <role>                     | M5 <name>                  <date>    |
| - <name>, <role>                     |                                      |
| Decisions:                           | Total budget: <amount>               |
| - <decision type>: <named>           | Contingency: <% of base>             |
| - <decision type>: <named>           | Top risks: <risk1; risk2; risk3>     |
+--------------------------------------+--------------------------------------+

Filled Example: Conversion-Rebuild Project

Software project (one-page charter)

Why

Trial-to-paid conversion dropped from 6.5% (Q1) to 4.2% (Q4). Customer interviews indicate the activation flow has regressed since the December redesign.

Success criteria

Lift trial-to-paid conversion to 6.0% by end of Q2 2026, measured in Stripe + Mixpanel.
Reduce time-to-first-value (sign-up to first successful API call) from 14 days to under 7 days.
Activation rate (% of trial users completing core action in 24h) at 65% or above.

In scope

Rebuild signup flow.
Add interactive product tour.
Instrument activation funnel events.
Refactor onboarding email sequence.

Out of scope

Do not redesign pricing page (separate cohort).
Do not change auth (out of scope).
Do not localise (English only).

Who

Sponsor: Maya Chen (VP Product)

PM: Alex Rivera (Product Manager)

Key stakeholders:

Sam Park, Engineering Lead
Priya Singh, Design
Marcus Wei, Growth

When + how much

M1 Discovery + new flow design (30 Apr 2026)
M2 New signup flow at 10% of traffic (31 May 2026)
M3 50% traffic on new flow (15 Jun 2026)
M4 100% traffic on new flow (30 Jun 2026)
M5 Post-launch review (31 Jul 2026)

Budget: USD 142K (USD 128K base + 11% contingency)

Top risks: 1. Activation regression at rollout (mitigation: gradual traffic ramp). 2. Engineering capacity conflict with Q2 platform work. 3. Marketing alignment on new positioning.

When One Page Works (and When It Does Not)

Situation	Verdict	Why
Project under USD 100K	Yes, one page is appropriate	Governance overhead does not scale with project size; smaller projects benefit from shorter charters.
Project under 12 weeks	Yes, one page is appropriate	Short projects do not produce enough new information to fill 5 pages anyway.
Internal team, no cross-department dependencies	Yes, one page is appropriate	Team has authority. The charter is a thinking artefact, not a negotiation tool.
Project in a PMO that requires PMBOK-format charter	Mostly no: use the lean format alongside the full format	Use the one-page as a sponsor-facing summary; the PMO file gets the full PMBOK format. Both can co-exist.
Cross-department project with steering committee	Probably no, but try	A one-page can defuse a 'how thick is the document' discussion. If steering rejects it, fall back to full format with the one-page as cover.
Regulated industry, audit trail required	No: use enterprise charter format	Audit defence requires more detail than one page can carry. Treat the one-page as the sponsor briefing, not the audit document.
Capex above USD 1M with board approval	No: use enterprise charter format	Board approval typically requires deeper detail on financial assumptions, risk, and governance.

Frequently Asked Questions

Can a one-page charter really replace a full PMO charter?

Sometimes. For projects under USD 100K with internal teams and no audit requirement, yes. For projects above USD 250K, in regulated industries, or with cross-department dependencies, no. The one-page can still exist as a sponsor-facing summary alongside the longer PMO charter (which lives in the project file). The Atlassian Project Poster format and the Stanford d.school project brief both demonstrate the one-page approach working for the right project size.

What is the Atlassian Project Poster?

A one-page project brief format Atlassian developed internally and published as part of their team playbook. It uses a similar 4-quadrant structure to the one-page charter above but is slightly more narrative-led. Atlassian's research suggests teams using a one-page format reach decision-making faster than teams using longer formats, with no significant difference in eventual delivery success when the project complexity is matched. It is one of the most cited one-page charter formats in modern PM practice.

How do you defend a one-page charter against a PMO that wants more pages?

Three arguments. First: cite PMI's position that PMBOK does not prescribe length, only the six required outputs (all of which can fit on one page for small projects). Second: produce the one-page version plus an offer to expand on request; most PMOs back down if the one-page covers all the required PMBOK outputs. Third: cite organisations using one-page formats successfully (Atlassian, Stanford d.school, many product-led tech companies). If the PMO still insists, write the full version and use the one-page as sponsor briefing.

What gets cut from a full charter to fit one page?

Detailed assumptions log, full RACI matrix, communication management plan, detailed risk register, full WBS, change control procedure, lessons-learned reference. These belong in supporting documents or in the project plan, not the charter. The one-page version preserves the six required PMBOK outputs (purpose, objectives, scope, requirements, milestones / budget, overall risk) and condenses the rest by reference.

Can the one-page format be used in PRINCE2?

Not for the full PID (PRINCE2 Project Initiation Documentation typically runs 15-50 pages and is mandated as such). But the Project Mandate (the trigger document at start of Starting Up) is often only 1-2 pages and can be authored on a one-page format. AXELOS PRINCE2 7 explicitly notes that management products can be 'right-sized' to project complexity, which gives cover for shorter formats on smaller PRINCE2 projects.

What is the difference between a one-page charter and a project poster?

They overlap heavily. A 'project poster' (Atlassian's term) is typically more visual (uses icons, larger fonts, can be printed and stuck on a wall). A 'one-page charter' is typically more textual (denser, follows the charter section structure). The content is similar; the visual presentation differs. Either format works for the same project size and complexity.

How do you handle stakeholder sign-off on a one-page charter?

Same as a longer charter, but faster. Print or PDF the one-page, sign-off block at the bottom (sponsor + PM names, date), distribute. Because the format is short, sponsors typically read it in the meeting rather than 'I'll review it and come back'. The faster sign-off is often the headline benefit of the one-page format.

Related on this site

A3 charter (one-page Lean version)Enterprise charter (when one page is not enough)Word template (full-format)PMBOK charter format Interactive charter generator (homepage)Scrum charter (lean by default)