Skip to content
PMPCAPM

Project Charter

A project charter is a document issued by the project sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.

Share:

Explanation

The project charter is the foundational document that gives a project its official standing within an organization. It is created during the Initiating process group and links the project to the strategic objectives of the organization. The charter includes high-level information such as the project purpose, measurable objectives, high-level requirements, summary milestones, overall budget, key stakeholders, and the assigned project manager along with their authority level.

The project sponsor, or another entity external to the project, typically issues the charter. The project manager may assist in drafting it, but the authority to approve and fund the project comes from the sponsor or an executive body. A signed charter represents organizational commitment and gives the project manager the green light to begin planning.

Because the charter is a high-level document, it does not contain detailed plans. Instead, it establishes the vision and boundaries of the project. It should be revisited when there are significant changes to scope or objectives. The charter remains relevant throughout the project lifecycle and is a key input to the Develop Project Management Plan process.

Key Points

  • Formally authorizes the project and assigns the project manager
  • Issued by the project sponsor or an external authority, not the project manager
  • Links the project to organizational strategy and business objectives
  • Contains high-level scope, milestones, budget, risks, and stakeholder information

Exam Tip

Remember that the project charter is the ONLY document that formally authorizes the project manager. Without a signed charter, the project does not officially exist.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Change Control Board (CCB)

A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Integration Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.