How do I deal with callbacks and warranty jobs without losing money?

Log every callback as its own job record linked to the original, with separate time and materials. Separate genuine warranty defects from new scope the customer folds in, in writing, before you return to site. Consumer guarantees apply automatically: services must be performed with due care and skill, be fit for purpose, and be completed within a reasonable time. These run alongside state statutory warranty periods. The margin loss comes from untracked scope creep around them, not the warranty fix itself.

Updated 05/09/2026

What are my actual warranty obligations as a tradie?

Every trade service in Australia carries two layers of obligation that you cannot contract out of, no matter what your terms and conditions say.

The first layer is the Australian Consumer Law (ACL) consumer guarantees. These are federal, apply to every trade in every state, and say your work must be done with due care and skill, be fit for the purpose the customer made known to you, and be completed within a reasonable time. As the ACCC states: If a service fails to meet a consumer guarantee, consumers have the right to a remedy from the supplier of the service.

The second layer is state-specific. For residential building work, statutory warranty periods for residential building work are typically 6 years for major (structural) defects and 2 years for non-structural defects from completion. These periods vary by state:

If you do maintenance-only or non-residential work, the state statutory warranty may not apply directly, but the ACL consumer guarantees still do. Either way, a genuine defect in your workmanship within these periods is yours to fix.

Why do callbacks eat into margins so badly?

The rectification itself is rarely the margin killer. What hurts is everything around it:

• Unlogged time. Most tradies do not track callback hours separately. The travel, the inspection, the fix, and the customer conversation absorb half a day, and none of it shows up against the original job's profitability. If you are not tracking profitability per job, callbacks vanish into overhead.
• Scope creep on site. The customer reports a dripping tap you installed. You arrive, fix the tap, and then they ask you to look at the shower head, adjust the hot water, and check a different tap in the laundry. You do it because you are already there. None of it was in the original scope, none of it is a warranty item, and none of it gets invoiced.
• No root-cause data. Without a log linking callbacks to the original job, trade, site, and cause, you cannot see patterns. You might have a supplier whose fittings fail at twice the rate of another, or a subcontractor whose installs generate three times the callbacks. Without data, you cannot fix the upstream cause.

The fix for all three is the same: treat every callback as a real job with its own record.

How should I log callbacks in my job management system?

Create a separate job record for every callback. Link it to the original job (most job management apps like ServiceM8, Tradify, simPRO, and Fergus let you link related jobs or use a reference field). On each callback record, capture:

• Original job number and completion date.
• Reported issue. What the customer described, ideally in their own words via text or email.
• Inspection finding. What you actually found on site, with photos.
• Cause classification. Was it a workmanship defect, a material failure, normal wear, customer misuse, or new scope?
• Time and materials used for the rectification.
• Outcome. Fixed under warranty, quoted as new work, or referred elsewhere.

Run a monthly filter on callback jobs. You want to know: total callback hours, total callback cost as a percentage of revenue, callbacks by trade or service type, and callbacks by original installer (if you run a crew). This is the data that turns callbacks from a vague cost into a manageable line item.

How do I separate a genuine defect from new scope?

This is where most money leaks. The customer calls about a problem. You go back. On site, they raise three more things. You fix them all because saying no feels awkward, and you leave having done an hour of free work that was never part of the original job.

The boundary is clearer than it feels in the moment:

• Genuine defect. Something you installed or built has failed in a way that falls below the standard of due care and skill, or is not fit for its stated purpose, within the warranty period. This is yours to fix at your cost.
• New scope. Anything the customer wants done that was not in the original contract, quote, or scope of work. This is new work. Quote it, get written acceptance, and log it as a separate job.

Before you return to site, get the reported issue in writing. A text message is enough. When you arrive, inspect only that issue first. If the customer raises anything else, say plainly: "That is outside the original job. I can quote that separately for you." Then follow up with a written quote. Most customers accept this boundary if you set it clearly and early. For more on quoting scope cleanly, see our quoting tips guide.

What records protect me if a callback becomes a dispute?

If a customer takes a warranty claim to a tribunal (NCAT in NSW, VCAT in VIC, QCAT in QLD), the outcome almost always turns on documentation. The records that matter most:

• Written scope or contract. What was agreed, what was included, and what was excluded. A signed quote with itemised scope is the minimum.
• Before and after photos. Timestamped photos of the completed work at handover. These are your evidence that the work was done to standard when you left.
• Completion sign-off. A signed record (physical or digital) from the customer confirming the work was completed and they were satisfied at handover. Most job management apps can capture this as a digital signature on site.
• Variation records. Any change to the original scope, agreed in writing before the varied work started. Verbal variations are the top source of payment and warranty disputes in construction.
• Callback inspection notes. What you found, photos of the issue, and your assessment of cause. If the issue is not a defect in your work, this is where you document why.

Keep these records for at least 7 years. That covers the longest statutory warranty period (6 years structural, plus a buffer) and your tax record obligations. A cloud-based job management system stores them automatically and makes retrieval straightforward if a dispute surfaces years later. If a customer refuses to pay after you have rectified, see our guide on what to do when a customer refuses to pay the final invoice.

How can I prevent callbacks in the first place?

You will never eliminate callbacks entirely, but you can reduce them and make the ones that happen cheaper to handle:

• Quality-check before you leave site. A 10-minute walkthrough and function test at completion catches most issues before the customer finds them. For plumbing, run every outlet and check every join. For electrical, test every circuit and switch. For building, check every door, window, and fixture.
• Photograph everything at completion. Especially concealed work (pipes in walls, wiring in ceilings, waterproofing membranes before tiling). These photos are your evidence if a problem surfaces months later.
• Use consistent materials from reliable suppliers. If your callback log shows a pattern of failures with a specific fitting, valve, or product, switch suppliers. The data from logging callbacks (step above) drives this decision.
• Brief the customer at handover. Walk them through what was done, how to use it, and what counts as normal maintenance versus something to call you about. A customer who understands their hot water system's pressure relief valve will not call you when it drips as designed.
• Offer a scheduled maintenance plan for high-value installs. A proactive check at 6 or 12 months catches small issues before they become warranty claims. It also keeps you in contact with the customer for future work and reduces the chance of a missed call when they need you next.

What if I cannot resolve the callback fairly?

Sometimes you and the customer will disagree on whether the issue is a genuine defect or not, on the standard of rectification, or on whether additional work is within scope. When that happens:

• Put your position in writing. State what you inspected, what you found, and why you believe the issue is (or is not) covered by your warranty obligations. Keep it factual and avoid personal language.
• Offer an independent inspection. Suggest a third-party licensed tradesperson or building inspector assess the work. This often resolves disputes before they escalate.
• Know your state tribunal. NCAT (NSW), VCAT (VIC), QCAT (QLD), SACAT (SA), SAT (WA). Filing fees are modest, you do not need a lawyer, and the process is designed for exactly this type of trade dispute. Under the ACL, a major failure in a service entitles the consumer to cancel the contract and obtain a refund, or to seek compensation for the drop in value below what was paid, but a minor failure gives you the right to rectify.

The distinction between major and minor failure matters. A major failure (the work is substantially unfit for purpose, or would not have been acquired by a reasonable consumer fully informed of the defect) gives the consumer the stronger remedy. A minor failure (the work can be rectified) gives you the right to fix it within a reasonable time. Document your rectification offer and timeline in writing.

What does a callback cost when you actually track it?

Most tradies underestimate callback costs because they do not separate them. When you start logging callback jobs with their own time and materials, a typical pattern emerges:

• Travel. An average suburban callback adds roughly 45 minutes to 1 hour of travel (round trip, assuming a 15 to 30 km radius), plus fuel, plus the opportunity cost of a job you could have been on.
• Inspection and diagnosis. Roughly 20 to 45 minutes on site before any fix starts.
• Rectification. The actual fix, which is often the shortest part.
• Admin. The phone call, the scheduling, the follow-up, roughly another 15 to 30 minutes.

Add those together and a single callback can absorb roughly 2 to 3 hours of productive time, even for a minor fix. At a typical sole-operator charge-out rate of around $80 to $120 per hour, that is roughly $160 to $360 in lost billable time per callback, before materials.

If you are running 2 to 3 callbacks a week without tracking them, that could add up to roughly $16,000 to $56,000 a year in unrecovered time (directional estimate based on typical sole-operator rates and suburban travel times). Logging callbacks does not eliminate that cost, but it makes it visible, and visible costs get managed. Taking a deposit before starting a job also reduces your exposure when callback costs surface later.

Ready to get callbacks under control?

The pattern is simple: log every callback as its own job, separate genuine defects from new scope in writing before you return to site, and review the data monthly. The statutory obligations are real, but the margin loss comes from the untracked scope creep around them, not the warranty fix itself.

If your current system makes this hard, or you want to see what automating callback tracking, completion sign-offs, and follow-up scheduling looks like for your trade, book a free 15-minute discovery call and we will walk through it.