When a worker’s role changes in your organisation, it’s essential to manage compliance correctly to avoid any gaps. Here’s how role changes and compliance work in Zipline and how to ensure a smooth transition.
🔗 How Role Changes Are Sent to Zipline
Role changes are typically sent to Zipline automatically via your HRIS integration.
Timing varies: some HRIS systems send updates on the day of the role change; others send them in advance.
✅ Approach 1 (Recommended): Collect Compliance Before the Role Change (Create an Application)
To avoid compliance gaps, we recommend managing role changes through an Application in Zipline before the change happens.
Scenario 1 (Ideal):
Application initiated in Zipline before the role change.
Application is Approved in Zipline.
Role change is sent to Zipline (worker steps into the new role fully compliant).
Why this is best: Compliance is fully cleared before Day 1 in the new role.
⚠️ Alternative Approaches (Still Supported)
Scenario 2:
Application is initiated before the role change but remains In Progress when the role change is sent to Zipline.
Worker moves into the new role but may be temporarily non-compliant until requirements are completed.
We are currently improving how this scenario is managed in Zipline.
Scenario 3:
Application is only initiated after the role change has already been processed in Zipline.
Worker is non-compliant from Day 1 until requirements are met.
We do not recommend this approach but recognise that in some cases it can happen.
We are currently improving how this scenario is managed in Zipline.
➡️ Approach 2: No Application, Just Change the Role
You can allow the HRIS role change to happen without creating an application.
In this case, if any compliance is missing, the worker will be non-compliant from the first day of the new role.
Zipline will automatically send reminders to the worker to complete outstanding checks.
Summary Table
Scenario | Compliance Status on Day 1 of Role Change | Recommended? |
Application Created & Approved Before Role Change | ✅ Fully Compliant | ⭐ Yes |
Application Created Before Role Change, But In Progress When Role Changes | ⚠️ Non-Compliant | No, but sometimes unavoidable |
Application Created After Role Change | ⚠️ Non-Compliant | No, but sometimes unavoidable |
No Application | ⚠️ Non-Compliant | In some scenarios |
By following these steps, you can maximise how smoothly role changes occur from both a compliance and experience perspective.