Project Charter: What It Is and How to Write One in an Hour (Without Falling Asleep)

Moving house without a plan has a certain drama. The movers arrive, look at you and say, "So, what are we taking?" You wave a hand in a circle that includes the sofa, the garden gnome, an unclear number of boxes marked "misc," and possibly the neighbor's ladder. Three hours later, the truck is full, the budget has doubled and somebody is crying over a lamp.

A project without a charter is that move. Everyone is working hard, nobody agrees on what "done" looks like, and the sponsor discovers in week six that the project includes a garden gnome. The fix is not a heavier process. It is one page, written early, read aloud and signed by the person who pays.

This guide explains what a project charter is, how it differs from its cousins, the ten parts it needs, three tiny examples (a website, an office move and a restaurant menu), the smells of a bad charter, what to do after you sign and how to draft one in about an hour. In the middle there is a builder that writes your first draft and warns you when something is missing. It continues what I started in the first part of my PMBOK series, where a made-up clinic gets a business case and a charter. Here we make the charter itself the star.

What a project charter is, and what it is not

A project charter is a short document that authorizes a project and sets its boundaries. It says that the project exists, why it exists, what it is meant to achieve, who is in charge, how much money and time it may use and what it will and will not include. When the sponsor signs it, the project manager has permission to start and a reference point to return to when things get fuzzy, which they will.

It is not a plan. The plan comes later and explains how the work will be done, by whom and in what order. It is not a contract with a supplier, which is a different kind of promise. It is not a business case either, which argues whether the project should be done at all. Here is the family, in plain words:

• The business case says why this is worth doing, comparing options, costs and benefits. It supports a decision.
• The project charter says yes, we are doing it, and this is the box we are doing it in. It records the decision.
• The scope statement describes in detail what is included, often after the charter.
• The project plan explains how, with tasks, dates, owners and risks.

For small projects, the charter and the scope statement are often one page. That is fine. What matters is that the answers exist, in writing, before the work starts.

The ten parts of a useful charter

You will see charter templates with forty fields. Ignore them. Ten answers cover almost everything, and each one has a question you can ask a sponsor over coffee.

1. Project name. Short, memorable and not "Project Phoenix 2.0 Final v3." A name people can say without sighing.
2. Purpose. Why does this project exist? One or two sentences, in the language of the business, not of the project.
3. Objective. What will be true when we are done? With a number and a date. "Reduce the time to answer a new inquiry from two days to one hour by March 31."
4. Success criteria. How would a stranger check that we succeeded? Two or three measures that do not require your opinion.
5. Scope: in. What is included? The main deliverables, in a short list.
6. Scope: out. What is not included? The most underrated line of the page. This is where tomorrow's arguments are born, so write them down today.
7. Budget and deadline. How much and by when? Including a contingency, and whether the deadline is a wish or a wall.
8. Key stakeholders and roles. Who is the sponsor, who is the project manager, and who else matters? A RACI chart can go with it, and a stakeholder map feeds the list.
9. Main risks and assumptions. What could go wrong, and what are we taking for granted? Three to five lines. The longer version lives in a risk register.
10. Authority and approval. What can the project manager decide alone, what needs the sponsor and who signs? For example, "The project manager may approve spending up to $2,000 per decision. Anything that changes scope, budget or the deadline goes to the sponsor."

Notice what is missing: no Gantt chart, no list of fifty tasks, no organizational philosophy. Those belong in the plan. The charter is the box. The plan is what you do inside it.

Three tiny examples

Here are three charters, deliberately tiny, so you can see the shape. They are made-up examples.

A website relaunch. Purpose: the current site confuses visitors and loses inquiries. Objective: a new site live by May 15 that increases qualified inquiries from 20 to 35 a month by August 31. Success: inquiries per month, measured with the contact form, and the page that answers "what do you do" understood by five test users in under ten seconds. In: new design, rewritten key pages, redirects, analytics. Out: a blog, a new logo, a store. Budget: $9,000 plus 10 percent contingency. Sponsor: the owner. PM: the marketing lead. Authority: up to $500 per decision. Risks: content arrives late, the old site's links break.

An office move. Purpose: the lease ends on June 30, and the team has outgrown the space. Objective: the team of twelve is working in the new office on Monday, June 24, with no more than one day of downtime. In: furniture, internet, phones, moving day, address changes. Out: a redesign of the layout beyond the standard plan, and any art. Risks: the internet provider's installation date, the landlord's final inspection.

A restaurant menu change. Purpose: costs are up and the menu has too many slow dishes. Objective: a new menu of 18 dishes on October 1 that lifts the average margin from 61 to 66 percent by December 31. In: recipes, costing, staff training, printing. Out: the wine list and the interior. Risks: a supplier price change, and a chef who loves the sixth dish on the old menu.

Each of them fits on a page and ends with a question: who signs? Which brings us to the most important part of the whole exercise.

The charter is a conversation

The signature is the least important part. The conversation that produces it is the point. Sit down with the sponsor, bring a blank page and a pen and ask the ten questions out loud. Do not fill in a form alone and email it. When you ask "What is out of scope?", the sponsor will pause, look at the ceiling and say, "Well, I thought the new phone system was part of this." Wonderful. You found that in week one instead of week eight.

A good rhythm for the first draft, about an hour:

• Minutes 0 to 15: interview the sponsor. Ask the ten questions. Listen more than you write.
• Minutes 15 to 35: write the draft. One page. Use the sponsor's words where you can.
• Minutes 35 to 50: read it to two people who matter. Someone who will do the work and someone who will be affected. Ask: "What is missing, and what surprises you?"
• Minutes 50 to 60: fix it and send it for signature. Keep the first version, so you can see later how the project moved.

For the people who will use the project's result, a stakeholder conversation is not a courtesy. It is a risk control, as I discuss in stakeholder mapping and in how to keep an executive sponsor engaged.

The smells of a bad charter

After enough projects, you can smell a weak charter from across the room. Here are the usual suspects.

• The Mood Objective. "Improve customer experience." Improve from what to what, by when? A mood cannot be checked.
• The Everything Scope. The "in scope" list has fourteen items and the "out of scope" list is blank. Scope creep has already moved in and brought its luggage.
• The Budget TBD. "To be determined" is fine on a Tuesday and fatal on a charter. Put a range and a date by which it becomes a number.
• The Committee Sponsor. Five sponsors means no sponsor. Choose one name.
• The Ghost Project Manager. "TBD." If nobody is named, nobody is in charge, and the project will find a leader the hard way: whoever panics first.
• The Authority Fog. Nobody knows what the project manager may decide. Result: every small decision becomes a meeting.
• The Unsigned Charter. It was "approved in the meeting," which means nobody can find it later.
• The Novel. Eleven pages, with a section on corporate values. Nobody read page three, and that is where the real risk was hiding.

If you recognize two of these in your current project, congratulations: you have found the cheapest improvement of the year.

After the signature: keep it alive

A charter that is signed and filed has done half its job. Three habits do the other half.

1. Reread it at each checkpoint. At every major milestone, ask: is the project still inside the box? If it has drifted, either bring it back or change the charter openly, with a new signature.
2. Run changes through one door. A request that changes scope, budget or deadline gets a description, a price and an approval before any work starts. There is a free change request log, and the idea is in how to say yes, no and not yet to scope creep.
3. Record decisions. A decision log turns "who decided that?" into a thirty-second answer.

Charters in the wild: construction and small business

Two quick notes from my own corner of the world.

In construction, the equivalent of a charter is often called the owner's project requirements, together with a budget and a schedule target. It is the document the designer, the builder and the owner's representative keep returning to. I describe that role in what an owner's representative is, and the full life of a building in project management in construction.

In small business, the best charter is the project card I use in Project Focus: a name, an owner, an outcome, a number and a deadline on a single note. It is a charter in miniature, and it has rescued more small projects than any big framework I know. A card is enough when the project is small. When the project touches money, other teams or a customer, the full page earns its place.

Which size do you need? Card, page or plan

Not every project deserves the same amount of paper. A rough guide I use:

• A project card (five lines: name, owner, outcome, number, deadline) for small improvements that one person can finish in a few weeks with little money at stake.
• A one-page charter (the ten parts above) for projects that touch money, customers, several people or a deadline that matters. This is the sweet spot for most small-business projects.
• A charter plus a plan for large or risky projects, such as a building, a system change or an opening. The charter stays one or two pages, and the plan grows around it.

If you are unsure, start with the page. It is easy to shrink a page to a card and painful to discover you needed a page after the money is spent.

What if the sponsor will not sign?

It happens, and it is a gift, because it tells you something important early. The usual reasons are worth knowing:

• "I am not sure what I want yet." Then the project is not ready, and the right next step is a smaller one: a business case, a prototype or a conversation with customers.
• "I do not want to be held to a number." Politely ask what number they would be comfortable with. A range and a review date often unlocks it.
• "Just get started." Offer a two-week start with a mini charter: one objective, one deadline and one sentence of scope, to be replaced by the full page in week two.
• Nobody has the authority. Then you have found the real project, which is finding the person who does.

A charter that cannot be signed is a risk report in disguise. Treat it as one.

Draft yours: the charter builder

The builder below turns your answers into a one-page draft, ready to copy. It also warns you when the objective has no number, when nothing is out of scope, when the sponsor is missing or the success criteria are empty. Fill in a real project, even a small one, and read the result aloud. If it sounds silly, it is probably because the project was never defined. That is the whole point of the exercise.

Interactive tool

The charter builder

Loading the tool…

What to do this week

Pick one project that is already running and has never had a charter. Spend an hour with the sponsor. Ask the ten questions and write the answers on one page. Pay special attention to "out of scope," since that is the line that will save you the most. Then sign it, put it where the team can see it and reread it at your next checkpoint. If you would like a hand building a charter, running a project with this kind of discipline, or being the owner's voice on a building, that is what I do with Project Focus, and you can tell me where you are stuck on the contact page.

A downloadable Excel and Word version of the charter, with a worked example, is on the publishing calendar for the toolkit.

What was the strangest thing that ended up in the scope of a project you worked on? Tell me in the comments.

More tools. The decision log, the stakeholder map and the risk register are free in the toolkit.

Frequently asked questions

What is a project charter?

A project charter is a short document, usually one or two pages, that authorizes a project and defines its purpose, objectives, scope, budget, deadline, main risks, roles and the authority of the project manager. It is approved by the sponsor and becomes the reference point for the whole project.

Who writes the project charter?

The project manager usually drafts it, with the sponsor, who owns the money and the result, approving it. The best charters are written in a conversation with the sponsor and reviewed by a few key stakeholders before signature.

What is the difference between a project charter and a project plan?

The charter says what the project is, why it exists, what it includes and who is in charge, in a page or two. The plan explains how the work will be done, with tasks, dates, owners, costs and risks in much more detail. The charter comes first and the plan lives inside its boundaries.

Does a small project need a charter?

A small project needs the answers, not necessarily a formal document. A project card with a name, an owner, an outcome, a number and a deadline is a charter in miniature. If the project touches significant money, other teams or customers, write the one-page version.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Useful Made me smile Go deeper on this

Be the first to react.

Comments

Loading comments…

Leave a comment

NameEmail (required, never shown)

What was the strangest thing that ended up in the scope of a project you worked on? Post comment

Your name and email create a small profile that shows you are a real person. The email is never shown. The first time, I send you a confirmation link, and every comment is reviewed before it appears. Please keep it respectful and leave links out.