Problem guide
Callbacks, rework and warranty work aren't tracked
Callbacks and warranty work go untracked because they are logged like new work, with nothing tying them to the original job, order, person or part. Software counts only what the person logging it marks: ServiceTitan's help center says recall jobs appear in its recall report only if they are properly marked as recalls. Ask one question at intake, link each return to the original work, record the cause, and review the pattern monthly.

How it actually happens
Here is a typical sequence at a service contractor. A crew replaces a rooftop unit on a small office building in the spring. In early summer the tenant calls about warm air. The call taker searches the customer, sees an open slot, and books a standard service call. Nothing on the screen asks whether this is the unit the company installed a few months ago, and she has three other lines ringing.
A different technician goes out. He finds a loose connection at the disconnect from the installation, tightens it, confirms the unit is cooling, and closes the job. He knows exactly what happened. Whether that knowledge reaches anyone depends on what he types in the summary, and on whether anyone reads it.
The job goes through billing like any other. The office invoices it at the normal rate. The building manager calls back annoyed, because the unit is brand new. The office credits the invoice. In the books there is now a service invoice and a credit memo, and nothing that says recall. If the company exports to QuickBooks Desktop from ServiceTitan, the job type never travels with it anyway.
Nobody tells the install crew. Their lead has no idea one of his connections came loose, so he has no reason to change how he terminates. Two months later the same building calls about the same unit, and the cycle starts over with a different call taker.
Run the same story with the recall booked properly and the pieces line up. The call taker marks it as a recall and picks the installation job. The return visit is no charge from the start. The technician records the cause as workmanship and names the original crew. The service manager sees it in the monthly recall list, and the lead hears about it while the job is still fresh.
The pattern holds outside the trades. A brand ships a replacement for a defective item as a fresh order. A manufacturer accepts a warranty return without tying it to the production run. A kitchen remakes a dish and the comp shows only as a discount. Each time the return is handled, and each time the record says nothing about why.
The difference between the two versions is one decision, made in a few seconds by the person taking the request, usually without the information to make it. Every later step, the report, the credit, the conversation with the team and the warranty claim, depends on that moment.
Why the link matters more than the count
A callback count tells you how often you redo work. The link to the original work tells you why: which team, which equipment or product, which part, which step. Only the link lets you separate your own workmanship from a supplier's failed part, and only the second kind can be claimed back. On federal construction it also tells you when your warranty ends, because each repair restarts its own year.
Signs you have this problem
- Nobody can say how many callbacks or warranty returns the business had last month without building a spreadsheet
- Return work is logged as ordinary new work, then billed, disputed and credited
- The same customer, site, unit or product keeps coming back with the same problem
- The person or team that did the original work never hears that it came back
- Warranty end dates live in a notes field, a binder or someone's memory
What usually causes it
- The person logging the request does not know it is a return, or has no quick way to mark and link itThe handoff gap
- Each return is handled as a one-off, so the cause found never becomes a record anyone can sortThe exception swamp
- Returns sit mixed in with ordinary work, so the pattern by team, product and part stays hiddenThe invisible queue
- Whoever handles the return learns whether it was workmanship or a failed part, and that finding never reaches the officeThe field-to-office split
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Does the person taking requests lack a quick way, or a habit, of marking a return?If yes: callbacks are lost at the first handoff. Add the one question and a recall or warranty type.
- Is the callback count in your software lower than your team's own sense of how often they redo work?If yes: returns are being logged as new work. Run the 90-day match below to find out how many.
- Are warranty end dates kept in notes, binders or not at all?If yes: nobody can tell at intake whether the return is covered. Store the start date and term as fields.
- Are returns closed with no cause recorded?If yes: you are counting callbacks but cannot fix them. Add the three-way cause on the return.
- Are failed parts replaced under warranty without a claim to the manufacturer or supplier?If yes: the cost of the part is landing on you. Match every warranty part to a claim each month.
How it breaks in each industry
- Residential HVAC and plumbing service
- The customer calls the same number as for any repair, and the call taker decides in seconds whether it is new work. ServiceTitan's contractor playbook describes the common industry definition as errors or omissions within 30 days of a service call or within one year of an installation, but every shop sets its own.
- Commercial HVAC and refrigeration
- Equipment is the unit of record: model, serial, install date and the manufacturer's warranty terms. A return trip may be the contractor's workmanship or the manufacturer's part, and only the technician on site can tell which. A poster on r/HVAC in May 2025 asked specifically for software that lets the field add equipment with its age and warranties.
- General contractors and construction trades
- Warranty items surface after turnover, often from the owner's facilities staff, and run through the project team rather than dispatch. On federal fixed-price construction with the warranty clause, every repair starts its own one-year warranty, so the date of each fix matters.
- E-commerce and consumer brands
- A customer writes in about a defective item and gets a replacement order or a refund. The replacement is a new order, the refund is a payment record, and the reason sits in a support ticket. Unless someone links the three to the original order and product, a bad batch looks like ordinary returns.
- Specialty manufacturing
- A customer sends parts back under warranty. The return authorization, the inspection finding and the original production run live in different places, so the question that matters, which run, machine or material caused it, gets answered by memory if at all.
Where it breaks between systems
- ServiceTitan recall reporting
- Recall counts by technician come from the Technician Performance report with a Recall Jobs column, or from the Recall % report. ServiceTitan notes that recall jobs show in the report only if they are properly marked as recalls. A return trip booked as an ordinary job is invisible to both.[1]
- ServiceTitan recall and warranty booking
- The call taker clicks Recall or Warranty, selects the job that caused it, and the new job is linked to the original automatically. Recall and warranty jobs are No Charge and Non-Convertible, and recalls do not affect technician conversion rates.[2]
- ServiceTitan recall from an existing job
- Only a job already marked completed can be recalled. When a recall or warranty job is booked from the previous job's page, required custom fields and pre-filled job summaries do not carry over, so the context from the first visit has to be re-entered.[3]
- ServiceTitan booking guides
- Each shop writes its own recall and warranty policy as guidance text the call taker reads, such as 30 days for service and 90 days for installations, which is ServiceTitan's example rather than a default. The page does not describe the software flagging a call that falls inside the window.[4]
- ServiceTitan and QuickBooks Desktop
- Job Type and Job Summary do not export to QuickBooks Desktop, and net-negative invoices export as credit memos. A job typed as a recall arrives in the books with nothing marking it as one.[5]
- Housecall Pro Property Profile
- The documented fields on an equipment item are item type, display name, make, model, serial number, install date and notes; no warranty term or expiry field is listed. The option to add an item on a job appears only when the job's service address is already on the customer profile.[7]
- Procore Observations (warranty type)
- Procore's default Warranty observation type covers a vendor coming to site to service or replace equipment under that equipment's warranty. It is built around the manufacturer or supplier returning, not the contractor's own workmanship callback.[8]
- Procore Observations (custom types)
- The grey default categories, including Warranty, cannot be edited, and a type already assigned to an observation cannot be edited either. A company that wants workmanship and manufacturer items kept apart adds its own types under the category before the first one is logged.[9]
By the numbers
| Figure | What it measures |
|---|---|
| 1% to 2% of sales[10] | Annual hard cost of callbacks reported by an informal survey of large builders who track them, in Builder magazine's 'Callbacks Revisited', April 5, 2002. Production home builders, not service contractors; the survey's size is not stated. |
| About $500 per home[10] | Typical soft cost to administer warranty work, from the same 2002 informal survey of large production home builders. |
| Under 10 days[10] | Consultants' target for a production builder's average completion time on a warranty call, in the same 2002 article, which adds that big builders often averaged more than 30 days. A target, not a measured average. |
Rules that apply
- 48 CFR 52.246-21(b) and (d), Warranty of Construction[11]
- On federal fixed-price construction contracts that include the clause, the contractor warrants the work for one year from final acceptance, and work repaired or replaced under the warranty carries its own one-year warranty from the date of the repair. Without the original job, the repair and their dates linked, nobody can say when each warranty ends.
- 48 CFR 52.246-21(e) and (g), notice and pass-through warranties[11]
- The contracting officer notifies the contractor in writing within a reasonable time after discovering a defect, and the contractor must obtain the warranties normal in commercial practice and, if directed, enforce them for the government. Manufacturer claims become part of the contractor's job.
Measure it in your own shop
From: Ninety days of completed work from the system you run it in, with customer, location or order, equipment or product, the person who did it, work type, completion date and invoice amount.
- Export the 90 days of completed work and sort it by customer or location, then by date.
- Flag every customer or location with a second visit or order inside your callback window for the same equipment, product or complaint.
- For each flagged pair, check whether the second one was logged as a recall or warranty item and linked to the first.
- Count the unlinked pairs. For all pairs, total the labor and parts on the return and what was invoiced, and tally the cause and the original person or team where you can tell.
Reading it: The unlinked share is how far your recall report undercounts. The labor and parts on returns, against what was invoiced, is the cost you are absorbing. Repeats by product, equipment type or team show where to fix first.
What does not fix it
- Switching on the recall feature
- It counts only the work someone marks. If the person taking requests logs a return as new work, the report stays clean and wrong.
- Tying callbacks to pay before tracking is reliable
- It gives everyone a reason to log returns as new work. Get honest marking first, then decide what to do with the numbers.
- Billing the return and crediting it if the customer complains
- It turns your own warranty into a billing dispute, and the credit memo in accounting says nothing about why the return happened.
What to try this week
- Write your callback window downDecide what counts as a return for your business, for example within 30 days of a repair, within a year of an installation, or within the warranty period on a product, and put it on the screen or sheet in front of whoever takes requests.
- Ask one question at intakeHave we worked on this problem, this equipment or this order recently? If yes, log it as a recall or warranty item tied to the original work, not as a new request.
- Record the cause on the returnBefore the return is closed, record one of three causes: our workmanship, a failed part or product, or something else. Name the original person or team and the part, if any.
- Keep warranty end dates as dataFor every installation or product sold under warranty, store the start date and the warranty term as fields on the equipment, product or customer record, not in free-text notes, so whoever takes the next request can see whether it is still covered.
- Review monthly, then close the loopOnce a month, sort the returns by team, product or equipment type, and cause. Tell the original team what came back and what was found, as a normal conversation rather than a penalty.
- Match warranty parts to supplier claimsFor every failed part or product replaced under warranty, check that a claim went to the manufacturer or supplier, and list the ones that did not.
Where do-it-yourself stops
These steps start a record and surface the obvious repeats. They still depend on someone asking the question and marking the work every time, and the link between the return, the original team, the part and the claim lives in several places. The lasting fix is a tool built around your intake, your work records and your equipment or product data, so a return is recognized when it is logged and the pattern shows without anyone building a spreadsheet. That is what a Workflow Spec designs.
Questions people ask
What counts as a callback?
Define it for your company. ServiceTitan's contractor playbook describes the common definition as errors or omissions within 30 days of a service call or within a year of an installation. Write your window down and show it to whoever books calls.
Why doesn't our software show our callbacks?
Because it counts only jobs that were booked as recalls or warranty work. ServiceTitan's own help center notes that recall jobs show in its report only when properly marked. A return trip booked as a normal call never appears.
Should we charge for a callback?
If it falls inside your workmanship warranty, no, and in ServiceTitan recall and warranty jobs are set to no charge automatically. Charging first and crediting later turns warranty work into billing disputes.
How long is the warranty on a repair?
On private work, whatever your contract or policy says. On federal fixed-price construction with the warranty of construction clause, the original work is warranted for one year from acceptance, and each repair carries its own one-year warranty from the repair date.
What do untracked callbacks cost?
The only published industry figures found are old and from production home building: a 2002 Builder magazine article put callback hard cost at 1 to 2 percent of sales for large builders. For your own shop, count the labor and parts on 90 days of return visits.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
