The template below shows the layout and formatting of the Progress Report. This is the general layout and format your project should have. Your information will have different lengths and content, but it should have the same basic look and feel. Note these important details:
Check out the Annotated Progress Report Template for details on the information your Progress Report should include.
This memo provides an update on our work from March 5 through April 11, including specific details on the work that has been completed and the work that is scheduled for the rest of the project.
Our group is analyzing the “Simple Sabotage Field Manual.” and writing a recommendation report that will explain how the company can improve the site’s readability, accessibility, and document design.
So far, our group has analyzed the Manual and addressed the structure of our recommended revisions.
During the first weeks on the project (March 5 to April 1), we analyzed the Manual and went over every page to check for consistency and quality. Every observation was recorded in a report in Google Docs. In the same document, we have solutions for each problem or ideas on how to improve the situation.
This Google Doc gives us a single place to brainstorm and try to solve the problems we found. This list is what we are going to reference for our recommendation in the report. They will be expanded as appropriate and researched in more depth if they make it into our final report.
For our recommendation report, we all worked on getting the structure set in the last week (April 5 to 11). We created a basic wireframe of what we need to do and fill out for the near future. From this we all talked about what needs to be done for each section and who is best fit to work on it:
Preliminary drafting will focus on sections of the report that must be complete before other portions can be written. Specifically, the body of the report must be written before portions of the Front and Back Matter can be written.
While Kai and Priya focus on writing these sections, Alex and Omar will help by finding supporting research and creating supporting visuals and diagrams for the body of the report.
We plan for this work to be completed by Friday, April 18.
With preliminary drafting complete, Alex and Omar will develop the recommendations section as well as the front and back matter. Kai and Priya will further develop the body sections, incorporating materials that Alex and Omar have provided.
We plan for this work to be completed by Thursday, April 24.
All members of the team will read the complete draft carefully from Friday, April 25 to Sunday, April 27. Members will focus particularly in reading sections they did not write to ensure that their own work is represented accurately and ensuring consistency among the sections.
As an example, Kai and Priya will ensure the following:
Our team will use the remaining time in the schedule (Monday, April 28 to Tuesday, April 29) revising the document as necessary, based on the comments and recommendations the team has gathered. We’ll make a final editing pass through the document on Tuesday, April 29
We plan for this Revision and Editing work to be completed by Tuesday, April 29, the Target Due Date for the project.
All work on the project must be completed by Tuesday, April 29, following the schedule shown in the Gantt Chart on the following page:
We have no concerns about completing our report by the target due date. We are all working well as a group and are confident that the remaining work will flow smoothly. You can access our working Google Docs at [link to google drive documents was here].
Our team looks forward to hearing your feedback on our progress. If you have any questions about our completed or scheduled work, please connect with our team leader, Priya, at priyakapoor@vt.edu or 540-555-1872.