Progress Report-Purpose and Expectations
Prepared by: Diane T. Rover and P. David Fisher
prog_rpt.html
Purpose
Periodic progress reports during the life of a project serve several important purposes:
Expectations for this Report
The written design team progress reports should follow the same format and style as the original proposal. This includes the first page with a project title, list of team members and executive summary. The Executive Summary would have much of the same wording as the executive summary in the original proposal. However, it would also provide a list of significant achievements to date and a statement as to whether or not the project is on schedule. The executive summary should clearly identify any possible impediments to meeting the original goals, objectives, or timelines. The body of the report should contain three sections: Introduction, Progress, and Plans.
The Introduction should state the period of time covered by this report. It should also state the projects purpose, goals, and objectives. Much of this information can be extracted directly from the RFP and the original proposal. Moreover, much of this same Introduction can be reused in future progress reports and in the final project report.
The Progress portion of the progress report should focus on the schedule contained in the proposal and should address the following:
The Plans portion of the progress report should also focus on the schedule contained in the original proposal and should address the following issues:
NOTE: Completing weekly, informal written progress reports facilitates the development of formal progress reports. The Management Skill Team and Doc Prep Skill Team may have recommendations on informal reports.