MONDAY · 8:15 AM
311 & public-works scheduling for municipalities
A sinkhole report just started a statutory clock.
A resident reported a sinkhole on Bank Street, and the statutory clock started the moment they hit submit. The week’s schedule didn’t break because your crew planned it badly — it broke because every service request is a web of dependencies: a statutory deadline, a traffic-control setup, a certified crew, a citizen appointment you already promised. When your software ignores that web, it lands on a dispatcher — and later, on an auditor. Crisphive carries the whole graph, so your people don’t have to.
This demo replays a real kind of morning: one emergency lands, and every job finds a new slot without breaking a promise. See how it works ↓
Jobs moved: 0Clocks breached: 0Resident callbacks: 0
Every field service day is a dependency graph. Most software pretends it isn't — and hands the graph to a dispatcher to solve in their head, under pressure, forty times a day. We think the schedule should carry that weight, not your people. That's the whole company.
— Why Crisphive exists
How it fits your day
When the day changes, the schedule keeps up.
Crisphive is the layer that carries your day’s dependencies — every job, every promise, every crew constraint. So when something breaks, the plan repairs itself instead of landing on a person. You keep the intake, the work orders, and the resident relationship; Crisphive keeps them from colliding.
The day changes
The report arrives however it reaches you — a 311 submission, a call to the council office, a hazard flagged in the field. A sinkhole on Bank Street, marked top priority, starts a statutory clock the moment it lands.
The schedule recomputes
The schedule re-plans your units against every hard rule — statutory clocks, traffic control, crew certification, citizen appointments — and returns a new plan plus a backup.
Your team is notified
You confirm once. Your resident notifications go out, your work orders update, your crews are re-routed — and you’re alerted the moment anything shifts again. Nothing else needed.
You never rebuild the day by hand. The schedule recomputes around the disruption, keeps every promise it can, and shows you exactly what moved before anything goes out. Confirming the new plan takes one click.
The rules of your day
Hard rules, not suggestions.
A schedule that ignores dependencies isn’t scheduling — it’s guessing, and a resident pays for the guess. Every plan Crisphive gives you respects every rule below. If a plan comes back, it satisfies all of them — no exceptions, no "hope the crew makes it."
Statutory SLA clocks
Some deadlines are law, not policy. A plan that would breach a statutory clock never reaches your crews — and the plan that protects it stays on record.
Audit-ready determinism
Every plan is reproducible — same inputs, same result. When council or an auditor asks why Unit 1 went to Bank Street, you replay the exact plan that made the call.
Citizen appointments
A promised appointment window is a hard rule. When the day reshuffles, the schedule moves your internal work around residents — not residents around your work.
Traffic-control dependencies
Your crew can’t open a live lane without setup. Traffic-control mobilization is planned as real work with real transit time — always visible on the plan, never billed.
Crew certification
Roads, signals, water — your crews carry different tickets. The schedule only sends a unit whose certifications cover the request, no matter who’s closest.
Break & collective-agreement rules
Break windows and collective-agreement rules are hard limits, not aspirations. The only plan you get back is the compliant one.
Getting started
Up and running in three steps.
Add your crews and their certifications
Sign up and add your units — the roads, signals, water, and parks crews — with the certifications, vehicles, and traffic-control gear the schedule has to respect.
Bring in your jobs and customers
Bring in the week’s requests and residents — by import, or right alongside the 311 and work-management tools you already use. Confirmed appointment windows come with them.
Let the day run itself
From then on the schedule keeps itself. Emergencies slot in, affected jobs move, and your team and customers hear about it automatically — you just confirm.
⏱ Most teams are live within a week — no technical setup
Outcomes
What changes for you. What your customers feel.
You — running the business
Run citizen services that survive the statutory clock.
- Dispatch stops rebuilding the week by hand. A morning of triage becomes one confirmation click.
- Statutory clocks never breach quietly. The schedule refuses plans a dispatcher under pressure might accept.
- Crews spend the day on the work, not the phone. Fewer callbacks, more jobs closed before the clock runs down.
- Every assignment has a defensible answer. When council or an auditor asks why, you replay the exact plan.
Your residents
One hazard report stops wrecking the week.
- The sinkhole is coned, assessed, and scheduled by noon — the emergency handled without the rest of the ward paying for it.
- Promised appointment windows hold. Residents aren’t rescheduled to absorb the city’s internal chaos.
- Statutory deadlines are met, not missed. The report they filed gets closed inside the clock the law sets.
- Honest answers when they ask. Every response says why in plain language, ready for the 311 status page.
Running more than one branch?
Set the rules once. They hold across every crew and depot. The statutory-clock, certification, and appointment logic you set up for one district applies to the next automatically. As you add units, wards, and depots, growth stops multiplying dispatcher chaos — the same plan holds up under a bad Tuesday whether you run one crew or forty.
Why it holds up
Built for the days that go sideways.
Re-planning is free
Re-planning is free and unlimited. Municipal weeks are volatile by nature — a hazard here, a no-show there — so you can re-plan on every disruption without ever watching a bill.
Dependable by design
Schedules come from a deterministic engine, not guesswork — the same situation always produces the same plan. AI helps explain the plan in plain language; it never decides who goes where.
Always a plan B
Every urgent booking comes back with a recommended plan and a backup. If the customer declines the first window, the next-best option is already on the table.
What operators say
Departments that stopped racing the clock
“Statutory clocks used to breach quietly — you'd find out in the monthly report. Now the schedule won't even produce a plan that blows a deadline, and when a sinkhole bumps a pothole crew, I can show council exactly why. That replay has saved me in two meetings already.”
Dale Whitmore
311 Operations Manager · City of Brookmere
“My dispatchers were rebuilding the week every Monday morning — one emergency and everything after it got shuffled by hand. Now the board re-plans in seconds and the citizen appointments we've already promised stay put. Complaints to the councillors' offices are down noticeably.”
Marianne Cote
Director of Public Works · Halloway County Public Works
“The part nobody believes until they see it: traffic-control setups and crew certifications are real constraints, not notes in a comment field. We stopped sending a crew out only to find the flagging crew was never booked. That alone was worth the switch.”
Luis Herrera
Field Operations Supervisor · City of North Elm
FAQ
Questions from the field
How are statutory SLA clocks enforced?
Is the scheduling auditable?
Can residents get confirmed appointment windows?
Does it work with our current 311 and work-management tools?
How long does setup take?
Where does our data live, and who owns it?
Your schedule should survive a bad morning.
Start free and watch a real municipal week re-plan itself — from booking Monday’s crews to cascading around a sinkhole without breaching a single clock.
Questions? support@crisphive.com · Free to start — no credit card required
See how the scheduling engine worksPricing — pay per job scheduled