The Project Charter: How to Authorize the Work and Align It to Strategy
AI can draft a project charter in minutes, but deciding why the project should exist, what belongs in it, and who has the authority to lead it still takes human judgment. Here’s how to get those decisions right before major commitments are made.
A sponsor drops a project on you on a Tuesday, half in a hallway and half in a follow-up email: “We need this by Q3. Can you run it?” No kickoff, no signed document, no ceremony. That moment, easy to miss, is where the work of developing a project charter begins.
A charter turns that loose ask into authorized work. It settles the questions a project can’t survive without: Why are we doing this? Who’s accountable for the result? Do you have the authority to request, coordinate, and use organizational resources to get it done? Leave those questions open and your project becomes significantly riskier.
A charter doesn’t answer every question the project will face. It establishes the business need, the objectives and the high-level scope — often before stakeholders fully realize where they differ. If the foundation is wrong, the effects compound all the way to delivery.
What’s changed is the speed. AI drafting tools now turn rough notes into a structured charter in minutes, so the blank page is no longer the hard part. The hard part is judgment: deciding whether the project deserves to exist and securing the authority to lead it. That still belongs to you. Here’s how to write a charter that does both.
What is a project charter?
A project charter is a document issued by the project initiator or sponsor that formally authorizes the project and gives the project manager the authority to apply organizational resources to it. That word, authority, is the whole point. A charter turns a proposed project into work the organization has agreed to undertake and sets the high-level terms for leading it.
A useful charter typically includes, or clearly references:
- The business need. The problem or opportunity the project exists to address.
- Objectives and success criteria. What a win looks like, in measurable terms.
- High-level scope. What’s in and out, at the altitude you can see from the start.
- Key stakeholders. The sponsor, customer, and roles who shape or approve the work.
- Assumptions and constraints. What you’re taking as given, and the limits on budget, time and resources.
- The sponsor and project manager. Who authorizes the work, and who runs it.
The format can vary, but a charter should answer four questions: Does the sponsor agree the project should exist? Do they know who's leading it? Have they defined what authority the project manager has to make decisions and apply organizational resources? And is that authorization captured somewhere you can point to?
The project charter at a glance
Keep this within reach. The core elements of a charter and what each one is really for:
| Element | What is captures | Why it matters |
|---|---|---|
| Business need | The problem or opportunity | Justifies the project’s existence |
| Objectives | Measurable target outcomes | Defines what “done well” means |
| Success criteria | How you’ll judge the result | Sets the bar before work starts |
| High-level scope | What’s in and out of bounds | Anchors against scope creep later |
| Key stakeholders | Sponsor, customer, delivery roles | Names who shapes and approves the work |
| Assumptions | What you’re taking as given | Flags what needs sponsor validation |
| Constraints | Limits on budget, time, resources | Sets realistic boundaries early |
Start with authority, not paperwork
The first job of a charter is to establish authority, so treat the assignment conversation as the moment to secure it. When a sponsor hands you a project, ask the questions that define the work: What’s the business need? What does success look like? What resources can I request or direct, and where do my decisions stop?
These questions start a negotiation over the shape of the project and the reach of your authority, and it positions you as a strategic thinker rather than an order-taker. Ask for a clear authorization before you commit significant resources to the work.
What if the sponsor won't give you a straight answer on where your authority ends? That happens, especially in matrixed organizations, and you can't let it slide. Write down the authority you're assuming — the calls you'll make on your own and the ones you'll escalate — and ask the sponsor to confirm or correct it. If the boundaries of your authority are unclear, treat silence as a reason to pause and confirm.
The sponsor only has to authorize the charter, not write it. Drafting is often the project manager’s job: write it, then get the sponsor’s approval. What matters is that someone with authority commensurate to the scope, impact, and investment that the project represents stands behind it.
Write it early, with the information you have
Write the charter at the start, before you have all the answers. It’s created during initiation, before significant resources are committed, so it will always rest on partial information. Keep the early version concise, as long as it clearly authorizes the work.
“We’re not done with requirements” is not a reason to wait. A good charter carries high-level requirements that focus the detailed work to come. If the requirements really are unknown, narrow the scope: charter a first phase that only authorizes discovery, with its own business need and budget ceiling. Later phases may require revised authorization or, in some organizations, a new charter based on what you learn.
Keep the charter alive across phases
A project charter is not something to file away after initiation. Revisit it as the project moves through phases to make sure the original authorization, scope, and success criteria still hold. Moving into a new phase does not automatically require a new charter; in most cases, the original charter remains in place. Whether a phase transition requires additional approval depends on the organization’s governance and the authority delegated to the project manager.
Some transitions need the sponsor back in the room. The trigger is concrete: when a change means you can no longer deliver what the charter promised, or it breaks the budget ceiling or the definition of done, it’s time to revisit and potentially revise the charter. The same goes when a run of change requests has subtly rewritten the project scope to the extent that the original charter no longer reflects the approved project direction. A refreshed charter refocuses the team on one vision, records the change officially, and reconfirms executive support when you need it most.
Use AI to draft; use human judgement to align
Modern tools can accelerate charter development without replacing the work that matters most. PMI Infinity™, our AI tool grounded in PMI standards and body of knowledge, can help transform rough notes into a structured first draft covering purpose, objectives, scope, stakeholders, assumptions, constraints, and success criteria. What AI can't do is align stakeholders, validate strategic intent, or secure authorization. Those responsibilities still belong to people.
Not sure how to frame the ask? Use Infinity’s Project Charter Generator Agent, or paste this prompt into Infinity and fill in the brackets with what you know:
Draft a project charter for [project name]. Use the information below and clearly flag anything missing or unclear.
- Business need / problem: [describe the need or opportunity]
- Project purpose: [what the project is intended to achieve]
- Objectives: [measurable outcomes]
- High-level scope: [in-scope items]
- Out of scope: [excluded items]
- Key stakeholders: [sponsor, PM, stakeholders]
- Assumptions: [known assumptions]
- Constraints: [budget, timeline, resources, compliance, etc.]
- Risks: [known risks]
- Milestones: [high-level timeline or key dates]
- Success criteria: [how success will be measured]
- Approval needs: [who must approve the charter]
Create a concise, review-ready charter with sections for business need, project description, stakeholders, assumptions, constraints, risks, milestones, success criteria, and approval requirements. Also identify any gaps that should be validated before sponsor review.
The structure gives Infinity enough information to generate a usable first draft. Asking it to identify gaps, missing information, or unclear assumptions can also help surface weak inputs early, before the charter reaches a sponsor.
The gain isn’t only speed. Charters are shaped from scattered inputs across functions such as marketing, IT, and finance. A tool like Infinity can consolidate those notes into one draft, then flag what’s weak: vague objectives, undefined metrics, missing exclusions, unvalidated assumptions. A practical rhythm is draft, gap-check, refine, incorporate feedback, then run a final validation pass.
Remember: AI can't authorize the project. It will draft, structure, and pressure-test the charter, but the approval, and the accountability behind it, belongs to a person. Drafting was always the fast part anyway. The real work comes after — reconciling stakeholders and earning the signature — and Infinity won't chase that sign-off for you. Treat its output as a strong first draft to sharpen.
The skill that matters most: alignment
The hardest part of chartering is making sure the project truly fits the organization’s strategy. The charter is an early chance to check strategic alignment, before the cost of changing course gets much higher. Run this quick pass before you take any charter to a sponsor:
1. Trace it to strategy. Line the business need up against a strategy or vision document. If they don’t connect, clarify the rationale, realign the charter, or escalate whether the project should proceed.
2. Make objectives measurable. Where possible, rewrite anything vague as an outcome you can verify at the end. "Improve the customer experience" becomes "Cut average support-ticket resolution time from 48 to 24 hours by Q3."
3. Draw the scope line. State what’s out of scope as clearly as what’s in. Exclusions prevent arguments later.
4. Name the authority. Be explicit about the decisions you can make and the ones that need the sponsor.
5. Confirm the yes. Get authorization in writing, even a one-line reply. A verbal approval may occur in practice, but the charter should be documented and the authorization recorded in writing whenever possible.
Fundamentals that carry the charter
The tools and templates will keep changing. These principles don’t:
- Authority is the point. A charter that doesn’t grant clear authority — for a project to exist, and for you to lead it—isn’t a charter, however polished.
- High-level beats over-detailed. An early charter should be brief. Detailed planning generally follows charter approval.
- Keep it current when it counts. Revisit the charter when major changes affect scope, objectives, authority, funding or success criteria.
- Alignment is the real deliverable. Sometimes, the best thing a charter can do is stop a misaligned project before it starts.
None of this requires a heavy process. A charter can be a page, an email, or other formal record, as long as it clearly authorizes the project and establishes who is leading it and what decisions they are empowered to make. Get it right and it keeps working long after kickoff: it holds the team to a specified goal, gives you standing when priorities shift, and reminds everyone why the project earned its place. Write it early, keep it honest when big things change, and it will keep doing that work for you.
Tags: Strategy | Project Management | PMBOK | Artificial Intelligence | Leadership
Build Your Project Charter with PMI Infinity
PMI Infinity is your AI that speaks project management, delivering project-specific guidance and agents grounded in PMI standards.
Quick answers to common project charter questions
Who writes the project charter?
The project charter is often drafted by the project manager, though in some organizations the sponsor, PMO, business lead, or project initiator may draft or co-develop it. What makes it a charter is that someone with the authority to start the project approves it.
What’s the difference between a project charter and a project plan?
The charter authorizes the project and captures the business need, objectives, and high-level scope The project plan goes deeper into details on how the work gets done. The charter is short by design; the plan is not.
Does a charter have to be a formal document?
No. It can be a template, a signed work order, or a sponsor email, as long as it clearly authorizes the project and captures the essential high-level information. The format is flexible; the authorization is not.
How long should a project charter be?
A project charter is usually concise and high-level, often just a few pages. If the document starts going deep into execution details, it may be drifting into a project plan.
Can AI write a project charter?
AI can produce a strong first draft from your inputs and flag gaps, weak objectives, and unvalidated assumptions. It can’t authorize the project. The decision, approval and accountability stay with a person.
About the Author
Project Management Institute
Author | PMI
Read More from PMI Blog
Related Insights
How Project Managers Spot Red Flags and Get Ahead of Them
Learn how project leaders spot red flags like scope creep and resource issues—and communicate risks to the C-suite before projects go off track.
You May Also Like
Certification
Project Management Professional (PMP)®
3+ years of experience leading projects
Certification
PMI Certified Professional in Managing AI (PMI-CPMAI)™ Bundle
No experience required
Invigorate your career with the gold standard certification for leading AI projects and driving real business impact.
AI in Project Management
AI is impacting the future of project management and changing how professionals approach projects. Learn how to leverage AI in project management today.