A row that is waiting on a named person
Anything can write a row. Only a process can say this one is with Priya, is due Thursday, and goes to her manager if nobody answers. That runs inside the app, over the same rows the pages read.
Purchasing
- Steps that wait for somebody
- Assign to a person, a team, a role, a field on the form, the person who submitted it, or an email address outside your company entirely. Reviewers approve, reject, or send it back for more information.
- Rules that branch on the data
- Route on the amount, the department, the risk score, the answer to a dropdown — whatever the form collected, or whatever a column on the row says now. Paths are ordered, with a default, so a request can never fall through.
- Deadlines and escalation
- Put a clock on a Step. When it runs out the work escalates to whoever you nominated, and the overdue task is visible in the inbox rather than discovered at the month-end review.
- People outside the company
- A vendor, a referee, a candidate's employer: they action their Step from an emailed link, attributed to them, with no account and nothing to provision.
- Every decision on the record
- Who decided what, when, and what the form said at the time — on the record page itself, and in an audit trail you can export as CSV on paid plans.
One form, one process. The route through it depends on the answer.
Purchase request
Anyone in the company can submit this.
Standing desk converter
How much?
Current desk is fixed height and I'm on calls most of the day.
Submit request
Rule
Under $1,000
AI approves
$1,000-$10,000
Manager
Over $10,000
FinanceCFO
Approved
Under $1,000: AI checks it against policy and approves. Nobody's inbox.
Type a number. The route follows.
Templates that use it
- AppPurchasingPurchase requisitions routed by spend threshold through department, finance and executive approval, then tracked as purchase orders against a register of approved vendors.
- FormVendor OnboardingMulti-team checks for compliance, legal, and finance.
- FormGrant ApplicationIntake, eligibility checks, reviewer scoring, and committee decisions.
What it does not do
- A Step's answers land on the record row. There is no separate case object with its own fields.
- Escalation is time-based. There is no round-robin or load-balanced assignment across a team.