twelfth · Glossary · Working in twelfth
Decision pipeline
Also called triage, pending
In twelfth, the decision pipeline is the path commercial work takes: surfaced into Triage, settled into Pending, then recorded as a decision.
What it means for retail and category teams
Most teams run an informal version: an issue is noticed in a report, discussed in a meeting and eventually acted on, with little record of which stage anything is in. twelfth makes the stages explicit. Triage holds lines that have been surfaced but not yet settled; Pending holds lines that are settled and waiting on the rest of the batch; the last stage records the decision and raises or closes the batch.
Why it matters
Separate stages mean 'noticed', 'being worked' and 'decided' are different states with different owners, rather than three shades of an inbox. That shows where work is piling up, and it means a person has reviewed every line before anything is recorded.
Illustrative example
The business and figures are illustrative, not customer data
A buyer opens a ranked view of availability, pricing and range opportunities. They resolve the work they own and bring the larger questions to a category manager. Each decision keeps its evidence and owner as the work moves forward.
In twelfth
The stages live inside a project, which the daily sync opens per supplier, per remit or per lane. twelfth proposes and people decide: the engine never commits a decision on its own, and guardrails decide when a line needs a second pair of eyes. Every recorded decision lands in the Decisions log.
Related terms
Related on twelfth.ai
- How a Twelfth pilot works
Start with one category, the buyers who know it and the data they trust.