Almost every ugly roofing dispute traces back to the same root cause: a scope of work that described the roof instead of describing the job. "Tear off and replace with architectural shingles, 30-year warranty" is not a scope. It's a headline. Everything the homeowner assumed, everything your crew guessed at, and everything the insurance adjuster later disputed lives in the white space underneath that sentence.
A scope of work is a liability document that happens to also sell the job. Written right, it makes the change order conversation boring, because you already told them this might happen and what it would cost. Written wrong, it turns a $1,400 deck repair into a two-week standoff and a one-star review.
Every scope problem falls into one of three buckets, and each one needs different language.
Most contractors write scopes that address none of these. They list products. Products aren't the fight. Assumptions are the fight.
A material list says "synthetic underlayment." An assembly description says where it goes, how much of it, how it's fastened, and what it laps over. The difference matters because the assembly is what actually gets installed and inspected.
Compare these two lines for the same job:
The second version does three jobs at once. It tells the customer what they're buying, it tells your crew exactly what to install so the truck gets loaded right, and it tells any future adjuster or attorney that you specified to code rather than to convenience. It also gives you a defensible number to point at when the customer's brother-in-law says you skimped.
Do this for every assembly on the roof: tear-off and disposal, deck inspection and repair, underlayment, drip edge, starter, field, hip and ridge, ventilation, penetrations, flashings, and cleanup. Ten to fifteen line items. That's the shape of a real scope.
Numbers end arguments. Adjectives start them.
If your takeoff produced squares, linear feet of ridge, linear feet of eave and rake, valley footage, penetration counts, and pitch breakdown — put those numbers in the scope. Not because the customer will audit them, but because they establish the boundaries of the deal. When your measurement says 2 pipe boots and there are 5 on the roof, the quantified scope is what makes that a conversation instead of an accusation.
This is where a takeoff-driven bid earns its keep. If your measurement data flows straight into the scope language, the numbers on the proposal are the same numbers your crew works from and the same numbers you priced. Three documents, one source of truth. When those diverge — when the estimator eyeballs the proposal from memory — that's when you eat the difference.
Include a stated tolerance so nobody nitpicks: "Quantities based on aerial measurement report dated [date]. Field conditions may vary by up to 5%; variance within this range is included in the contract price at no adjustment."
You cannot see the decking. You cannot see behind the chimney. You cannot count the layers from the ground with certainty. Pretending otherwise is how contractors end up eating $3,000 of plywood to keep a customer happy.
The fix is a unit price table in the proposal itself, signed at the same time as the contract:
Add the trigger language: "Concealed conditions will be documented photographically and communicated before corrective work begins. Unit prices above apply. Work exceeding $XXX in cumulative additions requires written authorization."
Now the mid-job phone call is a five-minute confirmation instead of a negotiation from a position of weakness — because you're standing on a roof they need finished today. Never negotiate price from a tear-off.
Contractors avoid exclusions because they feel negative. That's backwards. Exclusions read as expertise. A homeowner comparing three bids where two say "complete roof replacement" and one lists exactly what's in and out reads the third as the professional.
Standard exclusions worth naming explicitly:
Two extras that save real money: state that the dumpster/driveway arrangement is the customer's approved location and that driveway sealing or cracking from delivery trucks is excluded, and state your magnetic sweep policy while excluding liability for nails found beyond a stated period. Both are common small-claims triggers.
Workmanship disputes get resolved by whoever can point to a written standard. Make sure it's you.
Put a line in every scope: "All work performed per manufacturer's published installation instructions for the specified system and applicable local building code. Where the two conflict, the more stringent applies." Then name the specifics that actually get argued about on your jobs — typically fastener count per shingle and the pitch-specific requirement, valley method (closed-cut, woven, or open metal — pick one and write it), drip edge sequencing at eave versus rake, starter course at both eaves and rakes, and ventilation approach with net free area if you're balancing a system.
That last one deserves attention. Ventilation is the single most common source of warranty denial, and it's the thing customers understand least. If you're installing 40 feet of ridge vent, say what intake it's paired with and note in writing if existing intake is insufficient. "Existing soffit intake measured at approximately X sq in NFA; specified exhaust requires Y. Additional intake venting quoted as optional line item. Manufacturer warranty may be affected if intake is not corrected." You've now either sold the upgrade or documented that they declined it.
Final-payment disputes happen because nobody defined completion. Write it down:
Then state the payment trigger against that list. "Final payment due upon completion of the items above, not contingent on delivery of manufacturer warranty registration, which follows within 30 days." Ambiguity in the completion definition is how contractors end up financing the last 20% of a job for two months.
Weather delays, material backorders, and inspection scheduling are outside your control, and customers rarely account for them. Give them two dates: an estimated start window and an estimated duration, both with a stated basis. "Estimated start: week of [date], subject to weather and material availability. Estimated duration: 2–3 working days for the roof assembly, exclusive of inspection scheduling. Delays caused by weather, permit processing, or supplier backorder do not constitute breach and do not adjust the contract price."
Add one more line that prevents a specific and very expensive fight: what happens if the roof is opened up and weather turns. "In the event of weather during an active tear-off, the roof will be dried in with temporary protection. Interior damage resulting from weather events exceeding [rainfall/wind threshold] is excluded."
Write your photo protocol into the scope, because doing it is worthless if the customer didn't know to expect it and you can't prove when it was taken.
Minimum: pre-existing conditions before tear-off (including any damage to gutters, siding, landscaping, or interior you did not cause), deck condition after tear-off, any decking replaced with a visible count, all flashing and penetration details before they're covered, and finished elevations. Timestamp everything. This single practice eliminates more disputes than any contract clause, because most disputes aren't lawsuits — they're a customer with a bad memory and a photo you can send in ten seconds.
Nobody writes this from scratch at 9 PM after a full day of inspections. That's the entire reason bad scopes exist — not ignorance, but exhaustion. The estimator knows what should be in there and writes three lines anyway.
So build it once as a template with variable slots: quantities from the takeoff, system and color from the selection, unit prices from your current cost sheet, and job-specific conditions from the inspection notes. Then the estimator's job is filling in specifics and adding what's unusual about this roof, not reconstructing boilerplate from memory. Review the exclusion list twice a year and add whatever you got burned by since the last review — that list should grow, and every addition represents money you're no longer losing.
A good scope of work takes about six extra minutes per bid once the template exists. Compare that to one callback: the truck roll, the crew hours, the material, the awkward conversation, the review you don't get. Six minutes is the cheapest insurance in this business.