Designing a pipe
Phases, transitions and SLAs that make the process enforce itself.
A good pipe doesn’t just track work — it makes the wrong move impossible.
Phases and transitions
Each phase declares which phases a card may move to next. Cards can’t skip a required step because the transition simply isn’t offered. A phase marked as done ends the card’s lifecycle.
SLAs
Set a time limit on any phase. Choose the calendar that matches your
team: 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. Breaches are shown on the card and emitted as
card.late / card.expired webhooks.
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
Organisation roles cascade into the pipe. Override per-pipe with admin, member or viewer. Field visibility and editability are role-aware, so a viewer sees the board without being able to change it.
Next: Formulas and validation for correctness rules.