The playbook
Client Marketing Reports: Checklist
Use this client marketing reports checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect client decisions supported by the report. Check an actual client or workflow record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
Show what was delivered, what changed in customer outcomes, what remains uncertain, and what decision is needed next. Explain major differences from the previous period. A few relevant measures with context are easier to act on than an unfiltered dashboard export.
Before you use the checklist
Name the exact item being checked and its purpose. Gather outcome, work delivered, evidence, next decision. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Show relevant outcomes using agreed definitions | A dated observation showing how outcome was verified | account lead |
| Explain material changes with evidence and limitations | A dated observation showing how work delivered was verified | delivery owner |
| End with decisions responsibilities and next work | A dated observation showing how evidence was verified | business owner |
Check the failure path
- Look specifically for this failure: sending a large dashboard without explaining what the client should decide.
- Highlight the few measures that change the plan. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check next decision.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Show relevant outcomes using agreed definitions,” a meeting about the subject is not the evidence itself. Retain the relevant outcome and work delivered, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents help clients understand delivered work observed outcomes and the next decision deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow client decisions supported by the report using a consistent definition so later reviews can connect execution quality with useful results.
Follow one customer journey across the involved teams and systems. A correct step can still create a poor experience when its output is not usable by the next team. Verify the transitions as carefully as the individual tasks.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now