Revisit an AI answer when a new attachment arrives
Treat new information as a reason to review the earlier conclusion. Identify which assumptions it changes, check the affected claims against their sources, and update every working output that depends on those claims.
Ger Perdisatt, Acuity AI Advisory
2 min read
Keep the earlier position visible
Before adding the attachment, save the earlier answer with a short record of the inputs it used. Record the recommendation and any conditions attached to it. This gives you something concrete to compare with the revised answer and prevents a changed explanation being mistaken for a changed decision.
Check what the new file is and who supplied it. A later upload is not automatically a more authoritative source. Its date might be the export date of an older record. If it corrects a previous document, identify the correction explicitly and preserve the earlier version according to your normal records practice.
Follow the change into the working documents
Find the practical consequences of the earlier recommendation. A draft invitation may name the room. A booking tracker may show “ready to confirm”. A colleague may already have copied the recommendation into their own notes. Identify the affected records and their owners before treating the review as complete.
Update authorised drafts and mark unresolved items clearly. Do not send a cancellation or confirm a replacement merely because the assistant suggests one. Follow the normal approval route for the action. Open the saved version and verify that the outdated recommendation has actually been removed wherever it mattered.
Editorial guidance informed by Acuity's work with teams. Examples are fictional and client materials stay private. To record who owns an AI use and when it is reviewed, see AI Register.