Traditional Project Charter Template

---
title: "Traditional Project Charter Template"
methodology: "universal"
complexity: "advanced"
owner: "mirichard"
updated: "2025-08-05"
primary_principles: ["stewardship", "value-focus"]
secondary_principles: ["stakeholder-engagement"]
principle_rationale: "Secures sponsor agreement on predictive project objectives, scope and authority before detailed planning begins."
---


# Traditional Project Charter Template

## When to Use

- At initiation of a predictive project when authority and boundaries need sponsor agreement.
- When objectives, scope, assumptions, timeline, and stakeholders must inform detailed planning.

## When NOT to Use

- To authorize significant funding without the required business-case decision.
- Do not infer realized value from completed outputs, spending, or activity counts. See [Value equals output](../../../../../docs/principles/anti-patterns.md#value-output).

## Pairs Well With

- [Business Case Template](../../../../../domains/planning/templates/traditional/Traditional/Templates/business_case_template.md).
- [Traditional Project Management Plan Template](../../../../../domains/delivery/project-lifecycle/02-planning/project-management-plan/traditional-project-management-plan-template.md).

Selection context: Planning domain; universal methodology; advanced complexity. Match the situations above to project phase, risk, team size, and industry using the [decision-engine context model](../../../../../meta/architecture-research/800-801-context-assessment-model.md).

## Product-mode applicability

Use this existing artifact for a bounded initiative or increment inside product delivery, including project-within-product and product-within-project arrangements. Record the ongoing outcome hypothesis and product owner beside the bounded authorization. Identify funding/review authority, project-to-product decision boundaries and who accepts continuing ownership. A charter authorizes the project; it does not fund indefinite operations.

Apply the [delivery-mode decision guide](../../../../../docs/delivery/product-thinking-framework.md) before adapting the worksheet. Pure product operation need not create a new project record for every routine change; retain required governance and acceptance evidence.


## Purpose/Overview
This traditional project charter template provides a comprehensive framework for project initiation following established project management practices. It serves as the formal authorization document that defines project scope, objectives, and governance structure. The charter establishes clear boundaries and expectations for all stakeholders.

## Usage Instructions
1. **Stakeholder Input**: Gather requirements and expectations from key stakeholders
2. **Business Case**: Ensure the project charter aligns with the business case and strategic objectives
3. **Detailed Planning**: Use the charter as the foundation for detailed project planning
4. **Approval Process**: Obtain formal approval signatures before proceeding with project execution
5. **Baseline Document**: Treat the approved charter as a baseline for scope and change control
6. **Communication Tool**: Share the charter with all team members and stakeholders
7. **Reference Guide**: Use throughout the project for decision-making and scope clarification
8. **Change Management**: Update the charter through formal change control processes

## Project Information
- **Project Name**: [Project Name]
- **Project Manager**: [Name]
- **Sponsor**: [Sponsor Name]
- **Date**: [Date]
- **Version**: [Version Number]

## Project Purpose and Justification
[Describe why this project is being undertaken and how it aligns with organizational strategy]

## Project Objectives
### Primary Objectives
- [Objective 1]
- [Objective 2]
- [Objective 3]

### Success Criteria
- [Measurable success criterion 1]
- [Measurable success criterion 2]
- [Measurable success criterion 3]

## Project Scope
### In Scope
- [Item 1]
- [Item 2]
- [Item 3]

### Out of Scope
- [Item 1]
- [Item 2]
- [Item 3]

## High-Level Requirements
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

## Key Stakeholders
| Stakeholder | Role | Contact Information |
|-------------|------|-------------------|
| [Name] | [Role] | [Contact] |
| [Name] | [Role] | [Contact] |

## High-Level Timeline
| Milestone | Target Date |
|-----------|-------------|
| Project Start | [Date] |
| Phase 1 Complete | [Date] |
| Phase 2 Complete | [Date] |
| Project End | [Date] |

## Budget and Resources
- **Total Budget**: [Amount]
- **Key Resources**: [List key resources needed]

## Risks and Assumptions
### Key Risks
- [Risk 1]
- [Risk 2]

### Key Assumptions
- [Assumption 1]
- [Assumption 2]

## Approval
| Role | Name | Signature | Date |
|------|------|-----------|------|
| Project Sponsor | | | |
| Project Manager | | | |


*Template follows Traditional Guide project charter best practices*