Writing a Project Charter That Actually Aligns the Team
Most project charters fail quietly. They get signed, filed, and never referenced again because they read like a formality rather than an agreement. A charter earns its keep when it forces the sponsor, the delivery team, and the people who will be affected to agree, in writing, on what "done" means and who decides what. In a year like this one, with material lead times stretching and labour hard to hold onto, that shared understanding is worth more than any Gantt chart.
Think of the charter as the contract between the project and the rest of the organization. It authorizes the work, names the person accountable, and draws the boundary around what is in and out of scope. Below is a practical sequence for writing one that people will actually use.
What a charter must answer
Before you write a word, be clear that the charter exists to settle a small number of high-stakes questions. Keep it to two or three pages. If it grows into a plan, it stops being a charter.
Why are we doing this, and what business problem closes when we are done?
What does success look like, stated as outcomes a non-specialist could verify?
Who is the sponsor, who is the project manager, and what authority does each hold?
What is explicitly out of scope, so people stop assuming it is included?
What are the known constraints — budget, deadline, regulatory, supply — and the top risks?
How to draft it so it aligns people
Start from the problem, not the solution. Write one paragraph that a board member who has never heard of the project could understand. If you cannot explain the problem plainly, the team is not aligned yet — they are agreeing on a deliverable while disagreeing on why it matters.
Make success measurable and modest. Replace "improve efficiency" with something checkable: a date, a number, a condition. Two or three success measures beat ten aspirational ones. Vague objectives are where scope creep lives.
Name names, not departments. A sponsor is a person who can unblock funding and decisions, not a committee. Write the actual name. The same goes for the project manager and any key approver. Ambiguous accountability is the most common cause of stalled projects.
Write the out-of-scope list first. It is faster and more honest to agree on what you are not doing. This single section prevents more conflict than any other, because it surfaces silent assumptions before they become change requests.
State constraints and assumptions you can see. In 2022 that means being explicit about procurement lead times, price volatility, and whether the team is co-located or hybrid. An assumption written down is one you can revisit; an unwritten one becomes a surprise.
Confirm decision rights. Spell out who approves scope changes and at what dollar or schedule threshold. A charter that authorizes the work but leaves decision-making fuzzy will send every small choice back up the chain.
Getting it signed — and used
Walk the draft through with the sponsor and the two or three people most affected before you circulate it widely. The goal of that conversation is not approval; it is to find the sentence someone quietly disagrees with. Fix that sentence now and you have prevented a mid-project argument. Once signed, the charter becomes your reference point: when a new request arrives, you hold it against the agreed scope and outcomes rather than relitigating from scratch. That is the whole point — alignment you can return to, not a document you forget.
If you want a second set of eyes on a charter before it goes to your sponsor, XNM's program & project delivery advisory helps public-sector and capital-project teams set projects up so they hold together under pressure.