Most offboarding protocols stop at IT access and exit interviews. This checklist covers the revenue systems — the ones that keep making decisions after the rep is gone.
Standard offboarding covers two things well: IT access revocation and HR paperwork. Badge returned. Laptop wiped. Final paycheck confirmed. COBRA notice sent. From an HR and IT perspective, the rep is gone.
From a revenue system perspective, they are still very much present. Their name is on 40 accounts in Salesforce. Their commission plan is still active in Xactly. Their email sequences are still running from a mailbox that will start bouncing within hours. Their territory is defined in the comp plan but owned by no one.
This checklist is for the revenue systems — the ones IT doesn't touch, that HR doesn't own, and that Finance doesn't notice until the period closes and the numbers don't add up.
Before touching anything else, confirm the official termination date in your HRIS and what pay period it falls in. This is the anchor date for everything downstream. A departure logged as effective on the 15th of the period is treated very differently by most comp tools than one logged on the 16th — especially if the 15th is mid-accelerator territory.
Pull a report in your CRM filtered to accounts owned by the departed rep. This is the exposure list — every account that will be uncontacted, misrouted, or left in limbo without action. The report should include: account name, last activity date, opportunity stage (if applicable), and any active renewals.
The accounts with recent activity are the ones most likely to generate inbound responses in the next 72 hours. Those are the ones that bounce if you don't act immediately. — Ken Lannon, OrgDrift
This is the step most often missed — because it requires a manual action in a system that most managers don't have access to, and the notification chain rarely includes whoever owns ICM administration. The comp plan needs a hard stop date equal to the HRIS effective termination date.
Once you've taken action in each system, run a quick cross-system verification. The goal is to confirm that your HRIS, CRM, and ICM all reflect the same reality: this person no longer works here, their accounts are reassigned, and their comp plan is closed.
If you are using OrgDrift, this is a CSV upload — HRIS export and CRM export — that will surface any remaining mismatches between the two systems. You will get a specific list of accounts still in the departed rep's name, territories still mapped to their ID, and any comp records that haven't been updated.
The acute phase of a departure is the first 72 hours. But the chronic phase runs for 30+ days. Territory coverage, open pipeline disposition, and comp true-ups all require follow-through after the initial offboarding. Set a 30-day calendar item to confirm that all accounts have been contacted by the new owner, that no commissions ran through the departed rep's plan after the effective date, and that the territory has been formally reassigned in both CRM and the comp plan.
OrgDrift ships this checklist as a structured field kit on the Verify tier — including the scan template pre-configured for departure scenarios, the cross-system verification prompts, and the 30-day follow-up protocol as a trackable workflow.
Drop in a CSV export from your HRIS, CRM, or comp system. Get your ODIS in minutes. Your data never leaves your browser.
Scan my data →No IT ticket. No OAuth. No data upload to any server.
Get Drift Notes
Short, sharp field notes on data propagation, control risk, and audit pain.
The verification layer between your systems and your auditors.
“Your org changed. Nobody told your data.”
Every record sealed with a tamper-evident hash
Your data never leaves your browser
Enterprise compliance certification in progress