0% found this document useful (0 votes)
73 views

Project Name Project Handover: Action Statement Date Name Position Action Required Due Date

This document provides a template for a project handover report. It outlines the required sections including executive summary, introduction, purpose, stakeholders, background, objectives, scope, constraints, impacts, risks, handover, and maintenance/support. The document also includes sections for contact details, version history, and approval. The purpose is to obtain acceptance of deliverables, identify outstanding issues and responsibilities, and provide guidance on ongoing management of the project outputs.

Uploaded by

anarki85
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
73 views

Project Name Project Handover: Action Statement Date Name Position Action Required Due Date

This document provides a template for a project handover report. It outlines the required sections including executive summary, introduction, purpose, stakeholders, background, objectives, scope, constraints, impacts, risks, handover, and maintenance/support. The document also includes sections for contact details, version history, and approval. The purpose is to obtain acceptance of deliverables, identify outstanding issues and responsibilities, and provide guidance on ongoing management of the project outputs.

Uploaded by

anarki85
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Project name

Project Handover

Action statement
Date Name Position Action required Due date
(Review/Endorse/Approve)
Project name Project Handover

Document control sheet

Contact for enquiries and proposed changes


If you have any questions regarding this document or if you have a suggestion for
improvements, please contact:
Project Manager Insert Project Manager's name here
Phone Insert phone number here

Version history

Version no. Date Changed by Nature of amendment

09/07/2002 Initial draft.

Project Handover approval


The following officers have approved this document.

Customer
Name
Position
Date
Name
Position

Version 1.0 Page 2 of 12


Project name Project Handover

Executive summary
The Executive Summary is mandatory.
Provide a summary of the Handover Report. Focus on the status of the implementation (are
the outcomes operational) and how outstanding issues will be managed.
To delete this guidance text box, double click mouse in the left margin then press delete.
Type here

Version 1.0 Page 3 of 12


Project name Project Handover

1 Introduction
Text in this document which has been copied forward from the previous document
has been shown bold and italics “words copied from previous documents”.

2 Purpose of this document


The purpose of this document is to:
 obtain formal acceptance of the project’s deliverables from operational areas
 identify outstanding project issues and who is responsible for resolving them
(operational area or project team).

2.1 References
This item lists any documents to which this document refers and could include
reports on any previous investigations carried out. Include all previous documents
prepared as part of this project.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Type here

2.2 Project Customer


Enter the name of the Project Customer.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Insert name was the Project Customer.

Version 1.0 Page 4 of 12


Project name Project Handover

2.3 Project Sponsor


Enter the name of the Project Sponsor.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Insert name was the Project Sponsor.

2.4 Project Manager


Enter the name of the Project Manager.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Insert name was the Project Manager.

3 Stakeholders
This section should illustrate the engagement undertaken with stakeholders and the
key outcomes of that process as outlined in the completed community engagement
planner for the project. List all stakeholders with an interest in this document
including internal stakeholders (from regions/districts/divisions/branches with the
department) and external stakeholders. Stakeholders may be listed in tabular form
(as below). Include project customer and politicians as appropriate. Stakeholders
may be categorised (internal, external and so on) where appropriate.
To delete this guidance text box, double click mouse in the left margin then press
delete.

Stakeholder Stakeholder Responsibility Interest/context


area representative

4 Background
Provide here sufficient information to bring the reader up to speed on the subject
matter of the project, including a brief history.
This section should describe the history of the project. It should include details of:
- Who initiated the project and how it was initiated
- Include a clear statement of the real underlying problem to be addressed.
- Include a brief history of past community engagement, issues and outcomes.
- Identify the impact of problems/issues over time
- Include information on objectives in and out of scope.

Version 1.0 Page 5 of 12


Project name Project Handover

To delete this guidance text box, double click mouse in the left margin then press
delete.
Type here

5 Purpose/objectives of the project

5.1 Purpose/objectives
A statement of what the project was expected to achieve including potential benefits.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Type here

5.2 Links with the department’s strategic objectives


A statement of how the project links to the department’s Strategic Plan and
objectives.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Type here

6 Scope of project

6.1 In scope
This defines the project boundaries. The scope outlined in any previous document
should be confirmed here. List all items that were included in the scope of this
project and note performance of the project against scope items.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Type here

6.2 Related projects


List any related projects or proposals that may have affected this project and how
their relationships to this project were managed.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Type here

Version 1.0 Page 6 of 12


Project name Project Handover

6.3 Constraints
Describe anything that might have impacted on the successful development and/or
implementation of the project and how they were managed.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Type here

6.4 Overview of impacts


Outline the major impacts the project has had on the business and the potential
future impacts
Summarise thethat may eventuate
key financial under
impacts certain
on the conditions
operational (forofexample,
areas an increase
the business and
or decrease in customer demand
how they were or are to be funded. and so on).
To delete this guidance text box, double click mouse in the left margin then press
delete.
6.5 Funding issues
Type here

6.6 Risks
List the major ongoing risks as identified by the project and suggested mitigation
where applicable.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Type here

Queensland Transport and Main Roads Version 1.0 27 April 2006 Page 10 of 12
Project name Project Handover

6.7 Handover
Detail here any issues relevant to the operational areas and suggested follow-up
actions/instructions for dealing with the project’s deliverables on an ongoing basis.
To delete this guidance text box, double click mouse in the left margin then press
delete.
Type here

6.8 Maintenance and support


Detail any arrangement for ongoing maintenance or support of project outputs.
To delete this guidance text box, double click mouse in the left margin then press
delete.

Queensland Transport and Main Roads Version 1.0 27 April 2006 Page 11 of 12

You might also like