‘A person will check it’ sounds reassuring. It becomes useful only when that person knows what to check, has the source information and can stop the next action. Design the review into the workflow from the beginning.
Say what the review is for.
An AI-prepared reply can sound confident while missing a detail. A tidy summary can leave out an exception. Decide which parts need verification against an agreed source and which choices need a person’s judgement. Accuracy, tone, permissions and business commitments are different checks.
- Does the draft match the original request and the available facts?
- Are names, amounts, dates and commitments supported by the source?
- Does the reviewer have authority to approve the next action?
- Is anything uncertain, sensitive or outside the agreed process?
Keep the context beside the draft.
A review is harder when the source information sits in another system. Show the original request, the relevant records and any uncertainty alongside the prepared work. If the system cannot obtain enough context, it should make that gap clear instead of presenting a guess as a finished answer.
Preparation is not permission
Prepared work
A draft and its source context arrive together.
Human decision
The reviewer edits, approves or rejects the draft.
Permitted action
The workflow acts only within the agreed approval rules.
Make stopping as clear as approving.
The exception path should be visible and usable. A reviewer needs to be able to request more information, send the case to the right person or keep it out of automation. Define what happens if no one reviews it. A missed deadline should not silently become permission to send.
Review the decision, not just the wording.
Spot the promise that needs checking
Illustrative exercise. Customer: “Will my order arrive by Friday?” Order record: packed, courier not yet booked. Delivery guide: usually 2–3 working days after collection; estimates are not guarantees. Draft: “Your order is on its way and will arrive by Friday.” What would you change?
Reveal the unsupported claims
“On its way” conflicts with “courier not yet booked”. “Will arrive by Friday” turns a typical delivery estimate into a guarantee. Neither claim is supported. A friendly tone does not fix either problem.
Compare a corrected draft
“Your order is packed. Courier collection is still to be confirmed, so I can’t confirm Friday delivery yet. I’ll check the collection arrangements and come back to you.” The reviewer must agree who will check and when they will respond before sending this wording.
Choose the next action
Hold the original draft. Ask the fulfilment owner to confirm collection and the available delivery estimate. Then review the recipient, facts and exact final wording. If the deadline cannot be met, explain the available options without inventing a refund or expedited-service policy.
Try a change after approval
Suppose someone replaces “can’t confirm Friday” with “Friday is confirmed” after review. The earlier approval no longer covers the message. Route the changed version back to the reviewer. Keep the approved version and decision identifiable.
Take this into your work
Before sending: underline every promise, number and date. Point each one to a current source. Mark any unsupported claim “hold”. Confirm the recipient, the next action and who owns it. Approve the exact version that will leave the business.
Can this draft stand behind its promise?
Compare a draft with the facts you provide. Change the wording and run it again to see whether the decision changes.
Run it, change one detail, then compare the decision. Use sample text without customer or confidential information.
Use corrections to improve the process.
Look for repeated reasons that reviewers edit or reject work. An incorrect date might point to an outdated source. A missing qualification might mean the preparation instructions are incomplete. Fix the cause and try the same cases again. Keep enough of the review history to understand the decision, while avoiding unnecessary copies of customer information.
A practical check
Tick these as you work. Checks reset when you leave this page.
The right review boundary depends on the consequence of the action. Keep the first workflow narrow, test its exceptions and revisit the boundary as the business changes. A fluent draft is useful preparation. It is not evidence that the next action is appropriate.
Useful to someone you know?
Pass the article along.
