Project Charter Builder

What this tool does

CM8-235 builds project charters — the one-page authorisation document that starts a project properly. You enter the charter one element at a time: a purpose, each objective, each scope line, each milestone, each stakeholder. The tool assembles them into the classic one-page order, shows which of the ten sections are still missing, tracks which statements the sponsor has actually signed off, and prints the page. One file holds several charters — each element belongs to a named project.

Everything runs inside this single file. There is no account, no upload and no network request of any kind, so budgets, names and commercial reasoning never leave the computer you are using.

What a charter is

A project charter is the document that authorises a project: it says why the work exists, what it will produce, where its edges are, who is accountable, and how much may be spent — all on one page, signed by the person paying for it. It is the answer to the two questions that sink unchartered projects months later: "who said we could do this?" and "since when was that part of the job?"

The one-page discipline is the point. A charter that runs to thirty pages is a plan wearing the wrong name, and nobody with the authority to sign it will read it. One page forces every statement to earn its place, and it is the single most effective device ever invented against scope creep: when someone asks the project to absorb one more thing, the answer is not an argument — it is a page, held up, with the boundary already written on it and the sponsor's signature underneath.

The ten sections, and what good looks like

The tool models a charter as ten element types. A complete charter has something in every one; the section chart marks the classic must-haves in red until they exist.

• Section — What good looks like
• Purpose — One paragraph of business case: the problem as it stands today and why doing nothing is worse than doing this. If the purpose cannot be written, the project should not start.
• Objectives — Two to four measurable outcomes, each with a number and a date. See the next section — this is where most charters fail.
• In scope — The work explicitly included, named concretely enough that a stranger could tell whether a given task is inside it.
• Out of scope — The plausible extensions explicitly excluded. The most valuable lines on the page.
• Deliverables — Tangible outputs with an accountable person and, where it helps, a target date and acceptance criteria in the detail field.
• Milestones — A handful of dated checkpoints — enough to show the shape of the timeline, not a schedule. The tool refuses a milestone without a date; an undated milestone is a hope.
• Stakeholders — Named people with roles — at minimum the sponsor and the project manager. Departments cannot sign things.
• Risks — The two or three things already known that could derail it, stated honestly at the start rather than discovered in month four.
• Assumptions — What is being taken on trust, written down so that when one proves false everyone can see the ground moved — nobody has to be blamed for standing on it.
• Budget — The authorised amount, as one line or several. A charter budget is a ceiling, not an estimate: spending past it goes back to the sponsor.

Objectives must be measurable

"Improve quality" is not an objective; it is a wish, and a wish can never fail, which means it can never succeed either. "Cut machining scrap from 4% to 2% by the end of Q2" is an objective: it has a baseline, a target, a deadline and — written into the detail field — a measurement basis. Anyone can look at it a year later and say whether it happened.

The test is brutal and simple: is there a number in it? The tool applies exactly that test as you type an objective and tells you when the statement contains no number. It is a crude check — a date counts, and a number does not guarantee the objective is sensible — but a charter whose objectives all fail it is a charter that authorises nothing measurable, and the project it starts will end in an argument about what success meant.

Two to four objectives is the healthy range. One is usually too narrow to justify the spend; six or more means nobody chose.

Out of scope — the section that saves you

The in-scope list says what the project will do. The out-of-scope list is worth more, because it names the things people will assume are included and pre-empts each one while everyone is still calm. It deserves real thought, not a token line.

The technique is to imagine the requests before they arrive. Installing a CNC cell? Someone will assume night-shift working is part of it. Building a customer portal? Someone will assume it includes the mobile app, the migration of historical records, and support in four languages. Each of those may be a fine idea — as its own project, with its own budget. Write each one as an explicit out-of-scope line now, and the conversation in month three takes thirty seconds and stays friendly. Leave them unwritten, and each one arrives as a "small addition" that was "obviously always included", carrying no extra budget or time, and the project absorbs them until it fails. Scope creep is rarely one big change; it is a dozen unwritten assumptions, and this section is where they are killed cheaply.

A charter with an empty out-of-scope section is the reddest flag the tool can show — it means nobody has yet thought about where the edges are, and the edges are what the sponsor is signing.

The sponsor, and why unsigned charters are worthless

The sponsor is the person who pays — with money, people or political capital — and who has the authority to change or stop the project. Not the project manager, who runs it, and not a committee, which cannot be telephoned. One name.

An unsigned charter is a memo. Every power the document claims to grant — the budget ceiling, the scope boundary, the project manager's authority to make day-to-day decisions — exists only because the sponsor's signature put it there. Without the signature, the first executive who wants the scope changed simply changes it, and the page protects nobody. This is why the tool tracks sign-off per element and shows the percentage on a tile: a charter at 60% signed is not 60% authorised, it is unauthorised with paperwork in progress.

Getting the signature also does something quieter and more valuable: it forces the sponsor to actually read the page. Objections surface before the spending starts, which is the cheapest moment they will ever surface.

Charter versus project plan

The two documents are routinely confused, and merging them ruins both. The charter answers why, what and within which boundaries — one page, written once, changed rarely and only with the sponsor's signature. The plan answers how and exactly when — tasks, dependencies, resources and dates, owned by the project manager, revised every week without ceremony.

The charter's milestones are the meeting point: a handful of dated checkpoints that the plan then expands into hundreds of tasks. If the plan slips, the plan changes; the charter changes only if an objective, a boundary or the budget has to move — and that is a sponsor decision, not a scheduling one. A charter that needs updating every week has plan material in it; move that material out.

How to run a 45-minute chartering workshop

A charter written alone is one person's guess. The fastest way to a real one is a single short workshop with the sponsor, the project manager and the two or three people who know the work:

1. Purpose (10 minutes). The sponsor states the problem and why now, in their own words. Write it down close to verbatim — the sponsor's phrasing is what the sponsor will sign.
2. Objectives (10 minutes). Ask "how will we know it worked?" until every answer has a number and a date. Refuse adjectives.
3. Scope (10 minutes). Five minutes on what is in. Five minutes on the harder question: "what will people assume is included that is not?" Everything named goes on the out-of-scope list.
4. Deliverables and milestones (5 minutes). The tangible outputs and three to six dated checkpoints. Names against each.
5. Risks, assumptions, budget (5 minutes). "What already worries you?" and "what are we taking on trust?" Then the number, said out loud with everyone listening.
6. Read-back (5 minutes). Read the whole page aloud. Fix what makes anyone wince. Then ask the sponsor directly: "will you sign this?" If the answer is anything but yes, the gap it reveals is the most useful output of the meeting.

Enter the elements into the tool as they are agreed — the section chart makes it obvious what the room has not yet covered.

Keeping it current

Charters change rarely, but they do change: an objective is renegotiated, a boundary moves, the budget is raised. When that happens, do not edit history. Mark the old statement superseded and add the replacement as a new element for the sponsor to sign. The superseded rows stay on the record, and the charter table labels them — a year later, the trail of what changed and when is often the most instructive document the project has.

The status field carries each statement through its life: draft while it is being worded, proposed when it is in front of the sponsor, approved once signed, superseded when replaced. The sign-off checkbox is the fact of the signature; the status is where the statement sits in the process.

FAQ

Does every project need a charter? Every project big enough to argue about — as a rule of thumb, anything that crosses a team boundary, spends real money or runs longer than a few weeks. Below that, a confirmed email covers it. The discipline scales down: even the email is better with a purpose, a boundary and a name.

Who writes it? Usually the project manager drafts and the sponsor signs. The words can come from anywhere; the authority only comes from the sponsor.

How long should it take? A morning, including the workshop above. A charter that takes a month is being used to avoid starting.

Can one file really hold several charters? Yes — every element names its project, the stacked chart compares the charters side by side, and the approval table shows each one's state. The one-page charter table always shows the project with the most elements; filter to a single project to print that charter alone.

What if the sponsor will not sign? Then you have learned, at the cheapest possible moment, that the organisation has not actually decided to do the project. That is the charter working, not failing.

Is the budget figure a commitment? It is an authorisation ceiling. The detail belongs in a cost plan; the charter records the amount the sponsor has agreed may be spent, and passing it triggers a return to the sponsor, not a quiet overrun.

Saving your work

Elements, settings and the report header are written to this browser's local storage as you type, and the toolbar shows the time of the last save. That storage belongs to one browser on one computer: another browser, a private window, a second machine or a clean-up tool that clears site data will not have it.

Treat Export .json as the real save — one file containing everything, which Import .json restores anywhere. Export CSV gives you the register for spreadsheet work. Reset asks twice, then erases everything this tool has stored. There is no undo. A charter names people and money — treat exports accordingly.

Accuracy & disclaimer

This tool records agreements and counts them; the arithmetic is deliberately simple, and the judgements underneath it are all human. It cannot tell whether a purpose is honest, an objective achievable, a budget adequate or a signature freely given — and a charter is only as strong as the sponsor's willingness to enforce the boundaries it draws.

A charter is an internal agreement, not a contract, and nothing here is legal, financial or project-management advice. Organisations that use formal methodologies may have prescribed charter formats with additional required content — where one applies to you, follow it, and use this tool as the working record behind it.