A useful answer still needs a second look.
Review AI drafts for accuracy, missing evidence and unintended commitments. A practical checklist for summaries, client messages and everyday work.
Forge ProtocolPractical AI guides · Free with an accountHow we make these guides
A polished answer can still contain mistakes. Make a short review part of the work, especially when other people will rely on the result.
Decide what needs checking
Before you review an AI draft, ask where it will go and what happens if it is wrong. A private brainstorming list and a message confirming work to a client need different levels of attention. Match the review to the consequence of the output.
For an ordinary summary, keep the source beside the draft. For a message that will create a commitment, have the person responsible for that commitment check it. Where work needs specialist judgement, use the appropriate reviewer rather than asking the assistant to approve itself.
Decide what would stop you using the draft. Examples include a source you cannot locate, a number that does not match, or an instruction whose meaning is unclear. A stop condition is useful because it prevents polished wording from becoming a reason to overlook missing evidence.
The conversation
What would you try?
Ask a question, share what worked, or add a useful perspective. Keep it kind and on topic.
Loading comments…