Setup checklist: list the open obligations
Before changing the account, identify active work, pending approvals, unpaid or uncertain invoices and promised file handovers. Ending a subscription is not proof that every obligation has disappeared. Keep the original agreements and request records available to authorized staff. If the relationship ends under unusual circumstances, follow the relevant contract and professional advice rather than treating this operational checklist as a substitute for resolving a dispute.
Prepare the agreed delivery package
Identify the accepted final versions and any source files or licenses included in the service. Do not promise ownership or assets beyond the actual agreement. Give the client a clear description of what is being handed over and any appropriate retrieval deadline. Check that the delivery route works before removing the access needed to use it. A final message with a broken or inaccessible link is not a completed handoff.
Handle billing and access independently
Verify the actual cancellation or pause behavior for the payment arrangement in use. ManyRequests documents Stripe-related pause behavior, while manual arrangements require their own reconciliation. Do not equate an access change with cancellation of a charge. Likewise, stopping payment does not automatically prove all access has ended. Record each authorized change and its observed result, especially where a response is delayed or the outcome cannot immediately be confirmed.
Retain only what is appropriate
Apply the agency’s legitimate retention rules and access restrictions to historical material. Do not delete records impulsively to tidy the dashboard or keep everything indefinitely without a reason. The client-facing completion note should explain delivered items and any remaining practical action without exposing internal details. A good offboarding process leaves both parties able to understand the final state and avoids turning a closed commercial relationship into months of avoidable access questions.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- ManyRequests subscription pause conditions — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests managing requests and exporting data — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests admin, client and team permissions — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests general terms — not a verified affiliate contract — Merchant documentation · manyrequests.com · Merchant-controlled · checked 2026-09-19