Weekly Status Report: The Template Your Client Reads to the End

There are two kinds of status reports nobody reads. The first has four pages, twenty charts and a summary that doesn't summarize. The second is one sentence: "everything is moving as planned". The first is exhausting; the second tells you nothing. Clients want to know three things, and they want to know them in two minutes: are we doing well?, what happened? and do I need to do anything?

A weekly status report that works is short, always has the same shape and answers those questions in order. Below, a five-block structure, a filled-in example and a way to put it together in minutes from what's already in your tasks.

The five blocks

Block	Question it answers	Length
1. Overall status	Are we on schedule, at risk or late?	One line
2. Completed this week	What was delivered?	3 to 5 items
3. Next steps	What's coming next week?	3 to 5 items
4. Risks and blockers	What could delay things or is already stuck?	0 to 3 items
5. Decisions and requests	What does the client need to do or decide?	0 to 3 items

1. Overall status

One line, with a clear signal: on schedule, at risk or late. It comes first because it's the only thing some readers will read. If the status changed since last week, say so: "at risk (was: on schedule)".

2. Completed this week

Deliverables, not activities. "Roof plan approved" is a deliverable; "we worked on the plan" is not. If nothing was completed, write that. A week without deliverables is important information.

3. Next steps

What will be done next week and by whom. It's the team's commitment, and next week's report will hold you to this block.

4. Risks and blockers

This is where honesty lives. A risk is something that could still happen ("the supplier may delay delivery"); a blocker is something that's already stopping work ("waiting for system access"). For each one, write the impact and what's being done about it.

5. Decisions and requests

The block clients need the most and find the least. List what depends on them: approve version 2 by Thursday, send the logo as a vector file, choose between options A and B. Without this block, the report informs but doesn't unblock.

A filled-in example

For a clinic's corporate website, in Curitiba, in week 6 of 9:

Overall status: at risk (was: on schedule). The photo delivery was three days late.

Completed this week:

• "Specialties" page published to the test environment
• Appointment form integrated with the front desk's email
• Mobile version of the home page approved by the client

Next steps:

• Build the "Team" page as soon as the photos arrive (Marina)
• Review the specialty copy (Rafael)
• Set up the domain and certificate (Camila)

Risks and blockers:

• Blocker: without the team photos, the "Team" page can't move forward. If they arrive by Wednesday, the publishing deadline holds.
• Risk: the clinic management's review of the copy doesn't have a date yet.

Decisions and requests:

• Send the team photos by Wednesday
• Confirm who at the clinic reviews the copy, by Friday

You can read it in under two minutes. And notice that the report doesn't hide the problem: the client knows what's causing the delay and what they can do to fix it.

How often to send it

Weekly is the right rhythm for most projects: frequent enough that the client doesn't feel left in the dark, spaced out enough that there's something to report. Three adjustments help:

• Same day, same time. Predictability is worth more than content. When the client knows the report arrives every Friday at 4 p.m., they stop asking on Wednesday.
• Short, intense projects need more. In a two-week sprint, a brief mid-cycle update helps.
• Maintenance projects need less. A monthly close may be enough if the flow is stable.

How to put it together in minutes, from your tasks

The reason status reports become a burden is that someone writes them from scratch, trying to remember what happened. If the work is already recorded in tasks, the report is a reading of them, not a piece of writing.

1. Completed this week: filter the project's tasks completed in the last seven days. Block 2 practically writes itself.
2. Next steps: filter the tasks due next week. That's block 3.
3. Risks and blockers: look at overdue tasks, those stalled for days and those waiting on a reply. The schedule shows what slipped and the effect on the dates that follow.
4. Overall status and requests: you write these two with judgment, but with the other three blocks already on screen.

Tasskee has reports and dashboards that bring this picture together, and the weekly status report template gives you the five blocks ready to fill in. With the habit of keeping tasks updated throughout the week, putting it together takes a few minutes.

Or let the client check whenever they want

An alternative, or a complement, is to give the client a place to look. In the client portal, they see the project's progress, deliverables, stages and what's waiting for their approval, without depending on an email on Fridays. The weekly report becomes the commented summary, and the portal is the source of the details. Both use the same tasks, so what the client reads in the report matches what they see in the portal.

Mistakes that kill the report

• Writing activities instead of deliverables. "Meeting with the team" tells the client nothing.
• Dressing up the status. An "all green" that turns red from one week to the next destroys trust. Flag the risk when it appears.
• Forgetting the requests block. If the client is the cause of the delay, the report needs to say so politely and with a deadline.
• Changing the format every week. Readers learn where to look. Change the format and they have to start looking again.
• Sending a giant attachment. If it needs an appendix, the body of the report isn't doing its job.

Where to start

Next Friday, write the report for your most important project in the five blocks, in a single screen at most. Compare it with what you used to send. If it came out shorter and clearer, repeat it the following week and turn it into a habit. In a month, the client stops asking "how are we doing?" because the answer already arrives at the usual time.

Variations for three common situations

A project that's running late

When the status is "late", the report needs to be even more objective. Open with the new expected date, explain the cause in one sentence and make clear what changes in the plan. Don't apologize for three paragraphs: the client wants the new date and what will be done to keep it.

A week with no news

It happens, during waiting phases or long stretches of work. Send the report anyway, short: "no deliverables this week; the team is focused on X, due Thursday". Silence breeds anxiety; a short, honest report breeds calm.

More than one client, more than one project

Anyone running several projects risks spending all of Friday writing reports. Standardize the format, keep each project's tasks updated during the week and set aside a fixed block of time for writing. For an agency with many clients, the gain from having the report almost ready from the tasks is big.

One last test before sending

Reread the report pretending to be the client, without knowing what happens behind the scenes. Ask yourself: do I know whether we're on schedule? Do I know what was delivered? Do I know what I need to do? If any answer isn't clear in the first thirty seconds, the report needs adjusting. A good status report is one that, once read, doesn't generate a question in return.

If the report takes up your Friday, see how Tasskee's Status Report does the job: the five blocks become a template, the numbers come from task progress, AI drafts the text for each block and the PDF is ready to send.