The Departure Was Handled. Was It Closed?
Most organizations are decent at farewells and poor at closures. A resignation gets a card, a leaving do, warm words — and then the audit finds a laptop that was never returned, a CRM login that stayed live for five months, a leaving date that payroll’s records never quite matched, and a final expense claim that arrived after everyone had stopped looking. None of these happened because anyone was careless. They happened because the exit had no closing document — no checklist, no owner, no sign-off.
This separation form template is that closing document. It’s the HR-led record that ends an employment completely: every asset counted back in, every access right sunset on schedule, every final-pay item settled, and one signed file that answers any auditor, any insurer, any dispute — years later.
Classify the Exit Before Anything Else
Not all departures travel the same road, and the classification drives everything after it. A dropdown separates voluntary resignation, dismissal, redundancy, end of fixed-term contract, retirement, and mutual agreement — because each carries different obligations: notice entitlements, redundancy procedures, appeal windows, benefit continuations, and reference policies. Involuntary departures demand particular care and documentation, and the form gives them the same neutral, factual treatment as any other — which is precisely what protects the organization later. The last working day and the manager responsible complete the header every downstream step keys off.
The Asset Ledger — Counted, Not Assumed
Every item issued becomes a line to close: laptop, phone, monitor, keys, access badge, corporate card, uniform, tools, the security token nobody remembers issuing. Each carries a return confirmation, a return date, and — for hardware — a condition note. Where a departing employee keeps equipment temporarily (a contractual arrangement in some roles, a dispute in others), the form records that status explicitly rather than leaving it as an assumption that ages badly. The file upload field holds the signed asset receipt when your process uses one, and finance finally closes the loop on that deposit card everyone forgot existed.
Access Sunset, Scheduled to the Hour
Security incidents love nothing more than a credential that outlived its owner. The form coordinates the sunset deliberately: which systems the leaver held — email, CRM, finance, code repositories, building systems — who owns each revocation, and the effective time, which is not always the same for everything. A departing salesperson’s CRM access usually ends on the last day; their email may forward for weeks; their building badge may need to work until the final Friday evening. A multiple choice and a few date fields turn this from inter-departmental guesswork into a schedule IT can execute.
Final Pay, Without the Follow-Up Thread
The settlement items live here: untaken leave balances, outstanding expenses, bonuses prorated or clawed back per contract, benefit end dates, and any deductions. Captured once, they give payroll a complete, dated instruction set — and the departing employee a written picture of their final pay before it lands, which is how most final-pay disputes are prevented rather than resolved.
One Record, Signed and Sealed
The closing legal field captures HR’s certification that the checklist is complete — assets recovered or exceptions documented, access revoked on schedule, final pay instructed — with the manager’s acknowledgment alongside. The completed file lives in the response archive, and this is where its value compounds: when an auditor asks three years later how you handle leavers, the answer is a filter and an export, not a reconstruction. Role-based permissions keep departure records with HR alone — they contain exactly the personal and commercial detail that must not circulate — while read-only viewer seats let internal audit sample files without touching them. Webhooks can trigger your IT offboarding workflow the moment a form is filed. Offboarding administration sits beside the human resources templates, its HR sub-category, and the employment collection.
Frequently Asked Questions
What's the difference between a separation form and an exit interview?
Different documents for different jobs. The exit interview captures why someone left and what the organization can learn. The separation form closes the administrative loop: assets, access, final pay, and the compliance record. Every departure needs the second; the first is voluntary and qualitative.
Does the same form work for dismissals and redundancies?
Yes — the classification dropdown routes the process, and the neutral, factual structure is deliberately suited to involuntary exits, where documentation quality matters most. What differs by departure type are the surrounding procedures, not the closing checklist.
When should the form be opened?
The moment a departure is confirmed, not the last week. Assets need locating, access changes need scheduling across departments, and payroll needs complete final-pay instructions — all of which go wrong when the checklist starts on the leaving day itself.
What if an employee won't return company property?
Record it: the form documents the item, the request made, the dates, and the response. That record supports your recovery options — from payroll deduction where the law allows, to civil recovery — and demonstrates to auditors and insurers that the gap is a pursued exception, not an unnoticed one.
Who should have access to completed separation files?
HR only, with auditors on read-only seats where needed. These files combine personal data, security detail, and sometimes sensitive departure circumstances — the strongest argument for keeping them in a permission-controlled archive rather than a shared drive.