Construction Warranty Tracking: Run Callbacks in a CRM
It is the third week of December. A homeowner calls the office about a sticking patio door on a project you turned over in the spring. The office manager writes it on a sticky note and walks it to the PM, who is closing out three other jobs before the holidays. The PM means to call the framing sub. Two weeks later the homeowner calls again, this time angrier, and nobody can say who was told what or when.
That is warranty work in most small contractor shops: phone calls, texts and buried emails. The work is usually minor. The problem is that nobody owns the list or knows when each project's correction period ends.
Construction warranty tracking does not need a new software category. If you already run leads and jobs through a CRM, the same tools that move a prospect from first call to signed contract can move a warranty request from intake to closed, with a paper trail you can stand behind. Here is how to set it up.
Table of Contents
Why Warranty Work Falls Apart After Closeout
During construction, everything has a log: RFIs, change orders, pay apps. After substantial completion the team moves on, and warranty requests arrive after that structure is gone.
The usual failure points
Intake is wherever the call lands. The PM's cell, the estimator's inbox, the front desk voicemail.
Nobody tracks the clock. The office rarely has a list of which projects are inside their correction period and when each one ends.
The sub hand-off is verbal. "I called the roofer" is not a record.
Closure is never confirmed. The sub says it is fixed. Nobody asks the owner.
Warranty contacts are treated as a cost. A satisfied owner at the 11-month mark is the warmest contact you have.
None of these are hard problems. They are visibility problems, and visibility is what a pipeline is built to give you.
The One-Year Correction Period, in Plain Terms
On projects using the AIA A201-2017 General Conditions, two different obligations get lumped together as "the warranty."
The warranty (Section 3.5)
Under Section 3.5.1, the contractor warrants that materials and equipment are of good quality and new unless the contract documents say otherwise, and that the work conforms to the contract documents and is free from defects. It excludes damage from abuse, unauthorized alterations, inadequate maintenance, improper operation and normal wear and tear. It does not carry a one-year time limit.
The correction period (Section 12.2.2.1)
This is where the familiar one year comes from. If work is found nonconforming within one year after Substantial Completion (or of a designated portion, or a later warranty start date), the contractor must correct it promptly after notice from the owner, who is expected to give notice promptly after discovering the condition. If the owner does not give notice and a chance to correct during that period, the owner waives the right to require correction and to claim breach of warranty for it.
Section 12.2.5 says the one-year period relates only to the obligation to correct. Owners can still bring claims later within the statute of limitations or repose, and Section 13.7 caps claims at no more than 10 years after Substantial Completion, subject to applicable law. Contracts and state law vary, so have counsel confirm what applies to you.
What this means for your CRM
A handful of dates matter: the Substantial Completion date, the end of the correction period, any special warranty dates for specific systems, and the date the owner gave notice of each item. Those belong in fields on the record, not in someone's memory.
Item | Correction period (A201 12.2.2.1) | Warranty (A201 3.5) |
|---|---|---|
What it covers | Duty to correct nonconforming work after owner notice | Quality of materials, conformance, freedom from defects |
Time frame | One year after Substantial Completion (or designated start) | No stated time limit; bounded by law and Section 13.7 |
Owner's role | Prompt notice and a chance to correct | Claim within applicable limitations or repose period |
What to track in the CRM | Start date, end date, notice date, response date | Closeout date, special warranties, all correspondence |
Building a Warranty Pipeline in Your CRM
In a CRM like GoHighLevel, a pipeline is a set of stages that opportunities move through from left to right, viewable as a Kanban board or a list. Won and Lost stages are added automatically. Build a separate pipeline just for warranty so it never mixes with sales.
Suggested warranty pipeline stages
Request Received - the intake form was submitted or the office logged a call.
Triage - PM or warranty coordinator reviews photos and decides: warranty item, maintenance item, or new work.
Assigned to Sub - the responsible subcontractor has been notified in writing.
Scheduled - a visit date is confirmed with the owner.
Corrected - Awaiting Owner Sign-Off - the sub reports the work complete.
Closed (use the Won stage) - the owner confirmed the fix.
Not Covered (use the Lost stage, with a reason) - abuse, maintenance, or outside scope.
Each stage should answer one question: whose move is it?
Fields worth adding
Project name and address
Substantial Completion date and correction period end date
Trade and responsible subcontractor
Date of owner notice (the date the request first came in)
Photos and documents, using a File Upload custom field (HighLevel lists a 250 MB per-file limit and supports PDFs, images and Office files)
Coverage decision and reason
The intake form
Give every owner one link at closeout: a short warranty request form. Ask for contact info, project address, location in the building, a description, photos, and the best times for access. Put the link in the closeout binder and the final invoice email. When every request comes through one door, each submission's timestamp becomes your notice record. The construction CRM implementation guide covers staging a rollout without overwhelming the office.
The Automations That Keep Requests Moving
A pipeline shows you where things stand. Workflows make sure things actually move. Each of these is built from a trigger and a few actions.
1. Intake to triage
Use the Form Submitted trigger, filtered to your warranty form. Actions: create or update the opportunity in the Request Received stage, send the owner an acknowledgment by email and text, and use Add Task to assign triage to the PM or warranty coordinator. Add Task sets an assignee and a due date, with an option to exclude weekends.
2. Assignment to the responsible sub
Use the Pipeline Stage Changed trigger, filtered to your warranty pipeline and the Assigned to Sub stage. Actions: send the sub an email with the photos and the owner's access notes, copy the PM, and log it on the record. The internal task stays with your coordinator; the written notice goes to the sub. If your subs respond better to text, the SMS for contractors guide covers consent and message practices.
3. Response-time reminders
Pick a response standard your contracts and reputation can support. HighLevel's Wait action can pause for a set period of time, until a specific date, or until conditions are met. A simple pattern: after assignment, wait a set number of days; if the opportunity is still in Assigned to Sub, create a follow-up task for the PM and send the sub a reminder.
4. Owner sign-off
When the stage changes to Corrected - Awaiting Owner Sign-Off, text the owner a short "Is this resolved?" message. Use the Wait action's contact-reply option with a timeout. A yes moves it to Closed. No reply after the timeout creates a task for someone to call.
5. The 11-month walkthrough
At closeout, add the owner to a workflow whose Wait step holds until a date in a custom field: the 11-month mark after Substantial Completion. On that date, send a walkthrough invitation and create a PM task. The goal is to find and correct items while you still control the fix. Pair it with your appointment reminder setup so the walkthrough actually happens.
Documentation That Holds Up in a Dispute
Most warranty disputes come down to two questions: when were you told, and what did you do about it?
What every warranty record should show
The original submission with its timestamp and photos
Every email and text to the owner and the sub, logged on the contact
Stage changes, which HighLevel records in the opportunity's activity log
Before and after photos uploaded to the record
The coverage decision, and for anything marked Not Covered, the reason and the message sent to the owner
The owner's sign-off reply
Never decline coverage by phone only; follow up in writing. Record every attempt to reach a stalling sub. Archive closed records instead of deleting them, since limitation periods can run long after the correction period ends.
This is office discipline, not legal advice.
Turning Warranty Contacts Into Repeat Work
An owner whose problem was fixed quickly, with clear updates, often trusts you more than before anything went wrong.
After a request closes
Tag the contact, wait a short period, then send a check-in. If the owner is satisfied, it is a natural point for a review request through your existing process. Log any new work the owner mentioned as an opportunity in your sales pipeline.
After the 11-month walkthrough
The walkthrough is a scheduled, face-to-face conversation with a past client. Train your PM to ask one question at the end: "Anything else you're planning on this property?" Log the answer. Over a year, those notes become a list of warm leads. The pipeline reports guide shows how to see how many of them turn into signed work.
A report of requests by trade and by sub also shows you who generates callbacks, which is worth having at the next bid decision.
What I've Seen Inside Contractor Shops
In 30+ years in construction operations, I have watched warranty work get handled on legal pads, in Outlook folders, in a spreadsheet one person understood, and most often not at all. The company does good work, closes the job, and lets the relationship drift because no one is assigned to it.
Picture an office manager in January with a stack of closeout binders and a phone that keeps ringing. She knows something is coming due on half of those projects. She just cannot see what. When the shop finally puts warranty requests on a board, the first reaction is usually relief: everything is in one place and the office can stop being the memory for the whole company.
The second thing I see is that the 11-month walkthrough changes the tone of the relationship. Owners do not expect a contractor to call them. When you do, the conversation is about what is working and what is next, not about what went wrong. That is where repeat work comes from, and I am a big believer in letting automation handle the remembering so your people can handle the conversation.
A Practical Next Step
You do not need to build all of this at once. Start with the intake form and the warranty pipeline. Add the 11-month walkthrough workflow next. Layer the reminders and reporting on after your team is using the board every day.
If you would rather start with a setup already built for contractors, take a look at the R.CS product lineup to see how OpsHub is put together, or call (219) 600-5908 to talk through how your shop handles closeout today.
Sources
AIA Contract Documents: discussion of A201-2017 Sections 12.2.2.1 and 3.5.1
Miller Nash: Warranty vs. Correction Period, What's the Difference Between These Clauses
HighLevel Help: Adding Files to Contacts Using a Custom Field
FAQ
What is construction warranty tracking?
It is logging every post-closeout request, assigning it, tracking response time and recording the resolution, along with each project's correction period dates.
Is the one-year correction period the same as the warranty?
No. Under AIA A201-2017, Section 12.2.2.1 sets a one-year correction period after Substantial Completion. The Section 3.5 warranty has no stated one-year limit.
When should a contractor schedule the 11-month walkthrough?
About 11 months after Substantial Completion, so items can be corrected before the one-year period ends. A CRM workflow can send the invitation automatically.
How do I assign warranty items to subcontractors in a CRM?
Store the sub on the record and use a Pipeline Stage Changed workflow to email or text them photos and access notes. Keep the follow-up task with your own coordinator.
What documentation should I keep for warranty disputes?
The timestamped request, every message, stage history, before and after photos, the coverage decision and the owner's sign-off. Ask your attorney about retention.
