Industries
Built for businesses that buy labour in more than one way.
One data model underneath, a preset on top. The preset sets the unit of work, the cost lines and the deductions; the pricing, approval and costing logic never changes.
The principle
A job is a job. What changes is what you count.
A civils gang is paid by the shift and measured in metres. An electrician is booked by the hour. A haulier prices a route. An agency draws down a retainer. Underneath, they are all the same question: what did this piece of work earn, what did it actually cost, and who did the work?
Ordine keeps the answer in one shape — a job, its cost lines, the people or crews behind each line, and whether that line has been approved and paid — and lets the preset decide the vocabulary.
- Unit of work
- hours · shifts · metres · routes · retainer periods
- Cost line types
- labour · subcontractor · material · plant · permit · other
- Deductions
- CIS at the subcontractor’s rate, or none
- Approval
- routed by value and line type, always explicit
- Posting
- summarised to your accounting software, by job and cost type
Civils, utilities & telecoms subcontractors
Two-man gangs, day rates, standard and specialist bands, permits and traffic management as real money, a supply chain of self-employed people under CIS. Street works, ducting, reinstatement, fibre. The preset we built first, because it’s the business we came from.
- Unit
- shift · linear metres
- Labour
- gang day sheet, split across the crew, third-man cover handled explicitly
- Deductions
- CIS per subcontractor (0 / 20 / 30%)
- Extras
- permits & TM, plant, materials with waste
“Should we take this job, and which gang should do it?”
M&E, electrical & plumbing trades
Employed engineers alongside subcontractors. Service calls against install projects. Materials that make or break the margin, call-out and out-of-hours rates that nobody remembers to charge.
- Unit
- hours · job
- Labour
- engineer time at band rate; subcontract lines where used
- Deductions
- CIS where the work qualifies, otherwise none
- Extras
- materials with waste, van & plant, call-out bands
“Which of our jobs are we actually making money on?”
Logistics, haulage & fleet-heavy operators
The job is a route or a load. The cost is a driver, a vehicle for a day, fuel, tolls, and the hire you had to bring in when your own kit was out. The fleet cost layer we built for civils vehicles ports straight across.
- Unit
- route · load · vehicle-day
- Labour
- driver (employed or owner-driver)
- Deductions
- none, or CIS for site-based plant work
- Extras
- vehicle day cost, fuel, tolls, hire-in
“What does this route cost us with that vehicle and that driver?”
Agencies & project-based services
No materials, no CIS. People’s time against project budgets and retainers that draw down month by month. The number nobody sees until too late is work in progress — done, not yet invoiced, quietly eating the margin. Ordine shows work in progress before the invoice goes out.
- Unit
- hours · retainer period
- Labour
- staff cost rate; freelancer invoices as subcontract lines
- Deductions
- none
- Extras
- pass-through costs, software, travel
“Are we over-servicing this retainer?”
Not on the list?
The model doesn’t care what you call the work. If you can say what a unit of it is, who does it, and what else it consumes, a preset is a configuration exercise, not a rebuild. Tell us what you run and we’ll say honestly whether it fits.
Where we say no.
Fully salaried workforces with no job-level pricing decision don’t need Ordine — a good accounting system and a dashboard will do, and we’ll build the dashboard instead. Retail and hospitality are not a fit either; the unit of work is wrong and we won’t pretend otherwise.