Skip to content

← Journal

How Workridge came to be.

Workridge started with a simple observation from inside city government: the work was getting done, but it was impossible to quantify, and things were falling through the cracks and forgotten until they became emergencies. Here’s how a fix for that one problem grew into work-order software for Public Works.

Some ideas arrive in a flash. Workridge arrived in a meeting.

Before Workridge, Kyle was working for a municipality as a director, and had the privilege of sitting in on meetings where every department talked through the problems it was struggling with. Plenty came up. But one change stood out as the most impactful the city could make: moving from paper to a modern way of tracking work and keeping it accountable.

The trouble with paper and phone calls.

In many Public Works departments, work still comes in by phone and gets passed along on paper. A pothole is reported, a water line breaks, a park needs a repair. Notes get written down, handed off, and sometimes lost. Nobody can say for sure what’s open, who has it, or whether it got done. And an emergency depends on someone remembering to follow up.

General maintenance software exists, but it wasn’t designed around how a city dispatch desk actually runs. So the idea was to fix that one loop first: every job recorded, assigned, done with proof, and verified.

Built around the people doing the work.

Workridge follows the way Public Works crews already work. Calls, and problems crews find themselves, become jobs. The desk assigns them. Crews finish them on a phone, with a photo. A supervisor signs off.

A few decisions shaped everything else:

  • Proof of work. A job can’t be marked finished without a photo. A supervisor then verifies it or sends it back with a reason, and nobody verifies their own job.
  • Emergencies can’t slip. Emergencies skip the review queue and go straight to the on-call crew, with a response target of 30 minutes by default. If no crew has reached it in time, the supervisor is alerted, then the director 15 minutes later.
  • The city owns its data. A city can download everything, including jobs, history and photos, at any time, and that can never be switched off.

From a first version to a fuller toolkit.

Work began in late September 2026. Within the first days there was a working demo with a made-up sample city: crew phone screens, a dispatch queue, supervisor verification, priorities with target times, a dashboard, a map and a printable monthly report.

Since then, it has grown with optional tools a city can switch on or off: vehicles and equipment with maintenance schedules and QR tags, job checklists and inspections, stockroom parts, time tracking, daily logs for water and wastewater plants, and a page where residents can report problems. A view for elected officials shows only city-wide totals, the kind of numbers any citizen could get without an open-records request.

Lately, much of the work has gone into something less visible but just as important: trust in the records. Corrections are added alongside the original instead of writing over it, and every change shows who made it, when and why. Nothing a crew records is quietly lost.

Where it stands.

Workridge is live as a working demo with sample data. In a full rehearsal on the live system, an emergency that nobody had started alerted the supervisor right at the 30-minute deadline, and the director 15 minutes later, automatically.

It all began with a question in those department meetings: what would make the biggest difference? The answer was leaving paper behind. Workridge is our answer to how. You can see more of it on our Work page.

Let’s build together.

Tell us a little about what you have in mind. A few sentences is plenty to start.

Start a conversation