Everyday AI · Module 7

Record a run so someone can inspect it

Suggested time: 6 minutes.

A run record describes one use of your procedure. It should let a reviewer answer: what input did you use, what happened, what did you check, and what remains unresolved?

Use this compact format:

Run name and current pack: Procedure used: Input safety and completeness check: Start and finish times, if measured: Initial output saved at: Checks performed and source labels: Errors found and corrections: Unresolved items and why they remain open: Final decision and reviewer:

You can use a document section name instead of a file path. The key is that another person can locate the evidence.

A check record must contain evidence

Weak record:

“Looks good. AI checked it.”

Useful record:

“The invitation-review deadline in the output is 14 November 2026. R1.1 gives the same deadline. Supported. Venue confirmation remains pending in R1.2 and in the draft. No confirmed booking is claimed.”

Record corrections, too. Keep the initial response and label your final edited output, rather than replacing the initial response so the error disappears from view.

Measure the work you actually did

If you time a run, include reading, drafting, checking and correction in the work time. Record waiting separately if you want to understand the cause of a delay. Do not claim “saved 30 minutes” unless you have a meaningful comparable baseline.

A shorter drafting time can still lead to more review work. In this course, a supported output with a visible review record matters more than an unmeasured speed claim.