Project Charter

Document Code: PMBOK4.1.3.1

<Organization Name>

CEO of <Organization Name>

<Full Name>

Save your time - order a paper!

Get your paper written from scratch within the tight deadline. Our service is a reliable solution to all your troubles. Place an order on any task and we will take care of it. You won’t have to worry about the quality and deadlines

Order Paper Now

<Name and authority of the sponsor or other person(s) authorizing the Project Charter>


__________________ 2021

<Project Name>

Project Charter

Revision <6.0>

  1. Project Purpose

<This section briefly describes the purpose of the project and its justification. The justification describes the necessary information from a business standpoint to determine whether or not the project is worth the required investment. Justification describes one or more of the following factors:

  • Market demand (e.g., a car company authorizing a project to build more fuel-efficient cars in response to gasoline shortages)
  • Organizational need (e.g., a training company authorizing a project to create a new course to increase its revenues)
  • Customer request (e.g., an electric utility authorizing a project to build a new substation to serve a new industrial park)
  • Technological advance (e.g., an electronics firm authorizing a new project to develop a faster, cheaper and smaller laptop after advances in computer memory and electronics technology)
  • Legal requirement (e.g., a paint manufacturer authorizing a project to establish guidelines for handling toxic materials)
  • Ecological impacts (e.g., a company authorizing a project to lessen its environmental impact)
  • Social need (e.g., a nongovernmental organization in a developing country authorizing a project to provide potable water systems, latrines and sanitation education to communities suffering from high rates of cholera).

These factors may also be called incentives, opportunities or business requirements. The basic point of all these factors is that management should decide what the response should be to them, and what projects should be authorized and fixed in the Charter.>

  1. Measurable Project Objectives and Related Success Criteria

<This section describes the measurable project objectives and related success criteria:

  • Objective is something toward which work is to be directed, a strategic position to be attained, a purpose to be achieved, a result to be obtained, a product to be produced or a service to be performed.
  • Criteria are the standards, rules or tests on which a judgment or decision can be based or by which a product, service, result or process can be evaluated.>
  1. High-Level Requirements

<This section documents the requirements that satisfy the needs, wishes and expectations of the Customer, Sponsor and other project participants. Requirements are the certain conditions or capabilities that must be met or possessed by a system, product, service, result or component to satisfy a contract, standards, specifications or other formally imposed documents.

Requirements include the quantified and documented needs, wants and expectations of the Sponsor, Customer and other stakeholders of the project. In the phase of the Project Charter development, the requirements are usually less concrete; they becomes more concrete during the subsequent processes according to the gradual elaboration of the project.

Please note that the Project Charter contains high-level requirements only. The complete list of requirements should be presented in the Requirements Traceability Matrix.>

  1. High-level Project Boundaries and Key Deliverables

<This section provides a general description of the products or services that the project is supposed to produce; there is a brief description of the business need, a very general description of the product and an initial strategic plan.>

  1. Overall Project Risk

<This section describes the high-level risks and also provides a brief description of the project risk management implementation and the risk tolerance levels of the project Sponsor and Customer.

Please note that the Project Charter contains high-level risks only. The complete list of risks should be presented in the Risk Register.>

  1. Summary Milestone Schedule

<This section contains an aggregate schedule of works showing the dates of the main milestones. The Customer or performing organization can preset the milestones and the required dates of their execution. These dates can be identified as constraints on the terms. Use the following table.

Please note that the Project Charter contains high-level milestones only. The complete list of milestones should be presented in the Milestone List.>

No. Milestone Date
<Title of the milestone>
  1. Preapproved Financial Resources

<This section contains formal periodic restrictions on expenditures provided in the project or specified in the Agreement on project implementation.

Please note that the Project Charter contains summary budget only. The itemized budget should be presented in the Cost Baseline.>

  1. Key Stakeholder List

<This section contains the list of individuals, groups or organizations who may affect, be affected by or perceive itself to be affected by a decision, activity or outcome of a project.

Please note that only main stakeholders are specified in the Project Charter. The complete list of stakeholders should be presented in the Stakeholder Register.>

Full Name Position/Organization Role in the Project Telephone/E-mail
<Full name of the stakeholder> <Position of the stakeholder and organization name> <What kind of work is performed by the stakeholder in the project> <Key contact information of the stakeholder >
  1. Project Approval Requirements

<This section specifies what constitutes project success, who decides the project is successful and who signs off on the project. This section also identifies the acceptance criteria, including performance requirements and essential conditions that must be satisfied before the acceptance of the project deliverable.>

  1. Project Exit Criteria

<This section specifies what conditions need to be met in order to close or to cancel the project or phase (e.g., documented approvals, completed documents, completed deliverables).>


A Project Manager is identified and assigned as early in the project as is feasible, preferably while the project charter is being developed and always prior to the start of planning. It is recommended that the Project Manager participate in the development of the Project Charter because this document provides him/her with the authority to use the organization assets to complete the project and responsibility for the project objectives achievement.>

  1. Appendixes

<This section contains all appendixes to the document. In the absence of appendixes, this section is excluded.>

<Attention! Fill in the Quick Parts and update the Table of Contents before publishing the document.>


"Place Your Order Now And Our Professional Writers Will work on It And Deliver A perfect Paper Within The Deadline

Order Now