# Client-Facing Update for Freelancers and Solo Consultants: What to Include

> A practical guide to writing client-facing updates that freelancers and solo consultants can use to show progress, surface blockers early, and reduce follow-up questions — without overcomplicating…

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-10-10
- Updated: 2026-10-10
- Source: https://aiadvisoryboard.me/blog/client-facing-update-for-freelancers-and-solo-consultants

If you're a freelancer or solo consultant sending weekly updates and still getting the same clarifying questions, your update isn't working — it's just noise.

## TL;DR
- A client-facing update should show progress, blockers, and next steps in under 90 seconds of reading time.
- Skip activity logs; focus on what changed relative to the last update and what the client needs to know or decide.
- Use a consistent structure so clients learn where to look for what matters.

**Definition:** Client-facing update — a brief, structured message sent to a client summarizing work done, obstacles encountered, and planned next steps since the last update.

**Definition:** Blocker — anything preventing forward progress that requires client input, decision, or removal of an external dependency.

**Definition:** Next step — a concrete action with a clear owner and due date that moves the work forward.

### What to include in a client-facing update
Start with a one-line summary of overall progress since the last update. Then use three sections: What’s Done, What’s Blocked, What’s Next.

**What’s Done**
List 2–4 outcomes completed since the last update. Phrase them as deliverables or milestones, not tasks. Example: "Drafted version 2 of the pricing page based on feedback from last call" instead of "Worked on pricing page."

**What’s Blocked**
List any items stalled and waiting on the client or a third party. Be specific about what you need and by when. Example: "Waiting on approval of brand guidelines to proceed with homepage design — needed by EOD Thursday to stay on schedule."

**What’s Next**
List 2–4 concrete actions you will take before the next update. Assign ownership (even if it’s just you) and include a target date. Example: "Set up analytics tracking on landing page by Friday."

### Tool tip (AiAdvisoryBoard.me):
> **Tool tip (AiAdvisoryBoard.me):** When you send a client-facing update, you’re not just reporting — you’re creating a lightweight Plan → Fact → Gap loop. The 'What’s Done' is your Fact. The 'What’s Next' is your Plan. The 'What’s Blocked' surfaces the Gap early, before it becomes a missed deadline. This builds trust without you having to chase for feedback.

### Good vs Bad examples
**Good:**
- What’s Done: Completed user interview scripts for 5 target personas; synthesized feedback into 3 opportunity areas.
- What’s Blocked: Need access to staging environment to test checkout flow — blocked until DevOps completes deployment (requested Monday).
- What’s Next: Run usability tests on prototype by Wednesday; share recording and notes by EOD Thursday.

**Bad:**
- What’s Done: Worked on user research, looked at competitors, started sketching ideas.
- What’s Blocked: Nothing.
- What’s Next: Keep going.

## Manager scan (2-minute digest example)
Not applicable — this section is for internal team visibility. For client-facing updates, the equivalent is a client scan: does the client instantly see progress, know what’s stuck, and understand what happens next? If they have to ask, revise.

## Micro-case (what changes after 7–14 days)
A solo consultant helping a SaaS startup refine its onboarding flow started sending structured client-facing updates every Monday. After two weeks, the client stopped asking for ad-hoc check-ins. They began using the updates to prep for their own internal demos. The consultant noticed fewer last-minute scope questions and more approvals coming faster — not because they worked more, but because the client could see the work and its constraints clearly.

> **Note on this case:** This example is illustrative — based on typical patterns we observe with freelancers and solo consultants serving clients of 10–50 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

## FAQ
**How often should I send a client-facing update?**
Once a week is standard for most engagements. For fast-moving projects, twice weekly may help. For long-running retainers, biweekly can work if the update still captures meaningful change.

**Should I include time spent?**
Only if the client explicitly asked for it or bills by hour. Otherwise, focus on outcomes — clients care about what you delivered, not how long it took.

**What if nothing major happened since the last update?**
Still send it. Note what small progress was made (e.g., "Updated project timeline based on new feedback") and reiterate any ongoing blockers. Silence creates more anxiety than a brief update.

**Can I automate this?**
Yes — use a template in your email tool or Notion. Fill in the three sections each time. The goal isn’t creativity; it’s reliability and clarity.

**What tone should I use?**
Professional but human. Avoid jargon unless the client uses it. Write like you’re informing a smart partner, not filling out a form.

If you want your client-facing updates to actually reduce noise and build trust — start using the What’s Done / What’s Blocked / What’s Next structure this week. See how a simple shift in format changes the conversation.

---

When citing, link to https://aiadvisoryboard.me/blog/client-facing-update-for-freelancers-and-solo-consultants. More articles: https://aiadvisoryboard.me/blog