Check the results
How to assess a team's completion report.
A report is a claim. Verification is your job. Team members review each other's work, but you make the final check. Start with these three simple actions.
Three checks
| Check | How |
|---|---|
| 1. Open it | Open the reported file or screen yourself. Check that what was claimed really exists. |
| 2. Use it | Try the actions in your completion criteria. |
| 3. Check for damage | Confirm existing files and functions are unchanged. |
Illustration placeholder 1 · Report and verification
File name
assets/support/guides-checking.png · Recommended size: 1600×900
Reading a completion report and opening the result personally
Reading a report
Distinguish 'done' from 'verified.' Creating something and opening it to verify its behavior are different. If verification is not stated, ask, 'Separate what you directly checked from what you could not check.' The team's rule is to say when it does not know.
Ask another agent to review
A reviewer who did not build the result can spot omissions. Try this request:
Review this result as if seeing it for the first time.
- Check each requested completion criterion.
- List what does not work or is missing.
- Do not fix anything; report only.If something is wrong
- Briefly explain how the result differs from the report and ask the team to correct it.
- If the same problem repeats, Resetand have the agent reread the records before starting again.
- If you want to roll back, compare against the original copy you saved.
Checklist
- I opened the result myself.
- I tried the actions in the completion criteria.
- I checked that existing work is intact.
Next Use records effectivelyis a good next read.