Overview
Automated re-evaluation (fka Continuous Approval) is an optional setting on approval policies that automatically re-evaluates an invite whenever its visit details change after the initial approval. Without it, an approved invite remains approved even if someone edits the policy, sign-in fields, or data collection fields associated with it. With automated re-evaluation enabled, the policy re-runs from the most relevant point in the workflow, ensuring that any updates still satisfy your policy requirements.
This is useful for organizations with strict compliance or security requirements, where any change to a visit's details — a new visitor field, a different nationality, an updated badge type — should trigger a fresh review rather than carry over the original approval.
Enabling Automated re-evaluation
Automated re-evaluation is configured on a per-policy basis from the Workflow end step.
Navigate to Global overview > Visitors > Policies and open the policy you want to edit.
If the policy is already published, click the ellipses (...) and select Edit draft to create a new unpublished draft.
In the left-hand side of the policy builder, click Settings.
Under Re-evaluation, toggle on Automated re-evaluation (Re-run this policy when visit details change).
By default, if you use the Pre-registration step, you must enable re-evaluation.
Click Publish to make the change live.
If this policy is already being used by a sign-in flow, be sure to Update flows to reflect the new version.
Exempting fields from re-evaluation
Not every edit needs a fresh review. If a visitor’s arrival moves from Tuesday to Wednesday, the background check they already passed still applies. Exempt fields keep the existing decision for low-risk edits, so approvers see an invite again only when something they’d actually review has changed.
In the policy builder, click Settings in the left-hand panel.
Under Re-evaluation, find Exempt fields from re-evaluation.
Toggle on any fields you want to exempt:
Arrival date
Arrival time
Flow-defined fields: fields on the sign-in flow that aren’t defined as part of this policy. Changes made to Policy fields will always require re-evaluation.
Click Publish, then Update flows if the policy is already in use.
When an edit changes only exempted fields, the policy isn’t re-evaluated, and the existing approval stands. If an edit changes an exempted field and a non-exempted field together, the invite is re-evaluated using the rules above.
How re-evaluation works
When Re-evaluation is enabled, the policy listens for changes to the invite, the sign-in flow, and the policy fields after the initial approval. The re-evaluation behavior depends on which detail changed. You can view the approval attempts in the Approval Progress pop-out window.
Changes to the sign-in flow
If the sign-in flow associated with the policy has any changes made (for example, a sign-in field is added or removed) the invite will be re-evaluated from the beginning of the workflow.
Changes to a policy input field
Policy input fields are the host- or admin-provided fields that drive conditional routing in the workflow. When one of these changes:
If the field is used in a Condition step: the invite is re-evaluated starting from the step where the field was first used. When editing an invite, you'll need to confirm the change when saving.
The invite will update to show it was Edited, and the History log will record this re-evaluation reason.
If the field is not used in any Condition step: the invite is re-evaluated from the beginning of the workflow.
Changes to an evidence field
Evidence fields are policy fields collected through a Data Collection step (also referred to as Approver or Admin fields). When an evidence field is changed, the invite is re-evaluated, starting from the first downstream Approval step that depends on that evidence field. Approvals before that point remain valid.
Editing an invite under a Policy with Automated Re-evaluation
Invites cannot be edited until they have been approved. Once an invite is approved and Re-evaluation is enabled on the policy, any subsequent edits to the invite, the sign-in flow, or the associated policy fields will trigger a re-evaluation per the rules above. This does not apply to edits to Arrival date/time or flow-defined fields, if exempted, as shown above.
The approver(s) at the relevant step in the workflow will receive a new email notification prompting them to review the updated invite. The invite remains in a re-approval state until all required steps are completed successfully, at which point it is fully approved again.
If any approval step is denied during re-evaluation, the entire invite is denied; the previous approval does not persist.
What to know before enabling Automated Re-evaluation
Automated re-evaluation is off by default on every policy. It must be enabled per policy version, and the toggle does not carry forward automatically when you publish a new draft — confirm the setting on each new version.
Re-evaluation only applies to invites created on or after the policy version with Re-evaluation enabled. Existing approved invites on a previous version are not retroactively re-evaluated.
Approvers may see the same invite multiple times if changes are made repeatedly. Consider this when assigning approvers to high-traffic sign-in flows.