An agency status report should tell the client what changed, what is blocked, which decision is needed and what happens next. Build it from owned project records, then review it for accuracy and client relevance. Separate operational progress from marketing performance so the report does not confuse completed work with business results.
- Current project recordMaintain owners and task statuses.
- Check report claimsLink important statements to sources.
- Client decisionName the responsible contact.
- Owned next stepRecord the response back in project work.
Keep operational progress separate from measured performance.
Decide what the client needs to know
A status update should help the client understand progress and act on relevant decisions. It does not need to reproduce every internal task. Agree on the audience, purpose and reporting rhythm during onboarding.
- Operational updateWork, dependencies, and next steps.
- Performance reportMeasured outcomes from relevant sources.
- Defined periodState measure, period, and source.
Completed setup is not evidence that a campaign achieved its goal.
An operational update explains work, dependencies and next steps. A performance report explains measured outcomes from the relevant sources. They can appear together, but their meanings should remain clear. Completing a campaign setup is not the same as showing that the campaign achieved its goal.
Define a small report structure
| Report section | Useful content | Source owner |
|---|---|---|
| Since the last update | Meaningful completed work and changes | Delivery owner |
| Current work | Active deliverables and stage | Project owner |
| Blockers | Dependency, effect and required action | Blocker owner |
| Client decisions | Specific request and responsible contact | Relationship owner |
| Next steps | Planned action and conditions | Delivery owner |
| Measured results | Defined measure, period and source | Reporting owner |
If a section has no meaningful update, state that plainly or omit it according to the agreed format. Repeating old information can make a report look busy while obscuring what actually changed.
Prepare from the project record
Keep owners and task statuses current before assembling the report. If the project system does not reflect reality, generating a polished summary from it will repeat the error more efficiently.
- Check current statusKeep owners and tasks current.
- Verify the statementLink to the deliverable, decision or defined measure.
- Explain open dependenciesShow their effect on the next step.
- Prepare the reviewed summaryKeep claims consistent with the evidence.
Do not label work on track without a clear basis.
Require a source for each important statement. Link to an approved deliverable, recorded decision or defined performance measure. Avoid language such as “on track” without a clear basis. If timing depends on an unresolved input, show that dependency and its effect.
For an illustrative website engagement, design review may be complete while a client asset is still missing. The update can say which work was approved, which asset is needed and which next step depends on it. That is more actionable than labeling the whole project green.
Review before sharing
Have a named person check that the update matches the current project and is appropriate for the client. Remove internal comments, unrelated account information and unverified interpretations of performance.
If a summary is drafted by an AI tool, compare it with the source records. A fluent sentence can combine separate tasks or turn an intended action into a completed result. The reviewer should verify those distinctions rather than only edit the tone.
Turn decisions into owned actions
A report that asks for a decision needs to identify the person who can make it and where the response should go. Record the response back in the project so it is available to delivery.
When the client does not respond, follow the agreed escalation or review process. Do not let an old reporting request become a permanent hidden blocker. The approval workflow provides a more detailed model for version-specific deliverable decisions.
Measure usefulness
Review whether clients can identify their required actions and whether delivery can find the resulting decisions. Track reports prepared with outdated statuses, recurring clarification questions and blockers without an owner.
Useful reporting often starts with improving source records and responsibility. Changing the visual format alone cannot fix conflicting data. Once the record is trustworthy, a repeatable report can reduce preparation effort without hiding the judgment needed to explain what matters.
Choose a dashboard, a summary or both
Start with the decision the client needs to make. A dashboard can help someone explore current measures, while a short written or recorded summary can explain what changed and which action is required. Those are different jobs.
- Client decisionStart with action the client needs.
- DashboardExplore current measures.
- Written summaryExplain changes and required action.
- Project recordKeep important decisions accessible.
Test whether the actual audience can find an outstanding decision and explain the next step.
Test the format with the actual audience. Ask the client to find an outstanding decision and explain the next step. Check whether access, unfamiliar labels or too much detail make that harder. Avoid assuming that providing a dashboard means the client has understood the update.
If performance measures are included, identify their source and period. Keep the interpretation separate from the agency's delivery status. Use the format that supports the agreed communication, and keep important decisions in the project record regardless of how the update is presented.
Questions and answers
Should a status report include every internal task?
Include information relevant to the client’s understanding and decisions. Summarize meaningful progress, blockers and next steps rather than copying the task list. Internal detail can remain linked or available when it helps explain a particular issue.
Can an AI tool write the client status update?
It can help draft a summary if your agency permits the data use and the source records are reliable. A named reviewer should verify completion claims, dependencies, account boundaries and measured results before the update is shared.
What is the difference between progress and performance?
Progress describes work and delivery stages. Performance describes measured outcomes over a defined period using a stated source. Keep those separate so a completed deliverable is not presented as proof of a business result that has not been measured.