Separate cardholder, service owner, and access owner
The employee whose card was used is not automatically the person who decides whether protection is still needed. Record a business service owner, budget owner, dashboard access owner, and backup. Assign roles or group accounts where supported so a departure does not orphan renewal.
Do not copy full card data, passwords, or Activation Codes into the register. Store the provider account reference, approved payment method label, and link to the organization's credential manager. The register proves custody without becoming a new secret repository.
Record current commercial facts at purchase
Capture plan, amount, currency, billing interval, purchase date, next renewal, hostname scope, renewal behavior, online cancellation route, receipt, approver, and authoritative terms URL. At the stated current prices, Pro is $10 monthly or $99 annually, Agency is $299 annually, and Unlimited is $499 annually; verify again at each decision date.
Save evidence of what was approved rather than assuming the public page will remain unchanged forever. A dated receipt and approval record answer what the organization bought; the current page answers what a new purchase would buy.
| Register field | Example | Control |
|---|---|---|
| Service owner / backup | role names | must survive staff exit |
| Plan and interval | Pro annual $99 | verify against dated receipt |
| Next renewal | YYYY-MM-DD | calendar in billing timezone |
| Review dates | 45 / 30 / 7 days before | named decision at each gate |
| Cancellation test | portal path and test date | no cancellation performed during test |
| Final proof | confirmation and effective date | retained with approval |
Use three renewal gates
At 45 days, verify owner, access, scope, and budget. At 30 days, collect usage and decide renew, change plan, or cancel. At seven days, confirm the chosen action completed and evidence was received. The dates are operating examples; adjust them to the actual terms and internal approval lead time.
A reminder is not a decision. Each gate needs an owner, status, supporting evidence, and escalation when unanswered. Send escalation to the role responsible for the service rather than only to the departing employee.
Test the route without cancelling by accident
Confirm that authorized staff can reach the online cancellation flow and know which subscription it affects, but stop before final confirmation during a routine access test. Capture the documented steps, authentication requirement, and where final confirmation will appear.
When cancellation is approved, record the submission time, confirmation identifier, effective date, service behavior through term end, and any hostname or access cleanup. Verify the next invoice or account state rather than treating a button click as final proof.
Make staff departure a lifecycle event
Offboarding must reassign all four roles, revoke personal access, confirm the role account, and retest the register links before the employee leaves. Review upcoming 45-day renewal windows immediately so a near-term charge does not wait for the normal cadence.
The custody register passes when another authorized person can locate the contract, explain the scope, reach the cancellation path, and produce renewal or cancellation evidence without contacting the former employee. Link directly to the cancellation page for execution instructions.
Use the renewal custody register from “Renewal and cancellation evidence for subscriptions owned by changing staff” on a real first installation. Download AI Cost Circuit Breaker for free, begin in Monitoring, and move to enforcement only after the expected signals and rollback are verified.