Average ticket

What amount and job population define the average?

Average ticket is a ratio, so the population matters as much as the amount. Define the revenue being divided and the jobs being counted. The result makes sense when both sides use the same rules, dates, and records.

A report could describe all specified completed jobs, a selected opportunity population, or another defined set. Those measures can answer different questions. The same report label does not mean both reports count the same jobs. Check how each figure was worked out.

ServiceTitan's KPI guide distinguishes opportunity-job and total-job averages under its vendor definitions. This guide adopts no numerical target from that document. Its purpose is to show how a population difference can change the calculation.

The operations hub connects the definition with broader operating review. The pricing and dispatch data guide addresses the records and controls behind the reports. Here, a paired-population worksheet makes the ratio reproducible.

How can identical work produce two different averages?

Take six made-up completed jobs for a simple example. Their net invoice amounts are $0, $0, $200, $400, $600, and $1,000. This first example has no other invoices, credits, or changes. It shows the arithmetic; it does not describe a real company.

Total revenue is $2,200. Dividing that amount by all six completed jobs produces an average of approximately $366.67. Now assume a separate analytical rule selects only the four positive-dollar jobs for an opportunity-style comparison. Their total is still $2,200, but the denominator is four, producing $550.

The second result is fifty percent higher because fewer jobs enter the count. No customer paid more. No extra work took place. These are made-up figures. They are not a plumbing benchmark or a claim about the exact rules used by any software provider.

The positive-dollar rule is an assumption for this worksheet. A real report may use other rules for completed work, sold thresholds, or jobs that qualify. Check the report settings. Do not assume a provider always defines an opportunity as a job with a positive dollar amount.

The revenue per technician definition provides another denominator example. Different averages should prompt a population review before they become a conclusion about staff productivity or operating improvement.

Which current report settings need inspection?

ServiceTitan's dashboard business metrics documentation describes opportunity rules, invoice mapping, and date filters. It provides evidence of a vendor calculation, not a mandatory definition for every plumbing company or acquisition agreement.

Record which jobs meet the report's eligibility rule. Check completed status, threshold settings, job categories, and excluded work. If the setting changed between periods, retain the change date and calculate a compatible comparison where the records permit it.

Identify the revenue field. A gross quote, invoice subtotal, net invoice amount, and collected payment are different quantities. State how discounts, tax-related fields, adjustments, and non-job invoices are treated under the selected calculation rather than assuming the visible dashboard total is self-explanatory.

Inspect multiple invoices for one job and one invoice connected to multiple activities. The denominator should count its defined unit consistently. A duplicated export row can inflate job count or revenue without indicating any change in the business.

Check job assignment and attribution separately. The same work can appear in company, team, or technician reports under different rules. An average calculated from an individual report should not be assumed to reconcile directly to a company average without understanding that mapping.

How should credits and reporting dates be handled?

Choose which date the report will use and show how later changes are handled. A job can finish on one date, be invoiced on another, and be paid later still. Explain which date puts it in the job count. Show how a later credit changes the revenue being divided.

The IRS's Publication 583 supports retaining underlying receipts and business records. Use invoices and adjustment records to reproduce the amounts. The recordkeeping guidance does not prescribe an average ticket formula or tell a buyer which work should count as an opportunity.

Return to the hypothetical six-job example. Assume a $100 credit reduces job F's net amount from $1,000 to $900, with all other facts and both populations unchanged. Total defined revenue becomes $2,100.

The all-job average is then $350, and the four-job average is $525. Those changes follow from the credit, rather than a change in eligibility or job count. If the actual report applies credits by another date or rule, state that difference before comparing the results.

Do not count a credit as both reduced revenue and a separate reduction in the same numerator. Reconcile the adjustment once. Preserve the original invoice, the credit record, and the reporting treatment so the calculation can be reviewed.

What operating conclusions can the average support?

The average can describe the selected job population's revenue per job. It does not establish profit, cost efficiency, quality, or customer satisfaction. Review labor, materials, travel, callbacks, and other relevant costs before treating a ticket change as improved economics.

Job mix can alter the result. More larger installations and fewer small repairs can increase an average while changing the labor and materials required. Compare consistent categories when investigating price changes, and keep the combined figure alongside the segment view.

Booking success is a separate stage. The call-booking rate definition distinguishes calls, eligible leads, bookings, completions, and payments. A high ticket among completed jobs cannot show how many eligible inquiries never became work.

The marketing cost guide connects those stages to spending and collections. A campaign may generate larger completed jobs while also requiring more marketing cost. Average ticket alone cannot establish the campaign's contribution to profit.

For a buyer, the useful question is what explains the result and whether the same work, pricing, capacity, and report rules can continue. This definition supplies no universal ticket target or acquisition premium. Use the company evidence and proposed operating plan.

How do buyers, sellers and lenders use the figure?

A seller can use the worksheet to explain the work mix. Keep old and new report settings so a buyer can see whether larger jobs, new prices, or a different job count drove the result.

A buyer should test whether the staff, equipment, and demand can support that mix after closing. A higher average among completed jobs does not show how much work the company turned away or could not schedule. Follow the job records through to costs and payments.

A lender needs a wider cash and earnings review. Average ticket helps explain revenue; it does not prove debt can be paid. Show invoice and credit records beside the earnings model. The lender's own rules still apply.

Which common mistakes should the worksheet prevent?

Do not compare an opportunity average with an all-job average without showing both job counts. Do not drop zero-dollar work simply to improve the number. Do not count an invoice row as a separate job when two rows belong to the same job. These errors can change the result while the work stays the same.

Use this sequence to keep the worksheet reviewable:

1. State whether the measure covers completed jobs, opportunities, or another named set.
2. Export the job IDs and invoice amounts behind that set.
3. Apply the same threshold, status, and date rules to both periods.
4. Check credits, extra invoices, duplicate rows, and billing without a job.
5. Show the revenue and job count used in each average.
6. Explain the difference before making a pricing or staffing claim.

The glossary entry for average ticket gives the short definition. Keep the worksheet and records with the sale file so readers can check what changed.