SLA tracking that actually fires

Most tools let you set a due date. Few put that date in front of you while the work is still moving, on the card and on the board. A deadline nobody sees changes nothing.

Time limits live on the phase

In Track40 you set the SLA on the phase itself, where the work happens. Every card entering the phase inherits the limit. The pipe can carry its own expiry as well, so a card that stalls across every phase still surfaces.

Calendars that match how your team works

A two-day SLA means different things to different teams. Pick the calendar that fits yours.

• Wall-clock. Raw elapsed time.
• Weekdays only. Weekends don’t count.
• Business hours. Add a holiday list, so a ticket opened on Friday evening isn’t 12 hours late on Monday morning.

Late is shown while there’s still time to act

When a card breaches it shows “late by N days” on the card and on the board. A card.late webhook fires at the same moment, so downstream systems can react. The point of an SLA is to change behaviour while there is still time to act.