Write a one-page project charter with a complete library-booking example, practical field guidance and an approval and scope-boundary check.
The workshop develops the need, objective, scope, funding basis and authority one step at a time. A filled illustrative charter and a final field checklist help readers build and review their own authorisation page.
Start with authorisation
A useful charter tells people why the project exists and what has actually been approved. Group the information so a reader can follow the decision trail. A feature request becomes more useful when its underlying problem is visible. An objective should describe a result the sponsor can assess.
The proposed pilot aims to reduce booking calls from 120 to 80 or fewer weekly during a four-week review after rollout, while preserving an assisted booking route.
Set the scope boundary
The charter should make a useful commitment without pretending every detail is known. A clear result gives planning a better starting point. An early amount needs context about what it covers and how certain it is. Milestones should identify useful readiness or decision points.
Proposed points are authorisation, agreed requirements, pilot readiness and four-week benefit review. Readiness is targeted six weeks after authorisation, subject to the stated access assumptions.
Clarify roles and authority
The charter should help the project manager know which decisions they can make. A few significant assumptions and risks are more useful than vague confidence. An authorised project still needs relevant users and operating teams involved. Use this compact illustrative example as a structure to adapt.
Deliver booking, cancellation, staff training and support handover for three rooms. Exclude payments and other branches. Target readiness six weeks after authorisation. Funding cap: $18,000, subject to the stated estimate basis.
Review the draft with its readers
Test the charter as a decision document. A draft becomes an authorisation record through the actual governance process. The charter should remain a reference for the project’s purpose and boundary. Use the fields as prompts, then verify the finished page with the right people.
Funding basis and limit; major milestones; sponsor and project manager; operational owner; delegated authority and escalation route.
Contents
- Start with authorisation
- Choose a practical page structure
- Describe the business need
- Write a measurable objective
- Set the scope boundary
- Name deliverables and acceptance
- Show a credible funding basis
- Choose high-level milestones
- Clarify roles and authority
- Record the critical unknowns
- Include the people affected
- A filled one-page charter
- Review the draft with its readers
- Record the approval decision
- Use the charter during change
- Your blank-page drafting check
Using the PDF
Each numbered page contains an explanation, an original worked situation and a practical action. The bookmarks navigate the learning pages. A templates advertisement follows content page 5 and a Coursera Plus advertisement follows content page 15. The entire advertisement image is linked. Promotional links may earn Coursya a commission. A purchase is optional.
Frequently asked questions
Who is this guide for?
Write a one-page project charter with a complete library-booking example, practical field guidance and an approval and scope-boundary check.
How can I practise the ideas?
Follow the running case, work through the page actions and use the PDF bookmarks to revisit a topic. The final learning pages help you apply the decisions to your own project.
What does the download contain?
The PDF contains 19 pages, including 16 numbered learning pages, a cover and two linked advertisements. The book is written in English.


