Employee Offboarding Checklist & Exit Interviews

Most Indian HR teams have a well-rehearsed onboarding motion: offer letter, joining kit, induction deck, buddy programme, 30-60-90 plan. Ask the same teams for their employee offboarding checklist and you usually get something far thinner — a clearance form someone photocopied years ago, a WhatsApp message to IT about the laptop, and a relieving letter typed the night before it is needed. The last two weeks of an employment relationship get a fraction of the design attention the first two weeks receive, even though they carry more risk and produce more information.

That imbalance is worth fixing, and not for sentimental reasons. Exits are where your data walks out the door, where laptops disappear, where CRM access quietly stays live for eleven months, where client relationships wobble, and where your employer brand gets written by someone about to speak to twenty people in your industry. Exits are also the richest source of honest feedback you will ever get about your managers, pay bands, career paths and culture — if you collect it in a structured way and code it so it can be counted.

This is a build manual for a full offboarding programme in an Indian company: the offboarding process steps from resignation acceptance to relieving letter, the clearance workflow, the knowledge transfer handover, the exit interview design and question bank, the reason taxonomy that turns anecdotes into analytics, and the metrics that show whether any of it works. Statutory points are kept deliberately general. Notice periods, settlement timelines, PF and gratuity all vary by contract, by state Shops and Establishments rules and by currently notified central and state law — treat every legal reference here as a prompt to verify with your own counsel, not a rule to apply.

Why Offboarding Is a Brand and Risk Issue, Not Paperwork

Ask a founder what offboarding costs and you will hear "nothing, they're leaving." Ask again six months later why a key hire declined an offer, and you may learn that a former employee told them the company "makes you chase your money for three months."

Four kinds of exposure meet at the exit door.

Information and security risk. A departing employee holds credentials to email, repositories, cloud consoles, CRM records, customer lists and pricing sheets. Access that is not de-provisioned on a schedule simply persists. Where one person is admin for eight SaaS tools, an unmanaged exit leaves orphaned admin accounts nobody can find later.

Asset leakage. Laptops, phones, dongles, access cards, test devices, SIM cards. Any organisation that does not track assets against a person eventually writes off hardware it cannot account for, and recovery gets much harder the day after the last working day.

Continuity risk. The loss from an unstructured handover is not the tasks — it is undocumented context. Which client only responds on phone. Why that reconciliation script has a hardcoded exception. Teams absorb this silently and underperform for a quarter without knowing why.

Employer brand. Candidates check with people who left. Review sites, alumni groups and referral conversations are all downstream of how the last thirty days felt. A clean exit converts a leaver into a reference; a messy one closes off a boomerang hire you might have wanted in two years.

None of this is solved by a better PDF. It is solved by treating offboarding as a designed process with owners, sequencing, service levels and reporting — the way you already treat hiring or payroll.

The Offboarding Process Steps at a Glance

A complete process has seven phases. Most Indian companies do 1, 5 and 6 and skip the rest.

1. Resignation acceptance — receiving it, the manager conversation, the counter-offer decision, formal acceptance in writing.
2. Notice period planning — last working day, shortfall, early release or garden leave, handover plan.
3. Communication and backfill — telling the team and clients, raising the requisition, interim coverage.
4. Knowledge transfer — documented handover, shadowing, credential inventory, receiver sign-off.
5. Clearance — IT, finance, admin, manager and HR tasks running in parallel with defined SLAs.
6. Last day and exit interview — exit conversation, asset return, access revocation, document issue.
7. Post-exit — settlement, statutory touchpoints, alumni status, rehire eligibility, analytics.

An employee offboarding checklist that only covers phases 5 and 6 is a clearance form, not a programme. The value sits in the parts most teams skip.

Step 1: Resignation Acceptance and the Manager Conversation

Resignations should be in writing, addressed to the manager with HR copied, stating the intended last working day. Convert verbal resignations to written ones the same day — notice computation, settlement and relieving documentation all hang off a date that must be unambiguous.

Within one working day of a written resignation:

• HR logs it and triggers the offboarding workflow.
• The manager is notified and asked to hold a conversation within 48 hours.
• The employee gets an acknowledgement confirming receipt, stating the contractual notice period, and saying the last working day will be confirmed after the manager discussion.

That acknowledgement matters more than it looks. The commonest complaint from resigning employees in Indian SMBs is silence — days of not knowing whether the resignation was even received.

The manager conversation

This is a listening conversation, not a retention pitch. Give managers a three-question frame:

1. "Help me understand what led to this decision."
2. "Was there a point where something different from us would have changed the outcome?"
3. "What would make the next few weeks work well for you and the team?"

Train managers not to react defensively, not to argue with the reason, and not to promise anything about settlement or documents they do not control. They should also be told explicitly not to use guilt, not to hint that references depend on cooperation, and not to tell the wider team before the communication plan is agreed.

Deciding whether to counter-offer

Counter-offers are common in India and usually handled badly: reactive, individual, driven by panic about a delivery deadline. Set the policy before you need it.

• Eligibility defined in advance — typically strong performers in critical roles, never someone already on a performance improvement plan.
• Approval above the manager — the manager recommends, a function head plus HR approves. This stops loud roles being paid more than quiet critical ones.
• The offer must fix the actual reason. If someone is leaving because of their manager, a salary bump buys four months and a more cynical employee. If the driver is genuine market pay compression, a correction may be legitimate — and if it is, ask why it did not happen at the last review cycle.
• Time-bound and documented — a written revised offer with an effective date and a file note explaining the rationale.

Be honest about the cost. The fastest way to teach a team that resigning is how you get a raise is to make resigning how you get a raise. Many mature companies adopt a blanket no-counter-offer policy and invest in earlier, proactive pay corrections instead. Either position is defensible; deciding case by case with no policy is not.

If the offer is declined, the answer is "understood, thank you." No change in tone, no withdrawal of goodwill, no punitive treatment. Colleagues are watching.

Step 2: Notice Period, Shortfall, Early Release and Garden Leave

Notice period is where most Indian offboarding disputes begin. The rule is simple in principle: the notice period is whatever the employment contract says, read alongside the applicable state Shops and Establishments Act or standing orders where relevant. These vary considerably by state and employee category, so verify the currently notified provisions and take legal advice before relying on any general statement, including the ones here.

Confirming the last working day. Compute from the date the written resignation was received and publish it in the acceptance letter so there is no argument later.

Notice shortfall. If the employee wants to leave earlier, you generally choose between insisting on full notice, allowing a buyout per contract terms, or waiving part of it. Whichever you pick, put it in writing before the last working day and apply it consistently at the same level. Inconsistent shortfall recovery is a reliable source of grievance and accusations of favouritism.

Leave during notice. Many companies disallow it, or allow it with the notice period extended. State your rule in the acceptance letter rather than discovering it in week three.

Early release. Sometimes it suits you — handover is done, the role is not critical, or the person's presence is disruptive. Document the revised last working day in writing, and do not let early release quietly become either a punishment or a favour.

Garden leave. For senior roles or exits to a direct competitor, you may want the person on payroll but off systems and client contact. This only works if the contract contemplates it. Check your language and take legal advice on pay, benefits and restrictive covenants. Post-employment non-compete restraints are notoriously hard to enforce in India, so build your protection around confidentiality, data controls and access removal rather than assuming a clause will hold.

Resignation to Relieving Letter: A Day-by-Day Timeline

Illustrative, for a 30-day notice period. Adjust the day numbers to your own notice length — the sequence matters more than the dates.

Two notes. The relieving letter appears on the last working day, which is the standard good employers hold to — document generation should not be made conditional on money that legitimately takes longer to process. And everything after day 7 runs in parallel, which is exactly why manual checklists fall apart and a workflow tool earns its keep.

Step 3: Building the Exit Clearance Form as a Workflow

The exit clearance form is the most abused artefact in Indian HR. At its worst it is a paper sheet the departing employee physically carries desk to desk collecting signatures, with no due dates, no escalation and no record of what was actually checked.

Rebuild it as a workflow: parallel tasks, each with a named owner, a defined check, an SLA and an escalation path. The employee should not be the courier. The system should be.

Design principles:

• Parallel, not serial. Serial clearance is the main reason offboarding cycle time balloons.
• Owners are roles, not names in your head. If the IT manager is on leave, the task routes to a backup.
• Due dates are relative to the last working day, so the workflow recalculates automatically if that date moves.
• Nothing clears without evidence. "Laptop returned" carries an asset tag and a receipt, not a tick.
• Blockers surface early. A pending advance found on day 29 is a crisis; on day 10 it is a conversation.

Step 4: Asset Recovery and Access De-provisioning Sequencing

Sequencing is what people get wrong. Cut access too early and the person cannot complete their handover or download their own payslips, and feels criminalised. Cut it too late and you have an unmonitored open door.

A workable default for a voluntary exit:

LWD minus 15 to 10 - Remove admin and privileged roles first: cloud console owner, billing admin, HRMS admin, domain registrar, payment gateway. - Remove bulk export rights from CRM, HRMS and analytics; retain read access. - Transfer ownership of shared documents, dashboards, automations and scheduled jobs to the named receiver.

LWD minus 7 to 3 - Remove production, customer data store and financial system access. - Reassign tickets, open deals and shared inboxes. - Remove from external distribution lists, client groups and vendor portals. - Transfer any registrations or licences held in the person's name.

On the last working day - Collect physical assets against the asset register: laptop, charger, bag, mouse, monitor, headset, phone, SIM, dongle, access card, ID card, locker key, printed documents. - Take a signed asset return receipt listing condition and any agreed recovery for damage or loss, per policy. - Disable email login and single sign-on at end of day. Convert the mailbox to a delegated or forwarded state per your retention policy rather than deleting it. - Revoke VPN, MFA tokens, SSH keys, API keys and personal access tokens the person generated. This last item is the most commonly missed — disabling a user account does not always revoke tokens that user created. - Wipe or reimage returned devices only after confirming business data on them is backed up.

Within a few days after - Audit for orphaned accounts. Rotate any shared passwords the person knew, then fix the fact that you had shared passwords. - Remove from physical access, biometric and visitor systems. - Confirm removal from payroll, insurance and benefit vendor portals per policy and applicable rules.

Do not forget the human half. Give people advance notice of exactly what to return, in writing, and a workable process for remote employees — an insured, tracked courier pickup you arrange, not a demand that they figure it out. If you charge for unreturned assets, the policy must have been communicated at issue, not invented at exit.

Step 5: The Knowledge Transfer Handover Template

Knowledge transfer fails predictably: it is assigned to the person leaving, with no named receiver, no template and no sign-off. The result is a document written on the last afternoon that nobody reads.

Three rules fix it. Name the receiver by day five. Give the leaver a template, not a blank page. Require the receiver — not the leaver — to sign off that the handover is usable.

1. Role summary — what the role is accountable for in five bullets; who feeds work in and who receives output; the daily, weekly, monthly and annual rhythm.

2. Live work inventory — each active project or account with status, next milestone, deadline and risk; blocked items and what is blocking them; anything with a hard external deadline such as a statutory filing, client SLA or vendor renewal.

3. Stakeholder map — internally, who to go to for what including the informal routes; externally, each client and vendor contact with role, preferred channel, relationship notes and escalation contact. Note where a stakeholder needs particular handling, worded professionally.

4. Systems, tools and access — every tool, licence type, admin and what the role does in it; scheduled jobs, automations, alerts and recurring reports owned. Credentials never go in the document: list what exists and where it sits in the password manager, and transfer ownership separately.

5. Recurring processes — step-by-step for each routine task with frequency and dependencies; known failure modes and workarounds; where source files, templates and folders live.

6. Data, files and records — folder structure and locations; anything stored locally that must move to shared storage; records with retention or compliance obligations.

7. Institutional context — decisions taken and why, especially the ones that look wrong without context; approaches tried and abandoned, so the successor does not repeat them; open questions and unresolved debates.

8. First 30 days for the successor — three things to do in week one; three things not to change for a quarter, and why; who to build a relationship with first.

9. Sign-off — leaver confirms completeness, receiver confirms usability, manager confirms transition, all dated.

Support the document with two or three live walkthroughs and, where possible, shadowing in the final ten days. Add a code and infrastructure walkthrough for technical roles, and a joint call with each major client for client-facing ones, so the introduction happens with the outgoing person present and endorsing.

Enforce one rule: no manager clearance sign-off without receiver acceptance. It is the only mechanism that reliably converts handover from theatre into substance.

Step 6: Backfill and Internal Communication

Raise the requisition in the first week, not after the person leaves. Two decisions deserve deliberate thought. First, should the role be replaced as-is? An exit is one of the few natural moments to redesign, split, merge or retire a role. Second, who covers the gap? Interim ownership should be explicit and time-bound; "the team will absorb it" is how you generate the next resignation. Where the leaver is strong and the role critical, consider an internal move — internal backfill also signals real career mobility, which is itself a retention lever.

Telling the team. The employee should know when and how the announcement will happen, and ideally get to tell close colleagues first. A short, warm, factual note from the manager works best: what is happening and the last working day, specific thanks, who is taking over what in the interim and permanently, and how to reach the person for handover questions. Leave out the reason for leaving, where they are going, and any editorial about the decision. Those are the employee's to share.

Telling clients. For client-facing roles, transition communication goes out under the manager's or account lead's name. Introduce the new contact by name, reassure on continuity and confirm nothing changes in scope or SLA, give a clear cutover date, and where possible run a short joint call with both people present. Do this before the client finds out from a bounced email — a small failure that reads as a large one.

Step 7: The Exit Interview

This is the highest-yield step in the whole process, and the one most often done as a formality on the last afternoon with a form nobody analyses.

Who runs it. Not the reporting manager, ever. If the manager is a contributing reason — and manager relationship is one of the most common drivers of voluntary attrition in practice — the employee will not say so to their face. In rough order of quality: an HR business partner not embedded in that team; a senior HR leader for critical or senior exits; a skip-level leader where HR lacks a relationship; a neutral third party for very senior exits or where an allegation is likely. In small companies where the founder is effectively HR, the founder can run it, but should acknowledge the constraint and compensate with an anonymous written survey and a follow-up some weeks later.

When. Not on the last day, which is emotionally loaded, logistically busy and produces short, polite answers. Schedule it three to five days before the last working day, when the person has mentally moved on but is not yet in farewell mode. Consider a second touchpoint a few weeks after they have started elsewhere — post-exit feedback is usually more candid, because they are comparing you against a live alternative rather than a hypothetical one.

Format. A structured 45 to 60 minute conversation, supported by a short written survey completed beforehand. The survey gives comparable quantitative data across exits; the conversation explains the ratings. Do only one and you get either numbers you cannot interpret or stories you cannot count. Hold it in a private room or private call, do not record without explicit consent, and take notes openly.

Confidentiality, stated precisely. Vague promises destroy trust the moment they prove untrue. Say exactly what happens: individual verbatim responses are not shared with the reporting manager; themes are aggregated and reported to leadership at a level where individuals cannot be identified; where a team is very small, aggregation may not fully protect anonymity and you will say so; and certain disclosures — harassment, discrimination, safety, fraud, statutory violations — cannot stay confidential and will go to the appropriate internal process. That last point is not optional. A complaint of sexual harassment surfaced in an exit interview must enter your organisation's Internal Committee process, and the employee should be told that at the outset. Have counsel review your wording.

Getting honest answers.

• Start with what worked. People warm up on positives and then give you the negatives.
• Ask about the system, not the person. "What would have made the workload manageable?" gets further than "was your manager unreasonable?"
• Use the counterfactual: "What would have had to be true for you to stay?" is the highest-yield question in the bank.
• Be quiet after an answer. The second thing people say is usually the real thing.
• Do not defend. The instant you explain why a complaint is unfair, the interview is over in every way that matters.
• Do not negotiate. If retention was on the table it should have happened weeks earlier.
• Tell them what happens with the input. People are candid when they believe it goes somewhere.

What not to ask. Where they are going, what they are being paid, or who else is leaving — it is not your business and makes the conversation feel like intelligence-gathering. Anything that invites gossip about named colleagues. Anything touching protected characteristics: health, family plans, caste, religion, marital status. Anything implying that documents, settlement or references depend on the answers — never link the exit interview to clearance outcomes. And no leading questions; "you'd agree the culture here is strong, right?" produces nothing usable.

Exit Interview Questions India: A Themed Question Bank

Group questions by theme so responses code consistently. Ask twelve to fifteen, not all of them — choose by role, level and what you are currently investigating.

That final question consistently produces the single most valuable answer in the interview. Always ask it.

Coding Exit Reasons: A Taxonomy for Employee Exit Analytics

Free-text exit notes are unusable at scale. Ten HR people recording ten reasons in ten phrasings gives you ten stories and zero analytics.

Build the taxonomy in two levels: a primary reason and a specific sub-reason. Record exactly one primary reason — the dominant driver — plus up to two contributing reasons. Forcing a single primary makes the data countable; allowing contributors stops it being simplistic.

Two disciplines make this work.

Separate stated reason from assessed reason. The stated reason is what the employee said; the assessed reason is what HR concluded after the manager conversation, the interview and any pattern in that team. Record both. The gap between them is itself information — a wide gap in one team usually means people do not feel safe being direct.

Tag every exit regretted or non-regretted. Regretted means you would have kept them. The manager sets it and HR validates it against performance data, before the exit interview so it is not coloured by how the conversation went. Without this tag your attrition rate is meaningless: 18 percent made up of low performers is a healthy company, and 8 percent made entirely of your best engineers is an emergency.

Turning Exit Data Into Action

Collecting exit data and not acting on it is worse than not collecting it, because you have spent your employees' candour and returned nothing.

The quarterly themes review. Every quarter, produce a short exit analytics pack for leadership covering: total exits split voluntary/involuntary and regretted/non-regretted; primary reason distribution this quarter against the previous four; tenure profile of leavers, since exits inside twelve months point at hiring and onboarding rather than retention; function, level and location cuts; manager-level patterns where sample size permits; anonymised verbatim themes with three to five representative quotes each; and two or three specific commitments with owners and dates.

Keep commitments small and real. "Improve culture" is not an action. "Publish levelling criteria for the engineering ladder by end of next quarter, owner: Head of Engineering" is.

Manager-level patterns, handled carefully. This data is powerful and easy to misuse. Never act on a single exit interview — one negative interview is a data point, not a verdict. Set a minimum threshold and look across a rolling twelve-month window. Triangulate against engagement scores, transfer requests out of the team, absence patterns and skip-level feedback. When a pattern is real, start with coaching and only escalate if it persists. And give the manager themes, never verbatim comments that identify who said what.

Close the loop visibly. Once a year, tell employees what exit feedback changed. "Here are three things we changed this year because of what leavers told us" does more for internal credibility than any engagement campaign, and it lifts next year's response rate because people believe the exercise is real.

Documents to Issue at Exit

Document delays are the most common exit complaint in Indian companies and the most avoidable. Templates should be pre-approved by legal and generated from your HRMS, not typed fresh each time.

What relieving and experience letters should say: name and employee ID, date of joining, last working day, final designation, and a clear statement that the person is relieved of duties. An experience certificate may add a one-line factual description of the function and, if policy permits, a neutral good-wishes line.

What they should not say: the reason for leaving, performance ratings, disciplinary history, subjective character assessments, salary unless specifically requested and approved, or anything you would not defend in a legal proceeding. Coded negative language creates exposure and serves no legitimate purpose.

On withholding documents: treat it as a last resort and take legal advice first. Withholding a relieving letter as leverage to recover an asset or advance is common and risky — it damages your brand instantly and may not be defensible. Pursue genuine recovery claims on their own merits.

On verification: set a consistent policy for what you confirm to background verification agencies, typically dates, designation and rehire eligibility and nothing more. Route all requests through HR. Managers giving personal opinions to background check callers is an uncontrolled risk.

Full and Final Settlement: The Operational Touchpoints

Settlement computation is a topic in its own right. What matters for offboarding design is the handoffs.

Inputs to freeze: attendance and leave balance as on the last working day; notice served versus contractual; leave encashment eligibility per policy; pending reimbursements; variable pay eligibility per scheme rules; and recoverable items such as advances, loans, unreturned asset value where policy permits, and training bonds where enforceable.

Timelines: process settlement within the timeline your policy commits to and consistent with applicable central and state law, which varies. Verify the currently notified requirements for your establishment and state, and publish your internal commitment so employees are not guessing.

Transparency: give an itemised statement with a plain-English explanation of every earning and deduction. Most settlement disputes are communication failures — the employee does not understand the notice recovery line or the tax treatment, not that the number is wrong.

Statutory touchpoints at a high level: verify UAN and KYC before exit and mark the date of exit correctly, directing employees to the official EPFO portal for transfer or withdrawal rather than advising which to choose; check gratuity eligibility, nomination records and the applicable calculation basis against current rules rather than remembered thresholds; explain the exit-year income tax treatment at a high level and recommend a tax adviser for specifics; and confirm ESI and group insurance cessation dates in advance. Across all of these, verify currently notified rules for your establishment, state and employee category, and take professional advice where amounts are material.

Involuntary Exits, Redundancy and Absconding

Involuntary exits need the same operational rigour plus far more legal care. Termination in India is heavily regulated and varies by employee category, statute and state. Take legal advice on every involuntary exit before you act. Nothing here is legal advice.

Handling it with dignity. Whatever the reason, this is a person with a family and a rent payment. Have the conversation in person or on video, never by email, with two people present — the decision-maker and HR. Keep it short and clear: the decision, the effective date, the support offered. Do not relitigate reasons in that meeting. Have the paperwork ready; nothing is crueller than telling someone they are losing their job and making them wait a week to learn what they will be paid. Do it early in the day and early in the week so they have time to act and are not sitting alone through a weekend. Let them leave with privacy, without being escorted past the floor unless there is a genuine security concern. And offer real help where you can — extended insurance, a written reference commitment, introductions, outplacement. It costs little and it is remembered.

Redundancy. Where roles are eliminated for business reasons, selection criteria must be objective, documented and consistently applied, and process requirements differ significantly by employee category and state. This is where Indian employers most often create liability by moving fast. Involve counsel at the planning stage, not after the announcement. Plan for the survivors too: the people who remain calibrate their own loyalty by how their colleagues were treated, so communicate honestly and expect a period of reduced productivity and elevated attrition risk.

Absconding. Where someone stops attending without communication, follow a documented process rather than reacting: contact attempts through multiple channels over a defined period, written communication to the address on record, a reasonable opportunity to respond, and only then a documented conclusion per your policy and applicable law. Keep records of every attempt. Do not treat unreachability as automatic misconduct — people have medical emergencies. Take legal advice on the specific steps required for your establishment. Operationally these cases still need clearance: assets recovered, access revoked immediately, handover reconstructed by the team. Code them separately, because a rising absconding rate usually points at something specific — a shift pattern, a location, a manager or a hiring source.

Alumni Networks and Rehire Eligibility

Two lightweight things with disproportionate returns.

Rehire eligibility coding. At the close of every exit, record a status — eligible, eligible with conditions, or not eligible — with a short reason and an approver. Set it at exit while facts are fresh and make it visible to recruiters at the point of application. "Not eligible" should require a defined reason category and senior approval; it should never be one person's grudge.

Alumni relationships. Boomerang hires are among the cheapest, fastest and lowest-risk hires available: known performance, known culture fit, near-zero onboarding, plus outside experience. A working programme needs little — a personal-email opt-in captured during the exit interview, a quarterly note about company news and open roles, inclusion in the referral scheme since alumni refer well, and an occasional informal meet-up. Ask permission explicitly, honour opt-outs immediately, and keep alumni data separate from employee records with a clear retention rule.

Metrics to Track

Measure the process, not just the outcome. All targets below are illustrative starting points, not benchmarks — set your own from your baseline.

Common Mistakes in Employee Offboarding

• Treating the clearance form as the whole process. The form is the last five percent.
• Running the exit interview on the last day. You get politeness, not information.
• Letting the manager run the exit interview. You systematically filter out the most important feedback.
• Serial clearance instead of parallel. Every handoff adds a day and turns the leaver into an unpaid courier.
• Cutting access at the wrong time. Too early breaks handover; too late leaves an open door.
• Forgetting tokens, keys and shared credentials. Disabling an account is not the same as revoking what that account created.
• No named receiver for the handover. A handover with no receiving owner is a document nobody opens.
• Holding documents hostage. A brand disaster and legally risky. Take advice.
• Vague confidentiality promises. Say precisely what is shared, with whom, and what must be escalated.
• Collecting exit data and never analysing it. Free-text notes in a folder are not analytics.
• Acting on a single exit interview. Patterns require thresholds and triangulation.
• Blending regretted and non-regretted attrition. A single percentage hides the only distinction that matters.
• Improvising counter-offers. No policy means inconsistency and a lesson that resigning is how you get paid.
• Announcing the exit before telling the person how it will be announced. Small courtesy, large impact.
• No transition communication to clients. They should hear it from you, not from a bounce-back.
• Handling involuntary exits without legal input. The wrong place to economise on advice.
• No designed process for remote employees. Asset return and document delivery need a real remote path.
• Never closing the loop. If nobody hears what changed, candour dries up.

Automating the Checklist with HR Offboarding Software

All of this can run on spreadsheets and email. It just degrades the moment several exits overlap, and it degrades silently — you find out during an audit or a security incident.

What HR offboarding software should carry:

• Triggered workflows. Resignation logged, and every downstream task is created automatically with owners and due dates calculated relative to the last working day. Move that date and everything recalculates.
• Parallel clearance with SLAs. Each department gets its own checklist with reminders, escalation and a live view of what is outstanding.
• An asset register linked to employees. Every asset tagged and assigned, with return status, condition notes and a signed receipt, so recovery is a report rather than a memory test.
• Access de-provisioning checklists. Ideally integrated with your identity provider; at minimum a mandatory per-system checklist with a named owner and timestamp.
• Document generation. Acceptance, relieving and experience letters produced from approved templates with employee data merged in, so nobody retypes anything at 9pm.
• Structured exit interviews. Survey and interview notes captured against the employee record, with mandatory reason coding from your taxonomy.
• Exit analytics. Reason distribution, regretted versus non-regretted, tenure and function cuts, manager patterns, cycle time and SLA dashboards, on demand.
• An audit trail. Who cleared what, when, and on what evidence — invaluable in a dispute or an audit.

The point is not speed. It is that the checklist runs the same way for the junior analyst leaving in a quiet month as for the senior engineer leaving in a chaotic one.

Frequently Asked Questions

How long should an employee offboarding checklist take to complete?

The full cycle should fit inside the notice period, with clearance starting in week one rather than the last week. For a 30-day notice: acknowledgement within one day, acceptance within four, clearance workflow open by day seven, handover signed off a week before the last day, exit interview three to five days before, and documents on the last day. Settlement processing extends past the last working day per your policy and applicable rules, but everything else should be closed by then.

Who should conduct the exit interview — HR or the reporting manager?

HR, or a skip-level leader, never the direct manager. Manager relationship is one of the most common underlying drivers of voluntary attrition, and nobody criticises a person to their face during their notice period. For senior exits, use a senior HR leader or a neutral external party. Managers should receive aggregated themes afterwards, never verbatim comments.

Can we make the relieving letter conditional on asset return or repayment of dues?

Take legal advice before doing this. It is widespread and risky — it damages your employer brand immediately and may not be defensible depending on the facts and applicable law. The better approach is to pursue asset recovery and dues as separate claims on their own merits, under policies communicated before the exit, and to issue relieving documents on time.

What is the right notice period, and can we recover pay for shortfall?

The notice period is whatever the employment contract specifies, read alongside the applicable state Shops and Establishments Act or other statutes for that employee category. Shortfall recovery depends on your contract language and applicable law. Verify the currently notified provisions for your state and category, apply the rule consistently across similar employees, and document any waiver or buyout in writing before the last working day.

How do we get honest answers when people just want to leave quietly?

Four things move the needle: schedule the interview before the last day; be explicit about what is confidential and what must be escalated; ask about systems rather than individuals; and close the loop publicly once a year so employees believe the exercise is real. A short post-exit survey a few weeks after they have started elsewhere often produces the most candid data of all.

What should we actually do with exit interview data?

Code every exit against a fixed taxonomy with one primary reason and up to two contributing reasons, and tag it regretted or non-regretted. Review quarterly with leadership: reason distribution over time, tenure and function cuts, manager patterns where sample size allows, and anonymised verbatim themes. Close each review with two or three specific commitments with named owners and dates. Never act on a single interview, and always triangulate with engagement, transfer and absence data.

How should an involuntary exit differ from a resignation?

The operational steps are similar; the sequencing and legal care are not. Access removal happens immediately rather than in phases and is planned before the conversation. Knowledge transfer is compressed and often reconstructed from documentation. Team communication is brief and never explains the reason. Documents should be reviewed by counsel before issue. And the decision itself — particularly redundancy and performance terminations — needs legal input at the planning stage, because requirements vary significantly by employee category, statute and state.

Should we run an alumni programme and rehire former employees?

Yes to both, with structure. Boomerang hires bring known performance and culture fit with near-zero onboarding, plus outside experience. Capture a personal-email opt-in during the exit interview, send a quarterly note, and include alumni in your referral scheme. Pair it with a rehire eligibility code recorded at exit — eligible, eligible with conditions, or not eligible, with a reason and a senior approver — so recruiters have a clear answer at the point of application rather than an argument.

Bringing It Together

Offboarding is where good intentions fail most often, because it happens under time pressure, involves five departments who do not report to each other, and lacks the emotional momentum that carries onboarding along. That is exactly why it has to be designed rather than improvised.

The design is not complicated. Acknowledge quickly and warmly. Confirm the last working day in writing. Run clearance as parallel tasks with named owners and real SLAs. Sequence access removal so it protects the company without insulting the person. Make knowledge transfer a template with a named receiver and a sign-off. Run the exit interview before the last day, with someone other than the manager, and say precisely what is confidential. Code the reasons, read the data quarterly, and issue documents on time every time. Handle involuntary exits with dignity, discipline and legal input. And keep the door open, because the person leaving today may be the best hire you make in three years.

Two closing cautions. Verify every statutory point against currently notified central and state rules and your own contracts — notice periods, settlement timelines, PF, gratuity and termination requirements all vary, and no general guidance substitutes for advice on your situation. And remember that the last thirty days determine what someone says about you for the next thirty years of their career.

If you would rather not run all of this on spreadsheets and reminder emails, CozyHR can carry the operational weight: automated exit workflows that raise clearance tasks for IT, finance, admin and managers the moment a resignation is logged, asset and access tracking against every employee record, and one-click generation of acceptance, relieving and experience letters from your approved templates. Structured exit interviews feed straight into exit reason reporting, so the quarterly attrition review is a dashboard rather than a weekend of spreadsheet work. Take a look when you are ready to make your employee offboarding checklist run itself.