Project Management

Notes on Reporting Progress (ii)

From the Project Confusion in Transition Management Blog
Projects are about transition from one state to a desirably better state. Management is often viewed as a source of confusion. So lets break down the confusion and build up the means for transition to meaningful deliveries.

About this Blog


Recent Posts

Notes on Reporting Progress (ii)

User Acceptance Tests (documentation)

Start Right

Documents Supplied for Post-HOTO

Notes on Documenting Acceptance Tests


Agile, Agile Communications, App design, Communications Management, Give-back | Outreach, information communication technology, New Year, PMIef, Project Management, Quality, Risk, Risk Management, System design, Volunteering


These short notes are expanded from the previous blog article.

The project progress report may present concise information such as – 

  1. % Completion supplied from a project management tool
  2. Accomplishments & Plans moving forward to the next reporting period.
  3. Risks & Impediments for notification and guidance of the project management steering committee.

Information may be presented on a presentation deck or a simple single page i.e. pdf. The % completion may be on schedule completion or cost completion, or computed in a method agreeable by all parties. A reliable tool is usually adopted for the purpose.

% Completion

Previously Reported

Last Reported

This Report





This Reporting Period [date1] to [date2]


Scheduled Activities for Next Reporting Period

  • Win 1 created
  • Win 2 completed
  • Loss 1 could be a suspended or terminated activity due to whatever reasons
  • Planned activities to begin in next reporting period
  • Include all outstanding activities (to carry forward).

Delivered e.g.

Deliverables in Next Reporting Period

  • Product from Win 1
  • Service procedures Win 2
  • Pertinent documentation
  • Required documentation with deliverables e.g. manual no. 1 
  • Evidence of project activities, work performance and deliverables. 


Risks & Issues

Identified Risk


Response Plan

  • May include impediment requiring intervention of e.g. project sponsor, owner or project steering committee.
  • For issues (or risks) requiring intervention and or direction, provide not more than 2 viable solution options.
  • Brief pointers on plans to deal with known risks. And whether the plans are in place and tested.


For impact, include a calendar to highlight visually the workload of the project, e.g.

Posted on: September 24, 2022 02:23 AM | Permalink

Comments (3)

Please login or join to subscribe to this item
Binay Samanta Director| Project & Environment Consultants Dhanbad, Jharkhand, India
Very nicely elaborated steps in progress reporting of projects

Michael Coleman Memphis, Tn, USA
Nice overview! Progress reporting is necessary to generate data that contributes to future activities.

Latha Thamma reddi Sr Product and Portfolio Management (Automation Innovation)| DXC Technology Mckinney, Tx, USA
Very Nice Detailed overview of the 2future activities with good examples and data.. really impressed

Please Login/Register to leave a comment.


"When one door closes another door opens; but we often look so long and so regretfully upon the closed door that we do not see the ones which open for us."

- Alexander Graham Bell