Delegation of Authority: approvals that route themselves

Spend approval has always been the quiet tax on a construction business. Everyone knows who should sign off on what, but that knowledge lives in someone's head, in an email chain, in a phone call to the office. Deep Space now holds it as a rule the platform enforces on every purchase order, invoice, subcontract and SWMS, automatically, every time. Route by authority, not by guesswork Set each role's spend authority once in the Approval Thresholds matrix. From then on, every order is read against those thresholds the moment it's submitted. The engine finds the role whose authority covers the amount and routes it there. No one works out who approves. The order arrives in the right approval queue with the value, the cost code and a one-click decision. The approval rule stops being a thing people apply and becomes a thing the platform guarantees. Two ways to model authority Some businesses want every order to climb a chain, each level signing in turn as the value grows. Others want a single owner for each band of spend, the one role whose authority covers the amount, with no one underneath them touching it. Both are first-class now, chosen per step. Fixed role holds a step to named roles with a minimum value, so small orders skip it and approvers stack as the number climbs. DoA-driven routes by the thresholds matrix, where the role pool isn't fixed and the engine sends the order to the single role whose threshold first covers the amount. You can mix them inside one workflow, step by step. See the decision before you commit You used to configure limits and hope. The first proof that a rule worked, or didn't, was a live order routing somewhere you didn't expect. The Threshold simulator now resolves your configuration live. Type 80,000 and it shows the order routing to the role that covers it. Type 150,000, past the top of your matrix, and it shows the order exceeding every threshold and escalating to the catch role. You see the resolved decision, in the modal, before a single real order exists. Approval design stops being an act of faith. No order ever falls through The hardest case in any approval system is the order nobody's authority covers, the spend so large it clears every limit in the matrix. A naive system routes it to no one, and it sits. Deep Space closes that by design. When an amount exceeds every defined threshold, it doesn't dead-end. It escalates, deterministically, to the end of the chain, finishing at the workspace administrator. The fallback is automatic and needs no setup, so no workspace can ship with a hole in it. A project with no active workflow of its own falls back through the project chain to the workspace rule and, ultimately, to the workspace admin. There is always a defined approver. There is never a stuck order. In practice: the two-director builder Consider a commercial builder running two states off two different rules. In one, any order up to a set limit goes to the Construction Director, anything above to the Managing Director, and on the rare order that's both large and over its budget target, the Construction Director reviews first and the Managing Director gives final sign-off. In the other state, one director approves everything, with a second as backup. Before Deep Space, that was three written processes, an orders inbox, and a director opening the accounting system to check the budget on every order. The rules held only as well as the people holding them. Now it's two workflows in one workspace. Value-based routing sends each order to the right director on its own, the escalation step that puts a second director on the largest orders is built once and fires only when it's needed, and the budget figures the director used to go hunting for sit in the Budget Register, in the same platform. Three processes become two rules the system runs the same way on every order, while each director keeps exactly the control they had, and gets it back without the email. Built for an auditor's questions Authority changes over time, and a finance team has to be able to answer who could approve what, and when. Every threshold in the matrix is immutable and append-only. You don't edit a role's authority, you add a new threshold, and the previous one is superseded automatically with its effective date preserved. The history is the record. When someone asks why a 90,000 dollar order was approved by that role last March, the matrix tells them, exactly. Workflows and thresholds are scoped per document type, so purchase orders, invoices, subcontracts and HSEQ each carry their own rules, because a role's authority over a PO is rarely its authority over a subcontract. Approval becomes the platform's job, not the team's burden. Set the authority once, and Deep Space carries it on every order, routes it to the right hands, proves it before you commit, catches what exceeds it, and keeps the record an auditor would ask for. The right people stay in control of the money. They just stop having to chase it. Deep Space · Construction runs better here · Published 23rd June 2026