How it works
The system is built on one idea: every number has a single source. A number written in two places diverges between them, and the divergence is only ever discovered in a dispute.
1 · The bill of quantities is the origin
BOQ items are entered with their quantities and rates. Everything after is measured against them: the purchase order, the issue from store, the payment certificate, the daily report. The item is the link between plan and actual.
2 · Procurement comes before spend
Purchase request → quotations compared (cheapest and fastest flagged automatically) → purchase order approved → goods received. An approved commitment becomes actual cost on receipt, not before. And an order with fewer than the required number of quotations needs a written exception reason.
3 · The certificate is calculated, not typed
Certified quantities are checked cumulatively against the BOQ plan, and anything beyond it is rejected. Then the contract rates apply in order: the advance is recovered, retention is deducted, tax is computed on the correct base — and the rates are frozen into the certificate when it is created, so changing them later does not rewrite the past.
4 · Cash against commitment
The finance board compares what was certified against what was actually collected and paid: left to collect, left to pay, net cash, and net cash after the advance. Every payment is linked to its certificate and deducted from what it owes.
5 · The waste detector reads and never writes
Twelve deterministic rules run over your data on demand and change not a single row. Every finding carries its evidence: which item, which two numbers disagreed, and by how much. A reviewer can say “this is right” or “this is understood” — which is what a deterministic rule is for.
6 · Who sees what
| Role | Sees | Does not see |
|---|---|---|
| Company owner | All of their company's data, project profitability, and permissions | — |
| Engineer / staff | Assigned projects, purchase requests, reports, and quality | Money figures, team management, and unassigned projects |
| Site foreman | Today's tasks, labour attendance, material receipt and issue, and site photos | Money figures and certificate creation |
| Platform admin | Companies, subscriptions, and headline metrics | Customers' project data |
And the boundary is in the server, not the screen: a request arriving from outside the UI gets a 403, and that is tested role by role and route by route.
7 · On site, with no signal
The daily report and its photos are stored on the device while the connection is down and sent when it returns. A foreman is not asked to find a cell tower to record their day.
8 · Your data is yours
Every report exports to CSV and Excel, and purchase orders and certificates print in a form that can be sent to an external party. The audit log says who changed what, and when.