Businesses and projects rely on well-structured reports to ensure accurate communication about goals and objectives, requirements, designs, measuring and recording progress, etc. Unfortunately, many engineering reports and management reports are not as clear as it should be. In order to alleviate this problem - particularly for engineers and managers in the early stages of their careers – this ebook contains suggested frameworks for a selection of commonly used engineering project management reports. (Two other ebooks by the same authors contain frameworks for business management reports and system engineering reports.)

This ebook is intended as a report writing reference guide, from which ideas can be sourced about the typical structure and contents of commonly used project management reports. The ebook does not provide blueprints for all reports that a project manager might ever have to write, but it provides guidelines which should be tailored and adapted by common sense and experience, in order to suit specific circumstances.

The philosophy underlying this book is: contents follow structure - i.e. first carefully think about, and decide upon a report structure, and then systematically fill in the contents. When a report structure  is defined first, the gathering of information becomes focused, and unnecessary material is either not collected at all, or it can be filtered out systematically.

Besides briefly addressing the main generic elements of a report, report quality assurance and project management, frameworks for the following types of reports are provided in this ebook: 

• Contract Proposal

• Project Plan

• Progress Report

• PERT (Program Evaluation and Revision Technique) Report

• Trade-off Study Report

• Technical Notes

• Minutes of a Meeting

Each of these reports is briefly discussed in terms of its typical purpose and scope, followed by a suggested framework for the report.

About the Authors ...

Email with download link sent immediately after purchase.