Roofing contract template: 12 Sections to Define Scope, Price, and Changes

A roofing contract template helps a contractor and property owner agree on the roof work before the crew starts. It should identify the roof areas, materials, price, payment stages, and process for hidden damage. A short phrase such as “replace roof” leaves too many important decisions open.

This article gives you a fill-in framework, a worked scope example, and practical checks for changes, weather, cleanup, and warranties. Use it as a drafting aid. Roofing and home improvement contract rules vary by location, so have the final agreement and required notices reviewed for the job’s jurisdiction.

Start with the roof and the work, not a generic promise

A useful roofing agreement template defines what the contractor will remove, inspect, repair, and install. It also explains what the price excludes. This gives both sides a shared basis for evaluating extra work.

For example, a house may have a main roof, porch roof, detached garage, and low-slope addition. If the quote covers only the main roof, identify that boundary in writing and on a marked plan. Photos can support the description, but label them clearly.

The FTC’s home improvement guidance advises consumers to check contractor details and read written terms carefully. It also notes that contract requirements vary by state. A reusable form needs local review before use.

A fill-in roofing contract template

Replace the bracketed fields below and attach the approved scope, material schedule, and required legal notices. Do not leave key choices to a verbal discussion after signing. Keep a version number on the agreement and each attachment.

1. Parties and property

Contractor: [legal name, address, phone, email]. License or registration: [details where required]. Property owner: [legal name and contact]. Project address: [address]. Authorized decision-maker: [name and role]. Contract reference and date: [reference and date].

Confirm who has authority to approve work and changes. A tenant, site contact, or family member may help with access without having authority to change the price. Record both roles when they differ.

2. Roof areas and scope

Included roof areas: [marked plan reference]. Removal: [materials and layers within scope]. Inspection: [accessible conditions to review after removal]. Installation: [system and tasks]. Included associated work: [flashing, vents, gutters, or other items]. Exclusions: [specific areas and tasks].

Next, explain whether the work is a repair, recover, or full replacement. These approaches have different scopes. Avoid mixing them in the document or allowing the title to promise more than the detailed specification.

3. Materials and system details

Roof covering: [manufacturer, product, color, and specification]. Underlayment: [product]. Flashing: [material and scope]. Edge details: [scope]. Ventilation work: [design or approved details]. Fasteners and accessories: [system requirements]. Substitutions: [approval process].

Do not accept “equivalent” without a review method. A substitution may affect appearance, installation requirements, or warranty eligibility. Require the contractor to identify the proposed change and obtain approval before ordering or installation.

4. Measurements and quantity basis

Area basis: [survey or measurement reference]. Quantities: [relevant schedule]. Waste or ordering allowance: [basis]. Contract pricing method: [fixed price, unit rate, or other agreed model]. Quantity adjustment method: [if applicable].

Our article on a roofing squares calculator explains area and ordering checks. Keep those calculations distinct from the contract’s rules for final pricing. Ordering more material does not automatically authorize a larger bill.

5. Hidden damage and extra work

If removal reveals damage outside the included scope, the contractor will [document the condition, notify the owner, and propose options]. The change proposal will show [work, quantity, price, schedule effect, and payment effect]. Approval requires [approved signature or agreed lawful method].

Any temporary protective action will follow [defined authority and process]. Describe this carefully so the team can protect the property without treating an urgent condition as unlimited permission to expand the job.

The California CSLB’s home improvement contract guidance illustrates the importance of detailed scope, payment terms, and written changes. California’s rules are jurisdiction-specific; check the requirements where your project sits.

6. Permits and inspections

Permit responsibility: [party]. Included permit fees: [basis]. Required inspections: [responsibility and coordination]. Design or engineering responsibility: [where applicable]. Completion documents: [permits, inspection records, or other required evidence].

Also state who manages access for an inspector and how inspection delays affect the schedule. A contractor should not assume that the owner will arrange a step that the owner believes the contractor included.

7. Schedule and weather

Estimated start: [date or window]. Estimated completion: [date or duration]. Dependencies: [material delivery, access, approvals, and permits]. Weather delay process: [notice and revised schedule]. Daily protection and temporary weatherproofing: [responsibility and method reference].

A weather clause should explain communication and protection duties, rather than simply remove all schedule responsibility. Include how the contractor will secure incomplete work and who the owner should contact if a problem develops.

8. Price and payment stages

Contract price: [amount and currency]. Tax treatment: [where applicable]. Deposit: [amount and due date, subject to local limits]. Progress stages: [clear milestones and amounts]. Final payment stage: [agreed completion conditions]. Payment methods and references: [details].

Tie each stage to a clear event. “Second payment due halfway” can mean different things to each party. Instead, identify the completed work or delivery that supports the request and check local restrictions on payment schedules.

9. Access and property protection

Working hours: [hours]. Access areas: [driveway, gates, roof access, and storage]. Owner preparations: [vehicles, fragile items, pets, or other tasks]. Contractor protection: [landscaping, windows, paths, and other affected areas]. Utilities: [agreed use].

Before work, record visible conditions with dated photos. This helps both parties review a later concern. Also agree on the procedure for reporting damage and arranging repairs, rather than relying on an informal promise.

10. Cleanup and waste

Waste handling: [container, location, disposal, and responsibility]. Daily cleanup: [scope]. Final cleanup: [debris removal and agreed checks]. Material ownership: [unused materials and salvage]. Removal date for equipment and containers: [date or event].

For example, clarify whether the contractor removes old satellite mounts or leaves them for another trade. Also state whether gutter cleaning and debris checks form part of the work. Small omissions can become visible disputes at handover.

11. Workmanship and product warranties

Workmanship warranty: [provider, term, scope, exclusions, and claim route]. Product warranty: [manufacturer document and version]. Registration: [responsible party and deadline]. Maintenance conditions: [relevant document]. Transfer terms: [if applicable].

Keep these warranties distinct. A manufacturer product warranty and a contractor workmanship promise may cover different failures. Do not describe either as “lifetime” without explaining the actual terms and limits in the governing document.

12. Completion, changes, and required terms

Completion review: [walk-through and evidence]. Outstanding-item process: [record, owner, and target date]. Required notices and cancellation terms: [locally reviewed attachments]. Dispute process: [reviewed clause]. Agreement order of precedence: [document hierarchy]. Signatures and dates: [approved parties].

Finally, confirm that the signed package includes every referenced attachment. A material schedule that exists only in an estimator’s email should not remain outside the shared contract record.

A worked roofing scope example

Consider a fictional asphalt shingle replacement for the main house roof only. The marked plan excludes a detached garage and a low-slope addition. The contractor includes removal of one existing covering layer, the specified replacement system, and the listed flashing work.

The base price includes a stated amount of decking repair, while extra damage follows an approved unit rate. The agreement defines the unit, material specification, measurement method, and approval process. This is more useful than a line saying “bad wood costs extra.”

After removal, the crew finds a damaged area beyond the allowance. The supervisor photographs it, measures it, and sends a change proposal. The proposal shows the extra quantity, price, and schedule effect before the owner decides.

These are example choices, not standard quantities or rates. A different roof system or jurisdiction may need other terms. The important point is that the parties can trace the decision from condition to evidence, approval, and invoice.

Use a pre-start review to catch gaps

Before mobilizing, the estimator and site supervisor should review the signed scope together. Confirm roof boundaries, product details, access, material storage, and customer contacts. This reduces the chance that the crew works from an older quote.

Next, compare the contract with site observations. Our roof inspection checklist can help organize records, while qualified roof professionals should decide the actual design and safe work method.

Also verify the change process. Staff need to know who may approve extra work, what evidence to collect, and where to store the approval. A good clause has little value if the site team never sees it.

Keep the final record connected

At handover, gather the final scope, approved changes, invoices, inspection records, and warranty documents. Give the owner a clear record of outstanding items and contact details. Avoid marking every task complete merely to close the job in software.

For businesses handling many projects, roofing software features can help connect estimates, schedules, and customer records. Keep signed contract versions protected from casual editing.

Check the contract against the final invoice

Before requesting final payment, compare the invoice with the signed price and approved changes. List additions and deductions separately, then apply earlier payments once. The owner should be able to follow the path from the base contract to the balance due.

For example, a customer may remove a gutter task while approving extra decking repair. Both changes belong in the final account. Showing only the added work creates an incomplete picture even when the net total happens to be correct.

Next, check quantities for unit-priced work against the agreed measurement records. A supplier delivery note shows what arrived, but it may not prove the quantity installed or the quantity chargeable under the contract. Use the basis the parties actually agreed.

Also confirm the completion conditions for the final payment stage. These may include the agreed walk-through, documents, or other requirements. Follow applicable local rules and avoid treating a software status as proof that every condition is met.

If a small item remains open, record it with an owner and next action. The contract and local law should guide payment treatment. Do not invent a new rule during the handover discussion.

Finally, retain the final account with the signed scope, changes, and payment records. That file helps the contractor respond to future service questions and lets the owner see what the project included.

For repeatable administration, assign one person to check the document package before it reaches the customer. A short review can catch a missing credit, an old material schedule, or an unsigned change.

Make the scope clear before the roof opens

A roofing contract template works best when it connects the physical roof to specific materials, tasks, prices, and approvals. Complete the details, review local requirements, and brief the crew from the signed version. That gives both parties a clear basis for the work and any changes.