Roofing Estimate Template
A roofing estimate template for organizing roof scope, materials, labor, tear-off notes, disposal, extras, pricing, exclusions, and customer-facing assumptions.
What this roofing estimate template is for
Use this template to organize a customer-facing roofing estimate before work is approved or scheduled.
It keeps roof scope, material choices, labor notes, disposal notes, extras, and assumptions visible in one artifact.
What a roofing estimate should include
- Job address, roof area notes, tear-off scope, installation scope, materials, labor, disposal, and extras.
- Decking, flashing, ventilation, drip edge, underlayment, and cleanup notes at an operational level.
- Pricing, exclusions, assumptions, and customer-facing notes about changes that may require a separate change order.
Printable roofing estimate template
Print this roofing estimate artifact or copy the fields into your own estimating workflow.
Project and roof scope
Materials and labor
Disposal, extras, and price
Estimate boundary
A roofing estimate template organizes an estimate artifact. It is not an approval record for changed work.
Filled roofing estimate example
- Scope
- Tear off existing asphalt shingles on main house roof, install underlayment, drip edge, starter, architectural shingles, ridge cap, and standard cleanup.
- Materials
- Architectural shingles, synthetic underlayment, drip edge, starter strip, ridge cap, fasteners, sealant, and standard flashing accessories.
- Price
- $12,840 estimate based on visible roof scope, listed materials, labor, disposal, and stated assumptions.
- Assumption
- Decking replacement, hidden damage, or owner-requested extras are not included unless added through a separate change-order artifact.
Material, labor, and disposal notes
- Separate material notes from labor notes so the customer can see what the estimate covers.
- Include tear-off, haul-off, cleanup, and disposal notes when they affect price.
- State allowances or visible-scope assumptions in plain language.
Exclusions and assumptions
- Name work that is not included in the estimate price.
- Use assumptions for items that depend on access, visible conditions, owner selections, or later discovery.
- Keep assumptions operational and tied to the estimate artifact.
Change-order warning for roofing work
- If hidden decking damage, added accessories, or customer-requested extras change the scope, document the change separately.
- A roofing estimate is not a change-order approval record. Approval for changed work requires explicit client action where approval is relevant.
How StackQuotes supports estimate records
StackQuotes helps contractors organize estimate records, customer-facing scope, price notes, assumptions, and later change-order artifacts.
It does not turn an estimate template into approval, an invoice, a payment record, bookkeeping, or accounting.
Estimate boundary
A roofing estimate template organizes an estimate artifact. It is not an approval record for changed work.
When approval is relevant, rely on explicit client action rather than a draft, printed template, or conversation.
Common roofing estimate mistakes this helps avoid
- Leaving tear-off or disposal out of the customer-facing estimate.
- Combining materials, labor, and extras into one unclear line.
- Failing to state visible-scope assumptions.
- Letting hidden damage or added work proceed without a separate change-order artifact.
- Using the estimate artifact as if it were an approval record.
FAQ
What should a roofing estimate include?
Include roof scope, tear-off notes, materials, labor, disposal, extras, price, exclusions, and customer-facing assumptions.
Should hidden damage be included?
If hidden damage is not visible during estimating, list the assumption and document any later scope change separately.
Is this estimate an approval record?
No. It organizes an estimate artifact. Approval requires explicit client action where approval is relevant.
How should extras be handled?
List known extras in the estimate. If extras are requested later, organize them as a separate change-order artifact.