How do you structure your technician checklists?

My team is rebuilding our checklist templates and I want to get this right. We're currently at 12 techs across HVAC and electrical, and our checklists are either too basic (miss critical steps) or too bloated (techs rush through or skip them entirely).

What I'm trying to solve:

  • Consistent quality across different service types
  • Actual completion in the field, not checkbox fatigue
  • Clear pass/fail criteria that dispatch can act on

I've looked at the checklist best practices post but want to hear what's actually working in the field.

Specifically:

  • How many items is too many for a routine maintenance vs. a diagnostic?
  • Do you use conditional logic (show/hide based on job type) or separate templates?
  • Required photos — every job or exception-based?

Would appreciate any templates or frameworks you've pressure-tested.

Parents
  • Following this closely! Our team's checklists are all over the place — some techs have their own personal notes they add to every job and some don't document anything beyond the minimum.

    Quick question — when you all say "required photos" do you mean the tech can't mark complete without them, or just that they're prompted? And does that slow things down at the end of the day when they're trying to get home? Thanks so much for any insights!

  • @Deja — hard gate for us. Can't submit without photos. We're clear in onboarding that this adds 3-5 minutes per job but saves 30+ minutes on callbacks and disputes.

    On end-of-day rush: we moved photo review to dispatch, not the tech. Tech uploads, dispatch spot-checks next morning. Removed the bottleneck at 5pm.

Reply Children
No Data