Trigpoint
Collections › Method explainer › Sample delivery

Sample delivery: a review of the monthly client report

Allocation ledger review · Demonstration sample

This is a demonstration sample.

A freelance consultant sends six retainer clients a monthly performance report. She filled in an allocation ledger herself and sent it with a request for a review. Below, in order: the ledger she sent, the scope agreed before work began, and the review she received.

The ledger she sent

StepStageLevelReasonResidual workCheckTakeover
1 Export figures from three toolsGatherAct, undoableA wrong export can be redoneReads the export summary: date range, account name, row count(blank)She notices at step 2; re-exports at step 1
2 Compare with last month and the targets; write likely reasonsAnalyseAct, undoableThe assistant calculates faster than she doesA quick look at the resultKeep an eye out for anything oddShe notices when proofing at step 4; redoes step 2
3 Choose two or three recommendations for next monthDecidePrepareShe looks at it before using itPicks one versionShe has looked at itShe notices next month when reading the figures; resets at step 3
4 Write the report and chartsAnalysePrepareShe reads it before it is sentProofreads and traces figures to their sourceEvery summary figure and every chart in each report, against the comparison tableShe notices when proofing; fixes at step 4
5 Send to the client’s contactActAct, undoableThe assistant can send from her account and keeps a copyLooks at the sent copiesLooks at the sent copies once a monthShe
6 Mark as sent in the client trackerActAct unattendedA wrong entry is easy to fixChecks before invoicingBefore invoicing, the month’s six entries against the six sent emailsShe

The scope agreed beforehand

QuestionBefore the monthly client report goes to an AI assistant, which stages could go wrong with no one able to catch it?
BoundariesCovered: the level, residual work, check and takeover for each of the six lines. Not covered: steps outside the ledger, tool choice, filling in the ledger, implementation, and whether client contracts allow analytics data to be handled by AI. Consent for the review to enter the case library once de-identified: yes.
OutputA one-page review
What to sendOne filled-in ledger of six steps, with the steps, who answers for each, what an error costs and current practice
Form and timingIn writing; delivery within five working days of agreeing the scope; one follow-up after delivery

The review delivered

Finding: Five of the six lines need changes. The most urgent is step 5, sending.

LineProblemFindingReasoning and sourceEvidence
5 Send · actAutomation set too high · No one to take overLower to suggest: the assistant alerts her when the client name on the report does not match the recipient, and she still presses send. Takeover, written out: the wrong recipient or the client writes in; she contacts the wrong recipient and the affected client the same day.Sending speaks for her. An email to the wrong person hands one client’s data to another and cannot be recalled; keeping a copy does not make it undoable. The ceiling table caps this stage at suggest on both counts. Levels of automationTheory
3 Recommend · decideAutomation set too highLower to suggest: the assistant lists options with the figures behind each, and she chooses.A decide stage has a ceiling of suggest. “She looks at it before using it” is approving a prepared answer, not making the choice. Once acted on, a recommendation spends a month of the client’s budget. Automation complacency & biasTheory
2 Compare · analyseAutomation set too high · A person who can no longer step in · A check that does not workLower to prepare. She keeps, rewrites or drops every reason in every report against evidence she can name. Each month, one client in rotation, she does the analysis by hand first and then compares.The reason given does not answer the two questions: calculating faster is not a reason to raise the level. A made-up reason reads as well as a true one, and this analysis is what her clients pay for; a quick look at the result will not catch it. “Keep an eye out” is not a check. Ironies of automation; Automation complacency & biasTheory
1 Export · gatherAutomation set too high · A check that does not workOnce step 2 is at prepare, this step can keep its level, but the reason must also answer the second question: would an error travel on before she notices? Add a check: each month, for each client, one headline figure per tool against that tool’s own dashboard.While step 2 acts without review, a wrong export reaches the report before she notices, and this step’s ceiling drops one level. There is no check today. Out-of-the-loop performance problemTheory
6 Log · actAutomation set too high · No one to take overLower to act, undoable: the assistant logs the report only once it sees the email in her sent folder, with a link as the receipt. Takeover, written out: she notices when checking before invoicing and corrects the entry at step 6.Acting unattended needs something that reports a missed or wrong run with no one present; the ledger has none. If invoices go out from the tracker without her review, an error reaches the client and this step drops one more level. The ledger does not say; please confirm. Levels of automationTheory

Step 4, writing: the level, check and takeover are complete, so it is not listed.

Next steps (hers, in order):

  • From this week, she presses send herself at step 5; first, she turns off sending for the assistant.
  • At step 3, the assistant lists options and she chooses.
  • Step 2 moves to prepare, with the checks and the rotation above; the step 1 check is added at the same time.

Commitment: The target is that a wrong recipient and a made-up reason are stopped by her before the report goes out. The cost is one more round of checking reasons and recipients for each report. That time comes out of the roughly four hours per client she spends now; it does not disappear.

What to watch: Two numbers after the change: how many recipient mismatches she stops before sending, and how many reasons she drops or rewrites. If she rewrites none for several months in a row, look again at whether the step 2 check has become a formality.

Out of scope: Whether client contracts allow analytics data to be handled by an AI assistant. This review is not a compliance review.

Reviewed by Ansel · Review date: 2026-11-06

The scenario comes from the example ledger in Allocate a workflow before you hand it to AI, rewritten as the version she filled in herself without the skill.
Scope, what to send and the price are under Partnerships and enquiries ▸