Skip to content

For towns, villages and counties

Software for municipalities that runs the yard, the front counter and the safety program

Cor Pathway 360 is software for Canadian municipalities that keeps resident reports, permits, bylaw cases, work orders, town assets, bookings, cemetery records and the safety program in one system the town owns. There is no licence fee.

Or call Blake directly at 780-832-5158

Want to try it first? Report a test problem on the live app

  • The town owns the code and the data
  • No per user fee
  • Works offline in the yard
  • Every job routed by department

Which department are you in?

Every request, work order, purchase order and staff member belongs to a department, so each department head sees their own queue and their own spend.

Public Works
Work orders by department, the fleet with pre-trips, fuel and warranties, purchasing and stock, and every town asset with its condition and replacement year.
Planning and Development
Permits and licences from application to issue, inspections booked online against a cut-off, and an online portal where applicants upload and answer corrections.
Municipal Enforcement
Bylaw cases from complaint to compliance, with site visits, notices and follow-ups that fall due on their own. The complainant's name never reaches the property owner.
Community Services
Hall, rink, field and park bookings with conflict checks, closures, insurance certificates on file and set-up work orders raised from the booking.
Clerk and Legislative
Cemetery plots, rights holders and interments on a plot map, and public notices for road closures and water shut-offs emailed by neighbourhood.
Health and Safety
Inspections, hazard assessments, incidents, corrective actions and worker tickets, with a council safety report. COR-ready when the town is.

What changes first

From a pothole report to a closed work order, without the mailbox in the middle

In many towns a problem report goes into a web form that sends an email, with no ticket number and no way to check on it. Here the report is numbered, routed, worked and answered, and every step leaves a record council can count.

  1. Step 1

    A resident reports it

    They pick a category on the town's report page, drop a pin, add a photo and get a ticket number. No account needed.

    The town: Link to the report page from your website, or keep your own form and send its reports in.

  2. Step 2

    It lands in the Roads queue

    The report arrives numbered in the right department. A second report of the same pothole is flagged as a likely duplicate.

    The town: Someone in Roads reads it and decides what happens next.

  3. Step 3

    It becomes a work order

    One click turns it into a work order with the location and photos carried across. The crew closes it with notes and a photo.

    The town: Assign it to whoever is going out.

  4. Step 4

    The resident is told

    When the work order closes, the request resolves and the resident gets an email. Their status page shows it too.

    The town: Nothing. The reply goes out from the work.

Try step 1 yourself

Our test town's report page is live. Send a test report the way a resident would and you get a real ticket number and a status page you can check. What happens on the staff side is what we show you on a walkthrough.

One system, switched on a part at a time

What else a town can run on it

Each part has its own switch. Start with what hurts most and add the rest when the town is ready. The parts talk to each other: a permit can publish a road closure, a failed inspection raises a work order, and a booking raises the set-up job.

Service requests
A public report page per town, a webhook for your own form, staff entry for phone calls, and a status page residents can check.
Bylaw enforcement
Cases, visits with photos, warning letters and orders with compliance dates, and a clean-up work order when the town does the job itself.
Permits and licences
One engine for every type, from development and building permits to business licences, with review by department and renewal reminders.
Facility bookings
Bookable halls, rinks, fields and shelters, a public request form, and set-up work orders raised from the booking.
Map and public notices
A staff map of everything with a place, a public closures feed, and email notices by neighbourhood with a confirmed sign-up.
Work orders and purchasing
A board by department with labour, parts and costs, purchase orders with approval rules, and an export to your finance system.
Fleet
Pre-trip inspections and service schedules for every unit. A fuel log that reads your fuel card statement, and warranties shown on the work order before anyone pays for a repair.
Town assets
Buildings, playgrounds, fields, trails, signs, hydrants and culverts, each with a condition score, its history and a replacement list for the capital plan.
Cemetery records
Plots on a plot map, rights holders with transfers kept, interments within each plot's capacity, and burial and memorial permits.
Health and safety
Playground and facility inspections that work on a phone with no signal. Incidents and worker tickets are tracked too, and council gets a safety report it can read.

What it does not do

  • Anything in finance. Taxes and utility billing stay in the system you use now, and nothing here takes a payment.
  • Recreation program registration and memberships. Link to the system you use now.
  • Council agendas and minutes. Tenders and job postings stay on the sites that run them now.
  • Text message alerts and emergency alerting. Notices go by email, and Alberta Emergency Alert stays the emergency channel.

What stays the town's

The town owns the system, not a subscription to it

Your accounts, your data
The system runs on hosting and a database in the town's name. We are a member you invite in, and you can remove us.
Export whenever you like
Your records sit in a standard database. Taking them somewhere else is a normal export, not a support ticket.
No switch anyone can flip
The software is open source, so there is no licence server and no subscription that turns it off. That includes us.
A handover if we part ways
We hand over every credential we hold and the system keeps running. No export fee and no wind down charge.

How a town goes live, and how ownership and security work.

What it costs

Comparison table.
What you are buyingPrice
Cor Pathway 360 software$0 licence. The town owns it
Setup$3,000 to $10,000, set by the size of the town
Service packageFrom $1,500 a month, two year minimum

Scroll the table sideways to see every column. The first column stays in place.

The service package is the whole relationship: anything that goes wrong is ours to fix, two to three improvements land every month, error checks run every night and security is watched around the clock.

The full pricing, with two worked examples.

Questions towns ask first

Do we have to switch everything on at once?
No. Each part has its own switch, so a town can start with resident reports and work orders and add permits, bookings or the cemetery later. Nothing is lost when a part is switched off, and nothing is charged per module.
Can residents report problems from our own website?
Yes. The town gets its own report page with a ticket number and a status page, and you link to it from your website. If you already have a web form you like, it can send reports straight in instead, so residents see no change.
Who owns the data?
The town does. The system runs on hosting and a database in the town's name, and we are a member the town invites in and can remove. Your records sit in a standard database you can export whenever you like.
Is the software really free?
Yes. The town owns the code and its data, and there is no licence fee and no per user fee. What a town pays for is the service package: we set it up, keep it running, fix what goes wrong and keep improving it.
Is it a fit for a town our size?
It is priced and built for anything from a village with a handful of staff to a city of around 70,000 people. Bigger cities usually already run an enterprise system across finance and operations, and are better served by it.
Does it handle taxes, utility billing or payments?
No. Finance stays in the system you use now. Permit fees and booking amounts are recorded and marked paid, and purchase orders export to your finance system, but nothing here takes a payment.