{
  "slug": "technician-efficiency-proficiency",
  "title": "Technician Efficiency & Proficiency Calculator",
  "heading": "Technician Efficiency & Proficiency Calculator",
  "category": "financial",
  "url": "https://www.revenuelab.fyi/toolbox/technician-efficiency-proficiency",
  "summary": "Split flat-rate performance into the two numbers that actually explain it.",
  "description": "Efficiency and proficiency get conflated constantly, and mixing them up leads to wrong conclusions about a technician's real performance. Efficiency is flat-rate hours produced divided by hours actually clocked in — it tells you how fast the tech works against the book. Proficiency is flat-rate hours produced divided by hours available (clocked-in hours plus paid time off, training, and other non-productive paid time) — it tells you how much of the tech's total paid time converts into billable output, which captures absenteeism and shop-caused downtime like parts delays or lack of work. A tech can be 130% efficient (fast worker) but only 85% proficient if they're sitting idle waiting on parts or work orders three hours a day. Shops that only track efficiency miss the productivity killed by poor workflow, thin car count, or bad scheduling, and end up blaming the tech for a shop-level problem.",
  "formula": "Efficiency = Flag Hours ÷ Clocked Hours. Proficiency = Flag Hours ÷ Available Paid Hours. Utilization = Clocked Hours ÷ Available Paid Hours.",
  "dateModified": "2026-09-30",
  "run_url": "https://www.revenuelab.fyi/api/public/calc?tool=technician-efficiency-proficiency",
  "inputs": [
    {
      "id": "flagHours",
      "label": "Flat-rate (flag) hours produced",
      "kind": "number",
      "hint": null,
      "default": 176,
      "unit": "hrs",
      "min": 0,
      "max": null
    },
    {
      "id": "clockedHours",
      "label": "Hours clocked in on jobs",
      "kind": "number",
      "hint": null,
      "default": 152,
      "unit": "hrs",
      "min": 1,
      "max": null
    },
    {
      "id": "availableHours",
      "label": "Total paid hours available",
      "kind": "number",
      "hint": null,
      "default": 172,
      "unit": "hrs",
      "min": 1,
      "max": null
    }
  ],
  "outputs": [
    {
      "id": "efficiency",
      "label": "Efficiency",
      "format": "percent",
      "hint": null,
      "primary": true
    },
    {
      "id": "proficiency",
      "label": "Proficiency",
      "format": "percent",
      "hint": null,
      "primary": false
    },
    {
      "id": "utilization",
      "label": "Utilization",
      "format": "percent",
      "hint": null,
      "primary": false
    },
    {
      "id": "gapHours",
      "label": "Idle/non-billed paid hours",
      "format": "decimal",
      "hint": null,
      "primary": false
    }
  ],
  "worked_example": {
    "inputs": [
      "Flat-rate (flag) hours produced: 176 hrs",
      "Hours clocked in on jobs: 152 hrs",
      "Total paid hours available: 172 hrs"
    ],
    "outputs": [
      "Efficiency: 115.8%",
      "Proficiency: 102.3%",
      "Utilization: 88.4%",
      "Idle/non-billed paid hours: 20"
    ]
  },
  "how_to": {
    "title": "How to use this",
    "steps": [
      "Enter flat-rate (flag) hours produced (hrs).",
      "Enter hours clocked in on jobs (hrs).",
      "Enter total paid hours available (hrs).",
      "Read your efficiency on the right — it updates as you type.",
      "Hit Share to keep the scenario or send it to someone."
    ]
  },
  "scenarios": [
    {
      "name": "Conservative",
      "description": "Lower-end numbers — what if things land soft?",
      "values": {
        "flagHours": 106,
        "clockedHours": 91,
        "availableHours": 103
      }
    },
    {
      "name": "Typical",
      "description": "Defaults — the most common real-world setup.",
      "values": {
        "flagHours": 176,
        "clockedHours": 152,
        "availableHours": 172
      }
    },
    {
      "name": "Ambitious",
      "description": "Higher-end numbers — what if things really pop?",
      "values": {
        "flagHours": 282,
        "clockedHours": 243,
        "availableHours": 275
      }
    }
  ],
  "limitations": [
    "Results are estimates before tax, fees, and inflation unless an input explicitly covers them.",
    "Rates are treated as fixed for the whole period — variable-rate products will drift from this projection.",
    "This is educational maths, not financial advice. Check anything contractual with the lender or your accountant."
  ],
  "faq": [
    {
      "q": "What's a good efficiency number?",
      "a": "Experienced techs on straightforward maintenance and diagnostic work commonly run 110-140% efficiency. New techs or those doing heavy diagnostic/electrical work may run 85-100% and still be fully competent — flat-rate times assume average conditions that don't always match the actual car in the bay."
    },
    {
      "q": "Why can proficiency be low even with high efficiency?",
      "a": "Because proficiency captures time the tech is paid for but not working — waiting on parts, waiting on approvals, shop meetings, training. A 130%-efficient tech with only 80% proficiency is a fast worker being starved of consistent work, which is a scheduling and workflow problem, not a skill problem."
    },
    {
      "q": "How do I raise proficiency without overworking techs?",
      "a": "Fix the utilization gap first: better appointment scheduling, faster parts sourcing, pre-pulling parts before the car arrives, and reducing the time a tech waits for advisor approval on additional work. Those changes convert idle paid hours into billed hours without asking anyone to work harder."
    },
    {
      "q": "Should pay plans be based on efficiency or proficiency?",
      "a": "Efficiency, because it reflects what the individual tech controls. Basing pay on proficiency punishes techs for shop-level failures like parts delays, which breeds resentment and turnover even when the tech is performing well."
    }
  ],
  "related": [
    "https://www.revenuelab.fyi/toolbox/effective-labor-rate",
    "https://www.revenuelab.fyi/toolbox/bay-utilization"
  ],
  "license": "CC-BY-4.0",
  "citation": "RevenueLab — Technician Efficiency & Proficiency Calculator (https://www.revenuelab.fyi/toolbox/technician-efficiency-proficiency)"
}