The Project Charter & Kickoff

Before any real work starts on a project, someone writes a project charter — a short document (often a single page) that officially authorises the project and gets everyone aligned on the basics. It answers the boring-but-essential questions up front: what are we doing, why, who’s involved, and how will we know it worked? It feels like a formality on day one. It becomes priceless on day forty, when memories have drifted and people are quietly building different things.

The charter is the reference you point back to whenever scope, goals, or ownership get fuzzy. It’s not a detailed plan and it’s not a contract full of legal clauses — it’s a shared starting point that everyone has seen and agreed to. When a debate breaks out about whether something is “in” or “out,” the charter is what settles it without anyone having to win an argument from memory.

What’s actually in it

A good charter answers six things, and no more — brevity is the point.

• Objective — why the project exists, in plain language. Not “build a portal,” but “cut the time customers wait for a quote from three days to one.”
• Scope — what’s explicitly in and, just as importantly, what’s out. The “out” list prevents the slow drift covered later in this course.
• Stakeholders — who’s involved: the sponsor who pays and decides, the team who builds, and the users who’ll live with the result.
• Timeline — the key milestones and target dates, not a day-by-day schedule.
• Budget — the money and resources approved for the work.
• Success criteria — how you’ll measure “done well.” If you can’t say what success looks like, you can’t tell when you’ve reached it.

The sponsor’s sign-off is what actually authorises the project. Until someone with budget authority signs, you don’t really have a project — you have an idea people are interested in. That distinction matters: it’s the difference between “we should look into this” and “this is funded and happening.”

The kickoff meeting

The kickoff is the meeting where the team walks through the charter together for the first time. It’s not just an announcement — it’s where everyone reads the same page, asks “wait, is X in or out?”, and surfaces disagreements while they’re still cheap to fix. A good kickoff ends with no one wondering what they signed up for.

A charter is cheap insurance. Five minutes of “here’s what we agreed” beats weeks of “I thought we were building something else.”

A quick scenario

A team spends six weeks building a reporting dashboard. At the demo, the sponsor says, “Where’s the export to Excel? That was the whole point.” Nobody wrote down “the whole point.” A one-line success criterion — “users can export any report to Excel in one click” — would have caught that on day one. That single sentence in a charter can save a month of rework.

How to use it

You don’t need to be a project manager to benefit from charters. When you join something new, ask: “Is there a charter or a one-pager I can read?” If there isn’t, that’s a useful signal in itself — it often means scope and success aren’t agreed yet, and confusion is coming. You can even write a lightweight one yourself: a few bullets covering objective, scope, who decides, and what success looks like, then sent round with “Does this match everyone’s understanding?” That small act prevents a surprising amount of pain, and it makes you the person who brings clarity instead of the person caught in the confusion later.

Spot the charter element

Read each statement and decide which part of a charter it belongs to, then tap a card to flip it and check your answer.

Sort the charter elements

Drag each item into the correct section of the charter — or tap an item, then tap a section. Hit Check placement when you’re done.