Back to all articlesAgency customer operations

Design an Agency Client Report Around Decisions the Client Must Make

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A client can read every page of an agency report and still miss the approval that determines what happens next. The report may explain what the team completed, show encouraging results, and list upcoming work without saying which choices belong to the client.

Design the report in reverse: identify the decisions the client must make, assign an authorised decision-maker, and include only the evidence needed to make those choices responsibly. Separate those requests from information that needs no response. A report should make it possible to answer: What needs my attention, what are my options, and what happens if I wait?

The practical starting point is a reporting brief agreed with the client. It links each report section to its audience, decision, evidence, caveat, and requested response. That agreement matters more than a polished layout: it defines what the agency is asking for and what the client is authorising.

1. Agree on the decisions before choosing the sections

Start with the work that could change because of the next review. Ask the account lead and client sponsor to identify the choices expected before the following reporting cycle. Typical choices include approving a scope change, resolving a dependency, choosing between competing priorities, or accepting a recommendation to continue the current plan.

Then distinguish three kinds of material:

  • Client decision: a choice outside the agency's delegated authority, such as changing an agreed priority or committing additional resources.
  • Client input: information or access the agency needs, such as a confirmed product position or an available reviewer.
  • Status: information that helps the client understand progress but requires neither approval nor input.

Do not turn every operational adjustment into a client decision. If the agency already has authority to make it, report the adjustment as status where relevant. Asking permission unnecessarily slows delivery and obscures the decisions that genuinely need attention.

The reporting agreement should name who can decide, who advises, where responses are recorded, and how unresolved requests are handled. It should also state which work can continue while a decision is pending. A report cannot repair an authority gap simply by addressing a request to a senior person.

2. Give every section a decision-usefulness test

Before including a section, complete this sentence: “The reader needs this information to decide whether to ___.” If the sentence cannot be completed, test whether the material provides essential context for an active decision or exception. If not, move it to a supporting record or remove it.

This does not mean deleting all status information. Clients may need to know whether agreed work remains on course even when no intervention is required. The useful distinction is between a short statement of health and a catalogue of effort.

For a hypothetical content project, “Drafts prepared and reviewed” describes activity. “The agreed release remains feasible, but the client must choose a reviewer before final review can begin” connects progress to a dependency. The activity detail belongs underneath only if it helps the client judge that dependency.

Use consistent labels at the start of sections:

  • Decision required: the client must choose among stated options.
  • Input required: the client must supply something specific.
  • For information: no response is requested.

Acknowledging receipt is not the same as approving a recommendation. If acknowledgement itself is necessary, label it as a response request rather than hiding it inside an informational section.

3. Use this filled fictional report brief

Fictional worked example: The organisations, people, dates, quantities, and circumstances below are hypothetical. They illustrate a reporting design, not customer results.

Engagement: Northstar Studio supports Harbor Office Supply with a customer-facing resource launch. The agency can sequence work within the approved scope. The client retains authority over scope changes, business priorities, and publication approval.

Reporting agreement: A written report is issued each Tuesday during launch preparation. Requests are answered in a shared decision record linked from the report. A meeting is reserved for unresolved choices or conflicting instructions. Silence is not approval, and any later change to an approved choice is recorded as a new decision.

Intended outcome of this report: Select the launch package, confirm a reviewer, and decide whether an additional deliverable replaces existing work or waits.

Section A: Current position

  • Label: For information.
  • Audience: Client sponsor Maya Chen and operations lead Lewis Grant.
  • Decision supported: Whether intervention is necessary to protect the agreed release. No intervention is currently recommended beyond the requests below.
  • Supporting evidence: The core draft is ready for client review. Design preparation can continue. Publication remains dependent on content approval and reviewer availability.
  • Caveat: Readiness for review is not publication approval. The release remains conditional on the client decisions in this report.
  • Requested response: None. If the underlying business priority has changed, raise that change against Section B.

Section B: Choose the launch package

  • Label: Decision required.
  • Audience: Maya, as the client sponsor authorised to set priorities.
  • Decision: Launch the core resource first, or hold it until the supplementary guide is ready.
  • Supporting evidence: The core resource is ready for review. The guide still needs client-supplied examples. The current plan allows the core resource to be released independently.
  • Recommendation: Review and release the core resource first, then schedule the guide when its inputs are available.
  • Caveat: This recommendation favours earlier availability, not proven commercial superiority. The agency cannot yet establish which package will be more useful to customers.
  • Requested response: By Thursday at noon in the client's agreed time zone, record “core first” or “combined release,” with any conditions. If no decision arrives, publication stays on hold while independent preparation continues.

Section C: Confirm the client reviewer

  • Label: Input required.
  • Audience: Lewis, who coordinates client review resources.
  • Decision: Who will provide a consolidated client response and whether that person can approve content or only advise.
  • Supporting evidence: Comments from sales and operations have not yet been reconciled. The agency needs a consolidated position before revising the final draft.
  • Caveat: Naming a reviewer does not itself grant publication authority. Any approval limits must be explicit.
  • Requested response: By Wednesday afternoon, provide the reviewer's name, authority, and available review date. If unavailable, identify a substitute or confirm that the review schedule must change.

Section D: Resolve the additional deliverable request

  • Label: Decision required.
  • Audience: Maya, with Lewis advising on operational need.
  • Decision: Replace the supplementary guide with a requested sales handout, or defer the handout for separate planning.
  • Supporting evidence: The handout is outside the agreed deliverable list. Its intended audience and review owner are known, but the agency has not agreed effort or a delivery commitment.
  • Recommendation: Defer commitment until the client confirms its priority relative to the guide.
  • Caveat: A preference for the handout is not approval of additional cost or a revised delivery date. Those terms require separate agreement.
  • Requested response: Record “explore replacement” or “defer handout” by Thursday. No additional production begins on the basis of this report alone.

Section E: Confirmed decisions and next work

  • Label: For information.
  • Audience: Both client leads and the agency delivery team.
  • Decision supported: Whether execution still matches the client's recorded instructions.
  • Supporting evidence: The previously approved audience and core resource scope remain the working basis. Design preparation continues within that scope.
  • Caveat: Pending recommendations in Sections B and D are not confirmed instructions.
  • Requested response: None unless the record is inaccurate. Corrections must identify the decision being changed and the person authorising the change.

4. Turn the brief into a readable report

The brief is the specification for the report, not necessarily its final presentation. Keep the full fields available to the report owner, but organise the client-facing version around attention.

Open with the decisions and inputs required, naming an owner and response date for each. Follow with the evidence and recommendation for each request. Put general status and the confirmed decision record after the action material.

Within each decision block, keep the request, evidence, and caveat together. A client should not have to compare a summary on the opening page with a qualification buried at the end to understand what approval means.

Where several stakeholders receive the report, name the decision-maker rather than addressing requests to “the client team.” Invite advisers to contribute, but distinguish their comments from the authorised response. This reduces the chance that the agency treats an informal suggestion as a final instruction.

5. Show enough evidence to choose, not everything collected

Evidence should explain why the choice is being raised and what could make the recommendation wrong. It need not reproduce every working note.

For each request, separate three elements:

  • Observation: what the available record shows.
  • Interpretation: what the agency thinks that observation means.
  • Recommendation: what the agency proposes doing about it.

In the fictional example, an unfinished guide is an observation. The possibility that waiting will delay the combined release is an interpretation. Releasing the core resource first is a recommendation. Keeping these separate lets the client challenge the reasoning without disputing the underlying status.

State uncertainty where it changes the choice. If the evidence is insufficient, ask for a bounded investigation, an additional input, or a reversible next step instead of implying confidence. Conversely, do not add generic caveats to every sentence: qualifications should identify a real limit on the decision.

6. Specify what a usable response looks like

“Please review” is an incomplete instruction. It does not establish whether the agency needs corrections, approval, a preference, or confirmation of authority.

A usable response request includes the authorised responder, available options, response location, deadline, and consequence of delay. Explain the deadline through the work it protects, rather than using urgency as a substitute for reasoning.

Allow a client to reject the proposed options. Ask them to state the missing constraint or desired alternative so the agency can reassess the recommendation. A forced binary choice can conceal a misunderstanding about the business priority.

Keep approvals bounded. Agreement to investigate an alternative does not authorise production. Content approval does not necessarily approve extra expenditure. Where a request contains several independent commitments, split them so the client can accept one without inadvertently accepting all of them.

7. Recover when the reporting agreement breaks down

No response: Mark the request pending, remind the named owner, and state which work is paused. Escalate through the agreed contact route. Continue only work already authorised and unaffected by the missing choice; do not convert silence into consent.

Conflicting responses: Present the disagreement neutrally and ask the authorised decision-maker to resolve it. Record the final instruction before changing the plan. Do not select whichever comment is easiest to execute.

A request to approve everything in a meeting: Use the meeting to resolve ambiguity, then record each decision and its conditions. Discussion alone can leave participants with different understandings of what was approved.

A late reversal: Preserve the earlier decision and record the replacement, its owner, and its effect on the remaining work. Updating the report without that history can make a changed instruction look like an agency delivery failure.

Too many approval requests: Revisit delegated authority. The solution may be to let the agency make more routine choices within explicit boundaries, not to demand faster client responses.

8. Test the next report against observable outcomes

For the next reporting cycle, take the existing report and label every section as decision, input, or information. Remove duplicate material and rewrite each action request so it names an owner, options, supporting evidence, caveat, and requested response.

Before sending, ask a colleague to identify every client action without an explanation from the account lead. If they cannot, revise the report rather than relying on the review meeting to translate it.

After the response window, record:

  • How many requests received a usable response by the agreed time.
  • How many required clarification about what the agency was asking.
  • Which decisions were reopened because evidence, authority, or conditions were unclear.
  • Which work waited for a client decision, and which work continued under existing authority.

Use that record to change the reporting agreement. Clarification requests point to weak wording or missing evidence; repeated silence may indicate the wrong owner, channel, or cadence. The next report should make the unresolved choices easier to act on—not merely provide a longer account of what the agency did.

Agency operationsClient reportingClient approvalsDecision-making

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications