Project Charter Template

Put sponsor, scope, success measures and decision rights on one page and get it signed, so the hard disagreements happen now, when they are cheap. The longer tools (team plan, budget, communication plan, quality criteria) are in the Optional sections.

The charter is codified practitioner standard (PMI) that is little tested directly: practice, not research. SMART is a convention; the goal-setting research under it is strong. OKRs and executive sponsorship are practitioner tools. The contingency range in the Optional budget is a rule of thumb.

Use it when:

• A project has several stakeholders, unclear scope or real money or time attached.
• You are about to start and want the sponsor to commit to the same picture of "done" as you.
• You lead or run a project for a client, an owner or a board and need something to sign.

Skip it when:

• You have not yet agreed that the problem is worth solving: frame it first with 8.4 Opportunity Framing.
• The work is a small task for one person: a short action list in 8.9 Action Plan & Kanban is enough.

A charter's claim is procedural, not scientific: forcing sponsor, scope, success measures and decision rights into one signed document moves the hardest negotiations to the start, when disagreement is cheap, instead of the middle, when it is expensive. That claim is codified practitioner standard (Project Management Institute, 2025), widely adopted and little tested directly, so treat the charter as a negotiation device. The goal machinery inside it is layered the same way: SMART (Doran, 1981) is convention without an evidence base of its own, resting on goal-setting research on specific versus vague goals (Locke & Latham, 2002), and objective cascades such as OKRs (Grove, 1983; Doerr, 2018) are practitioner tools built on that same research.

So the sections below are a negotiation agenda: the case, the exclusions, who decides what, and the signature. The limit: a charter nobody signed is a memo, and a signed one that nobody updates goes stale.

Keep the problem statement free of a solution. If you wrote "implement", go back to 8.4.

Strong answer: "Quotes take about six working days; customers go to competitors who answer in two. If we do nothing, we keep losing the small repeat jobs." (illustrative)

Illustrative example: the company, roles and figures are made up.

A Danish machine workshop loses small repeat jobs because quotes take about six working days. The sales coordinator drafts a charter with the managing director as sponsor.

Section 1: the problem is slow quotes, not "no quoting system". Consequence of inaction: continued loss of small repeat jobs.

Section 2: objective: median request-to-quote time from six to two working days by 30 November; must-have: standard parts only.

Section 3: out of scope: the pricing model and the ERP replacement. Deliverables: a quote template, a part price list, a short training session. Scope changes: requested from the project manager, approved by the sponsor.

Section 4: spending above 2,000 euro or a moved deadline goes to the sponsor. Biggest risk: estimators ignore the template; two of them help design it.

Section 5: accepted after four weeks at two days or less. The managing director signs.