Project Charter Generator

Write a project charter your sponsor will actually sign. Fill in the objectives, scope, milestones, team, and risks, watch the charter build itself, and export it to Word or PDF.

Load an example:
Format:

Project Details

Project name
Sponsor
Project manager
Start date
Target end date
1
The problem, why now, and the business case
2
1.
2.
3.
3
In scope
•
•
•
•
Out of scope
•
•
•
•
•
•
•
•
•
•
•
Budget
Resources
Assumptions
•
•
Constraints
•
•

Leave empty to use the sponsor and project manager. Signature and date lines are added to the Word and PDF export.

Preview
Project Charter

Marketing Website Redesign

Project sponsor: Maria Lopez, VP Marketing
Project manager: Sam Carter
Timeline: Nov 2, 2026 - Mar 12, 2027

1. Background & Purpose

Our marketing site was built in 2021 and no longer reflects the product. Mobile visitors make up 58% of traffic but convert at half the desktop rate, key pages take over 4 seconds to load, and every copy change needs a developer. The redesign gives marketing a fast, mobile-first site they can update on their own.

2. Objectives

  1. Raise mobile conversion rate from 1.2% to 2.0% within 60 days of launch
  2. Cut median page load time to under 2 seconds on the top 20 pages
  3. Let marketing publish landing pages without developer help by the Feb 15 launch

3. Scope

In scope
  • New visual design and page templates
  • Migration of 40 existing pages and the blog
  • Headless CMS setup and editor training
  • Analytics and conversion tracking
Out of scope
  • Changes to the product app or signup flow
  • Translating the site into other languages
  • Rebranding (logo, brand colors)

4. Deliverables

  • Approved design system and page templates
  • Production site running on the new CMS
  • Redirect map for every legacy URL
  • Editor guide and recorded training session

5. Success Criteria

  • Mobile conversion rate at or above 2.0%
  • Lighthouse performance score of 90+ on key pages
  • Organic traffic within 5% of pre-launch levels after 30 days
  • Marketing ships 3 landing pages without engineering in the first month

6. Milestones

MilestoneTarget date
Discovery completeNov 13, 2026
Design approvedDec 11, 2026
Content migratedJan 29, 2027
LaunchFeb 15, 2027
Post-launch reviewMar 12, 2027

7. Team & Stakeholders

NameRoleResponsibility
Maria LopezSponsorApproves scope and budget, final sign-off
Sam CarterProject managerPlan, schedule, and weekly status reports
Priya NairLead designerDesign system and page templates
Tom BeckerFrontend developerBuild, CMS integration, performance
Content teamContent ownersCopy updates and page migration

8. Budget & Resources

Budget: $48,000 (design $18k, development $24k, CMS license $6k per year)

Resources: 1 designer, 2 developers at 60%, 1 content writer, agency support for QA

9. Risks

RiskImpactMitigation
Organic traffic drops after URL changesHighFull redirect map, crawl before and after launch, watch Search Console daily for two weeks
Content migration takes longer than plannedMediumFreeze new content two weeks before launch, migrate the top 20 pages first
Endless design feedback loopsMediumOne consolidated feedback round per milestone, sponsor breaks ties

10. Assumptions & Constraints

Assumptions
  • The current hosting contract can be ended in March
  • The product team provides updated screenshots by January
Constraints
  • Launch must happen before the spring campaign on March 1
  • Total budget cannot exceed $50,000

11. Approval

NameRoleSignatureDate
Maria LopezVP Marketing (Sponsor)____________
Sam CarterProject Manager____________
Charter check
8 / 8
  • Names a sponsor who owns the outcome
  • Has a start and target end date
  • Objectives are measurable (include a number or date)
  • Says what is out of scope
  • Defines success criteria
  • Every milestone has a date
  • Every risk has a mitigation
  • Someone signs off

What Is a Project Charter?

A project charter is the document that officially starts a project. In one to three pages it explains why the project exists, what it has to achieve, where its boundaries are, who is involved, and who has the authority to approve it. When the sponsor signs the charter, the project manager gets a clear mandate to spend the budget and pull in the people listed in it.

The charter is not the project plan. It does not list every task or schedule every week. Its job is alignment: getting the sponsor, the team, and the stakeholders to agree on the goal and the limits before anyone starts work. Most scope fights later in a project come from a charter that was never written, or one that skipped the out of scope list.

What to Include in a Project Charter

  • Background and purpose - the problem or opportunity, and the business case for solving it now.
  • Objectives - two to five measurable goals. A number and a date in each one makes them checkable.
  • Scope - what the project will deliver and, just as important, what it will not.
  • Deliverables and success criteria - the outputs you hand over, and how you will judge the result after launch.
  • Milestones - the handful of checkpoints the sponsor cares about, with target dates.
  • Team and stakeholders - who is involved and what each person owns. For detailed ownership, pair the charter with a RACI matrix.
  • Budget, risks, assumptions, and constraints - the money and people committed, what could go wrong, and the hard limits.
  • Approval - the names and signatures that authorize the project.

How to Write a Project Charter in 6 Steps

  1. Start with the why. Write the background in plain language. If you cannot explain the business case in four sentences, the project is not ready.
  2. Turn the why into objectives. Rewrite each goal until it has a number and a deadline. The charter check above flags objectives without one.
  3. Draw the scope line. List what is in, then list at least three things that are out. The out of scope list is the one you will point to in month two.
  4. Name the people. One sponsor who owns the outcome, one project manager who runs it, and everyone else with a clear responsibility.
  5. Set milestones and surface risks. Pick four to six checkpoints. For each big risk, write the mitigation now, while it is cheap.
  6. Review and sign. Walk the sponsor and key stakeholders through the charter, adjust, and collect signatures. Export it to Word or PDF for the record.

Project Charter Examples

Use the example buttons at the top of the generator to load a complete charter for a marketing website redesign, a sales CRM migration, or a mobile app MVP. Each one shows measurable objectives, a real out of scope list, risks with mitigations, and an approval table - edit any field to adapt it to your own project, or switch to the one-page format to see the lean version.

From Signed Charter to a Running Project

A charter is a snapshot. The day it is signed, the work moves somewhere else - and that is where most charters are forgotten. Download the milestones and deliverables as CSV and import them into t0ggles to turn them into tasks with due dates on a shared board. Track milestones and dependencies on the Gantt chart, send status reports from real progress, and keep the charter itself pinned as a note so the team can always check the scope line.

Free Project Charter Templates

Prefer to write it by hand? Copy one of these templates into your doc or wiki.

One-Page Project Charter

The lean version most teams actually read. Fits on a single page.

PROJECT CHARTER - [Project name]

Sponsor: [Name, title]
Project manager: [Name]
Timeline: [Start date] - [Target end date]

1. Background & Purpose
[Why this project exists: the problem, the opportunity, and the business case in 2-4 sentences.]

2. Objectives
1. [Measurable objective with a number and a date]
2. [Measurable objective]

3. Scope
In scope:
- [What the project will deliver]
Out of scope:
- [What it will not touch]

4. Success Criteria
- [How you will know the project succeeded]

5. Milestones
- [Milestone] - [Target date]
- [Milestone] - [Target date]

6. Team & Stakeholders
- [Name] | [Role] | [Responsibility]

7. Approval
[Name, title]   Signature: ____________   Date: ________

Full Project Charter (PMI-Style)

Every section the PMBOK guide recommends, for larger or regulated projects.

PROJECT CHARTER - [Project name]

Sponsor: [Name, title]
Project manager: [Name]
Timeline: [Start date] - [Target end date]

1. Background & Purpose
[Problem statement and business case.]

2. Objectives
1. [Specific, measurable, time-bound objective]
2. [Objective]

3. Scope
In scope:
- [Included work]
Out of scope:
- [Excluded work]

4. Deliverables
- [Deliverable]

5. Success Criteria
- [Measurable success criterion]

6. Milestones
- [Milestone] - [Target date]

7. Team & Stakeholders
- [Name] | [Role] | [Responsibility]

8. Budget & Resources
Budget: [Amount and breakdown]
Resources: [People, tools, vendors]

9. Risks
- [Risk] | Impact: [Low / Medium / High] | Mitigation: [Plan]

10. Assumptions & Constraints
Assumptions:
- [Assumption]
Constraints:
- [Constraint]

11. Approval
[Name, title]   Signature: ____________   Date: ________
[Name, title]   Signature: ____________   Date: ________

Agile Project Charter

Vision, mission, and working agreements for a Scrum or Kanban team.

AGILE PROJECT CHARTER - [Project name]

Vision
[One sentence: the future this project creates.]

Mission
[What the team will build, and for whom.]

Success Criteria
- [Outcome metric]
- [Outcome metric]

Scope Boundaries
In: [What the team owns]
Out: [What the team will not do]

Team & Roles
- Product owner: [Name]
- Scrum master / delivery lead: [Name]
- Team: [Names]

Working Agreements
- Sprint length: [2 weeks]
- Definition of done: [Criteria]
- Ceremonies: [Planning, daily standup, review, retro]

Release Plan
- [Release or increment] - [Target date]

Risks & Dependencies
- [Risk or dependency] - [Plan]

Frequently asked questions

Keep the charter alive

This generator gives you a signed starting point. A t0ggles board keeps it moving - milestones, owners, dependencies, and progress in one place your whole team can see. Try it free - no card required.

Start Free