Roofing contractor complaint handling compared with what actually happens

What to take away

What firms publish, and what crews do

Almost every roofing contractor with a website publishes a complaint process. Read enough of them and the same four routes appear: our defect, not our work, scope gap, expectation gap.

The published version follows the same shape in each firm: report the problem in writing, allow a stated number of days to attend, and allow access for a look at the roof. GAF's published warranty instructions, for example, tell a homeowner to contact the installing contractor before any claim is filed. The site behavior is not.

A roofing contractor's complaint process often sits inside a manufacturer warranty program. Each program ties the shingle warranty to written installation instructions.

GAF runs the Master Elite contractor program. Master Elite contractors can offer the Golden Pledge limited warranty. A leak on a GAF-warranted roof is a manufacturer question as much as a contractor question, and GAF's published process says so.

In practice, crews often diagnose on the roof before anyone has opened the warranty file. That turns a warranty call into a workmanship argument. CompanyCam or a similar photo app records the finding, but only if someone opens the job file first.

Owens Corning runs the Platinum Preferred contractor program, and those contractors can offer the Platinum Protection limited warranty. Owens Corning publishes installation specifications.

CertainTeed runs the SELECT ShingleMaster program, and those contractors can offer the SureStart limited warranty. CertainTeed publishes installation instructions that govern its warranty. A contractor who skips the ice-and-water membrane at an eave can be correct under local code and still void the shingle warranty.

Malarkey Roofing Products publishes installation instructions and shingle warranties from its Portland, Oregon base. Atlas Roofing Corporation does the same from Atlanta. None of these five is doing anything wrong. The point is that the contractor's complaint process and the manufacturer's published requirements are two documents. A complaint visit that reads only one of them will misroute the case.

The first hour, in practice

A roofing complaint is urgent in a way other trades are not, because water is either entering a building or it is not.

Three things in the first hour: acknowledge, ask whether water is currently entering, and give a time you will attend. If water is entering, treat it as an emergency regardless of whose fault it turns out to be. Arguing about responsibility while a ceiling is getting wet is the most expensive thing a roofing firm can do.

Diagnose before you discuss liability

Send someone competent, not someone senior. The job of the visit is to find out what is happening, not to establish who pays.

Do not concede on the roof and do not deny on the roof. Both are decisions made without the file open.

The four routes, plus the manufacturer warranty route

Most disputes are the third and fourth routes handled as though they were the first two. A firm that fixes an expectation gap by discounting has bought silence rather than solving anything, and it will meet the same complaint on the next job.

A typical pattern: a homeowner reports staining at a valley eight months after a re-roof. The crew attends, sees sound underlayment, and books a workmanship repair. The job file shows the valley was excluded from the agreed scope. The correct route is a scope gap, so the answer is a written quote for the valley, not a free repair.

Timing rules that hold under pressure

Set your own, write them down, and meet them. Four rules cover almost every complaint.

Rule four matters in this trade specifically. Customers accept weather delays readily when told the condition and resent them when given dates that slip.

What the crew should do on site

A complaint often arrives while a crew is still working. Give them one instruction: listen, record, escalate, and promise only a call back by a stated time.

That single rule prevents two failures. A crew member who argues turns a question into a grievance. A crew member who agrees that something is wrong commits the firm before anyone has looked at the file. Both belong in the written standards described in how to document roofing contractor service standards.

If a complaint concerns safety on site, treat it as a stop-work question rather than a customer service question. The OSHA guidance on fall protection in residential construction describes the methods available and puts the duty to apply what governs the site on the employer. A member of the public raising a concern is information you asked for.

Reviews, and how not to make it worse

A complaint sometimes arrives as a public review. Respond in public, briefly, without arguing, and move the detail to a private channel.

Never offer anything in exchange for removing or changing a review, and never ask only satisfied customers for one. The FTC guidance on soliciting and paying for online reviews sets out what marketers may and may not do here.

Ask every customer at the same point in the process, with the same message. That is both the compliant approach and the one that produces a review profile a reader believes.

The record, and what it is for

Every complaint gets a file. It records what was reported, when, and who attended. It records what was found with photographs. It records which route it went down. It records what was done and when it closed.

Retain it alongside the job file to the standard in the IRS guidance on the records a business should keep, because a complaint about a roof can resurface years later at a property sale. AccuLynx, JobNimbus or a similar job management system can hold the file in one place.

Reading the pattern, quarterly

Take every complaint from the quarter and sort by route. The mix tells you what to fix. No public dataset gives complaint volumes by firm, so your own count is the only figure that means anything.

Mostly route one means a workmanship problem, and the hold points in the roofing contractor quality assurance checklist are either wrong or not being run.

Mostly route three means your scope documents are unclear.

Mostly route four means the handover is too fast, and what a good one contains is described in the roofing contractor service quality guide for owners.

If one crew or one job type produces most of them, that is a training question, not a process question. It belongs with the progression in the roofing contractor hiring and training guide.

If one geography produces most of them, look at what is different about the building stock there. Use the reasoning in best markets for a roofing contractor business.

Common questions

Should I ever pay to make a complaint go away?

Where the fault is yours, fix it, which is not the same thing. Paying to settle a complaint about correct work teaches the market something you will regret.

What if the customer is wrong and angry?

Attend anyway and put the finding in writing. Being right without evidence in front of somebody is indistinguishable from being defensive.

How long should I stand behind work?

Two to five years is a typical workmanship term, and some firms publish one year on repairs. Manufacturer warranties run far longer, but they cover materials rather than the labor. Honor your published term without argument. Vague terms cause more complaints than short ones. Confirm the wording with your lawyer before you publish it.

Who should own the process?

One named person, with the owner reading every file for the first year. Delegating before you have seen the pattern yourself means learning about your firm through somebody else's summary.