Inspect partial work before retrying a task

A failed or interrupted run may have completed some writes. Review the partial state before repeating actions that could duplicate or overwrite work.

Work through these checks

1. Events

find the last known successful action. Record the evidence or the unresolved question before moving on.

2. Files

inspect existing outputs and temporary copies. Record the evidence or the unresolved question before moving on.

3. External effects

verify consequential requests separately. Record the evidence or the unresolved question before moving on.

4. Scope

decide what remains to be done. Record the evidence or the unresolved question before moving on.

5. Result

compare the new attempt with preserved outputs. Record the evidence or the unresolved question before moving on.

Put the checklist to work

If a report already exists but the summary response failed, inspect the report before generating another copy.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

A lost response does not prove an external action was rejected.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.