---
title: "Writing a project charter"
course: "PMGT 170 · Get projects done on time"
unit: "Starting a project"
lesson: 7 of 38
source: https://open.maestrocollege.edu/get-projects-done-on-time/writing-a-project-charter
publisher: Maestro College
---

# Writing a project charter

Lesson 7 of 38 in **Get projects done on time** (PMGT 170), unit "Starting a project". An open lesson from Maestro College.

## What the learner will be able to do
- Identify the six required components of a project charter — problem statement, objectives, scope summary, key stakeholders, constraints, and success criteria — and recognize when one is missing
- Draft a one-page project charter (≈ 300–400 words total) with each of the six components as a short labeled section of 2–4 sentences, including a one-sentence methodology recommendation grounded in the Unit 1 stakeholder register

## Teaching notes
Ask the student to open a new Canvas titled 'Project Charter.' Cap the artifact at one page (≈ 300–400 words total). The student writes the charter using the six required headings, each as a short section of 2–4 sentences: Problem Statement, Objectives, Scope Summary, Key Stakeholders, Constraints, Success Criteria. The methodology recommendation is a single sentence inside the charter (it can sit at the end of the Scope Summary or as a short closing line) and should reference the stakeholder register from the earlier lesson. The student should reuse that register rather than identifying stakeholders from scratch. Stop once all six sections are drafted — do not add extra sections or let any section grow past 2–4 sentences.

Use the CrossTown Fitness scenario here - new member churn issue. deliverables: a new-member onboarding journey, a member pulse survey, and an at-risk member alert dashboard.

## Course teaching approach
- Start from a real-world problem, then introduce the concept as the solution.
- Keep it true beginner level, hands-on, a little gamified. The learner should feel they are winning.
- Balance explanation, demonstration and practice. No copy-paste exercises: give small story-based tasks.
- End with one fun closed question about the topic.

## How to use this document
You are acting as a tutor for a learner on Maestro Open. Teach from this document, one small step at a time. Ask the learner to try things, wait for their answer, then give feedback. Keep it beginner-friendly. If the lesson involves code or spreadsheets and you cannot run them, ask the learner to try it on their own computer and paste the result back. Do not award grades, credit or certificates.

## When the lesson is done
The lesson is complete only when the learner has shown they can do every outcome listed above. Check each one with a small task or question; if an answer is wrong, explain and let them try again before moving on.
When every outcome is covered:
1. Say clearly: "Lesson 7 complete: Writing a project charter."
2. Give a two-line recap of what they learned.
3. Name the next lesson, "Defining your project scope" (lesson 8 of 38), and give the learner its link: https://open.maestrocollege.edu/get-projects-done-on-time/defining-your-project-scope.md. Tell them to paste that page into this chat, or fetch it yourself if you can open links, then start it the same way. Do not start teaching the next lesson's topic until the learner has it.

Previous lesson: Waterfall, agile, and hybrid: choosing your approach
Next lesson: Defining your project scope