One
queue
ApproveEvery item waiting on you, with a live pending count carried through to the mobile app menu.
- Purchase and subcontract orders
- Small works orders
- Subcontractor invoices
- Expenses, holiday, plant
UK-built · CDM · CIS · MTD
The engineer clocking in, the buyer raising an order, the clerk logging an invoice: all doing their own job. The management picture is assembled from what they did, current to the hour.

Orders, invoices, expenses, holiday and plant requests. In most firms each has its own route, its own chaser and its own person who forgot. Here they arrive together.
Every item waiting on you, with a live pending count carried through to the mobile app menu.
Authority is set by value, not by seniority alone, so the right number of signatures is enforced rather than remembered.
The approver hears about it where they already are, rather than finding it next time they log in.
The things everyone needs to know, and the things that come round again whether anyone remembers or not.
The reports menu holds fourteen items. These five carry most of the weight.
Every figure on these reports is a by-product of work already recorded: the timesheet line, the approved order, the supplier invoice, the valuation. Nothing is retyped and nothing is assembled by hand, which is why the cost position and the margin against it are current to the hour rather than to the last month end.
Reporting is only worth as much as the record underneath it. The log is added to, never edited.

The rest sit on the FAQ page, including payroll exports and the accounts package.
Same platform, same records. How people reach it, what it produces, and what it connects to.
Two articles on where site communication goes when nobody designs it.
