RIBA stages that invoice, record and close themselves.
The stage was signed off in March. The invoice went out in June. Between those two dates the work was done, the money was earned, and nothing connected the one to the other.
Stage gates that actually gate
A stage closes when its approvals are in, and closing it is what raises the invoice — not a note in someone’s calendar.
Across the Plan of Work
Built around the RIBA stages your practice already works to, from appointment through to handover.
The evidence kept as you go
Approvals, issued sets and sign-offs recorded at the moment they happen, so the stage record is complete without assembling it later.
The workflows this is built from
3 workflows · about 20 hrs/month- WF-02 — Stage-gate invoicing~7 hrs
The stage was signed off in March. The invoice went out in June.
4 automated · 1 human
- WF-01 — Statutory deadline tracking~9 hrs
A determination date passed and nobody noticed.
5 automated · 1 human
- WF-05 — Client approval register~4 hrs
They say they never approved it. You think they did.
4 automated · 1 human
We start with one workflow, priced before anything begins. If it works, we build the next.
Nothing here replaces the software you already run. It sits between those systems and does the part nobody has time for.
- CLUSTER
- RIBA WORKFLOW AUTOMATION
- WORKFLOWS
- 3
- FOR
- ARCHITECTURE