Why Your Project Reports Aren’t Working (And How to Fix Them)

Photo by Scott Graham on Unsplash

The project report is a part of project management. It describes what is taking place in a project.

Project reports have to be taken with attention. A good report summarises all the updates done by the team and turns them into a clear message. This makes everyone know the status of the project and what needs to be addressed next.

There must be three main things in every project report: status, challenges, and next steps. It also must contain who’s doing what and by when. These details together will give a clear picture of the overall project’s health.

Not Medium members? **Read here**

Why write project reports?

Reports are a way to share updates and keep everyone in the loop throughout the project stages. Without reports, project updates will be scattered and create a misunderstanding

In my earlier years, I viewed project reports as a check-off on a to-do list, so I didn’t pay much attention to the contents, but rather to how they would appear. I was doing it to keep stakeholders happy without really understanding their purpose.

The result? My reports were routine, which I perceived as unwanted assignments. Stakeholders would scan them over without getting a clue of the actual state of the project.

This approach turned in the wrong direction the moment the office renovation started. My reports were good, but did not clearly communicate the coordination issues of the flooring, electrical, and painting crews. At the time when the stakeholders realized that there was a scheduling problem, we had already spent a week over the schedule and exceeded the budget.

This experience helped me realize that project reports aren’t about impressing anyone, but about giving a diagnosis of the project’s health.

These are the mistakes that I have observed in the project report:

1. Not Tailored Based On the Audience

The same report can’t satisfy every receiver. Presenting the same information to all audiences can be confusing.

Executive Reports should be concise, as they oversee multiple projects and are concerned with the organization's overall impact. The report should have a short, executive summary that summarizes the project’s health, significant risks, and any key information the executive needs to know. It is generally more effective to have a one-page executive dashboard than a ten-page progress report.

Project Sponsor Reports should be more detailed about operations. Sponsors must know very much about the health of the entire project, budget usage, resource allocation, and risk mitigation strategies, since they are also responsible to ensure the success of your project. They want to know progress against milestones, decisions to be made, and what blockers may affect project delivery.

Client Reports require transparency and trust-building. Clients want to know how their projects are progressing and be assured of your project management competence. Focus on what has been delivered, milestones met or milestones not met, and the budget. Whenever you bring up problems, bring the solutions, too. Avoid reports that contain technical terms that the clients will not understand, and instead focus on results.

Each audience requires a varying degree of information presented in a project report; executives require an overview, sponsors want reassurances that their budget isn’t at risk, and clients want to know everything is fine. Writing a report to please them all is like trying to serve coffee that’s strong, mild, black, and with cream, at the same time.

Before starting to write any report, ask yourself a question: To whom is the report going to be addressed? What should they know? What do they need to do?

2. Including Unnecessary Information

If you’re new to project management, you may think that your job is to prove you’re paying attention to everything. But, your real job is to filter the noise and highlight what’s important for stakeholders.

Every report must tell a story, but that doesn’t mean you can include everything, like overloading a suitcase with things you’ll never use on your trip.

Picture this: You’re managing a restaurant renovation. Over the years, several restaurant tenants have occupied the same building. Now, you and your team are going to reconstruct the interior, and the landlord is taking advantage of the situation and is going to replace the entire roof.

While these roofing topics are outside of your scope, they could indirectly impact your workflow schedule.

During the coordination meeting, there are several stakeholder groups involved:

• The landlord of the property
• The landlord’s contractor team.
• You and your construction team.

The main topic is deciding which roofing equipment will be salvaged and which will be trashed, along with technical discussions about roofing materials and structural requirements.

Now consider which parts of this meeting information are unnecessary, necessary, or simply “nice to know” for your report.

You don’t need to overload your report with all the information from every meeting. When everything seems important, nothing is really important.

What the stakeholders need to know is:

• Current progress vs plan
• Roadblocks vs proposed solutions
• Budget vs actual spending
• Decisions made this week

By doing so, you help your stakeholders see the big picture instead of getting lost in irrelevant details.

3. Lack of Evidence

You say progress is 50%, but where is the evidence to support this claim? Project reports must include data that complements your statement, giving stakeholders confidence in your assessment.

During an office fit-out project, I received a progress update from a subcontractor stating that the meeting room built was 70% complete. When the client visited the site, they found only partition walls put up, no glass installed, and the floor hadn’t been touched. The percentage was based on the subcontractor’s statements, not on measurable actual progress. This mismatch between stated progress and what was done caused confusion.

To address this, I created a progress checklist for each room, breaking it down into measurable components, such as walls, electrical work, installing finishes, and final cleaning. I also collected weekly photos.

Providing clear evidence shows your professionalism and helps others trust you to complete a project correctly.

4. Reporting Only On What’s Going Well

Everyone loves good news (me included), but project reporting requires transparency. Sharing only the positive news, you’re delivering incomplete data that will lead to poor decisions.

It’s natural to want to present your project in the best light possible. Sometimes, project managers hesitate to report problems before they have solutions, hoping to resolve issues quietly.

This approach seems reasonable, but it will cause:

• Delayed problem-solving: issues that can be solved with early stakeholder input escalate into crises.
• Trust issues: When problems arise, stakeholders feel deceived and will question your competence.
• Poor resource allocation: Stakeholders can’t adjust priorities if they don’t know that problems exist.

Hiding problems doesn’t protect anyone; it just delays the inevitable and makes solutions more difficult.

5. Reporting Without Actionable Outcomes

Reports without actionable outcomes are just diaries. Project reports don’t just document what happened, but they also contribute to the decision-making process. If your stakeholders read your reports and are not sure what to do next, you need to review your reports.

The key to actionable reporting is in framing problems as decision points rather than just informational updates. Every problem you report should lead to a next step that moves the project forward.

Consider these two approaches when reporting the same issue in a home kitchen renovation.

a. Non-actionable report:

Issue Encountered:

• The electrician found outlet situation with kitchen island
• Might need code updates
• The timeline could be affected
• Working on solutions

Next Steps:

• Continue investigating electrical requirements
• Get back to homeowner with options

b. Actionable report:

IMMEDIATE DECISION REQUIRED: Kitchen Island Outlet Installation

Issue: The kitchen island requires two additional outlets to support the planned appliances.

Situation: Your kitchen island needs two additional outlets to power the planned appliances and meet safety requirements.

Impact: 1–2 day schedule delay, $250–400 additional cost.

Options Evaluated:

1. Built-in island outlets — 2 days, $400 (recommended)

Clean look, convenient for daily use.

Note: if existing underground piping can’t be used, add $500 for trenching and repiping.

2. Hanging ceiling outlets — 1 day, $250

Faster and cheaper, but cords hang down from the ceiling.

Recommendation: Option 1 — the built-in outlets will look much better and be more practical for using your mixer, coffee maker, and other appliances.

Required: Your decision by Thursday, 3/18, so we can order materials and stay on track for your party deadline.

Next Week: Complete all electrical work, then move to drywall installation.

There are benefits in this actionable report example:

1. Eliminates back-and-forth communication: you provide information so the client can make their decision.
2. Keeps the project moving forward: By giving a deadline, you prevent the project from getting delayed.
3. Builds trust: When you present evaluated options with recommendations, you show proactive problem-solving rather than just reporting.
4. Creates accountability: With a specific deadline and next steps, both you and the client know what needs to happen when. No one is left wondering.

Tips:

• When you spot a problem, think of solutions.
• Provide two to three realistic and feasible solutions, along with a corresponding recommendation.
• Set deadlines for the decisions made.

6. Reporting Too Late

Timing matters. Too late or inconsistent reports affect the visibility and urgency of the issue handling.

Often, PMs don’t want to send unclear updates because it appears that more questions will be coming, so they wait until they have all the answers. This kills projects.

Here’s a scenario:

Say you’re managing a cafe fit-out inside a mall. You’re almost done with all work: flooring, walls, and lighting, and now it’s time to install custom furniture: the bar counter.

The furniture team was supposed to work on Thursday, but didn’t show up. You called them and they said they will come next Monday. You didn’t include this in the weekly report because you want to wait for more details.

Your client invited the mall management for a walk-through on Friday to see the nearly completed space. The missing bar counter makes everything look unprofessional. Now you’re left trying to justify why the client wasn’t informed about the delay in advance.

I made this mistake in the past, when I felt the need to wait to have “complete” answers. I left the stakeholders with assumptions they might have.

Instead of waiting for perfect information, send what you know with a clear timeline for updates: Furniture installation delayed until Monday. We are investigating the cause and will update by Friday with a revised timeline and any additional impacts.

This approach does two things: it keeps stakeholders informed, and it shows that you’re taking charge of the situation instead of waiting for it to fix itself.

7. The Chaos Format

Changing the report format and layout isn’t recommended. The reason we maintain a structure and layout consistently is that stakeholders are able to read and understand it. Variety does not make a report interesting; it just makes more time for stakeholders to figure out what they think they’re missing, or what information they expect to see.

Tips:

1. Create a report template and use it every time.
2. Keep the same sections in the same order.
3. Use the same definitions for status indicators.
4. Only change the format if there’s a compelling business reason, such as: stakeholders demand specific requirements to be included in the report, or the current format causes frequent misinterpretation.

Wrap Up

A project report serves as a bridge between the project team and key stakeholders throughout the planning and completion phases. Project reports transform complex information into actionable tasks.