Designing a pipe
Phases, transitions and SLAs that make the process enforce itself.
Tracking work is the easy half. A well-built pipe makes the wrong move impossible.
Phases and transitions
Each phase declares which phases a card may move to next, so the path through the pipe is one you chose. A phase marked done ends the card’s lifecycle.
SLAs
Set a time limit on any phase. Pick the calendar that matches your team,
whether that is wall-clock, weekdays only, or business hours with a holiday
list. Add a pipe-level expiry to catch cards that stall across the whole
process. A breach shows on the card and fires a card.late or
card.expired webhook.
Conditional fields
show-if rules reveal or hide fields based on other field values, so
a card only ever asks for what’s relevant to its current situation.
Roles
Team roles cascade into the pipe. Override per-pipe with admin, member or viewer. Field visibility follows the role, so a viewer sees the board without being able to change it.
Next: Formulas and validation for correctness rules.