An AI email sounds polished, so the reviewer sends it. The message promises a date the team has not agreed. The tone check worked. The approval process missed the commitment.
Meaningful approval checks recipients, facts, promises and attachments before sending the exact reviewed version. Keep drafting and sending separate until the authorised process explicitly connects them.
Define permitted source material
Supply approved references and a clear purpose. Decide what happens when price, timing or scope is missing. Asking the owner can be more useful than generating a complete-looking message.
For an illustrative delay update, the draft may describe an agreed issue and next review date. It should not create a delivery commitment unless an authorised person supplies one.
Use a pre-send checklist
Ask reviewers to check:
Correct client, recipient and thread.
Facts supported by approved material.
Dates, prices and service scope.
Commitments within the approver's authority.
Attachments and appropriate information sharing.
Tone and a clear next step.
Check substance before polishing the greeting. A friendly unsupported promise remains unsupported. Give reviewers the sources they need alongside the proposed email.
Bind approval to the content
Make edits after approval visible. Agree which changes require another review. A revised commitment should not inherit approval given to different wording.
Inspect actual platform behaviour. Do not assume an approval label prevents sending, protects recipients or detects later edits. Those are capabilities to verify with the responsible owner.
Check what happens when a draft is rejected, an approver is absent or the send action fails. The work should remain visible and owned.
Make rejection useful
Record specific reasons such as missing source, wrong commitment or unclear request. Repeated reasons reveal intake or instruction problems.
Include correction effort when judging benefit. If reviewers rewrite every message, the drafting stage may not provide the intended help.
Expand by message type
Approval for routine updates does not establish suitability for complaints or commercial terms. Review each expansion against its consequences and decision rights.
Related guidance: guide to mapping the work before changing it.
Hili Consulting can help define useful email drafting support with clear approval ownership.
