How are you tracking parts usage per technician — not just per job?

We're currently monitoring parts consumption at the job level, which gives us visibility into what was used where. However, as we scale our operations across multiple regions, we're finding this insufficient for identifying patterns in individual technician behavior.

Specifically, we're trying to answer questions like:

  • Which technicians consistently use more parts than estimated?
  • Are there technicians who may need additional training on diagnostics to reduce unnecessary part replacements?
  • How do we distinguish between legitimate variance and potential material loss or misallocation?

Our current approach requires manual spreadsheet aggregation, which is neither scalable nor particularly accurate. Another way to frame this challenge: how are you connecting job-level inventory data to individual technician accountability without creating an administrative burden that defeats the purpose?

I'm particularly interested in whether anyone has implemented a sustainable workflow within FieldPulse, or if you've found it necessary to export data and build external reporting. From a governance perspective, the latter introduces more points of failure, but I'm open to practical solutions that have proven effective at scale.

  • In my experience the built-in reporting won't get you there. We tried for months.

    What actually works: export the work order data with technician and parts used, then pivot in Excel. Not elegant but it surfaces the outliers fast. I can usually spot who's burning through capacitors they don't need within a week.

    Downside is someone's doing this weekly. We rotate it between dispatchers so no one person gets buried.

    • Weekly export automation via scheduled report
    • Technician summary view, not job-by-job
    • Flag threshold: 15% above job estimate triggers review

    We've been running this for 6 months. Took one hour to set up, saves roughly 4 hours weekly vs. manual aggregation. Art's right that native reporting has gaps here.

  • Honestly... why track per tech at all?

    If the job gets done right and the customer doesn't call back, does it matter if someone used an extra fitting? I get the loss prevention angle but I've seen this turn into surveillance that drives good techs out.

    Maybe focus on callbacks and customer complaints instead. That's your real metric.

  • That's one perspective, but we're burning $40K annually on parts that don't hit customer invoices. Someone's eating that cost.

    We implemented a simple rule: parts over job estimate require supervisor sign-off in the field. Caught a $12K problem in month one. Not surveillance — accountability.

  • Another way to think about Ray's concern: the goal isn't to penalize variance, it's to understand it. We've found that technicians who consistently overestimate parts needs often lack confidence in their diagnostic skills — that's a training opportunity, not a disciplinary issue.

    The strategic question is balancing visibility with trust. Brandon's threshold approach may address this.

  • Fair point on the dollar amount. Sign-off in the field though... that's admin drag on every job. How's that working at volume?

  • Oh this is so helpful! I've been trying to figure this out too! We have a small team — just 8 technicians — but I noticed one of them seems to order way more filters than everyone else and I wasn't sure if that was a problem or just normal variation between jobs!

    So far I've been:

    • Checking the inventory reports every Monday
    • Comparing to last month manually
    • Talking to the techs when something seems off

    But it feels really reactive and I want to be more proactive! The idea of a threshold percentage is really smart! I think 15% might be too high for us since we're smaller? Maybe 10%? Or does that catch too much noise?

    Also does anyone have a template for the weekly report they wouldn't mind sharing? I could probably build one but if someone's already done the work...

    Thanks so much everyone this thread is exactly what I needed!!!

  • Pro tip: don't start with a percentage threshold. Start with dollars.

    At 8 techs, your noise floor is probably $50-100 per job. A percentage will flag a $5 variance on a $30 part same as a $500 variance on a $3K equipment job. Dollar threshold is cleaner when you're small.

    We've got 34 techs now and I still think about it in dollars first, percentages second.

  • quick question — does the parts usage in FieldPulse tie to the specific tech who logged it or just whoever was assigned to the job? we have multi-tech jobs and I'm not sure the data splits right

    • Logs to job, not individual tech
    • Primary assignee gets the attribution
    • Multi-tech: recommend separate child work orders if tracking matters

    Known limitation. We've requested per-tech logging but no roadmap visibility.