Between 7–9 a.m., Cityworks shows about 65% of our new work orders arriving, and dispatch ends up reassigning mid-route to keep our 2-hour response target. What scheduling changes have worked for you to smooth that peak, like staggered starts, preloaded routes, or a short on-call crew, without pushing overtime?
We built a tiny “surge pair” — two techs start 6:45 and clock out 3:15 — preloaded in Cityworks with last-30-day hot spots, which cut mid-route reassignments about 30% during the “65% between 7–9 a.m.” rush without any OT… If you’re locked to 7 a.m. starts, would holding one truck unassigned until 7:30 be feasible?
We set a Cityworks blackout for PMs/inspections during the ‘7–9 a.m.’ window so every truck launches open for new calls, then release the PM queue at 9:15; that cut mid-route reassignments and kept the 2-hour response without overtime. Small caveat: PM backlog can creep, so we block a quick catch-up slot on Fridays. Can your Cityworks config do a PM blackout, or would you need a simple dashboard rule?
We switched Cityworks to 5‑minute intake batches during “7–9 a.m.” and hold non‑emergency SRs in a tagged queue, then drop them to crews in three micro‑waves (7:05/7:10/7:15) so trucks launch clean without extending shifts; it kept us inside the 2‑hour target and eased dispatch churn. The caveat is it hinges on consistent priority tagging by call‑takers. Do you already use a simple P1/P2 on new SRs?
Quick example: we preassign one P1 “anchor” per zone the night before and freeze it until 7:20 so crews launch from home near hot spots, while we hold about 15% capacity unbooked until 9. @dispatch then drops the rest after a 7:10 check — could you pilot that for two weeks?