Skip to main content
ControlRoom

Project charter: scope, stakeholders and success criteria

A project start becomes governable when the objective, scope, stakeholders and success criteria sit in a short document: the project charter. In this lesson we write one for the example test-bench delivery.

This is lesson 2 of 10 in the project management basics course. In lesson 1 we distinguished a project from ordinary work and set out the objective, the constraints and the roles. Those answers now become a short start-up document: the project charter.

We stay with the illustrative example of the test-bench delivery: a mid-sized mechanical company in Northern Italy delivers a custom test bench into a client laboratory. Approved budget: €120,000. Planned duration: six months. These are sample figures, not a real case.

Why start-up needs a short document

A kick-off in which you introduce the team and open a shared folder is useful, but it is not enough. If the objective and the scope live only in the conversation, someone will retell them differently every week. The charter is there to prevent that: a short, written, approved reference from which the plan, the budget and the reviews all start.

It is not the detailed plan. The WBS, the Gantt chart and the line-by-line budget come in later lessons. The charter answers earlier questions: what we are doing, for whom, within which limits, how we will know it succeeded, and who is allowed to decide what.

One or two pages are enough. If the document grows into a pack, it is already mixing start-up with planning.

What a project charter should contain

A minimum structure, fit for an industrial delivery such as the example, looks like this:

SectionQuestion it answers
ObjectiveWhat must we achieve, in one sentence that can be closed?
Scope (in / out)What is included, and what is not?
StakeholdersWho has an interest, who decides, who can block, who accepts?
Success criteriaHow will we judge, at the end, whether the objective was met?
Constraints and assumptionsWhich limits and which assumptions do we make visible from the start?
Project manager authorityWhat can they decide on their own, and what goes back to the sponsor?
Reference milestonesWhich start-up and delivery steps are already known, before the detailed Gantt?

The project manager drafts the charter; the sponsor approves it. The client counterpart should at least recognise the objective, the scope and the acceptance criteria. When a decision changes the boundary, the charter is updated. The first version should not be left untouched while the work drifts.

Scope: in, out, and how a change is decided

Scope is the boundary of the work, not a list of every task. It is written in two columns: in and out. The «out» column prevents more friction than almost anything else, because it makes visible at the start what the client or the team might otherwise treat as included.

A scope change is not an accident: it is a decision. A request arrives, its effect on time and cost is made visible, and the sponsor (and, if it touches the client, the client counterpart) accepts or declines it. A record of that decision will save an argument from memory months later. The change process itself is the subject of lesson 10. At start-up, one rule is enough: no change to the boundary without an explicit yes and a stated effect on time and cost.

Stakeholders: who has an interest and who can block

A stakeholder is anyone who has an interest in the project or can influence its result. This is not a courtesy list. It tells you who must be kept informed, who must decide, and who can stop a delivery if they are involved too late.

On the example delivery the usual profiles are the internal sponsor, the project manager, design, purchasing, the workshop, the client technical counterpart and, if involved, client quality. One line each is enough: their interest, what they expect, what they have to approve. When two roles overlap, the guide to a technical team responsibility matrix can clarify them without stretching the charter.

Success criteria you can actually observe

Success criteria say how the result will be judged, not only what was done. «The client is happy» is a wish. «The bench is accepted against the agreed test protocol» is a criterion. You can deliver everything in scope and still miss a criterion, for example if the client technicians have not been trained.

Write a small number of them, make them observable, and tie each one to a date or to an acceptance record. These are the same criteria that will later feed the project review. For that meeting, the ten questions of a project review that decides remain the reference format.

Example: a charter for the test-bench delivery

Illustrative example, not a real project. A one-page draft charter can look like this.

Objective. Design, build, install and have a test bench accepted in the client’s laboratory within six months, against an approved budget of €120,000, according to an agreed test protocol, and train two of the client’s technicians.

Scope — in. Mechanical and electrical design; test sequence; build; installation and commissioning at the client; training of two technicians; as-built documentation.

Scope — out. Civil works at the client; changes to the client’s production line; a multi-year maintenance contract; additional instruments not in the original specification.

Main stakeholders.

StakeholderInterestWhat they approve or accept
Internal sponsor (operations)Delivery within the time and cost constraintsObjective, budget, scope changes
Project managerA single frame for plan, costs and decisionsDay-to-day coordination, escalation to the sponsor
Design / engineeringA technical solution that matches the specificationDesign choices and technical documents
PurchasingComponents on time and within the line budgetSuppliers and orders
Workshop and installationA build and an installation that can actually be doneBuild feasibility and the installation plan
Client technical counterpartA bench their laboratory can useInterim deliveries and the acceptance test
Client qualityConformity with the test protocolFormal acceptance

Success criteria (illustrative figures).

  • The bench is accepted against the agreed test protocol by the end of month six.
  • Two client technicians have completed training and can run the test sequence.
  • As-built documentation is handed over at acceptance.
  • The cost forecast stays within the approved budget of €120,000, or any variance has been approved in writing.

Constraints and assumptions already visible. The client laboratory is available only in the last three weeks. Some components have an eight-week lead time. The budget is already split by line, as in the project budget template.

Project manager authority. They can re-sequence work inside the approved milestones and budget, and they can deal with the suppliers already chosen. These go back to the sponsor: a budget increase, a different acceptance date, a widening of scope, or a supplier added outside the agreed list.

Reference milestones (before the detailed Gantt). Kick-off and charter approval; specification freeze; order of long-lead components; in-house test; installation at the client; acceptance.

This page is already enough to start the work. The WBS in lesson 3 will be built from here, not from a task list collected in a meeting that had no boundary.

Mini-exercise and checklist

Write the charter for your own project, or complete the test-bench one, in one or two pages. Then check:

  • ☐ The objective can be closed with a yes or a no.
  • ☐ Scope has an «in» column and an «out» column.
  • ☐ Each stakeholder has an interest and an approval or acceptance role.
  • ☐ Success criteria are observable, not only desirable.
  • ☐ The tightest constraints and assumptions are written down, not left implied.
  • ☐ It is clear what the project manager can decide and what goes back to the sponsor.
  • ☐ The sponsor has a date on which to approve the document.
  • ☐ A change rule is stated: no change to the boundary without an effect on time and cost.

If a line is still empty, the kick-off is not closed yet. That is the conversation to have now, not halfway through the delivery.

Previous and next lesson

Lesson 1 defined the project, the objective, the constraints and the roles. Lesson 3, planned for 24 November, moves on to the WBS: how to break down the test-bench work from this charter. The draft of lesson 3 is not in preview yet.

To put the start-up frame into a workspace, open ControlRoom Free or start from the resources and the guide How to get started with ControlRoom Free.

Compare with your real process: your first project starts free.

Start freeSee ControlRoom use cases