Project Charter Word Template: Copy-Paste Structure With Filled Examples (2026)

Copy-Paste Word Structure

Select the text below, paste into a new Word document, then apply Heading styles per the hierarchy section that follows.

PROJECT CHARTER

Project Name: <Name>
Version: 1.0
Date approved: <Date>
Sponsor: <Name, Role>
PM: <Name, Role>

1. PROJECT PURPOSE
<One paragraph, 50-150 words. Why this project exists.>

2. OBJECTIVES AND SUCCESS CRITERIA
2.1 Primary objectives (3-5)
- Objective 1: <SMART criterion>
- Objective 2: <SMART criterion>
- Objective 3: <SMART criterion>

2.2 Guardrail metrics (optional, 1-3)
- Guardrail 1: <metric the project must not violate>

3. SCOPE
3.1 In scope
- <Verb phrase, what the project includes>
- <Verb phrase>

3.2 Out of scope
- <Verb phrase, what the project explicitly excludes>
- <Verb phrase>

4. KEY DELIVERABLES
- <Deliverable 1>: <acceptance criteria summary>
- <Deliverable 2>: <acceptance criteria summary>

5. MILESTONES
M1. <Name>: <Target date>
M2. <Name>: <Target date>
M3. <Name>: <Target date>

6. BUDGET
Base estimate: <amount>
Contingency reserve (10-15%): <amount>
Total approved envelope: <amount>
Drawdown rules: <see budget section reference>

7. TOP RISKS
- Risk 1: <Description>. Impact: <H/M/L>. Probability: <H/M/L>. Owner: <Name>. Mitigation: <Action>.
- Risk 2: <Description>. Impact: <H/M/L>. Probability: <H/M/L>. Owner: <Name>. Mitigation: <Action>.

8. TEAM AND DECISION AUTHORITY
Sponsor: <Name, Role>
PM: <Name, Role>
Key roles: <Name, Role; Name, Role>
Decisions:
- <Decision type>: Responsible / Accountable / Consulted / Informed split.

9. APPROVAL
Sponsor signature: ____________________ Date: __________
PM signature: ____________________ Date: __________

Word Heading Hierarchy

Apply Word's built-in Styles, not bolded text. The Styles pane is the difference between a working charter and a document that crashes the accessibility checker.

Style	Use for
Heading 1	Document title only (e.g. 'Project Charter: <Project Name>').
Heading 2	Major sections (Purpose, Objectives, Scope, etc.).
Heading 3	Sub-sections within a major section (e.g. 'In scope' and 'Out of scope' under Scope).
Heading 4	Use sparingly. Most charters do not need this level.
Body Text	Default paragraph style. Use Word's built-in style, not custom formatting.
Caption	For figure / table captions. Often skipped; matters for accessibility and Word's automatic tables of figures.

Six Word-Specific Conversion Tips

1. Use Word's Built-in Styles

Apply Heading 1 / 2 / 3 via the Styles pane, not by bolding text. Tables of contents, navigation pane, and accessibility readers all depend on style use.

2. Avoid Manual Numbering for Sections

Word's automatic numbering (in heading styles or via SEQ fields) renumbers automatically when sections move. Manual numbering breaks at first reorder.

3. Embed Risk Register and Stakeholder List as Tables

Native Word tables are readable; pasted Excel often breaks formatting. If the register has more than 20 rows, link to a separate document.

4. Approval Block at the End

Sponsor and PM signature lines at the document end. Use a 2-column table with Name / Date / Signature columns. Avoid digital-signature plugins unless your organisation has standardised.

5. Track Changes for Sponsor Review

Enable Track Changes before sending to the sponsor. Accept / reject at sponsor's review, save the version, archive the redlined version separately.

6. Save As PDF for Final Distribution

PDF preserves formatting across devices. Keep the .docx as the authoritative editable version; PDF is for distribution only.

Word vs Google Docs vs Confluence vs Notion

Different tools fit different organisational patterns. The table below covers the four most common.

Microsoft Word

Pros: Universal. Print-friendly. Track Changes for review. Familiar for legal / compliance / regulated teams.

Cons: Version control is fragile. Collaboration is sequential not real-time. Heading styles often misused.

Best fit: Regulated industries, projects with external sign-off, government and enterprise PMOs that require audit-trailed documents.

Google Docs

Pros: Real-time collaboration. Built-in comment threads and suggesting mode. Version history. Easy share permissions.

Cons: Less polished print output. Some enterprise compliance teams reject for sensitive content. Heading hierarchy enforcement is weaker than Word.

Best fit: Startup and mid-market teams. Cross-functional projects with many reviewers. Iterative drafting before sponsor sign-off.

Confluence

Pros: Wiki structure (cross-links to related pages). Native macros for tables, decisions, and roadmaps. Easy to surface in project portfolios.

Cons: Sign-off / signature workflow weak. Print output mediocre. Less familiar for non-tech teams.

Best fit: Software / tech teams with Atlassian-aligned toolchain. Internal-only charters with no external approval requirement.

Notion

Pros: Flexible block-based editor. Database views for portfolios of charters. Templates and re-use are easy.

Cons: Enterprise / compliance maturity newer than Word or Google. Sign-off workflow lightweight.

Best fit: Startup PMOs, design-led teams, project-collection use cases where the charter sits inside a wider knowledge base.

Frequently Asked Questions

Where can I download the Microsoft Word template?

The plain-text version on this page is copy-paste-ready into Word: select all, paste into a new Word document, then apply Heading 1 to the title, Heading 2 to numbered sections, and Heading 3 to sub-sections. The Microsoft Office documentation provides template galleries; however, most published 'project charter templates' on third-party sites are over-engineered marketing assets. The plain-text structure above plus Word's built-in styles is sufficient for a working charter.

Should I use Word or Google Docs for a project charter?

Depends on the organisation. For external sign-off (sponsor outside your immediate team, legal review, regulated industry), Word is preferred because of Track Changes maturity and PDF preservation. For real-time collaborative drafting and review, Google Docs is preferred. Many teams draft in Google Docs, finalise in Word for sponsor sign-off, then archive the signed PDF.

What heading hierarchy should the charter use?

Use Word's built-in Heading 1 for the document title only, Heading 2 for the 8-15 major sections, and Heading 3 for sub-sections. Avoid Heading 4 unless absolutely necessary. The hierarchy is what generates a usable Table of Contents and what screen readers use for navigation. Plain bold-text 'headings' break both.

How do I add a signature block in Word?

Insert a 2-column table at the end of the document. Row 1: 'Approval'. Row 2 left cell: 'Sponsor: <Name>', right cell: 'Signature: ____________________ Date: ____________'. Row 3: same structure for PM. Avoid Word's built-in 'Signature Line' feature unless your organisation has standardised on digital signatures (DocuSign, Adobe Sign, etc.); the built-in feature is fragile across versions.

Does Microsoft publish an official project charter template?

Yes, via the Microsoft Office template gallery, but the published templates lean toward consumer / small-business use and are not aligned to PMBOK structure. For PMBOK alignment, use the structure on this page or PMI's published examples (PMI member access required). For PRINCE2 alignment, AXELOS publishes the official PID format under licence.

Should the charter be a single document or multiple files?

Single document for the charter itself. Separate files for the supporting artefacts: full risk register (Excel or risk management tool), stakeholder list (Excel or CRM), detailed budget forecast (Excel or finance system), detailed project plan (Project, Smartsheet, Jira). The charter references these by name and location, but does not reproduce their content. This keeps the charter readable and the supporting documents up-to-date.

How do I make the Word charter accessible (WCAG / Section 508)?

Six things. (1) Use built-in Heading styles for hierarchy. (2) Add alt text to all images and charts (right-click image > Edit Alt Text). (3) Use real tables not text-aligned-with-tabs for tabular data. (4) Set document language properties (File > Info > Properties). (5) Use sufficient colour contrast (minimum 4.5:1 for body text). (6) Run Microsoft's built-in Accessibility Checker (Review > Check Accessibility) before distribution. This brings the charter to WCAG 2.1 AA conformance, which is the standard for federal government and most enterprise procurement.

Related on this site

One-page charter (shorter format)Enterprise charter (15-section format)PMBOK charter format Filled charter examples How to write a charter Interactive charter generator