Separate plans from purchases
Label approved but unsubmitted requests separately from actual order IDs. A spreadsheet row containing a desired quantity is not proof that the panel accepted or charged for that request.
Transfer exceptions explicitly
List pending cancellation requests, possible refill cases and targets changed by the client. Include the relevant support reference so the new operator does not restart an unresolved conversation from incomplete information.
Reconcile the spending position
Provide the approved budget, recorded charges and confirmed available balance. Do not describe anticipated refunds or pending adjustments as money ready for the next order until they appear in the account ledger.
Decision checklist
| Decision | What to check |
|---|---|
| State | Planned versus submitted requests |
| Exceptions | Open support cases and changed targets |
| Money | Actual charges and confirmed credit |
Worked example
Hypothetically, an outgoing operator planned five Reel orders but submitted only three. The handover contains three order IDs and two explicitly unsubmitted rows. The incoming operator verifies those records and avoids either duplicating completed purchases or forgetting the remaining approved work.
Example figures explain the decision; they are not current prices or promised results.