Do you let technicians self-schedule, or is everything dispatcher-controlled?

We've been doing a hybrid model for about two years now and I would never go back to full dispatcher control.

Here's what works for us:

• Dispatchers own the "bucket" — what jobs need to happen today, in what general geographic zone
• Techs own the sequence — they can reorder their route based on traffic, part availability, or customer preferences they've built relationships with

The key is guardrails, not gates. We set rules: no moving jobs to tomorrow without dispatcher approval, no skipping high-priority calls, no swapping with another tech without checking availability. But within those lines? Let them run.

Pro tip: this only works if your techs actually care about efficiency. If you've got a crew that will milk the clock, keep the reins tight. But for self-motivated teams, you're removing a bottleneck and building ownership.

in my experience this works great until it doesn't

we tried letting techs self-schedule. three months in, half my crew was cherry-picking the easy jobs and leaving the nasty ones for whoever was last to the board. customer complaints went up. dispatcher was pulling her hair out trying to figure out why the "urgent" calls weren't getting touched.

went back to dispatcher control. complaints dropped back down. techs grumbled for a week then got over it.

maybe works with the right crew. mine wasn't it.

Thanks so much for this!! The cherry-picking thing is exactly what I'm worried about. We definitely have a couple techs who would absolutely do that...

Did you try any middle ground before going back to full control? Like maybe techs could only move things within their own assigned zone or something?

Another way to think about this is around capability building rather than just efficiency.

We've found that technicians who participate in scheduling decisions develop stronger customer relationship skills and better time management. They start thinking like business owners, not just employees. The operational benefit is real, but the cultural impact may be even more significant over the long term.

That said, we implemented this gradually — first with our most tenured technicians, then expanded based on demonstrated performance. It was not an overnight change, and we maintained dispatcher oversight for complex or high-value jobs throughout.

we tried zone-only. they just figured out which zones had the easy stuff and started "accidentally" ending up with those routes

look, some people are honest and some aren't. your call on which kind you employ

Nadia's gradual rollout is smart — we basically did the same thing without calling it that. Started with two senior techs, added a third when one retired, now we're at five self-scheduling with the rest still dispatcher-assigned.

What's interesting is the self-schedulers started coaching the others on route efficiency without us asking. Created this knowledge transfer that wouldn't have happened if I was still the bottleneck.

Pro tip: if you go this route, invest in training your techs to actually read the job details before they start moving things around.

I've seen techs rearrange their whole day because "the address looked closer" only to find out the job required a second tech or special equipment that wasn't available at their new preferred time. Dispatcher would've caught that. Tech staring at a mobile screen at 6am? Not always.

Not saying don't do it — just say your checklists and job requirements need to be bulletproof before you decentralize. The info the dispatcher holds in their head needs to live somewhere visible.

this is the thing right here

techs dont always read the notes. they see a pin on a map and go

we tried partial self schedule last year and i spent more time fixing mistakes than i would have just doing it myself

maybe if the app had better warnings or something

Teresa, that's a really helpful point — the team here is looking at better validation prompts for exactly this scenario. Josh too — the idea that job requirements need to be visible and enforced, not just present, is spot on.

We're still dispatcher-controlled but I've been wondering about a pilot with our two most senior techs. What would you say is the minimum app functionality you'd need to feel comfortable trying again? Would mandatory field validation before a move is saved help, or is it deeper than that?

mandatory checks would help yeah

also if they couldnt move a job that had certain tags on it without calling in. like "two person job" or "specialist required"

basically let them move the easy stuff keep the complex stuff locked