SLA Enforcement
Daily SLA checks with warning and breach notifications so nothing slips through the cracks.
Service Level Agreements (SLAs) put a clock on tasks that have a deadline. Workestra checks your open tasks once a day and sends notifications when they're at 75% of the SLA window (warning) and again when they hit 100% (breach).
Screenshot needed — add an annotated image showing this UI
How SLAs Work
Every task with a due date has an implicit SLA — the time from creation (or from a specific status change) to the due date. Workestra runs a daily check and flags:
| Threshold | What Happens |
|---|---|
| 75% of window elapsed | Warning — assignee notified, task shows a yellow SLA badge |
| 100% of window elapsed | Breach — assignee and project lead notified, task shows a red SLA badge |
Both thresholds trigger an in-app notification and can also route to email or Slack via automations.
What Gets Checked
- All open tasks (status not Done or Cancelled) with a due date
- Tasks in active projects only (paused / archived / completed projects are skipped)
Where SLA Status Shows Up
- Task list and board — colored SLA badge on the task card
- Task detail — warning or breach indicator near the due date
- Portfolio dashboard — projects with breached tasks are flagged as "at risk"
- Reports — breach counts per team, project, and assignee
Customizing SLA Behavior
Admin can configure at Projects → Settings → SLA:
- Warning threshold — default 75%, configurable between 50% and 95%
- Who gets notified — assignee only, assignee + project lead, assignee + full project team
- Notification channels — in-app, email, Slack (channels connected via Slack integration)
Acknowledging a Warning
When a task hits warning state, the assignee can Acknowledge it in the notification panel — this silences further pings on that specific task until the breach threshold is crossed.
Next Steps
- Automations — add custom escalation rules on SLA events
- Tasks — set due dates to enable SLA tracking
- Reports — breach analytics