What is average ticket in home services?

Average ticket is the revenue for a defined group of jobs divided by the number of jobs in that group. It describes average job value, not profit or customer satisfaction. For a useful home-service review, keep the revenue basis, job status, period and treatment of credits consistent in both inputs.

Start by deciding whether the measure describes completed jobs, scheduled jobs or another clearly named group. For an operating review of delivered service, completed jobs can be a useful basis. Match their revenue and count rather than dividing all-period revenue by whichever job total is easiest to obtain.

Decide how to handle cancelled work, zero-value callbacks, discounts, credits and jobs that span several days. A single roof replacement with several visits is different from several independent repair jobs. Use stable job identifiers and a written policy so the count does not change according to who prepares the review.

The service business KPI guide explains how this measure fits among other operating numbers. Keep the definition beside the result. If you report a scheduled average as a planning measure, label it as scheduled. It should not quietly become the completed-work average when the team discusses performance or job economics.

Suppose a hypothetical plumbing crew completes ten selected jobs with total revenue of $5,000. Average ticket is $5,000 divided by ten, or $500. That does not mean each job billed $500. Some may be small repairs and others larger projects.

Now suppose a $500 credit belongs to that same selected work under your revenue policy. Net revenue becomes $4,500 and the average becomes $450 if the ten-job count stays the same. The change reflects a revenue adjustment, not necessarily a change in the services delivered. Explain material credits so readers can understand why the average moved.

If the selected group contains no jobs, the ratio is undefined. Do not present zero as if it were an observed average ticket. Check the period and filters, then report that there were no qualifying jobs. Also avoid averaging weekly averages without considering job counts. Add the selected revenue and jobs across weeks, then divide the totals to get the combined result.

Average ticket often moves because the mix of services changes. An electrical team doing more panel replacements will have a different average from a team doing mostly short repairs. A cleaning business adding occasional deep cleans may see a higher average without changing the price of recurring visits.

Compare meaningful service categories and inspect job count alongside the average. For a hypothetical illustration, ten jobs at a $500 average produce $5,000 revenue. Five jobs at an $800 average produce $4,000. The higher ticket does not compensate for the lower count in that example. Neither result says anything about cost until those inputs are reviewed.

Use the technician performance guide to frame individual comparisons carefully. Assignments, helpers, available time and customer needs affect ticket value. A technician should not be encouraged to add unnecessary work to reach an average. The useful question is whether the agreed scope was understood, priced and delivered appropriately for that category of job.

When average ticket changes, inspect a small set of jobs behind the movement. Look for a shift in service mix, discounting, credits, incomplete work or a difference in how multi-visit jobs were counted. Start with the records rather than assuming the team sold more or less effectively.

Then connect the finding to a decision. If scope is consistently underestimated, improve the estimate handoff. If the business is receiving more small jobs, review capacity and contribution before deciding whether that mix fits the plan. A higher revenue figure can still come with higher materials or labor costs, so average ticket should sit beside a defined profitability review.

Treat average ticket as a calculation you make from appropriately selected revenue and job counts. The approved ServicePro IQ facts establish report and job-list details; they do not establish a dedicated average-ticket metric. Keep that distinction clear when using report information in your own analysis. Record the date range and counting policy so the next comparison measures the same thing.

ServicePro IQ adds business reports built from your Housecall Pro data. The Revenue page shows total and year-to-date revenue, a running-total line against the revenue goal, revenue by lead source, the job list and cancellations. Those details give you records to review alongside your own operating calculations.

Reports can be filtered by date range, by day, week, month or year, and by tag, tag combination, lead source and employee. Filters stay in place as you move between report pages. Use the same period and selection when comparing related figures. A report filter does not by itself establish that two groups performed equivalent work.

The Housecall Pro integration requires a Housecall Pro MAX account. ServicePro IQ reads your data without changing anything in Housecall Pro. Job and revenue figures refresh once an hour, at 20 minutes past the hour. After connection, your contact lets you know when reports are ready. See pricing and start the free 7-day trial with a specific set of jobs you want to understand.