A joiner mover leaver policy document is not the same thing as a joiner-mover-leaver workflow. The workflow is the automation that moves access and equipment through each stage. The policy is the written standard that says what should happen, who owns each step, and what "done" looks like, and it is the document auditors, new managers, and compliance reviews actually ask for by name. Most businesses have the workflow half-built and no policy document at all, which becomes a real problem the moment a SOC 2 auditor, a new HR hire, or an offboarding dispute asks "where is this written down."
In short. A joiner-mover-leaver policy is the written standard behind the automation: who owns each step when someone joins, changes role or leaves, the deadlines for granting and revoking access, and who approves exceptions. Auditors ask for it by name, and it closes the gaps a workflow alone cannot, such as missing access revocation deadlines.
This guide is the policy template itself: the exact sections, ownership assignments, and SLA language to include, ready to adapt to your organization rather than write from a blank page.
Why You Need the Policy Document, Not Just the Workflow
A working joiner-mover-leaver automation answers "what happens." A policy document answers "what is supposed to happen, who is accountable if it does not, and how do we prove it." These serve different audiences: your automation serves your IT and HR systems; your policy document serves auditors, new managers who need to know their responsibilities, and your own team six months from now when someone asks why an exception was made.
Compliance frameworks that reference access management (SOC 2 CC6.1-6.3, ISO 27001 Annex A.9, GDPR Article 32) specifically look for a documented policy, not just evidence that a system exists. A well-built n8n workflow with zero written policy behind it is a common finding in SOC 2 readiness audits, precisely because auditors cannot verify a process is followed consistently without a documented standard to check it against.
The Policy Template: Section by Section
Section 1: Purpose and scope
State plainly what the policy covers (all employee lifecycle events affecting system access and physical assets) and who it applies to (all employees, contractors, and temporary staff, explicitly naming contractors since this group is the most common gap in real policies we review).
Section 2: Ownership matrix
This is the section most policy templates skip, and the one auditors ask about first. Define exactly who owns each stage:
| Stage | Primary owner | Secondary approver | SLA |
|---|---|---|---|
| Joiner: account provisioning | IT/People Ops | Hiring manager | Before day 1, 100% of the time |
| Joiner: system access grants | IT | Department head | Within 4 business hours of start |
| Mover: role change access update | IT | New + former manager | Within 1 business day of effective date |
| Mover: access review (old role) | IT | HR | Within 3 business days |
| Leaver: access revocation | IT/Security | HR | Within 1 hour of termination notice for involuntary, end of last day for voluntary |
| Leaver: equipment recovery | IT/Facilities | HR | Within 5 business days |
| Leaver: knowledge transfer | Departing employee's manager | N/A | Complete before last day |
Section 3: The joiner standard
Every new hire gets provisioned access according to a role-based template, never an ad hoc copy of another employee's permissions. Copying an existing employee's access (a common shortcut) is how permission creep compounds silently over years; a role-based template, reviewed quarterly, keeps grants tied to actual job function.
Section 4: The mover standard
Every role change triggers a two-part review: granting new access needed for the new role, and explicitly revoking access tied only to the old role. The most common compliance gap in real audits is the first half happening (new access granted) while the second half is skipped (old access lingers indefinitely). This policy makes the revocation step mandatory and tracked, not optional cleanup.
Section 5: The leaver standard, split by termination type
Voluntary and involuntary departures need different SLAs. Voluntary: access revoked at end of final scheduled day, after knowledge transfer completes. Involuntary or for-cause: access revoked within 1 hour of the termination conversation, before the employee leaves the building or the call ends, with IT on standby to execute the moment HR confirms.
Section 6: Exception handling
Every real organization has exceptions (a departing employee needed for a 2-week transition period, a contractor extension). The policy must state that exceptions require written approval from a named role (typically CISO or Head of People) and an explicit end date, never an open-ended extension, since undocumented exceptions are exactly what turns into an audit finding a year later.
Section 7: Audit and review cadence
State explicitly how often the policy itself gets reviewed (we recommend every 6 months or after any compliance framework change) and how access grants are periodically re-certified (quarterly access reviews, where each manager confirms their team's current access is still appropriate).
The Ownership Gap: Three Gaps That Show Up Most Often
When organizations prepare joiner-mover-leaver policies for SOC 2 or ISO 27001 readiness, the same three gaps come up again and again, so it is safest to assume they exist until checked:
| Common gap | Typical fix |
|---|---|
| No documented SLA for access revocation timing | Add explicit hour/day SLAs per termination type, as in Section 5 |
| Mover access review not required (only new access granted) | Make old-role revocation a mandatory linked step, as in Section 4 |
| No named owner for exception approval | Assign a specific role, not "management," as approver |
These gaps explain why a policy document paired with the automated workflow closes gaps a workflow alone cannot: the workflow executes steps, but only the policy assigns accountability when a step is skipped or an exception is made.
How the Policy and the Automation Work Together
The policy document defines the SLA (revoke access within 1 hour of involuntary termination). The joiner-mover-leaver automation workflow is what actually executes that SLA reliably, triggering the revocation the moment HR marks a termination in the system, logging the exact timestamp for audit evidence. Neither one replaces the other. The policy without automation is unenforceable in practice; automation without a documented policy has nothing for an auditor to check it against.
The Three Core JML Workflows
Joiner Workflow
The joiner workflow triggers from a confirmed start date in your HRIS or ATS. Everything that follows is automatic.
The sequence begins with identity provisioning: creating the Active Directory or Okta account, setting the initial password, assigning the user to the correct groups and distribution lists based on department and role. This single step eliminates the most common joiner failure mode, the new employee who arrives on day one and cannot log in because IT was not notified in time.
Account provisioning follows: creating accounts in every system the role requires. A sales hire needs Salesforce, HubSpot, LinkedIn Sales Navigator, and the sales team Slack channels. A finance hire needs Xero, the finance Notion workspace, and read-only access to the data warehouse. The role-based access matrix defines exactly which accounts to create for each role, and the workflow executes all of them in parallel.
Equipment provisioning runs alongside: a ticket is created in your ITSM platform for laptop configuration, accessories, and shipping if the hire is remote. The ticket includes the start date, the hire's preferred setup from the offer stage form, and the delivery address.
Induction scheduling is next: the new hire is added to the onboarding Slack channel, the week-one calendar is populated with required meetings, and the pre-arrival email sequence begins 14 days before start.
Payroll setup is the final step: the hire record is created in the payroll system with the correct salary, start date, cost centre, and tax information pulled directly from the offer letter data.
Here is the n8n workflow structure for the joiner trigger:
Mover Workflow
The mover workflow is the most complex of the three because it must both add and remove access simultaneously. An employee moving from the marketing team to the sales team should immediately gain sales tool access and lose marketing tool access. If this happens manually, the access modification typically takes 2 to 5 days and often results in the employee retaining access to systems they no longer need, a security and compliance gap.
The mover workflow triggers from a role change event in the HRIS. It runs a comparison between the old role's access matrix and the new role's access matrix, calculates the delta, and executes additions and removals in parallel. The manager of the new department receives a notification with a checklist of items that require human judgement, such as knowledge transfer priorities and project handover timelines.
Cost centre updates happen automatically in the finance system. Reporting line changes update in the HR system and org chart tool. Physical access changes trigger a facilities ticket if the new role is based in a different location or requires different building access.
| Mover Action | System | Trigger | Automated |
|---|---|---|---|
| Access matrix delta calculation | IAM platform | Role change event | Yes |
| New system accounts | SaaS tools by role | Delta result | Yes |
| Old system access removal | SaaS tools by role | Delta result | Yes |
| Cost centre update | Finance system | Role change event | Yes |
| Reporting line update | HRIS + org chart | Role change event | Yes |
| Manager notification | Slack / Email | Completion of above | Yes |
| Knowledge transfer checklist | Task manager | Role change event | Human-assisted |
| Physical access change | Facilities ITSM | Location change | Yes |
Leaver Workflow
The leaver workflow is the most security-critical of the three. Every hour of delay between an employee's last working day and full account deactivation is an hour of unnecessary risk. Best practice is to deactivate accounts at the end of the last working day, not when HR gets around to notifying IT.
The leaver workflow triggers from a termination date in the HRIS, set when the resignation or termination is confirmed. The workflow schedules all deactivation actions to execute at 17:00 on the last working day.
At the scheduled time, the workflow deactivates the Active Directory or SSO account first, which cascades to all connected applications simultaneously. It then specifically terminates sessions in any application that does not use SSO: revokes API tokens, removes the leaver from shared inboxes, transfers their email to their manager, and cancels any scheduled send emails.
An equipment retrieval ticket is created with the return deadline and courier booking link if remote. Final payroll is triggered with the leaving date, outstanding holiday balance, and any contractual payments. A leaver survey is sent to the employee's personal email on their final day.
The average organisation takes 3.2 days to fully offboard a leaver manually. Automated offboarding completes in under 15 minutes on the scheduled date. For a 200-person company with 20% annual turnover, this closes a 40-person annual security window that would otherwise remain open for days at a time.
Role-Based Access Matrix
The foundation of effective JML automation is a role-based access matrix, a document that defines exactly which systems each role in the organisation requires access to. Without this matrix, the automation cannot know what to provision or deprovision.
The matrix is typically maintained in Airtable or a Google Sheet and looks like this:
| Role | Slack | HubSpot | Salesforce | Xero | Notion | GitHub | AWS |
|---|---|---|---|---|---|---|---|
| Sales Executive | sales, general | Read + Write | Full | Read | Sales wiki | No | No |
| Finance Manager | finance, general | No | Read | Full | Finance wiki | No | No |
| Developer | eng, general | No | No | No | Eng wiki | Full | Full |
| Marketing Manager | marketing, general | Full | Read | Read | Marketing wiki | No | No |
When a new hire is confirmed, n8n looks up their role in this matrix and provisions exactly the access in the corresponding row. When a mover changes role, it calculates the delta between their old row and their new row. When a leaver exits, it deactivates everything in their row.
Implementation Steps
Deploying JML automation follows a consistent pattern regardless of your existing tech stack:
- Week 1: audit current JML processes, map every manual step, identify which systems are involved for each role
- Week 2: build the role-based access matrix in Airtable or equivalent
- Week 3: configure the joiner workflow in n8n, test with a sandbox hire
- Week 4: configure the leaver workflow, test with a sandbox termination
- Week 5: configure the mover workflow, test with a sandbox role change
- Week 6: run parallel with manual processes for one cycle, confirm outputs match
- Week 7: go live, decommission manual steps
Most organisations achieve go-live within 6 to 8 weeks. The leaver workflow typically delivers the fastest perceived value because the security improvement is immediate and visible.
Frequently Asked Questions
Do we need a separate policy document if we already have a working automated workflow?
Yes, for any organization pursuing SOC 2, ISO 27001, or similar compliance frameworks. Auditors specifically request a written policy as evidence, separate from proof that a system exists, since a policy documents intended process and accountability in a way system logs alone do not.
Who should own the joiner-mover-leaver policy document itself?
Typically HR or People Ops owns the document, with IT/Security as a required co-signer, since the policy spans both HR process and technical access controls. Neither function alone should own it, since a policy written only by HR often lacks enforceable technical SLAs, and one written only by IT often misses HR process steps like knowledge transfer.
How often should the policy be reviewed and updated?
Every 6 months at minimum, and immediately after any change to compliance framework requirements, a significant reorg, or a security incident that reveals a gap in the current process.
What is the biggest mistake companies make with this policy?
Writing detailed joiner and mover sections while leaving the leaver section vague, especially around involuntary terminations. Since involuntary departures carry the highest security risk, this is precisely the section that needs the most specific, hour-level SLA language, not the least.
Can PURIST help draft this policy for our specific compliance framework?
Yes. A free automation audit includes a review of your current joiner-mover-leaver process against SOC 2 and ISO 27001 requirements, and we draft the policy document alongside building or auditing the underlying automated workflow.
Tags
Steve founded PURIST, a workflow automation studio working with n8n, Make and Claude AI, and is the point of contact on every project. Prices and features in our articles come from vendor documentation and public pricing pages. How we research and score tools.