Every record knows where it stands.
A workflow status names where each record stands — To Pay, Partially Paid, Settled — from its own data, so it never disagrees with the facts. Each state offers its next transitions; each transition opens a playbook.
States, transitions, playbooks.
Three pieces draw every process: where a record stands, the ways it can move, and the steps each move takes.
- 1
Where it stands
A state, read from the record's own data — its payments, dates and links. Nobody types it.
- 2
Where it can go
The transitions you draw from each state, offered only when they make sense.
- 3
How it gets there
The playbook each transition opens: the steps, the fields, the records it needs.
Where it stands, what comes next.
Wherever a record is worked on, its status comes first: the state it is in, the transitions offered from there, and the states each one can lead to.
- 1
Select a row
The bar above the grid shows its status and its transitions — one click opens the playbook.
- 2
Open it
Row Details opens on the status, big: the state, its reason, and every transition offered from it.
- 3
Point at a transition
The states it can lead to light up, a line to each — the way ahead, before anything is done.
A status read from your data, never typed
- 1
Name the states
Each state is a condition on the record: paid in full, partly paid, past its due date.
- 2
Draw the transitions
A line from one state to another, with the playbook it opens.
- 3
Follow every record
The status shows in the grid, sorts your views and lays out a board. Select a row or open it, and its next steps are right there.
What you get
Give a table a status that follows its data — payments, approvals, dates — with the transitions each state offers, drawn as a diagram and shown as a board.
Never out of date
Record a payment, tick a box, correct an amount: the status follows on its own, wherever it is shown.
A status that explains itself
One click on a status shows what made it.
Transitions with conditions
A transition opens only when its condition holds — and says what is missing.
Ready on day one
New workspaces start with the statuses of quotes, invoices, payments, bank lines, equipment lent out and tax filings — with their transitions and playbooks.
An invoice is linked to its supplier, its order and the payments that settle it; rollups add up what is linked. A workflow status then reads where each record stands — To Pay, Partially Paid, Settled — from the data, never typed by hand.
Used in
Frequently asked questions
Can someone set a status by hand?
No — and that is the point: a status is read from the data. To cancel an invoice, a playbook records the decision, a reason and a box ticked, and the status follows.
What if a transition doesn't land where it aimed?
Nothing is forced. The playbook's summary reads the status back and says which state the row reached — and why, when it is not the one the transition aimed at.
How many states can a workflow have?
Up to 60 states and 40 transitions per status column, and as many status columns as a table needs.
