ForHosting KIT · Developer Utilities

Generate an employee termination checklist by termination type

Employee departures involve more than ending access and collecting a laptop. Final wages, benefits communications, company property, internal approvals, and personnel records may each follow a different deadline or owner.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

This generator creates an ordered starting checklist for a voluntary resignation, an involuntary termination, or a layoff. It combines steps specific to the selected departure with standard offboarding controls. The result is general operational information, not legal advice, and should be reviewed against the laws, contracts, collective obligations, and policies that apply to the employee and employer.

Choose the termination type before planning the process

Select voluntary when the employee has resigned or otherwise initiated the departure, involuntary when the employer is ending one person's employment for performance, conduct, capability, or another individual reason, and layoff when a role or group is being eliminated for business or organizational reasons. That classification affects the early checklist items because the supporting record, communication plan, review path, and possible notice duties are different. Keep the description accurate and neutral. A resignation should have a retained written record and confirmed final date. An involuntary decision should have a documented lawful reason and the approvals required by policy. A layoff should have recorded business grounds and consistent selection criteria. Do not use the generator to decide which label makes a difficult situation easier; classifications can carry legal consequences. If facts overlap, such as a resignation offered during a planned reduction or a role elimination involving a disputed performance history, pause and obtain qualified local advice before communicating a final decision. Run the tool only after the organization has identified the factual basis it can consistently document.

Assign every checklist item to an owner and deadline

Turn the generated list into a working plan by adding a responsible person, due date, completion evidence, and escalation contact to each item. Payroll should verify wages, approved expenses, commissions, accrued leave treatment, lawful deductions, and the required payment date instead of assuming the ordinary payroll cycle applies. Benefits staff should prepare the notices, election instructions, plan contacts, and deadlines relevant to health, retirement, insurance, continuation, conversion, or unemployment processes. IT and facilities should inventory access and property, then coordinate timing with the manager so access is not removed too early or left open unnecessarily. The manager should prepare a factual handoff of work and records without copying personal data or sharing confidential reasons with colleagues. Human resources should keep decision records, delivered notices, acknowledgments, payment evidence, and property records in the correct restricted locations. For remote workers, plan secure return shipping and document custody. For international, unionized, sponsored, or leave-affected employment, add the specialist owners needed for immigration, consultation, collective agreement, leave, privacy, or records obligations.

Review local requirements before delivering the decision

A standard checklist is a control aid, not a determination that a termination is lawful. Before the meeting or departure notice, compare the plan with the employee's work location, employment agreement, offer terms, handbook, severance plan, collective agreement, protected leave, accommodation history, complaint history, and applicable public rules. Timing can be critical: some jurisdictions require final pay immediately or within a short period, while group reductions may trigger advance notice, consultation, government filing, or employee-representative procedures. Releases and severance agreements may require particular language, review periods, revocation periods, translations, or independent advice. Avoid promising benefits, references, unemployment outcomes, or tax treatment that the organization cannot guarantee. During communication, provide a concise written summary of effective dates, payments, benefits contacts, property return, and a channel for questions. Afterward, record what was delivered and when, complete access changes proportionately, preserve required business records, and limit internal disclosure to people with a genuine operational need. An API request costs $0.002. Schedule a later audit to confirm every item closed and any follow-up documents reached the former employee.

Coordinate a voluntary resignation

Give payroll, benefits, IT, facilities, and the manager one ordered list for a planned employee departure.

Prepare an involuntary termination

Organize decision review, meeting preparation, final pay, benefits communications, access changes, property return, and restricted records.

Plan a workforce layoff

Surface selection review, possible notice or consultation duties, severance support, and standard offboarding tasks before announcements.

Which termination types are accepted?

The accepted values are voluntary, involuntary, and layoff. An unrecognized value returns an invalid input error.

Does this checklist determine whether a termination is legal?

No. It provides general operational prompts and cannot evaluate local law, contracts, protected activity, selection effects, or the complete facts.

When must final pay be delivered?

The deadline varies by jurisdiction and sometimes by termination type. Payroll or qualified local counsel should verify the applicable rule.

Can the same checklist be used for a large layoff?

It is only a starting point. Group reductions may require additional selection analysis, advance notice, consultation, filings, or representative involvement.

What does an API request cost?

Each API request costs $0.002.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/legal2/employment-termination-checklist

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/legal2/employment-termination-checklist \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"termination_type":"layoff"}'
{
  "termination_type": "layoff"
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "legal2.employment_termination_checklist",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →