SLA tracking that actually fires

Most tools let you set a due date. Almost none make the deadline visible at the moment it matters — on the card, on the board, while the work is still in motion. A deadline nobody sees isn’t a deadline.

Time limits live on the phase

In BRAND_NAME an SLA is configured on the phase, not buried in a report. Every card that enters the phase inherits the limit. The pipe itself can also carry an expiry, so a card that stalls across all phases still surfaces.

Calendars match how your team actually works

A “2 day” SLA means different things to different teams. You choose:

• Wall-clock — raw elapsed time.
• Weekdays only — weekends don’t count.
• Business hours — with a holiday list, so a ticket opened Friday evening isn’t “12 hours late” on Monday morning.

Late is shown, not just logged

When a card breaches, it doesn’t quietly fail an audit — it shows “late by N days” on the card and on the board, and a card.late webhook fires so downstream systems can react. The point of an SLA is behaviour change while there’s still time to act.