In your Zipline portal, you may notice certain items categorised as Extra Checks. While they appear on a worker's profile, they behave differently to standard policy checks.
This guide explains what these checks are, why they appear, and how they impact compliance status.
What are Extra Checks?
Zipline works on a flow based compliance system, which makes it easy for you to manage compliance confidently as scale. Extra Checks are checks that are not part of a worker’s current compliance flow, as defined by your organisational policies (Compliance Matrix). They may have been started or completed at a different phase of compliance, that is, they are historical records of some kind.
| Compliance Flow Checks | Extra Checks |
Type | Defined in your Compliance Matrix | Imported or historical record |
Compliance Status | Affects "Compliant" status | No impact on status |
Reminders | Triggers automated emails/SMS | No reminders sent |
Visibility | Visible to Worker & Admin (except for admin only checks) | Visible in Portal only (Admin/Profile) |
Why do they appear?
Extra Checks usually surface in the portal under two specific conditions:
Non-Policy Records: A check record (like an old certificate or a specific check) exists on the person's profile, but it isn't currently required by the specific compliance flow assigned to them.
Zipline-Managed Requirements: Certain checks, such as ID Checks, are managed exclusively by Zipline Admins. These are surfaced for visibility but cannot be modified by Customer Admins.
Key Rules for Extra Checks
To ensure a smooth management experience, keep the following rules in mind:
Zero Friction: Extra Checks are designed not to interfere with your daily operations. Even if an Extra Check is in a "Zipline Review", "Customer Review", or any other unfinalised status, it will not prevent a worker from being marked as compliant.
No Automated Actions: Because these sit outside the active compliance flow, they are excluded from all compliance calculations and automated reminders/campaigns.
ReadOnly for Admins: If a check is "Zipline-owned" (like internal system IDs), Customer Admins cannot act on or manage these items. They are displayed for informational purposes only.
Best Practices
Review Before Promoting: If you find that an "Extra Check" is actually something all workers should have, you must add it to your Compliance Flow settings to make it actionable.
Information Only: Use the Extra Checks section to gain a 360-degree view of a worker's history without worrying that old or irrelevant documents will skew your compliance reporting.
Troubleshooting
Why is a worker "Non-Compliant" if their Extra Checks are all green?
Extra Checks do not contribute to the compliance percentage. Check the Policy Checks section to see which mandatory items are missing or expired.
I can't edit or delete an Extra Check. Why?
It is likely a Zipline-owned requirement (such as a platform ID check). These are managed by the Zipline administrative team to ensure system integrity and cannot be altered by organisation administrators.
Extra checks are not designed to be managed by users. If you really need to manage the check for that worker, adding the check to the worker’s compliance flow or creating an application with ad-hoc check would be ideal.