Client Progress Report Template for Agencies (Copy and Paste)

If you run an agency or freelance, you have probably sent a client update that took an hour to write and got a one-word reply. Or no reply at all.

The problem is rarely the work. It is the format. A good client progress report is short, predictable, and answers the questions the client is quietly asking: Are we on track? What have you done? What do you need from me?

Below is a template you can copy, a filled-in example, and some advice on cadence and common mistakes.

What a good client progress report includes

Six parts cover almost every project:

• Summary: one or two sentences with an overall status: on track, at risk, or blocked, and why.
• Done since the last report: finished deliverables, in plain language, not task names from your project board.
• In progress: what the team is working on now, with an expected date.
• Coming next: the next steps and when you plan to start them.
• What we need from you: decisions, files, or approvals, each with a date. This is the section that keeps projects moving.
• Risks or changes: anything that could affect the schedule, budget, or scope. Say "None" if there is nothing, so the client knows you checked.

The template

Copy this into an email, a document, or your project tool and fill in the brackets.

Subject: [Project name] progress report, [date range]

Hi [Client first name],

Here is where things stand on [project name].

1. Summary
[One or two sentences. Status: on track, at risk, or blocked, and why.]

2. Done since the last report
- [Deliverable or milestone, in plain language]
- [Deliverable or milestone]

3. In progress
- [What is being worked on now] (expected: [date])

4. Coming next
- [Next step] (planned start: [date])

5. What we need from you
- [Decision, file, or approval] by [date]

6. Risks or changes
- [Anything that could affect date, budget, or scope. Write "None" if there is nothing.]

Next report: [date]

[Your name]

A filled-in example

Subject: Website redesign progress report, Oct 14 to Oct 20

Hi Dana,

Here is where things stand on the website redesign.

1. Summary
On track. The homepage design is approved and development has started.

2. Done since the last report
- Homepage design approved
- Brand fonts and colors added to the style guide

3. In progress
- Building the homepage layout (expected: Oct 27)
- Writing copy for the services pages (expected: Oct 29)

4. Coming next
- Pricing page design (planned start: Oct 28)

5. What we need from you
- Photos of the team, by Oct 24
- Feedback on the services copy, by Oct 31

6. Risks or changes
- None

Next report: Oct 27

Sam

Notice what is missing: task IDs, internal chatter, and anything the client cannot act on or does not care about.

How often to send it

There is no single right answer, but these defaults work for most agencies:

• Active project with a deadline: weekly.
• Ongoing retainer: every two weeks or monthly, with a short note in between if something important changes.
• Long projects with clear phases: at the end of each milestone, plus a short weekly check-in if the client asks for it.

Pick a day and stick to it. Predictability matters more than frequency. A client who knows the report arrives every Friday stops asking "any update?" on Wednesday.

Five mistakes that get reports ignored

• Too long. If it does not fit on one screen, most clients will not finish it. Link to details instead of pasting them.
• Internal language. Clients do not know what "QA pass on the sprint backlog" means. Say "we tested the new pages and fixed three issues."
• No ask. If you need something from the client, put it in its own section with a date, not in the middle of a paragraph.
• Only good news. A report that never mentions risks teaches clients to distrust it. Flagging a small problem early is cheaper than explaining a big one later.
• Inconsistent timing. Sending a report when you remember, instead of on a schedule, trains clients to chase you.

When writing them by hand stops making sense

A template removes the thinking, but you still have to collect the facts: what moved on the board, what is finished, what is waiting. Across several clients, that adds up to hours every week.

At that point, it is worth pulling progress straight from the tool where the work already lives. If you are still deciding how to give clients visibility at all, our guide on sharing a Trello board with a client without giving them access covers the options and what each one exposes.

We built ClientReportly for this. You connect a Trello, Asana, or Notion board, and it generates PDF progress reports under your agency's name and gives clients a read-only portal, while the board stays private. It is one option among several. If you try something else, keep the six sections above, because they are what clients read.