Termination Meeting Standard Operating Procedure
A termination meeting SOP for preparing, conducting, and closing out an employee exit with HR, manager, IT, and security coordination. Use it to document the decision, control access revocation, and reduce confusion during a sensitive offboarding.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Corporate Hr · Healthcare Administration · Manufacturing Operations · Financial Services · Retail And Hospitality
Overview
This Termination Meeting Standard Operating Procedure template covers the full offboarding sequence for an employee separation: confirming authorization, coordinating HR and operational roles, preparing the termination packet, scheduling the meeting, timing access revocation, conducting the conversation, collecting company property, and closing the record.
Use it when a termination must be handled consistently, discreetly, and with clear ownership across HR, the manager, IT, and security. It is especially useful for same-day separations, sensitive conduct cases, layoffs, and any situation where system access, badge access, or facility access must be removed in a controlled order. The template helps you document who approved the action, who attended the meeting, what was communicated, what property was returned, and what follow-up remains open.
Do not use this SOP as a substitute for legal advice or as a generic performance management form. If the employee is simply receiving coaching, a PIP, or a warning, use a different document. If local law, union rules, or internal policy require additional notice, final pay handling, witness presence, or works council involvement, add those steps before rollout. The template is meant to standardize the process you already intend to execute, not to decide whether termination is appropriate.
Standards & compliance context
- This SOP supports ISO 9001-style documented information practices by defining approvals, records, and controlled follow-up for a sensitive process.
- It helps organizations maintain access control and separation-of-duties expectations that are common in security, audit, and governance programs.
- If the termination occurs in a regulated environment, add any required retention, witness, notice, or final-pay steps to match local labor law and internal policy.
- For safety-sensitive workplaces, align the handoff and access-removal steps with site security rules and any permit-to-work or badge-control procedures.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Steps
This section matters because it turns a sensitive separation into a controlled sequence with clear owners, timing, and verification.
- Confirm termination authorization
- Coordinate the termination plan with HR, manager, IT, and security
- Prepare the termination documentation packet
- Schedule a private termination meeting
- Verify access revocation timing
- Conduct the termination meeting
- Collect company property and confirm return expectations
- Disable system, badge, and facility access
- Document the meeting outcome and any deviations
- Escalate unresolved issues
- Escalate to HR leadership or legal counsel
- Complete post-termination follow-up
How to use this template
- 1. The HR owner confirms termination authorization, records the approving role, and verifies that the decision is ready for execution.
- 2. The HR owner coordinates the termination plan with the manager, IT, security, and legal or payroll as needed, then assigns each action and timing trigger.
- 3. The HR owner prepares the termination documentation packet, including the meeting script, final paperwork, property checklist, and any required acknowledgments.
- 4. The HR owner schedules the private termination meeting and confirms the attendee list, location or video link, and the exact point when access revocation will occur.
- 5. The manager or HR representative conducts the meeting, collects company property, and documents any deviations, employee questions, or escalation needs.
- 6. The IT and security owners disable system, badge, and facility access at the agreed time, then the HR owner closes the record and tracks any pending return items.
Best practices
- Assign one process owner for the termination workflow so timing, approvals, and follow-up actions do not split across departments.
- Confirm the access revocation trigger before the meeting starts, because a delay can expose systems, files, or facilities to unnecessary risk.
- Use a private setting and limit attendees to the minimum required roles to reduce confusion and protect confidentiality.
- Prepare the termination packet in advance so the meeting does not stall while someone searches for forms, scripts, or return instructions.
- Document the exact property returned, the items still outstanding, and the due date for any remaining returns.
- Keep the meeting script factual and brief, and avoid debating the decision during the termination conversation.
- Escalate immediately if the employee becomes distressed, refuses to return property, or attempts to access systems after notice.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who should use this termination meeting SOP template?
This template is for HR, the employee's manager, IT, security, and any authorized people leader involved in an employee separation. It works best when one role owns the process and the others provide approvals, timing, and access actions. If your organization uses legal counsel for higher-risk separations, add that role to the workflow. The template is designed for internal offboarding, not general performance management.
What kinds of terminations does this SOP cover?
It fits involuntary terminations, voluntary resignations with same-day offboarding, and sensitive separations where access must be removed quickly. You can adapt it for layoffs, misconduct cases, role eliminations, or policy-based exits. If the employee is leaving on good terms with a long notice period, you may shorten the security steps but keep the documentation and handoff sections. For complex cases, add a legal review checkpoint before the meeting.
How often should this SOP be used?
Use it every time an employee separation requires a structured meeting and documented follow-up. It is especially important when the organization must coordinate timing across HR, IT, facilities, and security. For routine resignations, you can use the same template with lighter escalation and fewer controls. The value is consistency: each termination follows the same documented sequence instead of relying on memory.
What are the most common mistakes this template helps prevent?
The most common failures are premature access revocation, missing documentation, unclear property return expectations, and inconsistent messaging during the meeting. Another frequent issue is not confirming who is present and who is responsible for each action. This template also helps prevent accidental disclosure of confidential reasons or unsupported statements. It gives the team a clear sequence so the process stays controlled and defensible.
Does this SOP align with compliance or documentation requirements?
Yes, it supports documented information practices that are consistent with ISO 9001-style record control and internal audit expectations. It also helps organizations manage security-sensitive offboarding in a way that supports access control, confidentiality, and incident prevention. If your workplace has regulated environments, you can add approval and retention steps to match internal policy, GMP, or other governance requirements. The template is a process tool, not legal advice.
Can we customize this for different termination types or jurisdictions?
Yes, and you should. Add jurisdiction-specific notices, final pay handling, union or works council steps, and any required legal review fields. You can also create variants for voluntary resignation, involuntary termination, retirement, or contractor offboarding. Keep the core sequence intact, then adjust the approvals, timing, and property return rules to match local policy.
What should be integrated with this SOP?
Common integrations include HRIS records, ticketing or task systems for IT and facilities, badge access systems, and asset inventory logs. Some teams also link the SOP to a document repository for the termination packet and acknowledgment forms. If your organization uses a runbook or case management workflow, map each step to an assigned owner and due time. That makes the process easier to audit and easier to execute under time pressure.
How do we roll this out without creating confusion?
Start by assigning one process owner, usually HR, and define which terminations require the full workflow. Then train managers on what they can and cannot say before the meeting, and give IT and security clear timing triggers. Pilot the SOP on a small number of separations and adjust the handoff points before broad use. The goal is to make the process predictable without turning it into a rigid script.
Related templates
Ready to use this template?
Get started with MangoApps and use Termination Meeting Standard Operating Procedure with your team — pricing built for small business.
