Project Management

Good Practices for Monthly Reporting

From the Project Management View from Rail Transit Programs and Projects Blog
by
A collection of articles sharing project processes, design and construction experience, best practices, and lessons learned along with operational knowledge related to executing programs and projects in the rail transit industry.

About this Blog

RSS

Recent Posts

Transitioning Constructed Products from Projects to Owner's Operations

Lessons to be Learned.  What Happens When the Buyer is Not the Owner, Operator and Maintainer of the Company?  

Managing Warranty After Achieving Contract Milestones

What Happens After the Buyer and Seller Agree on a Punchlist?

What is a Punchlist?

Categories

Acceptance, Analytics, ANSI, Asset Management, Best Value, Best Value Contractor Selection, Best Value Selection Criteria, Buyer, Certifications, Commissioning, Communications Management, Construction, Construction Completion, Construction Deliverables, construction manager, Construction Monitoring, Construction Submittals, Consultant, Consultant Contract, Contract Acquisition, Contract Completion, Contract Deliverables, Contract Delivery, Contract Development, Contract Integration, Contract Management, Contract Milestones, Contract Quality, Contract Requirements, Contract Submittals, Contracts, Decision Making, Definitions, Design, Design Bid Build, Design Build, Design Build Delivery, Design Deliverables, Design Services, Design Submittals, Design-Bid-Build, Division 1 Specifications, Document Control, Earned Value Management, Engineering, Estimating, Estimator, Ethics, Factory Acceptance Test, Final Acceptance, Final Completion, General Conditions, General Provisions, General Terms and Conditions, Good Practices, Government, Hard Risks, Hazards, Human Resources, Information For Bidders, Inspection, Inspection and Testing, Inspection Test Plan, Integration, Integration Management, Invitation For Bid, Key Performance Indicators, Knowledge Management, Maintenance, Management Integration, Managerial Time, Managing Change, Managing Changes, Master Project Schedule, Meeting Minutes, Mega Projects, NCR Process, Negotiations, Non Conformance Report, O&M Manuals, Oversight Reports, PM Fundamentals, PMBOK, PMI, PMO, Procurement Management, Professional Obligations, Program Management, program manager, Progress Reports, Project Charter, Project Controls, Project Engineer, Project Engineering, Project Integration, Project Interfacing, Project Management, Project Management Institute, project management office, Project Management Plan, Project Manager, Project Managerr, Project Planning, Project Records, Project Schedules, Project Team, Project Teams, ProjectManagement, Public Relations, punchlist, Quality, Quality, Rail Car Purchase, Rail Transit, Rail Transit Organization, Rail Transit Project, Rail Transit Projects, Railroad, Reliability, Resource Management, RFI Logs, risk, Risk Allocation, risk allocation, Risk Allocations, Risk Management, Risk Management, Safety, Schedule Interfaces, Schedule Management, Schedule Milestones, Scheduler, Scheduling, Scope of Work, Security, Seller, Site Acceptance Test, Soft Risks, Special Inspections, Specifications, Submittal Logs, Submittal Process, Substantial Completion, System Integration, System Integration Test, Systems, Systems Purchase, Testing/Test Management, Threats, Transformation, Transformational Projects, Transportation, Vulnerability, Work Area, Work Areas

Date

linkedin twitter facebook Request to reuse this  


One of the most obvious and far reaching arteries in the body of the project Communication Plans are the reports from the project team and contractors. The content of these reports is the life blood of the communication network to provide readers with objective information on the health of the project and individual contracts contributing to project realization.

From my experience on design and construction projects in the rail transit industry, the progress reports issued by the Project Manager (PM) will define current status and identify key performance indicators throughout the project life cycle. In addition to management accountability, the reports become the historical records for future use in planning projects and contracts. The reports provide data that can be used for estimates, schedules, production rates, and durations for design and construction processes as well as other qualitative project management knowledge areas such as risk management, quality, safety, procurement planning and contract administration.

Depending on the targeted audience, the monthly progress reports by the PM can have many formats, varied levels of content detail and different publishing and distribution dates. Reports may be tailored for internal customers, funding partners, executive management and oversight consultants. However, it is imperative that published reports use the same data base so that metrics match from report to report for the same reporting period.

Project Monthly Report content may include categorized topics such as: A) Project Scope/Description of Work/Project Changes. B) Summary Schedule/Project Milestones. C) Project Progress – Planned and Actual, Intermediate (Contractor) Milestones. D) Current Status-Reporting Period. E) History of Completed Work Milestones. F) Financial – Budget and Expenses. G) Other: Contingency Management, Contract Management, Risk Management, Resource Management.

Contractor Monthly Progress Report content may include categorized topics such as: A) Executive Summary, Contractor PM Assessment, and Issues Affecting Progress. B) Contract Scope/Description of Work. C) Summary Schedule/ Contract Milestones. D) Contract Progress – Planned and Actual. E) Subcontractor Milestones. F) Current Status-Reporting Period. G) Status Section – Critical Issues, Correspondence, Submittals, Deliverables, Contract Changes, Invoices. H) Financial Summary – Contract Amount, Payments, Proposed Changes. I) Other: Resource Management, Quality, Safety, Materials Management, Code Compliance. J) Attachments: Progress Photographs, Schedule, Logs, Certifications.

Good Practices for Monthly Reports
• Identify Project report requirements in the Project Management Plan (PMP)-Communication Plan, and in Project Management Office (PMO) procedures
• Specify Contractor report requirements contract documents
• Assure Key Performance Indicators (KPI) complement all type reports and supporting data is available to PMO and PM
• Ensure content, format, and language is consistent across all reports
• List contact information for PM and other primary content contributors

Good Practices for Distribution and Review
• Use a standard list of recipients including all project team members, designated PMO officers, and other targeted audience
• Distribute in a format that is readable across electronic medium such as tablets, and iPhone
• Discuss monthly reports at project/progress meetings
• Transmit reports with cover letter that summarizes PM cursory comments and assessments, items of interest, and items requiring project team action

TIP: KPIs that reflect unfavorably for multiple reporting periods and across significant number of projects in a program should be re-assessed against original assumptions.

TIP: PMO procedure should identify variance thresholds for KPI and planned/actual metrics where reports are required to specify PM project performance assessment and corrective action.

TIP: Photographs should integrated in reports and they should be updated for each reporting period, captioned, and reasonably reflect field conditions - no more than one month earlier.
      

NEW TIP:   Report format, content and distribution cycle should be aligned with the client’s unwritten expectations.

NEW TIP:    Distribution cycles should be timed to allow the readers to assess project health, undertake action and initiate decisions with the best data available.    Some reports are published 10 calendar days after the reporting period (Best), while others may be up to 10 weeks after the reporting period (Worst).  

NEW TIP:   Metrics and content should be rigorously tested and validated against leading indicators such as:  A) % Earned Value Remaining VS % Project Duration Remaining.   B) Manpower Headcount Available VS Manpower Headcount Required.    C)  % Budget Remaining VS % Project Duration Remaining. 

 


Posted on: January 26, 2018 06:57 PM | Permalink

Comments (12)

Please login or join to subscribe to this item
avatar
Henry Hattenrath Project Consultant| Tectonic Engineering MSA LLC New York, Ny, United States
The content was originally published in January 2017 under DISCUSSIONS. With encouragement from my PM.com peers, it is now part of a BLOG. Based on feedback, the Blog includes several NEW TIPS.

avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Great Tips - I recall this discussion and it was a great one. I actually recommend you submit it as an article after adding few items to it.

avatar
Najam Mumtaz Retired Lahore, Punjab, Pakistan
Project reports are required to be tailored to suite majority of stakeholders requirements, 100% accurate and should not be too lengthy (reader should not loose interest ).
Thank you Henry for great tips on monthly project status reports.

avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Good one Henry.

avatar
Riyadh Salih Saskatchewan, Canada
Thanks Henry for sharing, I guess for more sensitive projects requires a weekly status report.

avatar
Nenad Pesic engineer| Michelin Gerzat, France
Useful post Henry. I am with Riyadh, for more important projects weekly reporting is useful.

avatar
Eduin Fernando Valdes Alvarado Project Manager| F y F Fabricamos Futuro Villavicencio, Meta, Colombia
Thanks for sharing

avatar
Henry Hattenrath Project Consultant| Tectonic Engineering MSA LLC New York, Ny, United States
Riyadh. Nenad

Thanks for the input. I agree that some projects may require more frequent reports, including weekly and daily reports (see GPs for Field Monitoring.) But the content and purpose of each will be different from the Monthly Report and be complied based on client requirements and the communications plan in the PMP. It will also be balanced by the available staff to collect, formalize and formalize the content, and by the project control's support and organizational systems to provide data that is timed with a weekly report.

avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
Thanks, Harry! I also remember the original discussion. We have both weekly and monthly reports. The monthly are executive level reports.

avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
Very informative, and thanks for sharing this, Henry.

avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
My current project's PMO has decided to use a Daily Scrum approach to reporting progress: report what happened during the last period, report what will be worked on during the next period, report any obstacle impeding work. One suggestion was to include pictures of our Kanban boards. Any other suggestions to make it more of a dashboard for Senior Management?

avatar
Alexandra Cote Content Marketing| Paymo Romania
Great article, Henry! Very informative.

Please Login/Register to leave a comment.

ADVERTISEMENTS

"A mind once stretched by a new idea never regains its original dimensions."

- Anonymous

ADVERTISEMENT

Sponsors