Overview
Two features work together to help you automatically manage conditional checks across applications and ongoing compliance:
Application Routing allows you to build flexible application flows, where the checks needed can changed based on information provided about a candidate.
Conditional Rules let you define relationships between check types for ongoing compliance.
This article walks you through how to configure these features to reduce time-to-compliance and admin time, improve worker experience, and reduce compliance risk.
Application Routing
With Application Routing, you can:
Tailor compliance checks dynamically based on a worker’s circumstances
Remove redundant checks on applications – like exempting a National Police Check if an NDIS Worker Screening Check is already held
Build flexible flows that adapt based on real-time candidate input
Create reusable templates that can be applied across multiple flows.
How It Works
Candidates respond to a question you configure, with each path resulting in different routing actions.
For Example: Let’s say your flow includes a National Police Check. If a worker already holds a current, approved NDIS Worker Screening Check, they don’t need to complete the National Police Check.
Ask: “Do you have a current NDIS Worker Screening Check?”
If the candidate answers Yes, then: the system will automatically mark the National Police Check as Optional and Skip it.
Worker Experience - Application Routing
Routing questions are shown to candidates when they begin their application.
If there are multiple questions, they’re shown together.
Once answered, candidates are taken directly to their updated to-do list.
Admin Experience - Application Routing
You’ll see the routing question(s), answer(s), and status (e.g., Unverified or Verified) directly in the application sidebar. "Verified" displays based on a condition which you configure.
Exempted checks are clearly marked with the reason (e.g., “NDIS Approved”).
Conditional Rules
Conditional Rules are configured at an organisation level and apply across all relevant workers on an ongoing basis.
Rule Types
Two rule types can be configured: Instead Of, and One Of.
Instead Of - One check can be used instead of another.
Select one top-level check type and one lower-level check type. When the preferred check is satisfied, the alternative becomes optional
What happens
If the top-level check is Approved and Compliant, the lower-level check becomes Optional
A Conditional Rule label appears on both checks in the portal
If the top-level check lapse , the lower-level check reverts to its original setting (e.g. Required).
Example use case: A worker with a current NDIS registration satisfies the requirement instead of needing a separate Police Check.
Worker Experience - Instead of Conditional Checks
Workers will see a note against relevant checks to help them understand conditionality.
Admin Experience - Instead of Conditional Checks
The conditional rules will be clear in the portal:
One Of - Any check from a group satisfies the other check(s)
Select two or more check types. Useful when multiple checks serve the same compliance purpose.
What happens
If at least one check is Approved and Compliant, all others in the group become Optional
If multiple checks qualify, the one with the furthest expiry date stays Required – the rest become Optional.
A Conditional Rule label appears on all checks in the group
If all qualifying checks lapse, all checks revert to their original setting (e.g. Required).
Example use case: Either an AHPRA Check or a Custom Check for Professional Registration satisfies the professional registration check for a role.
Worker Experience - Instead of Conditional Checks
Workers will see a note against relevant checks to help them understand conditionality.
Admin Experience - Instead of Conditional Checks
The conditional rules will be clear in the portal:
Examples: Common Use Cases
Example: NDIS Checks - Can Be Used Instead of Police Checks
These feature is designed to work in coordination to handle the case where NDIS Worker Screening Checks can be used to cover National Police Checks. Our recommendations for how to configure the product for this are below.
Overall Settings Recommended
Conditional Rule: NDIS Check can be used Instead of National Police Check
Two Routing Templates: One template applies to flows for NDIS Homes, and another template applies to flows for Non-NDIS Homes.
Application Routing Scenarios
| Scenario: Yes, Candidate Has NDIS Check | Scenario: No, Candidate Has NO NDIS Check |
Flows for NDIS Homes |
|
|
Flows for Non-NDIS Homes |
|
|
* Identity Checks can also be changed to Optional and/or Skipped if desired.
Settings
How to Set Up Application Routing
Routing Templates are currently managed by Zipline. Please reach out to our support team with your use case, and the information below. We can assess if it is suitable for your use cases, and then help you get it set up.
Information Needed
To configure Conditional Check Routing, we use routing templates. Each template contains:
A routing question (e.g., “Do you have an NDIS Check?”)
A description shown to workers to help guide their answer (e.g., “Answer “Yes” only if you have a final clearance for “Employees”. Volunteer clearances not accepted.”)
One or more routing paths (e.g., Yes / No)
Each path can include:
An optional verification condition (e.g., NDIS Status = Approved)
One or more actions that exempt or modify checks
Viewing Routing Configuration
Go to Settings → QuickStart Preferences → Automations
Select Routing Templates
View by Template or by Flow
How to Set Up Conditional Rules
Note, this functionality is currently managed by Zipline, please reach out if you need it configured for you.
From Org Settings → Conditional Rules you can:
Enable / Disable — Toggle a rule on or off.
Edit — Change the check types included in a rule at any time.
Delete — Permanently remove a rule.
Common Questions
Common Questions
Can I include the same check type in multiple rules?
No. A check type can only belong to one Conditional Rule at a time.
Do Conditional Rules affect applications?
No. Conditional Rules apply to ongoing compliance only. They have no effect on applications.
Will workers be notified when a rule activates or deactivates?
Not automatically. Workers will see the updated status and the Conditional Rule indicator in their portal the next time they log in. Reminders are sent out as per the reminder schedule.
What if a worker submits and gets approved for an Optional check?
The compliance run will re-evaluate all rules at the next cycle and apply the correct statuses based on what is currently Approved and Compliant.
Can I set up a rule that applies to a specific flow?
Not yet. Conditional Rules currently apply at the organisation level across all workers.
Troubleshooting
Troubleshooting
A check is still showing as Required even though the rule should have activated
Confirm the qualifying check is both Approved (on the effective record) and Compliant — both conditions must be true
Check that the conditional rule is enabled
Compliance status may still be calculating
Verify the worker's flow includes both check types in the rule
The "Conditional Rule" label isn't appearing on a check
Confirm the rule has been triggered — the qualifying check must be Approved and Compliant
Refresh the worker's compliance record after the next enforcement run
Check that the Conditional Rule is not disabled in settings
I can't save a new rule — I'm seeing a validation error
For Instead Of: Make sure you have selected exactly one top-level and one lower-level check type
For One Of: Make sure you have selected at least two check types
Check that none of the selected check types are already used in another rule
A rule was active but Optional checks have reverted to Required unexpectedly
The qualifying check may have expired or changed its status
The rule may have been disabled
Check the check's activity history and the current conditional rule settings