Which approval this job needs. What this hour pays. Who's qualified and rested enough to send. What this client's invoice has to have attached. Operations make those calls from memory a hundred times a day. COIRE makes them from your rules, for any workflow, and keeps the record.
In build now. First domain pack: traffic management. Early partners wanted for the next ones.
Customisable Operational Intelligent Resource Engine. A core that resolves decisions from rules, and a pack of rules built for each operation that runs on it.
Your approvals, rates, qualifications, hours limits and client requirements, written as plain-English rules with effective dates. Not buried in code, not living in one coordinator's head. When a rule changes, it changes on the day and the history stays intact.
Every job runs through the rules. The engine works out the approval path, the pay, the resources and the paperwork the job needs, and shows its working, so a planner can see why and not just what.
Hard gates stop non-compliant work before it leaves the yard. Every gate can be overridden by someone with the authority, with their name on it. The override is the audit trail, not a workaround.
The core doesn't know what industry it's in. Each operation gets a pack: its entities, rules, documents and integrations, built for how it actually works rather than adapted from someone else's software.
Three stages. The first resolver runs on your real rules within weeks, not at the end of a project.
We sit with the people who run the operation and write down every decision it makes, what each one depends on, and what it costs when it's wrong.
Rules, entities, documents and the integrations you already rely on, such as accounting, payroll and scheduling. The hardest decision is built first and demonstrated on your own jobs.
Jobs go in. Resolved decisions, work packs, gates and invoices come out, with the record behind every one. When a rule changes, you change the rule.
COIRE isn't for every business. It's for the ones where the workflow is the hard part. It fits if:
The first pack is traffic management in Western Australia.
Approval path resolved from who owns the road. Scheme and award pay resolved per hour. Ticket and fatigue gates at dispatch. Per-client invoicing with the backing documents attached. Training providers, labour hire, plant and fleet operators and field services have the same shape, and the engine doesn't care what the rules are about.
Local government is next: works permits, traffic management approvals, road reserve conditions and works crews are the same rules from the other side of the counter. See COIRE for local government.
A gate that can't be overridden gets a spreadsheet on the side and a verbal approval, and then it protects nothing. Every hard gate in COIRE has an override path with a name attached, so judgment still gets applied and the record survives.
Mark Rossi ran operations at a WA traffic management company for ten years — from a 70-odd-person outfit to more than 500 staff and 300 vehicles, with one person over operations, fleet and maintenance. The processes and systems that carried that growth were his, and most of the decisions lived in his head.
COIRE started as the system he'd have paid for at the time. It became an engine for any operation that runs the same way.
COIRE is in build now. Before general release we're working with a small number of operations: the traffic management pack first, then a handful of partners in other industries who want the engine built around their workflow, and first access when it's ready.
If you've got a workflow nothing off the shelf handles, book a scoping call. Bring the decision your coordinators get wrong most.