ReviewLesson 4 of 86 minutes

Know when the work is done.

A confident completion message is a starting point for review. Open the output and check the things that matter.

You can give a precise correction and verify that it worked.

1

Ask what changed

In the same Codex task, ask for the files it changed, the checks it ran, and anything it could not verify. If it says a test passed, ask what the test actually covered.

2

Inspect the actual output

Open the checklist. Read the labels, try every control, and narrow the browser window. For a document, open the document. For a spreadsheet, inspect the numbers and formulas. Match your check to the deliverable.

3

Report the problem with evidence

Instead of Make it better, say: When I press Reset, the completed count stays at 3. Reset both the checkboxes and the count, and test that sequence. Attach a screenshot when appearance is the problem. Remove private information from anything you share.

4

Check the revision

Repeat the action that failed. For larger work, agree a structure, finish one representative part, and then extend it. Ask for another review after the last change. Your decision to publish or send is a separate step.

Try this in the app
Review the checklist we just built. Report the files changed, the behaviours you tested, and anything still unverified. Check that Reset clears every checkbox and resets any completion count. Open the final preview for me to inspect.

Sources and availability

Checked 6 September 2026. Labels and access can vary by app version, account, and workspace. Practice examples are created for this guide.

OpenAI: Work with files OpenAI: Prompting

Before you move on

I can explain what was checked and what still needs a human decision.

Next: Keep useful context →