Average ticket is total revenue from a specified group of HVAC jobs or invoices divided by the number of eligible jobs or invoices in that same group.
Which average should the buyer use?
Choose the measure that answers your question. A dispatcher planning service capacity may want revenue per completed visit, including callbacks and zero-dollar visits. A sales manager may want revenue per sold opportunity, excluding unsold estimates under a documented rule. A lender comparing historical earnings needs realized job revenue tied to the income statement. Calling all three numbers average ticket can create disagreement even when everybody used the software correctly.
Identify the event counted in the denominator. A customer may receive a diagnostic invoice, approve a repair that afternoon and pay a separate invoice after the part arrives. Is that one service job, two visits or two invoices? Recover the job, visit, invoice and payment identifiers before calculating an average. For a transaction comparison, include a bridge showing how the selected unit relates to completed work and cash.
Check whether the numerator includes sales tax, gratuities, rebates, financing fees or discounts. A customer invoice and a bank deposit can differ for several legitimate reasons. An instant equipment rebate may appear on the signed contract, while a card processing fee is deducted when the payment settles. Keep gross selling price, recognized revenue and net collection separate, and label the figure actually used.
Why separate service lines and job status?
A furnace replacement and a routine maintenance inspection have very different prices and cost structures. A blended average can rise because the shop completed more installations, even when the price charged on every individual service item remained unchanged. Divide results by service repair, maintenance, replacement installation, construction and other material lines. Then compare month-to-month movement within each group.
ServiceTitan’s public playbook presents field staff targets in defined operating categories. Its dashboard documentation distinguishes job averages and opportunity metrics, and its technician report discusses revenue assignment. These are helpful references for interpreting a configuration. Ask to see the seller’s report settings before comparing its apparent average with a software benchmark. A default sold threshold can exclude small jobs that legitimately contribute revenue.
What does a mix shift do to the arithmetic?
Illustrative composite — not a real client. A shop completes 240 repair jobs averaging $420 and ten installations averaging $9,000. Total revenue is $190,800 across 250 jobs, producing a blended ticket of $763.20. Next month it completes 220 repairs at the same price and twenty installations at the same price. Revenue rises to $272,400 across 240 jobs, producing a blended ticket of $1,135.
| Population | First month | Second month |
|---|---|---|
| Repair average | $420 | $420 |
| Installation average | $9,000 | $9,000 |
| Blended average | $763.20 | $1,135.00 |
| Number of completed jobs | 250 | 240 |
The blended ticket increased by almost 49% while neither department raised a price. A buyer forecasting a permanent improvement should ask whether the installation mix can continue and whether the branch has enough crews, equipment, leads and working capital. A few large jobs can also dominate a smaller shop’s monthly average. Examine the median and the number of jobs in several price bands before drawing conclusions.
How should callbacks and zero-dollar invoices be treated?
Show the business purpose of the measure. An operations view should capture time spent on callbacks because that work consumes capacity. A measure of revenue per paying repair can exclude a no-charge visit if the report clearly labels the exclusion. Publish the callback count, technician hours and direct cost alongside the paying-job average. A rising paying-job ticket can mask margin lost when the same technician returns twice.
Suppose one technician produces $18,000 from 40 paid repairs and handles ten zero-dollar follow-ups. The average paid repair is $450. Across 50 completed visits, the revenue per visit is $360. The gap tells you to examine return-trip causes, travel time and parts availability. It does not establish poor workmanship by itself. Some follow-ups are planned completions or warranty commitments the company knowingly priced into the original sale.
How do you reconcile the source data?
Export completed jobs, invoices, discounts, credits, voids and payments. Group invoices by the chosen job identifier, then compare the monthly totals to recognized revenue. Identify deposits for uncompleted work and credits posted after the original month. Test a sample across the smallest and largest invoices and inspect the original job records. A single commercial progress billing can distort a residential service report if the department coding is wrong.
If two technicians share a job, allocate the same total revenue using the agreed split for an individual scorecard. For the company average, count the underlying job only once. Ask whether a job that moved between branches is credited to both. Reconcile the branch totals to company revenue and explain any assignment retained for coaching that cannot be added across the organization.
How do price, volume and job mix each contribute to sales?
Hold two variables constant while you test the third. Begin with last year’s completed jobs by category and last year’s realized net price. Apply this year’s prices to the old mix to estimate the price effect. Then use the current category counts and prices to show the combined effect of volume and mix. Retain the underlying counts because different calculation orders can assign the interaction between changing prices and changing quantities differently.
Take a repair category with 200 jobs at $400 last year and 180 jobs at $450 this year. Revenue moves from $80,000 to $81,000. The ticket rose 12.5%, yet total revenue in that category grew only 1.25% because twenty fewer jobs closed. If each repair also took longer or required a more expensive part, contribution could have fallen. Use your actual job-cost records to decide what the new price accomplished.
Apply the same exercise to installations, maintenance and commercial work separately. A blended ticket tells you how many dollars the average job generated. It cannot tell you what part arose from changed pricing decisions unless you also know what the company sold and how often.
Why should you sample near the software’s sold threshold?
A software rule may exclude jobs below a set invoice amount from a sold-job average or a technician performance report. Review jobs just below and just above that threshold. A small pricebook increase can push many service visits into a different reporting group. Revenue may change little while the number of eligible invoices and the reported average change substantially.
Compare the dashboard with an independent calculation from all completed job identifiers. Apply the exact minimum charge, exclusions, department filters and credit policy, then see whether you can reproduce the displayed value. Repeat the process for a month before and after a price or software change. If your buyer cannot reconcile the pre-change month, avoid presenting a continuous history as though the definition remained constant.
Ask about manual job closeouts too. A technician might leave a repair ticket open until a part arrives and issue a zero-dollar callback invoice when the work is complete. A visit-based measure should reflect both trips. An invoice-based measure may reflect one charge. Preserve the identifiers so the underlying customer economics remain visible under either report.
How can you evaluate a proposed increase before adding it to earnings?
Select tasks representing a meaningful share of current completed work and compare the posted price with actual net invoices. Document discounts, member benefits, overrides, dealer finance fees and subsequent refunds. Use recent customer decisions to test whether higher prices affected conversion or the mix of tasks sold. A higher ticket on fewer completed repairs may support less contribution than the pricebook suggests.
For your buyer model, show three schedules: realized historical results, price changes verified on completed jobs and proposed changes yet to reach customers. When you know which dates and job categories support the numbers, you can estimate implementation timing and the training required. Keep any buyer-specific price increase separate so a bid does not attribute future actions to the seller’s historical earnings.
How should you use average ticket in a deal model?
Start your review with completed job volume by type, then apply the verified average for that job type. Estimate materials, labor, subcontract and financing costs separately. Build a second version using fewer higher-priced installations so you can see how a modest mix change alters cash needs. New equipment can require a supplier payment before the financing provider releases customer funds.
Use the technician productivity calculator and the field roster to connect job values to staffing. Check replacement conversion before assuming the shop can increase high-ticket sales at will. If an owner promises a price increase after closing, ask for a dated pricebook, examples of completed invoices and evidence that customers accept the new prices. A proposed increase belongs in a forecast until actual invoices establish the result.
Finally, compare gross profit per job and per paid hour. A $2,000 repair with a costly component may support less overhead than several smaller diagnostic jobs completed on one dense route. Your valuation case becomes more informative when it explains what each dollar of additional ticket size contributes after the company fulfils its promises.
Save the original invoice export and report settings alongside the summary delivered to the buyer. If the company later switches dispatch software or changes its sold threshold, rerun one historic month under both definitions. The resulting bridge can explain apparent improvement or deterioration without attributing a reporting change to technician performance. This matters especially when a seller’s remaining payout depends on achieving a revenue or margin target.
For your next monthly meeting, pull one discounted job, one callback and one unusually large installation. Can you find each in your numerator and denominator? If you can explain all three treatments to your service manager, your average is easier to reproduce.
Where can you go next?
What else should you know?
Should average ticket use invoices or collections?
Select the basis that matches the decision. Completed net invoice revenue is useful for job production, while settled collections help with a cash forecast. Show the bridge between the two when deposits, unpaid invoices, processing fees or refunds cause the totals to differ.
Why is the median ticket helpful?
The median identifies the middle job when invoices are ranked by value. It helps reveal whether a handful of unusually large installations are pulling the arithmetic average upward. Review the median, mean, job count and revenue share of the largest jobs in each service line.
Do maintenance visits count even when prepaid?
For a visit-based capacity measure, count the completed visit. For a revenue measure, assign earned revenue according to the company’s accounting policy without recording the same dues again. A zero-dollar field invoice may describe a prepaid entitlement rather than an unproductive or unpaid customer.
Can I use average ticket to compare two technicians?
First compare assigned job types, lead sources, territories, experience and rules for shared jobs. An installer and a maintenance technician have different opportunities. Look at contribution, callback cost and paid hours alongside the ticket amount before attributing differences to selling ability or field performance.
Which sources informed this page?
- Contractor Playbook, residential field staff KPIs · ServiceTitan, November 21, 2026
- Dashboard business metrics and denominator definitions · ServiceTitan, November 21, 2026
- Technician Dashboard revenue report · ServiceTitan, November 21, 2026
Where can you apply this definition?
- Will the HVAC consumer-financing programs survive your purchase?
- How to read an HVAC profit and loss statement before you buy
- Residential, commercial and new-construction HVAC buyers
- The end of the 25C tax credit and the shift to state rebates
- The technician shortage and HVAC company values
- How does your HVAC revenue mix affect earnings?
- What do your HVAC technicians produce per workday?