Project Charter Template

Using this Template

To create a Project Charter from this template, simply:

1. Delete this page.
2. Replace the title on the cover page with, "Project Charter:", the name of your project and the organization information.
3. Replace the [bracketed text] in the document header with your project name.
4. Save your document with a filename of your choice.
5. Update the filename in the document footer by right-clicking and selecting Update Field.
6. Complete the entire template. Each section contains abbreviated instructions, shown in italics, which can be removed once your document is finalized. Tables are also provided as a suggested layout for some of the information required.
7. Update the table of contents by right-clicking and selecting Update Field, then Update entire table.

You can also use the companion document, "Project Charter Guide", if you would like more information about a particular section of the Charter, or about the Project Charter in general.

Document Purpose

The Project Charter is "a document issued by the project initiator or sponsor that formally authorizes the existence of a project, and provides the project manager with the authority to apply organizational resources to project activities."^{Footnote 1}

The purpose of the Charter is to obtain formal approval on the general parameters and structure of the proposed project, including:

• the project objectives and outcomes, benefits, scope and risks;
• the project deliverables, schedule, milestones, and estimated costs; and
• the project organization, governance structure and stakeholders.

1.1 Document Change Control

This section serves to control the development and distribution of revisions to the Project Charter. It should be used together with a change management process and a document management system.  It is recommended that changes to the Charter are documented only by adding annexes to the original Project Charter.  This will keep an accurate history of the original document that was first approved.

1.2 Executive Summary

• Provide a brief summary of the project in business terms demonstrating alignment with the ultimate/strategic outcome targeted by the participating organization(s).
• Summarize the most important aspects of the project by answering the questions:
  • How and why the project was initiated?
  • Who will use the final deliverable of the project?
  • Who will be impacted by the project?
• The following elements are usually covered in the Executive Summary:
  • project goals and objectives;
  • major milestones;
  • key deliverables;
  • key risks; and,
  • estimated total costs

1.3 Authorization

This section contains the signature of key stakeholders, which shows they agree with their role and the description of the project as it appears in the Project Charter.

This Project Charter formally authorizes the existence of the project, Project Name, and provides the project manager with the authority to apply organizational resources to the project activities described herein. If there is a change in the project scope, the Charter will be updated and submitted for re-approval.

______________________________________________________
Full name

______________________________________________________
Date

Executive Sponsor

Position, Client Organization

______________________________________________________
Full name

______________________________________________________
Date

Project Sponsor

Position, Client Organization

______________________________________________________
Full name

______________________________________________________
Date

Project Manager

Position, Your Organization

______________________________________________________
Full name

______________________________________________________
Date

Title

Position, other supporting organization

______________________________________________________
Full name

______________________________________________________
Date

Title

Position, other supporting organization

2.1 Project Summary

• This section briefly summarizes the entire Project Charter, highlighting the significant points of interest to the reader. It includes all of the information required for approval by the key stakeholders.
• The summary should also include some background information on the project that includes the reason/s for creating the project (e.g. a business need, a legal requirement, etc.), and mention the key stakeholders who will benefit from the project results.

2.2 Project Goals, Business Outcomes and Objectives

This section describes the project goals and links each of them to related measurable project objectives. In addition, business outcomes to be derived from the project goals and objectives should be presented as outlined in the business case. Measurement criteria, which will be used to confirm that an objective and the outcome have been reached, must also be provided.

Keep in mind that goals are high-level statements, usually broad general intentions that are typically intangible or abstract.  Project objectives are concrete and measurement criteria usually confirm if an objective has been met.  Business Outcomes are results expected at the end of the project. Outcomes can be expressed in just a few words that describe a general aim.

Add rows as required.

2.3 Project Scope

2.4 Milestones

Identify the significant points or events in the project (phases, stages, decision gates, approval of a deliverable, etc.).  This can also represent a high-level project schedule.

2.5 Deliverables

• Identify and define the key deliverables the project must deliver in order to achieve the stated objectives.
• Also include internal project deliverables required in the Project Management Process for review and approval (e.g. project transition plan, communication plan, lessons learned etc.).
• Determine the criteria that will be used to assess the quality and completion of each deliverable.
• Indicate the stakeholder(s) responsible for approving each deliverable.
• Add rows as required.

The deliverables section can be used to build the top levels of a project's Work Breakdown Structure, which divides the big deliverables for a project into smaller, more manageable parts.

2.6 Project Cost Estimate and Source of Funding

2.6.1 Project Cost Estimate

This is where you record a summary of cost estimates for all of the resources (human, material and financial) required to produce the deliverables and meet the objectives established for the project. For input and to make sure the full project scope is covered, refer to the items listed in the initial Work Breakdown Structure and the project effort estimates. Don't forget to include one-time as well as on-going costs. For example, the estimated cost to sustain the product(s)/service(s) of the project should be provided. Modify the table as required.

The business case for the project should contain cost estimates that can be used as the basis for this summary.

Figure 1 - Text version

The diagram is of a sample template for estimating project expenses by phase and fiscal year. The template includes a column for project phase or deliverable and columns for the project's fiscal years.

Under each project phase or deliverable are itemized estimated expenses including salary, O&M, Professional Services, Capital and Other (e.g.) revenue for which projected costs can be inputted into each fiscal year.

2.7 Dependencies

This is where you list dependencies for the project such as:

• A predecessor/successor relationship exists with another project (MOU, partnerships, etc.);
• A related project expects a deliverable from your project;
• Your project expects a deliverable from a related project; or
• Your project delivers a product, service or result that will or needs to be released with another new product, service or result.

2.8 Project Risks, Assumptions, and Constraints

3.1 Project Governance

• This is where you show how your project is governed and the corporate governance bodies that may be involved in the approval process. In other words, it shows how decisions are made, and who makes which decisions.
• A diagram should be used.
• If committees are shown in the diagram, include a description of these committees in the Roles and Responsibilities section.

3.2 Project Team Structure

• Use an organizational chart to show the structure of the project team as well as the  relationships between team members
• You should also show how the team interacts with, or relates to the governance structure for the project.
• For small projects, the names of the team members can be included; for larger projects, the organizational chart should name the groups or entities that form the project teams.

3.3 Roles and Responsibilities

• Define the roles and responsibilities assigned to each member of the project team as well as any stakeholders and working groups that have a significant influence on the project.
• Include all committees and entities identified in the sections, 3.1 Project Governance, and 3.2 Project Team Structure.

Project Role [Project Manager]

Responsibilities

Assigned to

Project Role [Business Analyst]

Responsibilities

Assigned to

Project Role [Project Review Committee]

Responsibilities

Assigned to

3.4 Project Facilities and Resources

• Describe, if applicable, the project's requirements for facilities and resources, such as office space, special facilities, computer equipment, office equipment, and support tools.
• Identify the person or team responsible for obtaining the specific items needed to support the project's development environment.