At 9:40 am on a Monday, Owen opens the company website and finds a domain parking page. He is the operations coordinator at a 150-person consulting firm, barely three months into the job. For the last forty minutes clients have been calling to say their emails to the firm are bouncing. The COO asks him who handles the domain. Owen has never heard the word "registrar," and nobody within earshot has either. The person responsible for managing the domain was Helen, who ran operations for nine years and left in November. Her offboarding checklist had been completed, every box ticked; somehow this tiny but critical item never made it to the checklist.
An offboarding checklist covers only the duties a company has already identified. Those it hasn’t stay attached to the departing employee's own accounts, cards, and inboxes until something stops working. The gap does not appear on the last day. It appears months later, as an outage nobody can trace.
Most offboarding advice is about the checklist: make it longer, give each item an owner, review it with HR and IT. That is sound advice for the duties on the list, but it doesn’t reach the items that were never on it.
An Offboarding Checklist That Worked Exactly as Designed
Helen gave a month's notice and left on good terms. HR processed her final pay and benefits and collected her laptop and keys. IT suspended her account and deleted her mailbox after the standard 30 days. Finance canceled her company card on her last day and reviewed her recent statements for recurring charges. Each team finished its list, and each list was correct.
The domain was on none of them. Years earlier, before anyone formally managed the firm's systems, Helen had registered it herself, under her own account, with her own card and her own email. Her handover notes came from her job description, which said operations, so they never mentioned it. The renewal, about twenty dollars a year, fell outside the three-month window finance reviewed. When it came due in March, it tried a card that no longer existed, and the warnings went to a mailbox that had been deleted in December.
Why Three Correct Checklists Still Missed One Duty
HR knew the person and her duties on paper. IT knew the systems on its inventory. Finance knew the charges inside its review window. The domain sat in the one place where those three pictures did not overlap.
In Panopto's survey of 1,001 US adults at companies with 200 or more employees, respondents said 42% of the expertise their role requires is known only to them. Helen's duty is tribal knowledge in its plainest form: undocumented, absent from every job description, and invisible to every list. It had become hers the way things do over nine years, on an afternoon when handling it herself was easier than asking someone else, which is one reason why experienced employees skip documentation without being careless.
What Recovering an Expired Domain Costs
Owen spends the day learning what a registrar is. The domain account is tied to Helen's deleted mailbox, so he cannot reset the password, and he has to prove to the registrar that the company owns a domain he didn’t know it had. Recovery is usually possible: ICANN's Expired Registration Recovery Policy requires generic top-level domain registries, such as .com, to offer a 30-day redemption grace period after deletion, though earlier grace periods and recovery fees vary by registrar. The fee can run well beyond the original twenty dollars, and every hour of it is an hour of missed client email.
Nobody in this story was careless. Helen did her handover, and HR, IT, and finance did their lists. That is why more process rarely fixes it: each team completed its part of the process. Our post on what your company loses when employees leave describes the wider version of this pattern.
Why Asking the Departing Employee to Write It Down Misses It
The standard fix is a request in the final two weeks: write down everything you handle. It asks the most of a person with the least time, and it returns only what that person remembers doing. A duty that has run quietly for years does not feel like a duty. Our post on why your knowledge transfer plan is three years too late makes the broader case for capturing earlier, what happens when a key employee leaves follows the same gap over the next 90 days, and our guide to preserving institutional knowledge before it walks out the door covers the practices in more depth.
What Changes When the Answer Already Exists
Run that day again, but with one difference. Two years before Helen left, a colleague asked in Slack who held the login for the domain. Helen answered that she did, that it was registered under her account, and that the renewals went to her email. The colleague saved the thread, because the answer solved their own problem and they wanted it findable. Saving took three clicks.
Pravodha keeps that thread attributed to Helen, searchable by topic, and marked as useful by the colleagues who found it valuable. Her profile shows the topics colleagues relied on her for, so when she gives notice, the person running her offboarding can read it and find "domain" on it, with her explanation attached. The registration moves to a shared account while she is still in the building. If it is missed anyway, Owen searches "domain renewal" on the first morning and finds the thread, with Helen's name on it, instead of spending the day finding out what a registrar is.
Saved-thread capture works only when someone saved the thread. A duty that never came up in conversation is not captured, and Helen could have held something nobody ever asked about. Questions about ownership, though, such as who holds the login, whose card it is billed to, and where the notices go, tend to be asked at least once, because the person asking needed the answer.
What to Add to Your Offboarding Checklist Before the Next Departure
A team can narrow this gap before anyone resigns.
- Inventory what is tied to a person: domains, SSL certificates, software licenses, social accounts, and admin logins registered under an individual's name, email, or card. Move each to a shared role address that forwards to at least two people, billed to a company account.
- Change the exit question from "what do you do?" to "what do you handle that is not in your job description, and where do the notices for it arrive?"
- Have one person read the HR, IT, and finance lists for each departure side by side and ask whether, together, they describe everything the departing employee touched.
- Review what colleagues relied on the person for before the last day, while they are still reachable to confirm it.
- Log each gap that slipped between teams in one line, and review the log quarterly to see which handoff keeps leaking.
Owen's Monday began with a parking page and a question nobody could answer. The Monday worth aiming for begins with a thread from two years ago and a registrar login that already belongs to the company.
Pravodha is built around the capture model. It integrates with Slack, Microsoft Teams, and your email to preserve the institutional knowledge your team generates every day: attributing it to the people who created it, surfacing peer validation, and making it permanently searchable without adding any burden on the experts.