October in the Texas Hill Country is a strange month for an HVAC shop. Afternoons around Boerne and Kerrville can still call for cooling, and the first cool mornings send homeowners to the thermostat to switch on heat for the first time since spring. That first startup is a real test. Systems your crews installed, repaired, or tuned up during a long summer now have to run a different way.
Some of those jobs come back. A part fails early. An install detail gets missed. A diagnosis does not hold once the weather changes. The customer calls, a truck rolls, and the second visit usually goes out at no charge. That is often the right call. The mistake is letting the cost of that trip vanish inside the books.
Why fall brings callbacks forward
ENERGY STAR recommends a heating system check up in the fall, because contractors get busy once winter arrives. That advice lines up with how a residential service calendar actually fills: tune ups, first heat calls, and the occasional system that ran fine all summer and struggles on its first cold morning.
For the shop, that means callbacks tend to show up right as the schedule gets tight. A return trip in a slow week is an annoyance. A return trip in the first heating rush pushes out a paying call.
What a callback really costs
Trade coverage of callbacks keeps returning to the same advice. ACHR News business writing has encouraged contractors to keep accurate records of every callback, run the callback percentage against all calls, and figure what each one costs in labor and materials. Contractors quoted in ACHR News also describe breaking callbacks down by cause, such as equipment failure or installation error, and by technician.
In plain books terms, a callback usually carries a tech’s paid hours including drive time, fuel and wear on the truck, replacement parts or materials, dispatch and office time to schedule and close it, and the paying ticket that could have used that slot. The first four are real, recordable costs. The last one never shows up on a P&L at all, which is exactly why the recordable costs deserve a clean line.
An illustrative callback example
Here is a round, hypothetical example. The numbers are made up for teaching, not an industry benchmark.
Picture a residential shop in Kerrville that runs 400 service and repair calls in October. Sixteen of them come back as callbacks, so the callback rate for the month is 4 percent. Each return trip takes about two and a half hours of a tech’s paid time once you count the drive out Highway 16 and back. At $40 an hour for wages and payroll costs, that is $100 of labor. Add $60 in parts, $25 for fuel and truck wear, and $15 of office time to schedule and close the ticket. Each callback costs roughly $200.
Sixteen callbacks at $200 each is $3,200 for the month, and none of it appears on an invoice. If the costs land in general payroll and supplies, it hides there too. Now tie one of them back to its original job. Say the first visit was a $1,000 repair that looked like it earned $400 of gross margin. After a $200 callback, that job really earned $200. Half the margin went back out the door on the second trip.
And the forty hours of tech time those sixteen trips used could have been several paying calls in a busy heating week. That part never posts to the books.
Where the cost hides in the books
In a lot of small shop books, a no charge callback leaves almost no footprint. The tech’s hours roll into general payroll. The part comes off truck stock or gets bought on a supply house account coded to general supplies. The invoice total is zero, so the field software may not even push the ticket into the accounting file.
Two problems follow. First, the original job keeps a margin it did not fully earn, because the cost of finishing it landed somewhere else. Second, the owner cannot tell whether callbacks are rare noise or a pattern tied to one equipment line, one crew, or one kind of diagnosis.
A simple callback habit for Kerrville shops
You do not need new software to start. You need a consistent tag and a consistent place for the cost to land. Flag the ticket as a callback at dispatch. Link it to the original job, customer, and tech. Cost the labor and parts to that callback even when the invoice is zero.
If you work in QuickBooks Online Plus or Advanced, projects let you assign bills, expenses, and timesheets to a customer or project so income and cost sit together. A callback can ride on the original job or on a dedicated callback class. Pick one method and stick with it.
Two edge cases keep the data honest. If a manufacturer covers a part or pays a labor allowance, record that credit against the same callback so the net cost is real. If the customer pays for the second visit because it was a genuinely new problem, it is not a callback. Tag it as regular service so the count stays clean.
A callback tagging checklist
Before the first real cold front, make sure each of these is true:
- Every callback ticket carries the same tag, spelled the same way, every time.
- Each callback links back to the original job, customer, and technician.
- Labor hours, including drive time, are costed to the callback even when the invoice is zero.
- Parts pulled from truck stock are recorded against the callback, not buried in general supplies.
- A cause is recorded for each one: part failure, install, or diagnosis.
What to read each month
Once the tags are consistent, a monthly review takes minutes. Look at callbacks as a share of total calls. Look at total callback cost for the month. Sort by cause: part failure, install, or diagnosis. Then ask whether the original jobs still earned the margin you celebrated.
Keep the tone practical. The goal is a clear picture for pricing, training, and scheduling, not a blame board. A shop running a handful of trucks between Fredericksburg, Comfort, and Boerne can learn a lot from one heating season of clean callback data.
What to do this week
Start before the next first heat call lands. Pick one tag name. Tell dispatch and the techs what counts as a callback. Decide where callback costs ride, and write that down.
Then pull September’s zero dollar tickets and see how many were really return trips. Even a rough count gives you a starting line for the heating season. As a bonus, the IRS reminds owners to keep records that support the expenses they report, and tagged callback costs are exactly that kind of record.
Before the first heat call
Books literacy only. Not tax advice. Give the callback its own line.
Sources
ENERGY STAR: Maintenance Checklist (schedule heating check ups in the fall): https://www.energystar.gov/saveathome/heating-cooling/maintenance-checklist
ACHR News: You’ve Fixed the Problem, Now Fix the Fixer (callback rate against all calls; labor and materials cost per callback): https://www.achrnews.com/blogs/17-opinions/post/97647-you-ve-fixed-the-problem-now-fix-the-fixer
ACHR News: Coping With Callbacks (tracking callbacks by cause and by technician): https://www.achrnews.com/articles/92608-coping-with-callbacks
Intuit QuickBooks help: Add new transactions to a project in QuickBooks Online: https://quickbooks.intuit.com/learn-support/en-us/help-article/time-tracking/add-new-transactions-project-quickbooks-online/L7X1nx6J1_US_en_US
Intuit QuickBooks help: Track hourly labor costs and profitability by project in QuickBooks Online: https://quickbooks.intuit.com/learn-support/en-us/help-article/regular-payroll/track-hourly-labor-costs-profitability-project/L9ZxBA4sn_US_en_US
IRS: What kind of records should I keep (records that support business expenses): https://www.irs.gov/businesses/small-businesses-self-employed/what-kind-of-records-should-i-keep
