Write a project scope statement that states inclusions and exclusions in unambiguous terms.
Project Management
Writing Project Charters and Project Initiation Documents
A focused course on writing the charter or project initiation document that gives a project formal authority, clear scope and a governance structure it can be managed against.
🗓️Duration5 training days
📚Content4 modules · 8 sessions
🎓On completionAccredited attendance certificate
About the programme
Course Overview
A project that starts without a clear charter or initiation document tends to accumulate scope, informal sponsors and conflicting expectations that surface only once delivery is under way. The charter, or project initiation document, exists to prevent that: it authorises the project, states what success looks like, sets out governance, and gives everyone something to point to when scope is challenged later. Writing that document well is the entire focus of this course, from the initial business justification through to the level of detail a sponsor can actually approve. Working section by section, covering objectives and scope, deliverables and exclusions, governance and roles, budget and tolerances, and high-level risks and assumptions, participants use real project scenarios rather than a blank template. Attention also goes to the conversations that should happen before the document is signed: testing assumptions with the sponsor, resolving scope ambiguity, and setting tolerances that make later escalation meaningful rather than automatic. The course finishes with a charter or initiation document structure participants can apply to their own project, plus the judgement to know which sections need real detail and which can stay brief.
Expected Learning Outcomes
Draft measurable success criteria that a sponsor can use to judge the project's outcome.
Define a governance structure with named roles, decision rights and escalation routes.
Set schedule, cost and scope tolerances that trigger escalation only when genuinely needed.
Capture high-level risks and assumptions in the initiation document rather than leaving them implicit.
Secure sponsor approval by resolving scope and budget ambiguity before the document is signed.
Distinguish detail that belongs in the charter from detail that belongs in later planning documents.
Who Should Attend
Project managers writing a project charter or initiation document for the first time.
Programme and portfolio staff who review or approve initiation documents before funding release.
Business analysts and project sponsors involved in defining project scope and justification.
Practitioners of stage-gated project management methodologies responsible for producing a project initiation document.
Project management office staff who set the initiation document standard for their organisation.
Consultants and contractors who must produce a charter acceptable to an external client.
Course Modules
Select any module to see its sessions and points.
01From Business Justification to Charter
2 sessions · 8 points
Session 1Establishing the Business Justification
- State the problem or opportunity a project addresses in terms a sponsor recognises immediately.
- Summarise options considered and the reasoning for the option the project will deliver.
- Link the project's objectives to a specific organisational goal or strategic priority.
- Identify the sponsor and confirm they have the authority the charter will rely on.
Session 2Defining Scope, Deliverables and Exclusions
- Write a scope statement that lists deliverables and explicitly states what is out of scope.
- Translate a sponsor's verbal expectations into deliverables with agreed acceptance criteria.
- Identify scope boundaries most likely to be contested later and resolve them before sign-off.
- Cross-check scope statements against the budget and schedule to confirm they are consistent.
02Governance, Roles and Success Criteria
2 sessions · 8 points
Session 1Setting Governance and Decision Rights
- Define project roles, including sponsor, project manager and steering group, with decision rights.
- Set an escalation route that states which decisions each role can make without further approval.
- Establish a meeting and reporting cadence appropriate to the project's size and risk.
- Name the process for approving changes to scope, budget or schedule once the project starts.
Session 2Writing Measurable Success Criteria
- Draft success criteria that separate project output from the benefit the organisation expects.
- Write acceptance criteria specific enough that delivery can be objectively judged against them.
- Distinguish must-have criteria from criteria that can be traded off if constraints tighten.
- Agree success criteria with the sponsor in writing before planning work begins.
03Budget, Tolerances and Risk
2 sessions · 8 points
Session 1Setting Budget and Schedule Tolerances
- Estimate an initial budget range appropriate to the confidence available at initiation.
- Set cost and schedule tolerances that trigger escalation without inviting constant approval requests.
- State assumptions behind the budget so later variance can be traced to a specific cause.
- Align funding release points with project stages or major decision gates.
Session 2Capturing Risks and Assumptions at Initiation
- Identify the highest-impact risks and assumptions known at the point of initiation.
- State each assumption in a form that can later be tested and confirmed or corrected.
- Assign early ownership for the risks most likely to affect scope, cost or schedule.
- Decide which risks belong in the charter and which are better tracked in a later risk register.
04Approval, Communication and Document Control
2 sessions · 8 points
Session 1Securing Sponsor Approval
- Prepare a sponsor conversation that surfaces scope and budget objections before formal sign-off.
- Present trade-offs between scope, time and cost in terms a sponsor can decide on quickly.
- Handle a sponsor request to compress the schedule without silently absorbing the risk.
- Record formal approval in a way that is unambiguous if scope is challenged later.
Session 2Maintaining and Communicating the Charter
- Communicate the approved charter to the project team in a form they will actually reference.
- Update the charter through formal change control rather than informal renegotiation.
- Use the charter as the reference point when resolving a scope dispute mid-project.
- Archive charter versions so the current baseline is always clear to the whole project team.
What the participant receives
4 course modules
A structured syllabus
8 training sessions
across 5 days
32 detailed points
Applied, detailed content
Accredited attendance certificate
On completing the programme
Complete your registration
We will contact you within one business day to confirm.
Ready to start?
Reserve your seat and start building the skill.