Works permits. Traffic management plan approvals. Road reserve conditions. Your own crews' tickets, hours and plant. Every one of those is a decision an officer makes from rules they carry in their head, dozens of times a week. COIRE resolves them from the rules themselves, and keeps the record.
Early access. We're looking for two or three WA shires to build the local government pack with.
The work that exists because the rules live in email, spreadsheets and memory. Each of these is a workflow COIRE runs by the rules, with a person still making the call where a call is needed.
A contractor's plan lands in the inbox. Someone checks it against the Code, the Standard and the shire's own conditions, chases what's missing, writes the approval and its conditions, and diaries the expiry. COIRE checks the plan against the rules first, lists what's missing before an officer opens it, drafts the conditions from the road and the works, and tracks expiry and inspection.
Utility works, road openings, crossovers, verge treatments, private works. Conditions resolved from the road, the asset and the type of works rather than copied from the last one. Bonds and reinstatement inspections tracked through to release, so nothing sits unreleased for a year because nobody looked.
Who has to be told — residents, emergency services, transport operators, Main Roads where a state road is touched — comes from the closure itself. The notifications, the advertising dates and the conditions are generated, not remembered.
Jobs scheduled against tickets, fatigue and available plant. Prestarts on the crew's phone. Hours costed to the job and the asset, with the Award applied per hour instead of reconstructed at payroll. Nobody rostered onto work they're not current for.
Insurances, inductions, Main Roads registration and tickets checked at engagement and again at every job, not once a year in a spreadsheet nobody trusts. An expired ticket stops the job before it starts.
COIRE is not a replacement for your corporate system, and it doesn't ask you to change how the shire works.
Mark Rossi ran operations at a WA traffic management company for ten years — 500 staff, 300 vehicles, works on local roads across the state. That's a decade of submitting plans to shires, waiting on approvals, and watching good officers drown in the paperwork that came with every one of them.
COIRE's first pack is being built for the contractor side now. The local government pack is the same rules from the other side of the counter, and it gets built with the shires that want it, not sold to them afterwards.
We'd start with the one that hurts most — usually works permits and traffic management plan approvals — running on your real rules and your real applications within weeks, before anything is committed.
If you're a CEO, director of infrastructure or the officer who actually does this every week, book a scoping call. Bring the approval that took longest last month.