Which workers can you compare fairly?
Group by role, territory and assignment before reviewing productivity. Installation crews, residential service technicians and commercial maintenance specialists earn revenue under different scheduling and billing patterns.
One lead technician might supervise an apprentice on every changeout. Another drives to isolated rural calls with a full service workload. A company average can obscure both facts. Use a consistent technician code and record the trade or line of business so you can filter comparable work.
Your roster is also an operating map. Ask who can supervise particular jobs, handle after-hours diagnostics and step into a dispatcher’s urgent callback. The person with the highest revenue is not necessarily the person whose absence creates the biggest schedule problem.
How do dispatch and payroll fit together?
Match paid hours to the payroll window, then pull only jobs completed in that same interval. Establish an invoice rule for split crews so revenue does not appear twice.
A job sold in June, installed in July and collected in August creates three different dates. Pick the completion or invoicing basis your analysis is testing and preserve it across technicians. Exclude refunds and credits according to a stated rule, then reconcile the combined attributed revenue to the company’s job report.
Billed utilization divides billed hours by paid hours. Flat-rate shops may post standard hours that differ from elapsed time. If you use that convention, label it and resist treating the result as a timecard audit. Use callbacks, collected revenue and service quality alongside the hours measure.
What changes your conclusion about a high performer?
Review callbacks, job mix and the support required to produce the revenue. Average ticket can rise when a technician receives more replacement opportunities without any change in diagnostic skill.
If you’re selling, show buyers how dispatch allocates high-value leads and where supervision time is charged. If you’re buying, ask for an anonymized sample of credited jobs, especially jobs completed by two people or finished by another crew the following week.
A credential entry can flag a follow-up but cannot prove authorization. Match the technician to the applicable certification type, review the actual evidence and protect personnel records. Use a separate transition plan for retention conversations and backup coverage.
How do you set up your working copy?
Pick one payroll window where your timekeeping and dispatch data are both complete.
- List the role, location and normal schedule for each anonymized technician code.
- Tie completed jobs and revenue back to invoices. Count only once when crews share credit.
- Review callback attribution and time spent mentoring before you compare individual results.
What will you find in the file?
The row is designed to follow a technician from the time record through the completed-job result.
| Worksheet field | How to use it |
|---|---|
| Technician code | Keep the code stable without disclosing personal contact details. |
| Role / line | Separate tasks with meaningfully different billing patterns. |
| Period | Identify the payroll and dispatch date window. |
| Days worked | Count actual worked days in that window. |
| Paid hours | Include paid time under the agreed pay-period definition. |
| Billed hours | Use billed hours from your dispatch or invoicing system. |
| Completed jobs | Count finished jobs under the written completion rule. |
| Net job revenue | Use net job revenue after relevant credits. |
| Callback jobs | Flag return visits according to a consistent callback definition. |
| Billed utilization | Divide billed hours by the hours paid. |
| Revenue per day | Divide net revenue by actual days worked. |
| Average ticket | Divide net job revenue by completed jobs. |
| Callback share | Compare callback jobs with the selected completed-job population. |
| Credential / expiry | Record applicable trade credentials and verification references. |
How should you define a row before comparing technicians?
Choose one technician, one clearly defined role and one reporting period. If a person spent half a quarter doing residential service and half supervising installations, a single blended row can obscure both contributions. Use an appropriate separation when your records support it and document the time basis. A worker assigned to training, callbacks or installations can look artificially weak beside someone dispatched exclusively to high-value replacement opportunities.
Use a stable technician code in the working file distributed for early diligence. Keep the identifying crosswalk and personnel records in the restricted location managed by the employer. Record role, period and relevant credential status without distributing home contact details or unrelated personnel information. In a small shop, even a coded role can identify an individual, so consider the intended recipient and transaction stage.
Agree on the definitions with payroll and dispatch before importing totals. Days worked may exclude vacation and leave, while paid hours can include training, travel or on-call pay. Billed hours may reflect the customer-facing flat-rate amount rather than time physically spent on site. Each measure can be useful when defined, but a mismatch can create a persuasive-looking utilization percentage that answers no meaningful question.
How do you reconcile the numbers to an ordinary working week?
Select a week with a mix of routine calls, a callback and at least one shared job. Begin with the dispatch log and match each completed job to its technician assignment, invoice and final status. Identify cancellations, reschedules and estimates that did not become a completed job. Do not credit an individual with revenue simply because their name remained on a sold estimate after another crew delivered the installation.
Compare scheduled time to payroll and timekeeping records. Review travel, training, meetings, holiday pay and after-hours work using the employer’s actual definitions and policies. Record any period in which the technician was on leave or assigned to nonbillable supervision. The purpose is to understand the denominator for the business analysis. Payroll compliance questions should go to the appropriate payroll or legal professional.
Trace net job revenue to the accounting records with attention to refunds, financing charges, credits and team-based installations. If two technicians worked on the same job, establish a consistent assignment rule or keep it at the crew level. Giving both people the entire invoice can make workforce output exceed the company’s actual revenue. Preserve the adjustment method so the reviewer can reproduce it for another period.
What should you investigate when a row looks unusually strong or weak?
Start with the work assigned. A senior diagnostic technician serving older equipment can generate many replacement opportunities. A maintenance technician completing prepaid visits may generate less invoiced revenue per day while fulfilling a valuable contractual obligation. A new apprentice paired with a lead may add capacity without receiving a separate job assignment. Compare people doing comparable work before deciding what the result means.
Examine callback records in context. Find out whether the company counts every return visit, only confirmed workmanship issues or visits attributed to the person who made the original repair. A skilled technician asked to resolve another employee’s difficult callbacks may appear to have a high callback rate if the system records the responder rather than the originating job. Review a sample of tickets and explain the assignment rule.
Consider geography and scheduling. Excess travel time can reduce completed calls per day even when the technician handles jobs efficiently. A dispatcher who sends one employee repeatedly across the territory can create a route-planning problem that looks like individual underperformance. Use the actual timestamps, service areas and job mix to identify the change that would improve the business.
How do the results translate into a buyer’s staffing forecast?
Model a vacancy at a specific role rather than removing an average technician. A departing licensed supervisor, lead estimator or refrigeration specialist can affect jobs beyond their own billed hours. Identify who can cover the work, what overtime or subcontracting it requires and which service commitments may be delayed. Record whether a backup has actually performed the work.
Estimate recruiting and training costs separately from recurring replacement pay. A new person may need time before producing at the departing employee’s pace. If the buyer assumes the service manager can cover the route, test whether that leaves dispatch, supervision or sales uncovered. The best staffing forecast shows which people can actually perform each job at the same time.
Ask the operations manager to review a low-demand period as well as peak weeks. A strong summer can obscure underused capacity in spring, while a quiet month may reflect scheduled training or station coverage for commercial contracts. Compare like periods and explain exceptional weather, major projects, employee absences and the mix of work.
How should the seller use the roster in employee discussions?
Keep sale diligence separate from performance management. A single average ticket or utilization figure can reflect pricing policy, dispatch choices, job type and recordkeeping, in addition to the employee’s work. Review the underlying service outcomes with managers before drawing personnel conclusions. If a figure is incomplete or an employee changed roles, state that plainly.
Use the verified schedule to identify skills coverage, training priorities and succession needs. Protect confidentiality when preparing retention plans or arranging buyer interviews. The incoming owner should receive enough evidence to assess staffing capacity and training needs while respecting the stage of the transaction and the rules governing employment records. A useful roster supports a specific operating decision, such as who can supervise the next installation crew or cover an absence during peak season.
How would you apply this to your shop?
Illustrative composite — not a real client. A service technician works five days, receives 40 paid hours, records 28 billed hours and completes 16 jobs generating $8,000 of net revenue. The row produces 70% billed utilization, $1,600 revenue per day and a $500 average ticket. With two recorded callbacks against that group, the callback share is 12.5%.
Before interpreting the result, check when those callbacks occurred and whether they related to work the same technician actually performed. A tech assigned to repair someone else’s work can look worse even when they resolved the quality problem. Your attribution rule determines what the measure answers.
Check where maintenance-plan fees were recognized. A technician can complete valuable prepaid work while recording a zero-dollar customer invoice that day. Compare the technician’s assignments and the shop’s revenue recognition before using revenue per day in a retention or compensation conversation.
Where can you go next?
What else should you know?
What if two technicians share an installation?
Agree on an attribution rule before you analyze the roster. You might track the job at the crew level or allocate revenue under a documented method. Either way, reconcile the combined attributed amount to the single invoice so one completed installation never creates two full tickets.
Why might billed utilization exceed 100 percent?
Some systems assign a standard number of billed hours to a flat-rate task. A technician who finishes efficiently can receive more standard hours than clock hours. Verify how the company records travel, overtime and training before deciding whether the result reflects a data problem or the pricing system.
Should a warranty callback appear as a separate sale?
Record the callback workload and any actual billed amount according to your definitions. Check whether a repair was a separate repair or a return to correct an earlier job. Giving a free callback the same sales treatment as a new paid service call can distort average ticket.
Can I share technician names in early diligence?
Start with stable anonymized codes when the review only needs roles, production and credential coverage. Keep any authorized personnel detail in your controlled diligence process. Use the codes consistently so a buyer can compare cohorts or ask follow-up questions without receiving personal contact details too early.
Which sources informed this page?
- Section 608 Technician Certification · U.S. Environmental Protection Agency, November 21, 2026
- Recordkeeping · Internal Revenue Service, November 21, 2026