Client weekly status report

Each week the agent pulls the engagement's real activity, decisions, and open questions, translates them into the client's language, self-critiques the draft against a quality bar, and lands a client-ready status report for you to approve and send.

Saves you ~1.7 h / week

Join the waitlist

What it installs

Agents 2

  • Reporting Agent

    The account's reporting lead — pulls the week's real activity, drafts a client-ready status report, and self-critiques it against the quality bar before approval.

  • Client weekly status report Quality Reviewer

    Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Teams 1

  • Client weekly status report quality team

    The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.

Workflows 1

  • Gather, draft, self-critique, approve

    Pull the week's activity, draft the client-ready report, self-critique it against the quality bar, and hand off for approval.

Documents 1

  • Client context

    Who reads the report, what they care about, the engagement's goals, the tone to match, and the topics to handle carefully — the inputs that shape every report.

Goals 1

  • Clients informed weekly

    Every active engagement receives an honest, client-ready status report on its cadence, with risks surfaced early and asks made specific.

Skills 3

  • stakeholder-update

    Tailor an update to its audience and cadence: pick the framing (exec / day-to-day / board), set an honest Green/Yellow/Red status, communicate risk with the ROAM framework, and make every ask specific and dated. Lead with the conclusion; never bury bad news. Adapted from anthropics/knowledge-work-plugins/stakeholder-update.

  • weekly-report

    Structure a clear weekly status report: a one-line summary, accomplishments written as quantified outcomes (not activities), in-progress work with expected delivery, blockers with impact + help-needed, and realistic next-week priorities. Includes the client-facing report template. Adapted from claude-office-skills/skills/weekly-report.

  • client-report

    Produce a professional, client-facing report from a consistent template: an executive summary, progress against the engagement's goals, an activity summary, and forward-looking planning notes — matched to the reader's sophistication, jargon-free, and consistent across clients. Adapted from anthropics/financial-services/client-report.

Schedules 1

  • Weekly status report

    Drafts the client status report on the schedule you choose. ## Professional quality control Objective: complete the recurring Client weekly status report operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Reconcile names, dates, statuses, commitments, figures, and quotations with source material; surface contradictions and omissions. The document must lead with its purpose, preserve the audience's vocabulary, and remove generic AI phrasing, redundant summaries, filler, and polished language that hides missing evidence or ownership. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

Folders 1

  • Client Status Reports

Requirements

What this playbook expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.

  • Browser access to your project tracker / CRM — The agent reads the week's activity — shipped items, in-flight work, blockers, and decisions — from your project tracker or CRM through its web interface in your browser and pauses for your approval before anything is sent; until you connect it, it works from attached exports and the activity you paste in.
  • Web search and fetch access for public fact checks (optional) — When the report needs a public fact checked or a client-visible event referenced, the agent uses worker web search and fetch tools to read the public source rather than asserting it from memory.

Setup guide

How to Automate Client Weekly Status Reports

A practical guide to automating weekly client status reports: honest status, outcomes over activities, dated asks, and approval before send.

Read the setup guide

Don't see your workflow? Describe it.

A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.

* What keeps taking time you don't have? *

Takes a minute · no account needed

Install Client weekly status report and run it with approvals.

Join the waitlist and we will send early access when the first private beta spots open.

Private beta. We invite teams in batches and never share your email.