Project Status Report

What is a project status report?

A project status report is a weekly one-page summary of where a project stands: what was completed this week, what is on track for next week, what is behind schedule, what is blocking progress, and what the team plans to do next. It converts the 30-minute weekly status meeting into a 5-minute asynchronous update that serves the same purpose — keeping stakeholders informed — at a fraction of the time cost.

Melororium's Project Status Report pre-populates the data sections from the project board: tasks completed this week (from the Kanban board), hours logged (from the Time Tracker), and upcoming milestones (from the project calendar). The PM adds the RAG status (Green / Amber / Red), the blockers section, and next week's plan. The PDF is ready to send in under 5 minutes.

Why project status reporting is undervalued

Most agencies generate status reports only when clients ask — typically when a client is concerned about something they haven't heard. At that point, the status report is reactive: an explanation for why something wasn't communicated proactively, not a demonstration of proactive management.

Proactive weekly status reports, sent consistently on a fixed day each week, do the opposite: they establish a cadence of transparency that builds trust before problems occur. A client who receives a status report every Friday knows what's happening and doesn't need to ask. When problems do occur — a blocked dependency, a delayed deliverable — they appear in the Friday report with context and a plan, not as a surprise complaint.

What the project status report contains and why each section matters

RAG status — the single most important field

Green: project is on track and no significant risks. Amber: project is at risk — a specific issue could impact delivery if unaddressed. Red: project is behind — delivery will be impacted unless immediate action is taken.

The RAG status is the field that forces honest assessment. It's easy to write a status report that says everything is fine when the project is actually amber. A single-color status that the PM has to set explicitly — and that the client sees every week — creates accountability. Consistent amber status without resolution is a problem the PM and client both need to address.

Completed tasks vs. planned tasks

The completed section shows what was planned for the week and what was actually finished. If the plan was 8 tasks and 6 were completed, the completion rate is 75%. Over multiple weeks, a consistent completion rate below 70% signals a planning problem: the team is consistently over-committing relative to capacity.

Blockers with specific context

"Waiting on client feedback" is not a blocker description. "Design revisions waiting on client approval since [date] — if not received by [date], the development phase start date shifts" is a blocker description. The specific, dated format turns blockers into actionable items — for the PM, for the client, and for the stakeholder reading the report.

Next week plan as a commitment

The next week section isn't "we'll continue working" — it's a specific list of what will be completed by the next status report. This commitment structure creates weekly accountability and gives the client specific things to follow up on if the next status report doesn't confirm completion.

Project status report vs. project meeting

A weekly status meeting with 4 participants produces 2 hours of combined time cost every week — 100 hours per year per project. A weekly status PDF consumed asynchronously in 3 minutes per person produces 12 hours of combined time cost for the same period. The status report saves 88 hours per project per year.

Melororium generates project status reports from live project data. Agency plan for 10 users is $59/mo.