2.9.2: How to Write a Project Charter That Aligns and Authorizes
- Page ID
- 49255
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)How to Write a Project Charter That Aligns and Authorizes
A C-Bay Practicum Planning Guide for Milestone 1
Introduction: What Is a Project Charter—and Why It Matters
A Project Charter is more than a formality—it’s the first official signal that a project exists and is authorized to move forward. It sets the tone, defines the rules, and names responsibilities before any work begins.
For planners, it’s a leadership moment. For clients, it’s a trust document.
In Milestone 1, you will produce a Project Charter for the University College of Medical Sciences (UCMS) that:
- Defines the problem
- States the project’s intent
- Establishes scope and constraints
- Outlines success measures
- Names critical stakeholders
Done well, it becomes the foundation for all subsequent planning.
What a Project Charter Is—and Is Not
A Project Charter is:
- A formal authorization of project work
- A structured agreement between client and planner
- A scope-defining and stakeholder-aligning document
- A reference for all future planning phases
A Project Charter is not:
- A detailed work plan
- A list of tasks or a Gantt chart
- A technical design document
- A brainstorming outline
Think of it as a boundary-setting and alignment tool—defining what the project is, why it matters, and who must be involved.
Why the Charter Comes First
Without structure and agreement, early-stage ambiguity leads to rework, delays, scope creep, and friction. A strong charter:
- Creates shared understanding
- Names key priorities and boundaries
- Establishes a planning rhythm
- Gives the team permission to proceed
Clients value charters for their clarity and accountability before budgets are spent or timelines promised.
The Standard Structure of a C-Bay Charter
1. Project Title, Prepared By, Date, and Version
Professional header with project name, your/team name, date, and version number (e.g., Version 1.0).
2. Purpose / Objective
State why the project is needed and what it will achieve, from the client’s point of view.
Example:
UCMS relies on disconnected spreadsheets and paper records, creating compliance risk and inefficiency. This project will define a roadmap for a centralized digital system supporting curriculum planning, stakeholder coordination, and regulatory alignment.
3. Business Context and Alignment
Show how the project aligns with UCMS’s mission and operational needs.
Example:
This project supports UCMS’s operational modernization goal ahead of its accreditation review, ensuring compliance, improved reporting, and enhanced user experience.
4. Scope Overview
Clarify inclusions and exclusions for this phase.
Example:
Scope includes stakeholder interviews, requirements documentation, workflow mapping, and high-level timeline definition. Technical development is excluded.
5. Project Constraints
List the most critical constraints, noting which is fixed.
Example:
Planning timeline is fixed—design documentation must be approved by July 15. Other constraints: HIPAA compliance, existing IT infrastructure, SME availability.
6. Success Criteria
Define 3–5 specific, measurable outcomes.
Examples:
- Stakeholder interviews completed and summarized
- Workflows documented and validated
- Technical requirements outlined in report
- Charter signed by all parties
- Delivered on time and within scope
7. Stakeholders and Roles
List individuals, titles, roles, and influence types.
Example:
- Dr. Alok Varun – Dean of Admissions – Sponsor
- Dr. Alex Serman – CIO – Reviewer, Technical Lead
- Dr. Wendy Sheen – Director of PMO – Governance Lead
- Sukhjit Singh – Project Manager – Execution and Coordination
8. Risks and Assumptions
Name at least two risks and two assumptions.
Risks:
- Delays in scheduling stakeholder interviews
- Conflicting system expectations between departments
Assumptions:
- UCMS will provide access to sample curriculum data
- Stakeholders available within project timeline
9. Major Deliverables and Timeline
List deliverables with target dates.
Example:
- Draft Requirements Document – April 10
- Workflow Maps – April 20
- Final Planning Package – May 5
- Charter Sign-Off – May 10
10. Approval Section
Include name, title, signature, and date for authorization.
Common Mistakes to Avoid
- Writing from your perspective instead of the client’s
- Using vague goals (“improve operations”)
- Leaving stakeholder roles generic
- Over-promising scope or under-defining success
Final Thought: Your First Act of Leadership
Ask yourself:
If handed to a project team next week, would they know what to do, who to talk to, and what to aim for?
If yes—you’ve succeeded. If no—revise until it leads with clarity.