Project charter: how to write one with template and examples

What is a project charter?

A project charter is a short, formal document that officially approves a project and gives the project manager authority to use company resources to get it done. It's the single source of truth for what the project will accomplish, who's involved, and what success looks like.

In plain terms, it's a written agreement that says: "Yes, this project is approved, here's what it covers, and here's who's running it." The project charter document is created right at the start – before detailed planning begins.

In project management, the PMI's PMBOK Guide treats the charter as the foundation document that kicks off the entire project lifecycle. Everything that follows – the plan, the tasks, the meetings – traces back to it.

To clear up a few common mix-ups, here's what a project charter is not:

• Not a detailed project plan: it's a high-level summary, not a task-by-task breakdown.

• Not written in isolation: the sponsor signs it, but the project manager usually drafts it.

• Not set in stone: it can be updated if the scope or goals change significantly.

Why a project charter matters before you start work

The purpose of a project charter is to align stakeholders, secure formal approval and prevent scope creep before any real work begins. Without one, teams often start strong only to realize halfway through that the sponsor expected something different.

A good charter gets everyone on the same page before a single task is assigned.

It also gives the project manager authority to move forward, allocate resources, and act as a reference point when priorities are questioned mid-project.

Here's why teams take the time to create a project charter:

• Formal authorization: the sponsor's signature grants official approval and budget.

• Clear accountability: defines who owns what and who makes final decisions.

• Shared understanding: everyone sees the same goals, scope and success criteria.

• Risk visibility: surfaces assumptions and constraints early, before they become problems.

In short, a charter helps you start faster and saves hours of back-and-forth emails once the work is underway.

Elements every project charter should include

Every project charter covers a core set of elements, even if the format varies by company. Knowing what's included in a project charter helps you fill one out confidently when it's your turn. Here are the sections you'll find in nearly every charter.

Scope and objectives

Scope sets the boundaries of what the project will and won't deliver. Objectives are the specific, measurable goals it aims to achieve – they answer the questions, "What are we solving?" and "What does success look like?"

A strong scope and objectives section includes the core problem you're addressing, the primary outcome (such as "Launch new product feature by Q3"), key deliverables, and explicit out-of-scope items. Calling out what the project won't cover is just as important as saying what it will – it's the simplest way to prevent scope creep later on.

Stakeholders and roles

This section lists everyone with a stake in the project and clarifies who can make which decisions. A stakeholder is anyone affected by or who can influence the project – from the executive sponsor to the end users of the final product.

Typical roles to document include the project sponsor (the executive who funds and approves the project), the project manager (responsible for day-to-day execution), core team members (the people doing the work) and key stakeholders (department heads, end users or partners who need to stay informed). While the project manager usually writes the charter, the sponsor signs it.

Timeline and milestones

The timeline gives a high-level view of when the project will happen – not a detailed schedule, but the major phases and key dates. A milestone is a significant checkpoint or deliverable, like "prototype complete" or "user testing finished."

A timeline section typically lists the project start date, three to five major milestones, and the target completion date. Detailed task scheduling belongs in the project plan – the charter just gives stakeholders a realistic picture of when to expect results.

Budget overview

The budget section summarizes the total expected cost and the main categories that money will go toward, such as labor, software or external vendors. It also names the funding source – which department or budget line is paying for the work.

This isn't a line-item budget. It's a high-level estimate that may also flag constraints, like "must stay under $75,000." When the sponsor approves the charter, they're committing this budget to the project.

Risks and assumptions

Risks are potential problems that could derail the project. Assumptions are things you're taking for granted, like "the vendor will deliver on time." Naming both early helps the team prepare for surprises instead of being blindsided by them.

Here are some quick examples:

• Risks: a key team member might leave, a vendor might be delayed, or regulatory approval might take longer than expected.

• Assumptions: stakeholders will give feedback within three business days, existing infrastructure can support the new feature, and the budget won't be cut mid-project.

This section isn't about pessimism – it's about realistic planning.

Success criteria

Success criteria define how you'll measure whether the project achieved its goals. They're specific and observable, not vague statements like "improve customer experience." Examples include "launch the new feature to 500 beta users by Oct. 15" or "complete migration with zero data loss and less than two hours of downtime."

When everyone agrees upfront on what "done" looks like, there's far less debate when the work wraps up.

Project charter vs. project plan vs. business case

These three documents are easy to mix up, so it helps to see them side by side.

The key distinction is simple: the charter authorizes the project and defines what success looks like, the plan breaks down how you'll get there and the business case explains why the project is worth doing in the first place.

Who writes and signs the charter?

So who writes a project charter? Usually, the project manager – often with input from the sponsor and key stakeholders. The sponsor, who is typically the executive funding the project, reviews and signs the final version.

The sponsor's signature is what gives the charter its authority.

Without it, the document is just a draft. With it, the project is officially authorized to proceed.

In larger organizations, a project management office (PMO) may provide a template or review the charter for consistency. If you're a first-time project manager, working closely with your sponsor on this document is completely normal – and expected.

Steps to create a project charter from scratch

Now that you know what goes into a charter, here's how to write one. These steps work whether you're starting from a blank page or filling in a template.

1. Gather inputs from the sponsor and the team

Before you write anything, gather information from the people who requested the project and those who'll do the work. A short kickoff conversation is often the fastest way to align on the sponsor's vision, high-level goals, known constraints and who needs to stay informed.

Taking time on this step keeps you from writing a charter in a vacuum – and from having to rewrite it later when you realize you missed something important.

2. Define objectives and success measures

Turn the sponsor's vision into specific, measurable objectives. Each one should answer: What will we accomplish, and how will we know we succeeded?

Here's the difference between vague and specific:

• Vague: "Improve customer experience."

• Specific: "Reduce average support response time from 24 hours to four hours by Dec. 31."

Write objectives in plain language and skip the buzzwords – clarity beats cleverness every time.

3. Outline scope, deliverables, and constraints

Spell out what the project will deliver (in-scope) and what it won't cover (out-of-scope). Listing out-of-scope items upfront is one of the easiest ways to prevent stakeholders from adding requests mid-project.

Also note any known constraints, such as "must use existing infrastructure" or "deadline cannot move." Clear boundaries keep the team focused on the work that matters.

4. Map stakeholders and governance

List every person or group with a stake in the project, then clarify each person's role and decision authority. A simple table format works well: name and role in one column, responsibility in another, and decision authority in the third.

Also, document how often stakeholders will receive updates – a weekly email or a monthly steering meeting, for example. Clear governance prevents confusion when disagreements come up.

5. Estimate timeline and budget

Create a high-level timeline with three to five major milestones and a target end date. This isn't a Gantt chart – it's a roadmap showing phases and key checkpoints, like "Phase 1 (Weeks 1-2): Requirements gathering" or "Phase 2 (Weeks 3-6): Development and testing."

For the budget, provide the total estimated cost and break it down into major categories such as labor, tools, and external services. The sponsor approves both – if either feels unrealistic, negotiate adjustments before finalizing.

6. Identify major risks and mitigations

Brainstorm potential risks with your team and sponsor. For each one, note a mitigation plan – what you'll do to prevent it or reduce its impact.

For example, if a key developer might leave mid-project, cross-train a second developer. If a vendor could miss their deadline, build a two-week buffer into the timeline. Listing risks doesn't mean the project will fail – it means you're planning realistically.

7. Review, refine, and secure approval

Share the draft with your sponsor and key stakeholders. A short review meeting, walking through the charter section by section, often catches misalignments before they become bigger problems.

Once everyone agrees, the sponsor formally signs and dates the document – and the charter becomes your official authorization to start work. Store it in a shared location, like a project folder or knowledge base, so the team can reference it throughout the project.

Tips to keep your charter clear and concise

Many charters become too long or too vague to be useful. The best ones are short, specific, and easy to reference at any point during the project.

A few simple habits go a long way:

• Use a one-page format: Stick to one or two pages whenever possible, using bullets and short paragraphs instead of dense prose. If your charter runs to five pages, it's probably covering too much detail.

• Write in plain language: Skip jargon and acronyms that not everyone will understand. "Help marketing and sales share customer data more easily" beats "operationalize synergies across cross-functional verticals" any day.

• Link to supporting documents: Reference the requirements spec, project plan, or risk register rather than cramming everything into the charter itself. Tools like MeisterTask let you attach documents directly to project boards, so everything stays centralized.

Free project charter template you can copy in MeisterTask

If you'd rather not start from a blank page, MeisterTask offers a ready-to-use project charter template you can copy and customize. It's structured around the same elements covered above – objectives, scope, stakeholders, timeline, budget, risks and success criteria – so you can fill in the blanks with confidence.

What makes the template especially useful is that it lives inside a MeisterTask project board. Once your charter is approved, each milestone can become an actionable task without switching tools or copying details across documents.

Project charter examples for different project types

Seeing real-world project charter examples helps the framework click. Here are four short examples showing how the same structure looks across very different projects.

Product launch

• Project name: Mobile app dark mode feature

• Objective: Launch dark mode on iOS and Android by Nov. 30

• Scope: Design, develop and test dark mode UI; update settings menu; create in-app tutorial

• Out-of-scope: Redesigning other features, tablet optimization

• Stakeholders: Product manager (sponsor), lead designer, two developers, QA lead

• Timeline: eight weeks

• Budget: $25,000 (internal labor)

• Success criteria: Live by Nov. 30, adopted by 30 percent of users in the first month, fewer than five critical bugs

• Key risks: App store approval delays (mitigation: submit two weeks early)

Marketing campaign

• Project name: Q4 holiday email campaign

• Objective: Drive a 15 percent increase in online sales in November and December

• Scope: Five-email series, graphics, automation setup, A/B testing

• Out-of-scope: Social ads, influencer partnerships, website redesign

• Stakeholders: Marketing director (sponsor), email manager, designer, copywriter

• Timeline: six weeks

• Budget: $8,000

• Success criteria: All emails sent on schedule, 25 percent open rate, $50,000 in attributed revenue

• Key risks: Designer unavailable (mitigation: line up a freelance backup)

IT system rollout

• Project name: Cloud storage migration

• Objective: Migrate company files from on-premises servers to the cloud by March 31

• Scope: Vendor selection, 10 TB data migration, permissions, staff training

• Out-of-scope: Files older than five years, third-party app integrations

• Stakeholders: IT director (sponsor), systems admin, two IT support staff, department heads

• Timeline: 12 weeks

• Budget: $15,000

• Success criteria: Zero data loss, less than four hours of downtime, 90 percent of staff trained within two weeks

• Key risks: Slow data transfer (mitigation: migrate during a low-usage weekend)

Process improvement

• Project name: Streamline invoice approval

• Objective: Reduce invoice approval time from 10 business days to three

• Scope: Map current workflow, identify bottlenecks, automate routing, update policies

• Out-of-scope: Changing accounting software, renegotiating payment terms

• Stakeholders: CFO (sponsor), finance manager, AP lead, IT support

• Timeline: 8 weeks

• Budget: $5,000

• Success criteria: Approval time drops to three days or less, zero invoices lost, 100 percent of the finance team trained

• Key risks: Resistance from approvers (mitigation: involve them in the design)

Keeping the charter alive during the project

A charter isn't a "write once and forget" document. To stay useful, it should remain a living reference you can return to whenever questions come up or decisions need to be made.

Update when scope changes

If the scope, timeline, or budget changes significantly, update the charter and have the sponsor re-approve it. Think of it like a contract – any changes to the agreement need both sides to sign off.

Minor adjustments don't require a full revision. But major shifts – a new deliverable, a deadline that slips by more than a few weeks, or a substantial budget increase – do.

Link sections to Kanban tasks

Once the charter is approved, break the milestones into specific tasks on a Kanban board. MeisterTask makes this easy: you can attach the charter to the project and create tasks that map directly to each milestone, so the team always sees how their daily work connects to the bigger picture.

The charter is the "what." The Kanban board is the "how."

Store version history securely

Save each version of the charter with a date stamp, especially if it gets updated during the project. Version history helps the team track how the project evolved and provides an audit trail for stakeholders.

MeisterTask's Notes feature lets you store the charter and related documents in a single, secure, centralized location. With ISO 27001 certification and full GDPR compliance, your project data is protected, which matters especially in regulated industries or the public sector.

Turn your charter into action with MeisterTask

You now know what a project charter is, how to write one, and what to include. A strong charter aligns everyone on goals, scope, and success before the work begins, which saves hours of confusion once the project is in motion.

Now comes the fun part: turning those milestones into tasks and getting things done. MeisterTask helps you do exactly that, with intuitive Kanban boards, customizable templates, built-in collaboration, and enterprise-grade security (ISO 27001 certified, GDPR compliant, and hosted in Germany).