Project Charter Template
Project Name:
Project Manager:
Prepared by: Date: Version #:
Synopsis: Briefly summarize the salient aspects of the project by answering the
questions "Why?" (purpose), "What?" (product description/ scope), "When?"
(time), and "How much?" (resources) – this summary is expanded in the
sections below….
Purpose/ Identify the need the product is intended to meet (either as a problem to
Business Need: solve or as an opportunity to exploit) and the customers or end users who
are to receive, make use of, and benefit from the product developed by the
project
Product Where possible, identify what product is to be delivered at the end of the
Description and project, and at any interim delivery points. Describe the product sufficiently
Deliverables or to enable the project team and client to understand what is being created.
High Level Where relevant identify the project boundaries, exclusions and interfaces.
Requirements: Alternatively, identify the requirements the project has to fulfil and how the
requirements will be identified, defined and tracked through to delivery.
Objectives and Briefly indentify any key objectives the project is expected to achieve such
success criteria as contracted completion dates, agreed prices, safety, training, etc. For
each objective define the measured success criteria (KPI) and if appropriate
who determines success – maximum 4 or 5 KPIs
Summary # Milestone Description Date
Milestones
1 Any contracted or other key Milestone dates
2 Add rows as needed
Benefits Identify the high level benefits the project is expected to enable, the person
realisation: responsible for realising each benefit, and how the benefit will be tracked
(reference benefits management plan).
Assumptions, Briefly identify salient / high level assumptions, constraints, and known
Constraints, risks, if any, which can be anticipated to have a major impact on the
Risks: process and/or outcome of the project
1 of 2
Word Template: [Link]
Authorisation Assigned project sponsor, responsibility and authority level
levels: Assigned project manager, responsibility and authority level
Any other authority such as Change Control Board or steering committee,
their , responsibilities and authority levels
Escalation routes
Project Briefly indicate general approach to managing the work including:
Management: Project management team
Summary schedule
Summary budget (cash flow)
Summary strategy, method statement, and methodology for accomplishing
the work (eg, an Agile development within a PRINCE2 framework)
Resources: Indicate required and/or available resources to be used on the project. As
appropriate, indicate financial, personnel, and material resources (such as
facilities, equipment, supplies, and services)
Stakeholders: List the primary stakeholders including Sponsor, Customer and any other
key person or organisation with their role
Acceptance / Exit Indicate who will accept each specified project deliverable and the method
Criteria: and criteria to be used to accept them as complete and adequate
References: List any documents referenced in the text above or that are important to the
work of the project: contracts, business case, specifications, SoW, etc.
Change Indicate the procedures to be used for making and documenting changes to
Management: this project charter
Other: Identify and explain any other matters that are important for the initiation
and conduct of the project. Focus on charter issues of importance between
the customer, th project sponsor and the project manager. This section is
not for describing the project plan
Charter Approval: Name and authority of the project sponsor and any other person approving
this project charter, with space for signatures and dates.
2 of 2
Word Template: [Link]