---
ref_id: PR01
ref_type: Process
ref_name: "Develop Project Charter"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.1.6.1"
companion_ref_shortcode: PG-APG-4.1
related_skills:
  - SKL-01-01
  - SKL-01-02
  - SKL-02-01
  - SKL-02-02
related_artifacts:
  - A01
  - A02
  - A04
  - A05
  - A14
file_path: "reference/processes/PR01-develop-project-charter.md"
---

# PR01 — Develop Project Charter

**Ref ID:** PR01
**Type:** Process
**PMBOK8 Source:** §2.1.6.1
**Version:** 1.0.0

---

## Definition

Develop Project Charter is the process of developing the document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.

## Key Characteristics

- **Formal Authorization:** Establishes the project's formal existence and registers it under organizational governance.
- **Resource Authority:** Grants the project manager recognized authority to commit organizational resources to project tasks.
- **Strategic Alignment:** Directly links the project's purpose and outputs to the sponsoring organization's strategic goals and business case.
- **Pre-Planning Boundary:** Sets the high-level boundary, scope, and financial authorization limits before detailed planning begins.
- **Sponsorship Commitment:** Solidifies the commitment and expectations of the project sponsor or authorizing entity.

## PMBOK 8 Context

Under PMBOK 8, the project charter is an essential element of the **Governance Performance Domain**. It initiates project governance by defining the authority structures, escalation routes, and baseline success criteria. This process is performed once or at predefined points in the project or phase life cycle (such as the start of a new phase to reconfirm business alignment and authorization).

## Inputs

| Input | Description | Source |
|---|---|---|
| Business Documents | Business case and benefits management plan providing justification and intended value. | Sponsoring Organization |
| Agreements | Legal contracts, letters of intent, or service level agreements (SLAs) forming the project basis. | External/Internal Sourcing |
| Enterprise Environmental Factors | Regulatory, marketplace, and organizational infrastructure conditions. | Enterprise |
| Organizational Process Assets | Templates, policies, and lessons learned from past historical projects. | PMO Registry |

## Outputs

| Output | Description | Destination |
|---|---|---|
| Project Charter | The formal authorizing document containing high-level requirements and objectives. | A04 Project Charter |
| Assumption Log | Initial record of all high-level technical, resource, or operational assumptions. | A05 Context Register |

## Tools and Techniques

- **Expert Judgment:** Guidance from subject matter experts in business strategy, technical execution, and industry regulations.
- **Data Gathering:** Brainstorming, focus groups, and structured interviews with key stakeholders and sponsors.
- **Interpersonal and Team Skills:** Facilitation, conflict management, and active meeting management to build consensus.
- **Meetings:** Planning sessions and kick-off discussions with sponsors, business analysts, and the core team.

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A01 | Artifact | Justification for project initiation and expected value |
| A02 | Artifact | Success criteria and benefit alignment case |
| A04 | Artifact | Principal output of this process |
| A05 | Artifact | Supplying initial assumptions, constraints, and environmental context |
| A14 | Artifact | Downstream comprehensive planning framework |
| PR02 | Process | Supplier of initial stakeholder and authority context |
| SKL-01-01 | Skill | Establish Governance Framework |
| SKL-02-01 | Skill | Author Project Charter |

## Practitioner Notes

Practitioners executing this process should seek answers to the following vital questions:
1. What specific business need, opportunity, regulatory requirement, or strategic objective is this project intended to address?
2. Has the project manager been officially assigned with clear, documented authority before detailed planning starts?
3. Are the expected benefits, success criteria, and high-level boundaries explicit enough to support downstream planning?
4. Are the sponsor and authorizing authority at the correct level to commit funding and resources?
5. What major assumptions and constraints are being accepted at the time of charter approval?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.0 | 2026-06-02 | Rebuilt to align with canonical REF file structure and YAML front-matter | PMO Director |

---

*Authority: PMBOK8 Guide §2.1.6.1; Process Groups Practice Guide §4.1*
