A client found out their website relaunch was pushed back three weeks not because the agency told them, but because they noticed the live date on the shared calendar had quietly moved. By the time the account manager got on a call to explain, the client had already forwarded the old launch date to their board. The relationship survived, technically, but it never quite recovered.
That agency had been running weekly check-in calls and sending long update emails. Neither worked. The calls were informal enough that bad news got buried in small talk, and the emails were long enough that clients stopped reading them.
A well-structured project status report would have flagged the delay before it became a surprise. That is what this template is for.
What a project status report actually is
A project status report is a structured, recurring document that tells a client exactly where their project stands during a given period, usually a week or a fortnight. It covers what was completed, what is coming next, the current health of the timeline, any risks on the horizon, and a snapshot of budget.
It is not a meeting agenda, a project plan, or an invoice. It is a communication tool that keeps clients informed without requiring them to ask questions.
For agencies, sending a consistent project update template each week serves two purposes: it keeps the client in the loop, and it protects the agency by creating a paper trail of decisions, delays, and scope.
Why most agency status reports do not work
Most agencies do send updates. The problem is the format.
- They are too long. A three-page narrative update written for someone who reads every word is not a status report - it is a journal entry. Most clients will not read past the first paragraph.
- They are too vague. "Good progress this week" tells a client nothing useful. If the milestone was due Friday and it is now Monday, clients deserve to know that clearly, not discover it themselves.
- They are written for the wrong person. Account managers often write reports for other account managers: full of project terminology, internal shorthand, and process detail. The client - often a founder, CMO, or department head, wants a different level of detail.
- They use the wrong format. A wall of prose buries the signal. Clients who are time-pressed will scan for the one thing they care about, is this on track? - and if they cannot find it fast, they will call you to ask.
The fix is not to write better prose. It is to use a structured template that forces the important information into a predictable format every single time.
What a client actually wants to know in a status report
Strip away everything else and most clients are asking five questions:
- Are we on track? Green, yellow, or red, give them a direct answer at the top.
- What did you do this week? A short, specific list. Not "worked on the website" or "completed homepage wireframes and got them to review."
- What are you doing next? And by when. This is accountability.
- Is there anything I need to worry about? Be honest. If there is a risk, name it early.
- How is the budget tracking? Even retainer clients want to know this. Surprises here are the ones that end contracts.
Every section in this template maps to one of those five questions.
What to include in a weekly project status report
1. Project Overview
The basics that make each report self-contained: project name, client, account manager, report date, and the reporting period (week or month). Include an overall status indicator on track, at risk, or off track so the client knows the headline before they read anything else.
Colour-coded status labels (green, yellow, red) work well here. They are fast to read and unambiguous. Avoid softening the language. "Slightly delayed" means less than "At Risk."
2. Executive Summary
Three to four sentences covering what happened this period, what is coming next, and any critical issues. This is the part most clients actually read. Write it last, once you have filled in everything else.
Keep it factual. "We completed the integration with Stripe. The checkout flow is now in QA. One blocker on the client's API credentials is holding up the final test run." That is a useful executive summary.
3. Milestones and Progress
A table listing each key milestone with its due date, current status (green/yellow/red dot), percentage complete, and a brief notes column. Six rows covers most projects.
The status dot column does most of the work. A client can scan six dots in two seconds and know exactly where the project health is without reading a sentence.
4. Completed This Period
A bullet list of what actually got done. Be specific and concrete. "Delivered revised brand guidelines to client" is better than "brand work." Six lines is the right number, if you need more, your sprint may be too large.
5. Planned Next Period
Another bullet list, but this one includes a "by when" column for each item. This is the most powerful section for managing expectations. It is a commitment, not a vague promise. Both sides can refer back to it.
6. Risks and Blockers
A table covering any known issues: what the issue is, its impact level (high, medium, or low), who owns it, what the resolution plan is, and the target date to resolve it.
High-impact items should show up here even if they are not yet causing delays. This section is what separates agencies that manage risk from agencies that are always chasing fires.
7. Budget Snapshot
Approved budget, spent to date, remaining, and hours logged this period. Include a simple visual indicator showing what percentage of the budget has been consumed.
For fixed-price projects, this section tells clients they are getting what they paid for. For retainers, it keeps both sides honest about scope creep before it becomes a conversation.
Project Status Report Template
Use this template as a starting point. The PDF is formatted for print and email, covers all seven sections above, and includes colour-coded status indicators throughout.
Download Free Project Status Report Template (PDF) →
The template is designed to take less than fifteen minutes to fill in each week. If it is taking longer, the project scope may need to be broken down further before reporting.
How often should you send project status reports
For most agency projects, weekly is right. It creates a rhythm clients come to expect, and it means problems surface within days rather than accumulating for a month.
Some agencies use bi-weekly reports for longer, slower-moving projects. Monthly is rarely enough, anything that goes wrong can sit unaddressed for four weeks before a client even knows about it.
For active retainers with regular deliverables, weekly makes sense even if a given week has light activity.
Consistency matters more than the volume of news to report.
Red, amber, green: using status indicators without panicking your client
The traffic-light system (red, amber, green) is standard in project management for good reason. It is fast and unambiguous. But agencies sometimes avoid marking things amber or red because they are worried it will alarm clients unnecessarily.
That instinct is understandable and exactly wrong.
Clients who only ever see green status reports develop two problems. First, they stop reading because nothing ever changes. Second, when something does go red, it comes as a complete surprise, and the trust damage is much worse than if you had flagged it as amber two weeks earlier.
Use the status indicators honestly. Green means the milestone is on track with no known issues. Amber means there is a risk or minor delay but a clear path to resolution. Red means the milestone is delayed or blocked and needs a decision or action.
When you mark something amber, pair it with a brief explanation in the notes column and a resolution plan in the risks section. Clients do not panic at amber they panic at unexpected red.
FAQ
What is the difference between a project status report and a client report?
A project status report is project-specific and tied to a timeline. It tracks milestones, tasks, and delivery against a schedule. A monthly client report is typically broader covering work done, results achieved, and metrics across a retainer period. Both serve communication purposes, but they operate at different levels.
How long should a weekly project status report be?
One to two pages. If it is longer, you are reporting on too much detail or not structuring it well. The goal is for a client to scan it in under three minutes and come away knowing exactly where things stand.
Should the client see the status report before the weekly call?
Yes. Send it at least an hour before any standing call. This shifts the call from information delivery to discussion. Clients who have already read the report can come prepared with specific questions, which makes the conversation more useful for everyone.
What if there is nothing to report?
There is always something. Even a quiet week is worth documenting: what is still on track, what is coming next, and confirmation that no blockers emerged. A brief status report in a light week is far better than silence, which clients typically interpret as a sign that something has gone wrong.
Can this template work for a client portal?
Yes. Many agencies embed their weekly status report directly in their client portal rather than emailing a PDF. This keeps the audit trail in one place and gives clients an easy way to view the history of updates without digging through inboxes. If your agency uses a portal, a consistent report format makes it much easier to structure the content view.
See also: client onboarding - setting expectations around how and when status reports will be delivered is a good step to include in onboarding.