What Is a Project Charter? Definition and Uses

A project charter is the short, signed document that authorizes an improvement project. On a single page it states the problem, the goal, the scope, the business case, the team, and the timeline — and it carries a sponsor’s signature. That signature is the point. An idea with a charter has resources, boundaries, and a leader accountable for results. An idea without one is a hallway conversation.

How it’s used

The charter is the first deliverable of the Define phase and the reference document for everything after it. The problem statement describes what is wrong in observable, measurable terms. The goal statement defines success without prescribing a solution. The scope names the first and last process step the team may touch, so the project cannot quietly swallow the whole company. The business case explains why this problem, why now, and what the organization gains by fixing it.

A charter is also a living document. At each tollgate review, the team and sponsor check it against what the data has since revealed. If the Measure phase shows the baseline is different from what everyone believed, the goal may need revision — formally, in writing, with the sponsor’s agreement. That discipline is what keeps a project honest.

A worked example

Consider an illustrative case: a regional furniture maker whose custom orders keep missing promised delivery dates. The charter’s problem statement reads: over the past six months, a significant share of custom orders shipped after the promised date, driving complaint calls and discounting. The goal: cut late shipments substantially within five months without adding expediting cost. Scope: from order confirmation to loading dock — supplier lead times and the sales quoting process are explicitly out. Team: a Green Belt lead, a scheduler, two shop-floor leads. Sponsor: the operations director, who signs it. Now everyone knows what the project is and, just as importantly, what it is not.

• Writing a solution into the charter — “implement new scheduling software” is a purchase order, not a problem
• Setting a goal with no baseline, which makes success unverifiable
• Defining scope so broadly that the project can never end
• Skipping the sponsor’s signature and hoping authority materializes later
• Filing the charter away instead of revisiting it at every tollgate

A charter is not the paperwork before the project — it is the project, stated plainly enough to be held to.

The charter is core vocabulary from the first belt onward. Our free White Belt program — about six hours, ending in a 30-question exam — introduces what a charter is and why sponsors sign it. Green Belt ($299, roughly 35 hours) is where you draft one yourself, defend it at a simulated tollgate, and revise it as the data talks back.