Offboarding Checklist: A Respectful and Secure Employee Exit

Offboarding coordinates the employment end date, final work, pay inputs, property, access, records and communication. It protects both the departing employee and the organisation when responsibilities are clear and timed correctly.

Create one confirmed exit record

Record the employee, employment entity, reason category, notice dates, agreed last working day and approvals. Resolve conflicting dates before sending instructions to payroll or IT. Store sensitive reasons separately from routine operational notifications.

Explain the timeline

Give the employee a checklist for handover, company property, expenses, benefits, final settlement, documents and contacts. State what depends on another process and avoid promising a payment date that has not been confirmed.

Plan knowledge transfer

The manager should identify open decisions, recurring tasks, files, deadlines, stakeholders and risks. Transfer work to named owners and confirm access to the records they need. Do not ask the departing employee to copy confidential material to personal storage for convenience.

Coordinate access securely

IT, facilities and system owners need the final working date, any approved garden leave or immediate restriction, and the access-removal time. Preserve business records through approved methods. Forwarding email indefinitely can expose personal correspondence and create unclear accountability.

Reconcile money and property

Check attendance, leave, incentives, approved expenses, advances, loans, notice treatment and recoverable property under the applicable terms. Payroll should receive controlled inputs and a reviewer should compare the final calculation with approvals. Do not make an unapproved deduction simply because an asset record is unclear.

Handle statutory and employment documents

Prepare required service, tax, benefit or separation documents through the approved process. Requirements and timelines vary by employment context and applicable law, so the organisation should maintain a current checklist rather than relying on memory.

Communicate the departure

Agree a respectful internal message covering the date and work handover. Avoid disclosing the reason unless appropriate and authorised. Tell relevant clients or vendors who now owns the work.

Verify closure

• Final working date consistent across systems
• Payroll inputs and expenses approved
• Access removed and assets reconciled
• Handover accepted by new owners
• Benefits and documents addressed
• Personal data retained or removed under policy

After closure, give the former employee one route for a genuine query. A professional exit is not only a security control; it is the final evidence of how the organisation treats people when the employment relationship ends.

Final-pay, notice and separation requirements depend on the employment terms and applicable law. Verify the current rules for the specific case.

Example: access timing

An employee works until Friday evening but the system closes access at Friday midnight. IT can schedule deactivation while the manager confirms that business records are stored in the approved location. If the employee is released from duties earlier, HR must communicate the approved access time explicitly. Guessing can either interrupt legitimate work or leave an avoidable security gap.

Different exits need different coordination

A resignation with notice allows planned handover. Retirement may involve benefit and knowledge-transfer support. The end of a fixed term requires confirmation of dates and obligations. An immediate or sensitive exit may require restricted communication and closely coordinated access. The core controls remain, but timing and who receives information should reflect the case.