Start with the system of record
The system of record is the account, provider, merchant, bank or recipient that can confirm the real-world state. Before delegating, write down the exact change you expect, the latest acceptable date, and where you will verify it. If you cannot name those three things, the task is not yet bounded enough.
Use the strongest available evidence
| Level | What it shows | How to treat it |
|---|---|---|
| 1. Agent statement | The agent reports that it acted or finished. | A lead to check, not proof. |
| 2. Draft or activity log | What the agent prepared or attempted. | Useful for audit and correction. |
| 3. Submission confirmation | A request reached a provider or recipient. | Proof of submission, not necessarily outcome. |
| 4. Provider record | The source account shows the requested state. | Strong evidence of the current state. |
| 5. Settled downstream result | The next bill, posted payment, delivered item or recipient confirms the result. | Strongest practical check when consequences settle later. |
What to verify for common agent actions
| Task | Weak signal | Better evidence | Final follow-up |
|---|---|---|---|
| Cancellation | Agent says “canceled” | Provider confirmation and account status | No renewal charge after the billing date |
| Refund | Merchant says “initiated” | Refund reference, amount and original payment method | Correct credit posted to the payment account |
| Plan change | Offer summary | Written order with total, fees, term and effective date | Account status and next bill match |
| Appointment | Draft time or calendar entry | Provider confirmation with date, place and conditions | Provider still shows the booking before travel |
| Email or message | Prepared draft | Sent-folder record with correct recipient and attachment | Recipient acknowledgement when important |
| Purchase | Cart or checkout screen | Order confirmation with item, total and delivery details | Charge, shipment and return window match |
Pause before hard-to-reverse actions
Require a fresh, specific approval before the agent sends a message, shares sensitive information, accepts contract terms, changes or closes an account, places an order, moves money, or substitutes store credit for a refund. The approval should show the recipient, action, price or amount, important terms and information being disclosed.
If the screen is ambiguous, stop. A second review is cheaper than correcting the wrong recipient, plan, charge or cancellation.
Result verification checklist
Checks stay in this browser tab and are not uploaded or saved. Print this section if you want a case record.
Task: ____________________ Reference: ____________________
Expected by: ____________________ Checked on: ____________________
A framework, not a success claim
This checklist is platform-neutral researched guidance. It has not been validated as a guarantee that an agent, merchant or provider will complete a task. Deadlines and dispute rights vary, so use official provider or regulator guidance for the specific case.
See how Agent Taskbook labels evidence, or apply this framework to a Meta Muse task guide.