An employee lifecycle process is easier to manage when every hire, role change, and departure follows the same documented path. This employee onboarding and offboarding SOP template gives SaaS teams a practical structure for assigning responsibilities, approving access, handing over equipment and accounts, and completing a final access-revocation audit.
Overview
A SaaS employee onboarding and offboarding process should connect people operations, managers, IT, security, and finance without relying on informal messages or individual memory. The objective is not to create more administration. It is to make important steps visible, repeatable, and easy to verify.
Use this standard operating procedure template as a starting point for employees, contractors, interns, and other users who receive access to company systems. Adapt the applications, approval levels, retention requirements, and handoff rules to your organization. The process should work for both a small team with a lightweight identity provider and a larger company with automated provisioning and multiple security groups.
Keep the SOP in a controlled location with an owner, version number, and review date. A broader operations manual and SOP review calendar can help you track this document alongside other recurring business processes.
Scope and roles
Define who owns each stage before publishing the checklist. A typical division of responsibility looks like this:
- People operations or HR: creates the employee record, confirms the start or end date, communicates required forms, and coordinates the process.
- Hiring manager: defines the role, approves business access, prepares the first-week plan, and confirms the handoff when someone leaves.
- IT or the system administrator: provisions equipment and accounts, applies role-based access, records assets, and disables or removes access.
- Security or compliance owner: reviews higher-risk permissions, confirms exceptions, and checks that the final audit is complete.
- Finance or payroll: confirms compensation, expense, billing, and final-payment actions where applicable.
One person may perform several roles in a small business. The important point is to assign an accountable owner for every task and an approver for access that could expose sensitive information or affect production systems.
What to track
The most useful employee onboarding SOP templates track status, owner, due date, evidence, and exceptions. Avoid a checklist that only says “set up accounts.” Name the system, the access level, and the person responsible for approval.
1. Pre-start onboarding checklist
Begin onboarding after the start date and role have been confirmed. Complete only the actions that are appropriate before the person joins.
| Task | Owner | Approval or evidence |
|---|---|---|
| Create the employee or contractor record | People operations | Confirmed start date and role |
| Record manager, department, location, and worker type | People operations | Approved personnel details |
| Prepare equipment and asset record | IT | Device identifier, condition, and assigned user |
| Create the identity-provider account | IT | Account owner and sign-in method recorded |
| Assign baseline groups and applications | IT | Role-based access approved by manager |
| Prepare team introductions and first-week schedule | Manager | Calendar or onboarding plan |
Use role groups rather than one-off permissions whenever possible. A software engineer, customer support specialist, and finance user should not receive the same default access simply because all three are employees. Add elevated or production access as a separate approval step.
2. First-day and first-week onboarding
The IT onboarding checklist should include a secure sign-in process, multi-factor authentication enrollment where used, device configuration, password-manager access, and instructions for reporting access problems. Do not place initial credentials in an ordinary email or shared document. Give the new team member a clear path for completing account recovery and security setup.
The manager should confirm that the employee can access the tools needed for the first assignment, understands communication channels, and knows where process documentation lives. Keep training tasks separate from access tasks so an incomplete orientation does not hide a technical problem.
For a repeatable team process, link the onboarding SOP to an employee onboarding playbook containing team-specific information such as recurring meetings, deployment conventions, escalation paths, and documentation locations.
3. Role changes and transfers
Onboarding should not be limited to new hires. A promotion, departmental transfer, extended leave, or change from contractor to employee can alter access requirements. Track the effective date, old role, new role, manager approval, access to remove, and access to add.
Use a remove-then-add review for sensitive systems. First identify permissions that are no longer necessary; then approve the new role-based access. This prevents old access from accumulating as responsibilities change.
4. Offboarding checklist
Offboarding begins when the organization receives a confirmed departure notice or termination instruction. The checklist should distinguish between a planned departure and an immediate access change, since the timing and communication plan may differ. Follow applicable employment, contractual, and internal requirements rather than assuming one sequence fits every situation.
| Task | Owner | Completion evidence |
|---|---|---|
| Confirm final working date and departure type | People operations | Approved record and notification list |
| Identify systems, groups, devices, and credentials | IT | Access inventory or account report |
| Approve ownership transfers | Manager | Named recipients for files, projects, and accounts |
| Disable identity-provider account and sessions | IT | Timestamp and administrator record |
| Revoke application, VPN, repository, and privileged access | IT or system owners | System confirmations or audit entries |
| Collect or remotely manage company equipment | IT or manager | Asset status and handoff record |
| Complete payroll, benefits, and expense actions | Finance or HR | Internal completion record |
| Run final access-revocation audit | Security or IT | Signed checklist with exceptions resolved |
The final access-revocation audit is the control that closes the process. Check the central identity system, directly managed applications, administrative consoles, source-code repositories, cloud platforms, shared inboxes, support tools, password managers, collaboration spaces, and physical access where relevant. Record systems that could not be checked and assign a follow-up owner rather than marking the task complete without evidence.
Cadence and checkpoints
A good SOP uses both event-based checkpoints and recurring reviews. The event-based workflow runs for each hire, transfer, or departure. The recurring review identifies gaps that individual checklists may miss.
Suggested checkpoints
- Before the start date: confirm role, manager, equipment, baseline groups, and required approvals.
- On the first day: verify identity setup, device readiness, security enrollment, and access to essential tools.
- At the end of the first week: ask the manager and employee to report missing or unnecessary access.
- At a role change: compare old and new permissions and record the effective date.
- On the final working day or approved cutoff: execute account disablement, ownership transfers, equipment recovery, and access revocation.
- Monthly or quarterly: sample completed records, review exceptions, and compare active users with current personnel records.
The right cadence depends on the number of systems, user turnover, privilege levels, and internal risk tolerance. A small team may review the process quarterly. A team with frequent contractors or substantial production access may need more frequent checks.
For operational visibility, add open onboarding and offboarding items to a weekly operations review. A weekly operations review template can provide a place to track overdue approvals, unresolved access exceptions, and recurring process risks.
How to interpret changes
Review the checklist as a source of operational signals, not just completion data. A rising number of overdue tasks may indicate unclear ownership, late notice from people operations, or an approval step that does not match how the team works. Repeated access exceptions may show that role groups are incomplete or that a system is being managed outside the normal identity workflow.
Track a small set of practical variables:
- Number of onboarding records completed on time
- Number of offboarding records with unresolved exceptions
- Time between the confirmed departure point and account disablement
- Number of applications requiring manual provisioning or revocation
- Devices awaiting return, reassignment, or secure disposition
- Access requests rejected or revised by an approver
Do not treat these measures as a performance score without context. A new application rollout, reorganization, acquisition, or change in contractor volume can temporarily alter the numbers. Look for repeated patterns, document the cause, and prioritize improvements that reduce ambiguity or manual handoffs.
When the process crosses several teams, map the workflow from personnel record to final audit. A process mapping template helps show where information waits, where ownership changes, and where an account can remain active because no system owner was identified.
When to revisit
Review this employee onboarding and offboarding SOP at least monthly or quarterly, depending on the size and complexity of the team. Also update it whenever the recurring data or underlying workflow changes. Useful triggers include adopting a new identity provider, replacing a major collaboration or payroll tool, changing cloud administration practices, introducing a new employment model, reorganizing departments, or adding a system with privileged access.
Refresh application examples and identity-management terminology twice a year, even if no major incident has occurred. Confirm that account states, group names, device procedures, approval points, and audit evidence still match the tools your team actually uses. Remove obsolete applications from the checklist so reviewers do not assume that an unchecked legacy item still matters.
To put the template into operation today:
- Copy the onboarding and offboarding tables into your task system or operations manual.
- Replace generic application categories with the systems your team uses.
- Assign one owner and one approver for every access and asset task.
- Add a required evidence field for account changes, transfers, and exceptions.
- Run the checklist against one recent hire and one recent departure to find missing steps.
- Set the next monthly or quarterly review date and record it in your SOP index.
Keep the completed records restricted to the people who need them, and avoid storing unnecessary personal or credential information in the checklist. A concise, current process is more useful than a detailed document that no longer reflects the team’s systems. Revisit it after each meaningful workplace-tool change and during scheduled access reviews so the employee lifecycle process remains practical, auditable, and easy to follow.