Note: This Document Is Only Valid on the Day It Was Printed

Project Mandate.doc

Project Mandate

Project Name:
Date: / Release: / Draft/Final
Author:
Owner:
Client:
Document Number:

Note: This document is only valid on the day it was printed

The source of this document will be found in the Project file

Revision History

Date of next revision:

Revision Date / Previous Revision Date / Summary of Changes / Changes Marked

Approvals

This document requires the following approvals. A signed copy should be placed in the project files.

Name / Signature / Title / Date of Issue / Version

Distribution

This document has been distributed to:

Name / Title / Date of Issue / Version

page 1 of 3

Project Mandate.doc

Overview

Purpose / The information in the Mandate is used to trigger Starting up a Project (SU). It should contain sufficient information to identify at least the prospective Executive of the Project Board and indicate the subject matter of the project.
It will also be used to create the Project Brief.
Contents / The Project Mandate will vary depending on the nature of the project, tailor the proposed list to suit the requirements of your project:
Responsible Authority 3
Background 3
Project Objectives 3
Scope 3
Constraints 4
Interfaces 4
Customer’s quality expectations 4
Outline Business Case 4
Project Tolerances 4
Associated documents or products 4
Key appointments 4
Customer and interested parties 4
If additional information is available then either include or refer to where else in the project files it is held.
Advice / A Project Mandate may come from anywhere, but it should come from a level of management that can authorise the cost and resource usage. It is input to Starting up a Project (SU).
Ensure that the Project Mandate describes what is required, that there is sufficient detail to allow the appointment of an appropriate Executive and PM. Also ensure that the level of authority is commensurate with the anticipated size, risk and cost of the project and that all interested parties are identified.

Responsible Authority

Background

Project Objectives

Scope

Constraints

Interfaces

Customer’s quality expectations

Outline Business Case

(present the reasons for the project)

Project Tolerances

Associated documents or products

Key appointments

(an indication of who are to be the Executive and PM and other key project posts)

Customer and interested parties

(list the customer, user and other known interested parties)

page 1 of 3