A project status report for clients covers four sections: a summary of overall progress, work completed this period, upcoming work, and anything you need from the client. Here's exactly how to write each section, with examples, and the mistakes that make most status reports go unread.

If you're looking for a broader overview of all freelance client communication types beyond status reports, see our complete freelancer client communication guide.

---

The 4-Section Structure

Every effective client status report follows the same skeleton, regardless of industry or project type:

1. Summary — One to two sentences. The single most important part of the report. Most clients read this and skim the rest.

2. Work Completed — Specific, not vague. Bullet points, not paragraphs.

3. Upcoming Work — What happens next, ideally with rough timing.

4. Client Action Items — Anything you need from them, with a deadline if it affects the project timeline.

That's the entire structure. Everything else is optional padding that slows the client down.

If you need a shorter, less formal format, see our weekly client update template with copy-paste examples.

---

Section 1 — The Summary

This is the part clients actually read. Everything below it is reference material they skim or skip. Write the summary as if it's the only sentence they'll see.

Weak summary: "This week we made good progress on various aspects of the project and things are moving along well."

This says nothing. It's the equivalent of "fine" when someone asks how you're doing.

Strong summary: "Homepage design is complete and approved. We're on track for the July 15 development handoff, with no current blockers."

Specific, confident, and answers the question every client actually has: are we on track?

Formula for a strong summary: [What's done] + [Current status: on track / ahead / behind] + [Anything urgent, or "no blockers"]

---

Section 2 — Work Completed

Use bullet points. Each bullet should be specific enough that the client could explain it to someone else if asked.

Weak:

• Worked on the design
• Made some progress on the backend
• Fixed some bugs

Strong:

• Finalised homepage layout for desktop and mobile (3 breakpoints)
• Implemented the user authentication flow with email verification
• Fixed the checkout page crash reported in Tuesday's QA session

The difference is specificity. "Worked on the design" could mean anything. "Finalised homepage layout for desktop and mobile" tells the client exactly what exists now that didn't exist a week ago.

A useful test: if you removed the project name, could someone tell this update apart from a generic placeholder? If not, it's too vague.

---

Section 3 — Upcoming Work

This section sets expectations and prevents the most common client anxiety: not knowing what happens next.

Weak: "Next we'll continue working on the project."

Strong: "Next week: building out the checkout flow and integrating the payment gateway. Targeting end of next week for a working test version."

Include rough timing where you can. Clients don't need exact dates for every item, but "next week" versus "in the coming weeks" communicates very different levels of confidence.

---

Section 4 — Client Action Items

This is the section freelancers most often forget, and it's the one that prevents the most project delays.

If you need something from the client — feedback, approval, assets, access, a decision — say so explicitly, with a deadline tied to its impact on the timeline.

Weak: "Let us know if you have any feedback."

This is too passive. The client doesn't know if this is urgent or optional.

Strong: "We need your approval on the homepage design by Thursday to keep the July 15 launch date on track."

This tells the client exactly what's needed, by when, and why it matters. It's far more likely to get a timely response.

---

A Complete Example

Subject: Acme Corp Redesign — Status Report, Week of June 23

Summary: Homepage design is complete and approved. Mobile layouts for the top 3 pages are finished. On track for the July 15 development handoff.

Work Completed:

• Finalised homepage design across desktop and mobile
• Built responsive mobile layouts for Home, About, and Services pages
• Completed navigation restructure based on user testing feedback
• Resolved the header overlap issue flagged in last review

Upcoming Work:

• Inner page templates (Contact, Blog, Case Studies) — targeting completion by July 3
• Beginning development documentation handoff

Action Items:

• Approval on the homepage design needed by Thursday to stay on schedule
• SVG logo files needed for the footer (current PNG has resolution issues at small sizes)

---

The Most Common Mistakes

Burying the lede. If the most important information is in paragraph three, most clients never see it. Lead with the summary, always.

Writing for yourself instead of the client. Internal jargon, technical detail nobody asked for, and process descriptions the client doesn't care about all slow the report down. Write for someone with zero context on the technical details — they care about outcomes, not implementation.

No clear action items. A status report that doesn't tell the client what's needed from them produces silence. Silence produces delays. Always end with a clear ask, even if the ask is simply "no action needed — just keeping you posted."

Inconsistent frequency. A weekly report that becomes biweekly, then monthly, then stops entirely erodes client confidence faster than almost anything else. If you can't sustain weekly, commit to biweekly from the start rather than letting cadence slip.

Length creep. Status reports tend to get longer over time as freelancers try to demonstrate value by including more detail. The opposite is true — concise reports signal confidence. Verbose reports signal anxiety about whether the work speaks for itself.

---

A Faster Way to Write These

The structure above takes 15–30 minutes to execute well — pulling together what you did, organising it, writing it in a tone that's specific but not robotic.

Briefloop generates this exact structure automatically. You provide your notes (or connect Toggl Track, Loom, or your Upwork contract and Briefloop pulls the data itself), and it writes a status report following this four-section structure — summary, completed work, upcoming work, and client action items — in under 60 seconds.

For freelancers who use Toggl Track for time logging, our Toggl to client report guide covers how to turn time entries directly into a status report.

For Upwork contracts specifically, see our Upwork weekly update message guide, which covers platform-specific norms and Job Success Score impact.

---

Frequently Asked Questions

How long should a project status report be? 200–350 words for most projects. Long enough to cover all four sections with specificity, short enough that a client can read it in under a minute. If a single section is running long, it usually means it needs to be split into bullet points rather than written as a paragraph.

How often should I send status reports to clients? Weekly for active projects longer than two weeks. For shorter sprints, send a report at the end of each phase or milestone. For long-term retainer clients, weekly or biweekly both work — consistency matters more than frequency.

What's the difference between a status report and a progress update? Largely interchangeable in practice. "Status report" tends to sound more formal and structured, often associated with agency or enterprise contexts. "Progress update" sounds more conversational. Both should follow the same four-section structure.

Should a status report include hours worked? For hourly contracts, yes — include hours logged this period, ideally broken down by task. For fixed-price projects, hours are usually not necessary unless the client specifically asks for time tracking transparency.

What if there's bad news to report — a delay or a problem? Include it directly in the summary, not buried lower in the report. State what happened, why, and what you're doing about it. Clients respond far better to early, honest communication about problems than to a status report that quietly omits the issue and lets them discover it later.

Can I automate writing project status reports? Yes. Tools like Briefloop connect to your time tracking (Toggl), video notes (Loom), or platform data (Upwork contracts, Fiverr orders) and generate a structured status report automatically, following the same four-section format outlined above.

---

Briefloop is an AI client director for freelancers. Connect Toggl, Loom, Upwork, or Fiverr and get a professional status report in under 60 seconds. Try it free →