A cracked seam that shows up eight months after a resurfacing job is either a legitimate warranty claim or a dispute waiting to happen — and which one it becomes usually comes down to whether you have records. Paving companies handle plenty of documentation during a job: bids, material tickets, crew logs. Warranty and callback tracking after the job is done tends to fall through the cracks, literally and figuratively. This guide covers what belongs in a proper warranty and callback log, and how to stop losing money and reputation to claims you can't prove, disprove, or even remember.

Why Paving Companies Need a Dedicated Warranty and Callback Log

Asphalt and pavement work carries real warranty exposure. Workmanship warranties on paving jobs commonly run one to two years, and material or manufacturer warranties on things like sealcoating products or striping paint can extend further. Without a system to track what was promised, when, and to whom, a paving company is left relying on memory, scattered text threads, and whoever happened to answer the phone when the customer called.

That gap causes two very different problems. First, legitimate warranty issues get missed or mishandled, which damages the customer relationship and the referrals that come with it. Second — and more expensive — undocumented callbacks get treated as free warranty work when they're actually new damage, misuse, or a separate issue entirely outside the original scope.

What Fields Belong in a Digital Warranty and Callback Log

A usable warranty and callback log needs to answer five questions instantly: what was originally done, what's being claimed now, who's responsible for the fix, how long is the company on the hook for it, and what actually happened when someone showed up to look at it. That means each entry should capture the following core fields.

Job and Customer Information

• Original job number and address, tied directly to the job file
• Customer name and contact information
• Original contract or invoice reference
• Scope of original work (e.g., mill and overlay, sealcoating, striping, crack fill)

Warranty Terms

• Type of warranty (workmanship, material, or manufacturer-backed)
• Warranty start date (typically the completion or acceptance date)
• Warranty expiration date
• Specific exclusions noted in the original contract (e.g., damage from heavy vehicles, tree root intrusion, standing water)

Claim or Callback Details

• Date the issue was reported and by whom
• Description of the reported problem in the customer's or reporter's own words
• Before-and-after photos, time-stamped and tied to the specific location on the job
• Whether the issue falls inside or outside the stated warranty scope

Responsibility and Response

• Crew or subcontractor responsible for the original work
• Assigned team member or sub responsible for investigating the claim
• Date the site was inspected and findings from that inspection
• Response time from claim reported to site visit completed

Resolution and Closeout

• Determination: covered, denied, or partially covered, with the reasoning documented
• Repair date and description of work performed
• Cost of the repair and who absorbed it (company, subcontractor backcharge, or customer)
• Final sign-off, ideally with the customer's acknowledgment that the issue is resolved

Warranty Claim vs. Callback: What's the Difference?

These terms get used interchangeably, but they're not the same thing, and the distinction matters for how each entry gets handled. A warranty claim is a defect in the original work covered under the terms the company agreed to — a seam that separates prematurely, an area that didn't compact properly. A callback, more broadly, is any request for the crew to return to a site after the job was considered complete, which may or may not turn out to be a covered warranty issue once it's actually inspected.

Every callback should be logged the moment it comes in, before anyone determines whether it's covered. That single habit protects the company both ways: it prevents legitimate warranty work from getting lost, and it creates the documentation needed to push back on a callback that turns out to be unrelated to the original job — like damage from a delivery truck driving across a lot months after paving.

How to Track Warranty Claims by Crew and Subcontractor

A warranty and callback log becomes a quality control tool the moment you can filter it by crew or subcontractor rather than just by customer. If one crew or sub generates a disproportionate share of callbacks compared to the volume of work they've done, that's a pattern worth a direct conversation before it costs more in warranty labor than the job ever earned in profit. Without a structured log tying each claim back to who did the original work, that pattern stays invisible.

How Commander ERP Tracks Warranty and Callback Data

Commander ERP builds warranty and callback tracking directly into the same system that manages the original job, instead of treating it as a separate spreadsheet someone has to remember to update months later.

Warranty Records Tied to the Original Job File

Every warranty entry in Commander ERP links back to the original job — crew, materials, cost codes, and completion date — so there's no separate lookup required when a callback comes in eight months later.

Photo Documentation With Timestamps

Field crews can attach before-and-after photos directly to a warranty or callback record from a mobile device, creating a time-stamped record that holds up whether the claim is being approved or disputed.

Automatic Warranty Expiration Tracking

Commander ERP tracks warranty start and end dates per job, so office staff aren't manually calculating whether a claim that comes in fourteen months after completion still falls inside a one-year workmanship warranty.

Callback Trends by Crew and Subcontractor

Because every callback ties back to the original crew or sub, Commander ERP makes it possible to see patterns — which teams are generating repeat visits — instead of noticing it anecdotally after the fact.

Best Practices for Managing Paving Warranty Claims

• Log every callback the moment it's reported, before determining whether it's covered.
• Photograph the original completed work so there's a baseline to compare against later claims.
• Put warranty terms and exclusions in writing on every contract, not just verbally at the walkthrough.
• Respond to warranty claims promptly — a slow response is often what turns a minor issue into a dispute.
• Track resolution outcomes so you can spot crews or subs generating repeat callbacks.
• Get a signed closeout acknowledgment from the customer once a warranty repair is complete.

Frequently Asked Questions

How long should a paving company keep warranty records?

At minimum, records should be kept for the full length of the stated warranty period, though many paving companies retain them longer since disputes can sometimes surface after the formal warranty has technically expired.

Is every callback automatically a warranty claim?

No. A callback is any request to return to a completed job site; whether it's actually covered under warranty depends on inspection and the terms in the original contract. Logging every callback as it comes in — before determining coverage — protects the company either way.

What photos should be taken for warranty documentation?

At minimum, photos of the completed original work and photos of the reported issue at the time of the callback, ideally from a similar angle and location so the comparison is clear.

Can warranty tracking help identify problem subcontractors?

Yes. Logging warranty claims and callbacks by the crew or subcontractor responsible for the original work makes it possible to see which teams generate a disproportionate number of repeat visits.