Before calling a task complete, compare the result with the original request and later corrections. Check the account, object, destination, period, format, and exclusions that matter to the task.
A successful operation can still produce the wrong result. Review the thing the user asked for.
Check the right evidence
| Task | Inspect before delivery |
|---|---|
| Research or synthesis | Sources supporting the important claims, unresolved conflicts, and material coverage gaps. |
| Connected-app edit | The actual changed fields or content in the intended object. |
| Browser workflow | The destination state or provider result after the interaction. |
| Desktop document | The saved or exported artifact, including the affected content and relevant layout. |
| Local file | The exact file, readable content, required format, and usable location. |
| Sharing | The created link or destination and exactly what it exposes. |
| Code change | The relevant diff and behavior checks at the requested delivery stage. |
| Deployment or package release | The delivered version observed at the destination. |
| Handbook change | The updated canonical guide and consistent rendered/exported content. |
For an uncertain write, inspect the destination before repeating it. For pending work, follow Long-running work instead of treating a queued request as completed.
Inspect an output yourself
Use the source or application that owns the result. Open the changed document or setting. For a file, open the exact saved copy; check that it contains the requested change rather than an earlier version.
If the agent only supplied a local path, establish which computer or host owns that path. Use Work with local files to inspect an accessible file. Follow Save and share results when the requested outcome includes a shareable copy or link.
For a research summary, open a source beside an important conclusion and check its support. A list of search results does not establish the summary's claims.
Return a clear completion message
Lead with what is now available or what changed. Include the actual artifact, object, or page reference. Summarize the check that established the result and any material remaining limit.
A useful format is:
Result: what was completed and where to inspect it.
Verification: the relevant readback or check.
Remaining issue: only if something material is still unresolved.
Next step: only if needed to reach the requested outcome.
Use accurate delivery states: drafted, saved, committed, merged, deployed, and published are different outcomes. A handbook-only request can finish with an updated handbook; it does not automatically require product implementation, a bundle refresh, or a package release.
Deliver useful partial work honestly
If one source is unavailable, preserve the valid result from other authorized sources. Say what is verified and how the missing source affects the conclusion. If a file was generated but not delivered, retain it and identify the remaining delivery step.
Do not label an intended experience complete because a tool exists or a local check passes. If the product falls short of the handbook, record the observed gap while preserving the intended behavior.
Stop after sufficient verification
Choose checks that resolve concrete remaining risks. A changed heading needs different evidence from a provider write or deployment. Once the result is adequately checked, deliver it rather than repeating broad checks without a reason.
For a workflow you plan to repeat, use Evaluate task results to record what was actually exercised and what remains untested.