By job

Not every process is a request

Some things are just a body of records a team works inside: the kit you own, the sites you maintain, the contracts you hold. Nobody submits them and nobody approves them. They still need an owner, a state and a history.

Build an app for free Browse templates

The spreadsheet is right for about a year

It starts as one tab with twelve rows and ends as the file everybody knows is wrong. Two people edit it in different copies. A column called Status means something different in each half. Nothing records that the laptop went in for repair in March, so nobody can answer whether it is worth repairing again in August. The data is not wrong because anybody was careless — it is wrong because a spreadsheet has nowhere to put who owns a row, what happened to it, or what it has cost since.

Today

One file, several copies, and no way to tell which is current
Custodian is a name typed by hand, spelled three ways
Status is a colour on a cell, and the legend is in someone's head
History lives in email threads and a folder of receipts
"What have we spent on this one?" means adding it up by hand
Nobody notices a warranty expiring until something breaks

On stepbase

One register, edited in place, with the same rows everyone sees
Custodian is a link to a person your other apps already know about
State is a column with fixed options, and a board you drag cards across
A history you can write into, sitting on the record it is about
Spend rolls itself up from the maintenance log — no adding up
A dashboard of what it is, where it is, and what it has cost

Start from a template

Every template is fully editable: change the stages, forms, and routing to match how you work.

Asset Register

Every laptop, monitor and desk the company owns: who has it, where it is, and what it has cost since.

View template

What makes it work

Tables & recordsColumns, links, rollups, views, policies Pages & boardsRecord pages, boards, tiles, public links Analytics & auditTiles, charts, cycle time, the audit trail Flows & approvalsSteps, Rules, Outcomes, deadlines, escalation

FAQ

Common questions

Yes. Import a CSV into a new table, or map its columns onto a table a template brought with it. Nothing has to be retyped, and you can keep running the sheet alongside it while you check the numbers agree.

No, and you probably should not. A tracker has no form to submit and nothing waiting for sign-off — someone adds a row, someone else moves it on. Add a Step later, behind the one number that actually warrants a decision.

Yes. An app can declare that it depends on a shared table rather than creating a second copy. If your workspace already has one with the columns it needs, it is used; if not, it is created for you.

Yes, and that is the point of keeping state in a column rather than in a process. An asset can come out of retirement, an order can go back a lane when a delivery is short, and nothing has to be re-authored for it.

Whoever you grant the app to, as a viewer, a member or a builder. Inside it, a row policy can narrow the table to the records somebody owns and a column policy can hide a field — purchase values from everyone but finance, for instance.