Compliance
SLA, deadlines, and automatic escalations
Create deadline contracts with automatic multi-level escalation.
7 min · Operations managers, Risk
SLA rules enforce your operational commitments automatically — no manual monitoring required.
Deadline types
Three ways to set a deadline
Fixed deadline
Specific calendar date
- •A specific date set at run creation.
- •Useful for regulatory deadlines and audit cycles.
- •Example: annual security review with a mandatory date in the contract.
Relative deadline
N business days from start
- •Calculated from run start or task assignment.
- •Example: '3 business days after onboarding start.'
- •Automatic adjustment for non-business days configured by the admin.
Field-driven deadline
Uses the date filled by the executor
- •The deadline is derived from a date field filled during the run.
- •Example: 'incident resolution must happen within 48h of the date entered in Incident detected at.'
- •Flexible for processes where the deadline depends on collected data.
Setup
How to configure a chained escalation
- 1
Open the task in the Flow editor
Select the task and click 'Due date & SLA' in the right-side panel.
- 2
Set the deadline type and value
Choose between fixed, relative, or field-driven deadline. For relative deadlines, enter the number of business days and the reference point (run start or task assignment).
- 3
Add an alert threshold
Configure an early notification: for example, 'notify owner 24h before expiry.' The owner receives an in-app and email notification.
- 4
Add escalation levels
Each escalation level fires after a configurable delay. Example: 'escalate to manager 2h after breach, then to director 4h later.' Add as many levels as needed.
Use cases
Common use cases
- GDPR breach response — Fixed 72-hour deadline for data breach notification to the supervisory authority.
- Vendor renewal — Alert 30 days before contract expiry to start the review process.
- Invoice approval — 5 business days for financial approval with automatic escalation to the CFO.
- Security audit — Quarterly scheduled review with a 10-day completion SLA.
- Access review — Annual permission review cycle with a regulatory fixed deadline.
What happens to in-progress runs when I change a deadline rule?
Existing runs keep their current deadlines. Only new runs created after the change use the updated rule.
Can I pause an SLA?
Not directly. You can extend the deadline manually on a specific run.
Do SLA breaches appear in the audit trail?
Yes. Every escalation event is logged with timestamp.
Can I see which templates breach most frequently?
Yes, in the SLA dashboard available on Business and Enterprise plans.
Automate your deadline commitments
Configure SLAs and escalations to never rely on manual monitoring.