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

Hi everyone! Hope you're all having a great week so far!

So our team has been growing (we're up to 14 techs now!) and I'm wondering if we should start letting our senior technicians do some of their own scheduling. Right now I control everything from the dispatch board — who's going where, what order, the whole thing. It's worked fine but honestly it's getting to be a lot, especially when I'm out sick or on vacation and someone else has to cover.

I've heard some teams let techs claim open jobs or move things around within their own routes, and I'm curious how that works in practice. Does it actually save time or does it just create chaos? What about when customers request specific techs — do you let the tech handle that directly?

Really appreciate any insights! We're trying to figure out what "good" looks like as we scale up. Thanks so much in advance!

Parents
  • 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?

Reply
  • 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?

Children