5 Essential Roofing Estimating Best Practices for 2026

Most bad roofing estimates are not wrong because of math. They are wrong because the estimator, the crew, the office, and the homeowner were all working from a different mental picture of the job. The number on the page looked clean. The job underneath it was something nobody had fully agreed on.

So here is the short answer for 2026, before any of the detail. A reliable roofing estimate is built on five repeatable controls, in this order: (1) write the scope before you price anything, (2) take off measurements separately from pricing decisions and correct every plan area for pitch, (3) cost the job on true labor and overhead rather than only the material on the truck, (4) keep records that can explain the estimate a year later, and (5) review every customer-facing claim before the proposal leaves your office. Get those five right and your estimate stops being a guess wearing a tie.

Notice what is not on that list: a magic spreadsheet, a single perfect markup percentage, or a piece of software that prices the job for you. Tools help. They do not replace judgment, a current measurement, and a review step. The contractors who hold margin in a soft market are the ones whose estimates are legible — anyone on the team can open the file and see exactly what was promised, what it was based on, and why it costs what it costs.

The sections below walk each practice in field detail: real pitch factors, real waste-factor ranges, a labor-burden breakdown, current code triggers that quietly add line items, and copy-ready checklists you can lift straight into your process. The audience is the working estimator and the owner who signs off on the number, not a classroom.

Why estimating discipline is the difference in 2026

Material prices move. Insurance rules shift. Crews turn over. The one thing inside your control is whether your estimating process produces the same quality of decision every time, regardless of who builds the estimate. That consistency is what separates a shop that nets a healthy margin from one that wins a lot of jobs and wonders where the money went.

Think about the path an estimate travels. A sales rep promises a scope. An estimator prices it. A production manager schedules and orders to it. A crew installs against it. The office invoices and reconciles it. If any link in that chain has to guess what the previous link meant, you lose money — on a callback, a change order you eat, a material shortfall, or a customer who feels misled. Every one of the five practices below exists to remove a guess from that chain.

A second reason discipline matters more now: estimates increasingly get scrutinized after the fact. Adjusters compare your scope to their scope. Homeowners screenshot your proposal and text it to their brother-in-law who "does construction." If your estimate makes a claim you cannot support — a lifespan, a warranty term, an energy savings number — it is no longer a private internal document. It is a representation, and representations have to be true.

The rest of this is the playbook. Work it in order. The order is the point.

1. Write the scope before you price anything

An estimate should open with a scope statement, not a price table. The scope is your internal agreement about what you believe you are selling, what you are excluding, and what still needs to be confirmed. Skip it, and every number downstream is fragile — the price might be perfectly accurate for a job the customer never expected to buy.

The reason this comes first is simple. Scope is the only document that everyone — sales, estimating, production, the homeowner — has to agree on for the rest of the estimate to mean anything. A precise price attached to a vague scope is worse than a rough price attached to a precise scope, because the precise number creates false confidence.

What a usable scope actually contains

At minimum, a scope should name:

• Property and roof identification — address, which roof or which sections, and the system or service type (tear-off and replace, recover, repair, maintenance).
• Tear-off assumptions — how many existing layers you are assuming, and what happens if you find more once you open it.
• Deck and substrate assumptions — what you expect the deck to be and how you will handle rotten or non-code sheathing if it shows up.
• Ventilation and drainage notes — intake and exhaust approach, and whether you are changing it.
• Underlayment, ice barrier, and flashing scope — what you are installing, where, and to what standard.
• Disposal, access, and permit responsibility — dumpster placement, driveway limits, and who pulls the permit.
• Selected materials — exact product line and color, rather than a generic "architectural shingle."
• Explicit exclusions — anything the base price does not cover, stated in plain language.

The last line is the one that saves jobs. If you cannot verify the deck until you tear off, say so. If damaged sheathing is excluded from the base price and will be handled by unit price or change order, state that before the homeowner signs — not after the crew finds three sheets of soft plywood over the garage.

Honest scope language vs. overclaiming

A good scope is specific enough to guide the crew but careful enough to avoid certainty you cannot defend. Do not write that all hidden conditions are included when nobody has seen them. Do not imply a roof section is dry, structurally sound, or warranty-eligible unless you have evidence and the authority to say it.

This is also where a planning tool earns its place. A platform like RoofPredict is built around the property record rather than the individual estimate, so an estimated roof-age range, prior storm exposure, photos, and earlier service notes stay attached to the same address. That matters at scope time: a roof that has had three leak calls and a 12-year-old age estimate should not be scoped like a clean first visit. RoofPredict does not inspect the roof or certify its condition — it does not climb the ladder for you — but it tells you which homes are actually due and surfaces the history so the person writing the scope starts informed instead of blank.

Copy-ready scope template

ROOFING SCOPE — INTERNAL (complete before pricing)

Property: __________________________   Date: __________
Estimator: ________________   Measurement source/date: __________

System/service:   [ ] Tear-off + replace  [ ] Recover  [ ] Repair  [ ] Maint.
Sections in scope: ____________________________________________
Existing layers assumed: ____   If more found: [ ] unit price [ ] change order
Deck assumption: ____________   Bad-deck handling: $______ per sheet (unit)

Underlayment: ____________   Ice barrier req'd? [ ] Y [ ] N  (code/climate)
Drip edge: [ ] eave [ ] rake   Flashing: [ ] step [ ] counter [ ] pipe boots
Ventilation: intake ________  exhaust ________  [ ] changing  [ ] matching
Penetrations: ______________   Skylights: ______________

Access/staging notes: __________________________________________
Disposal: ____________   Permit by: [ ] us [ ] owner

Selected material (line + color): _____________________________

EXPLICIT EXCLUSIONS (state plainly):
- ________________________________________________________
- ________________________________________________________

UNKNOWNS / CONFIRM BEFORE SEND:
- ________________________________________________________

The U.S. Small Business Administration's guidance on planning a business stresses spelling out exactly what you sell and how you deliver it — the SBA's write-your-business-plan material is the company-level version of this same habit. A scope statement is that discipline applied one job at a time.

2. Separate measurements from pricing — and correct for pitch

Good estimating keeps two questions apart. What is there? is a measurement question. What will we charge to do the work? is a pricing question. When those blur together, the estimate becomes impossible to review, because nobody can tell whether the price moved because the roof got bigger, the material changed, the waste factor changed, or someone adjusted the margin.

Keep the takeoff in reviewable fields: roof areas, slopes by section, linear footage of eaves, rakes, ridges, hips, and valleys, penetration counts, and field notes on access. Keep pricing in separate fields. A manager should be able to look at the takeoff alone and judge whether the measurement is right, then look at pricing alone and judge whether the price is right.

Always price by sloped area, never by footprint

This is the single most common takeoff error, and it is pure money. The roof is bigger than the building. A 1,200-square-foot footprint on a 6/12 roof is not 1,200 square feet of roofing — it is about 1,342 square feet, because the slope stretches the surface. Order or price off the footprint and you are short roughly 12% before you even add waste.

The fix is the pitch factor (slope multiplier), calculated as the square root of 1 plus (rise/12) squared. Multiply the plan/footprint area by the factor to get true surface area. The common ones:

The roof pitch factor reference at TruTec lays out the full chart if you need pitches between these. Two practical points: pitch also changes labor (steeper is slower and triggers fall-protection and steep-charge line items), and aerial measurement reports usually already return sloped area — confirm whether a number is plan or sloped before you trust it.

Waste factor: a range, not a reflex

Waste is the material you buy and do not install — cut-off at hips and valleys, starter and ridge cuts, breakage, and overage you keep on hand. The reflex "add 10%" is a decent default for a plain roof and a real underestimate for a cut-up one. Tie the number to the roof's geometry.

Guidance from Roofr's waste-factor breakdown and the RoofPredict waste-factor guide lands in the same ranges: 5–10% simple, 10–15% moderate, 15%+ complex, with tile higher because of breakage. Two cautions. First, waste is computed on the sloped area, after the pitch correction — never on the footprint. Second, valley material and starter/ridge are often counted as their own line items; if you count them separately, do not double-count them inside a fat global waste percentage.

Take off the whole roof, not only the field shingles

A shingle-only takeoff is how shops bleed margin one accessory at a time. It is also the most common rookie error in the trade, because the field shingles are the loud number and everything else is quiet until the truck shows up short. The field shingles are the obvious cost, but the accessories and edge details add up fast, and they are exactly the items an inexperienced estimator forgets — then the crew is short on a Friday and someone makes a parts run that eats an hour of profit. A full takeoff captures every quantity the crew will actually open on site.

The linear measurements — eaves, rakes, ridges, hips, valleys — are not optional detail. Starter, drip edge, hip-and-ridge cap, and ice barrier are all priced off them, so a takeoff that only records area cannot price the job correctly. Record edge footage by type, every time.

A worked example, start to finish

Walk a single hypothetical so the steps connect. Say a simple gable roof has a 1,400-square-foot footprint at a 6/12 pitch, 110 linear feet of eaves, 110 linear feet of rakes, and 60 linear feet of ridge, in a climate that does not trigger an ice barrier.

First, pitch-correct the area: 1,400 × 1.118 ≈ 1,565 square feet of sloped roof, which is 15.65 squares. Apply a 10% waste factor for a simple gable: 15.65 × 1.10 ≈ 17.2 squares of field shingles, which you round up to whole bundles. Starter runs the eaves and rakes: 110 + 110 = 220 linear feet. Hip-and-ridge cap covers the 60 feet of ridge. Drip edge runs all 220 feet of edge. Underlayment covers the full 15.65 squares plus a little lap. Notice what happened: pricing the footprint instead of the sloped area would have started you at 14 squares, undercounting field material by more than a square and a half before waste — on a small roof, that is a parts run and a margin hit on every job you build that way.

Date and source every measurement

Roofs change. Storms, temporary patches, active leaks, and prior repairs make an older measurement incomplete for a new proposal. A stale-but-precise-looking record is more dangerous than a rough note, because the clean formatting stops people from asking questions. Stamp every takeoff with its source (field visit, aerial report, prior job, owner-provided) and its date.

This is another spot where keeping evidence attached to the property pays off. When measurement photos, the takeoff, and the assumptions live on the same property record, the next estimator can see why a quantity was used and whether it came from today's visit or a three-year-old job. The goal is the same throughout: don't hide judgment inside the number — put quantities, assumptions, and logic in fields a reviewer can actually check.

3. Cost the job on true labor and overhead, not material on the truck

Material quantity is only one leg of an estimate. Labor time, supervision, travel, setup, access, safety, staging, disposal, warranty admin, and office work decide whether the job is profitable. A small material miss is a rounding error you can absorb. A labor plan that ignores access, sequencing, or steepness can eat the entire job margin.

Write labor in job language, then price it

Before you put a dollar on labor, answer the operational questions in plain words: How many crew-days? What access method — ladder, lift, crane? Normal hours or restricted? Occupied building? Interior protection, daily cleanup, temporary dry-in, traffic control, or coordination with another trade? Commercial and multifamily work needs more of this language than a simple residential repair, but every estimate benefits from a visible labor plan that a production manager can sanity-check.

Build the labor rate on burden, not the wage

The wage on the pay stub is not what an hour of labor costs you. The loaded cost adds payroll taxes, workers' compensation (high in roofing), general liability, and other employer costs. Industry pricing guides commonly model a labor burden in the neighborhood of 25–35% on top of base wage — the build-folio roofing pricing guide walks the math — and workers' comp alone is often a roofer's single largest overhead category because of the class-code rate. Use your actual numbers from your carrier and accountant; the point is that you price labor on the burdened rate, not the raw wage.

A simplified illustration, clearly hypothetical: say a 4-person crew at a $25 base wage works an 8-hour day. Base labor is $800. Apply a 30% burden and the day costs roughly $1,040 in labor before you have priced a single bundle. Now apply that to the number of crew-days the job actually takes, including the slow steep-roof hours, and you have a labor number you can defend.

Know where the money goes on a typical re-roof

You cannot set markup intelligently if you do not know your cost structure. A rough sense of how revenue splits on a residential re-roof, drawn from contractor pricing breakdowns, helps you see whether an estimate is in a sane range:

These are directional benchmarks, not a guarantee — your shop's real percentages come from your own profit-and-loss statement. The build-folio overhead and profit guide is a fair starting reference, and it makes the key point that the old "10 and 10" rule (10% overhead, 10% profit, a 20% markup) is usually too thin to cover a real roofing overhead load. The SBA's break-even and startup-cost guidance is the underlying idea: you have fixed and variable costs, and every job has to carry its share of both.

Markup vs. margin — the mistake that quietly kills shops

This trips up newer estimators constantly. Marking up cost by 20% does not give you a 20% margin. If your job costs $10,000 and you add 20% markup, you sell at $12,000 and your margin is $2,000 / $12,000 = 16.7%, not 20%. To actually keep a 20% margin you have to divide cost by (1 − 0.20), i.e. sell at $12,500.

Memorize the divide-don't-add rule, or wire it into your estimating template so nobody has to remember it under pressure.

Standardize the routine, flag the exceptions

The goal is not to make every estimate slow. It is to make common assumptions reusable and unusual ones loud. Decide which assumptions are standard (normal business-hour access, typical staging, standard cleanup, a defined payment schedule) and which trigger a manager's review. A sample approval-trigger list:

• Night work or restricted working hours
• Crane or lift required
• Occupied critical facility (hospital, school, occupied multifamily)
• Steep or fragile surfaces beyond your standard crew
• Long material carry or no driveway access
• Customer-provided materials or unusual substitutions
• Any exclusion that could surprise the homeowner

Where repeat-customer or property history matters, keep it in front of the estimator. If a property has a pattern of leak calls, tenant sensitivity, or a prior dispute, the labor plan should reflect that reality before the price goes out — not after the crew arrives and discovers it.

Price the change order at the estimate, not in the moment

The most predictable change order on a re-roof is bad sheathing, and the most expensive way to handle it is to negotiate the price while a crew stands on an open roof. Decide the unit price during estimating, state it in the scope, and get the homeowner's acknowledgment before work starts: "Decking is sound to visual inspection; if rotten or non-code sheathing is found during tear-off, it will be replaced at $X per sheet and documented with photos." That sentence converts the worst on-site argument in roofing into a routine, pre-agreed line. The same logic applies to any condition you cannot verify until you open the roof — multiple existing layers, failed flashing behind siding, or a soft fascia. Name it, price it, and put it in the scope so the field decision is execution, not negotiation.

This is also a margin discipline, not only a customer-relations one. A change order priced under pressure tends to be priced low, because the crew wants to keep moving and the salesperson wants to keep the customer happy. A change order priced calmly at the estimate carries its real labor and material cost plus the same margin as the base job. Over a year of re-roofs, the difference between those two habits is real money.

4. Keep records that explain the estimate a year later

An estimate is also a record. Months later, the homeowner asks why a line item was excluded. The crew finds a hidden condition. The office compares sold scope to completed work. Tax time arrives and you need to support income, expense, and job-cost numbers. A usable estimate file answers those questions without anyone relying on memory.

The IRS instructs small businesses to keep records that support income, expenses, and credits, and to retain them as long as needed to prove the items on a return — see the IRS recordkeeping page. For roofing estimates specifically, that means saving: the signed proposal, the material selection, the dated measurement and its source, labeled photos, customer communications, change-order terms, the payment schedule, permit notes, warranty documents, and final job notes.

Records make your next estimate better

The quiet payoff is estimating accuracy over time. If you can compare estimated labor to actual labor, estimated material to actual material, and original scope to change orders, you can learn from finished jobs instead of guessing. Without those records, pricing stays anecdotal — you remember a job "felt tight" but you cannot turn that into a better assumption for the next bid.

This is precisely where a property-centered system helps, because roofing work repeats across the same addresses for years: inspection, estimate, repair, maintenance, replacement. When the record stays attached to the property, each future estimate starts with real context instead of a blank page. It is also the natural home for re-engaging an old book of business — past estimates and customers who never closed are some of the best outbound targets you have, and a tool that flags which of those roofs are now likely due (by age range plus storm exposure) turns a dusty CRM into a worklist. RoofPredict is built for exactly that targeting job; it does not decide who to mail or what to charge, it tells you which roofs are worth the stamp.

Keep records factual

One discipline that protects you: label conditions by who observed them. Photos get an area and a date. Notes separate observed conditions from customer statements from internal assumptions. If a homeowner says there was a leak in the back bedroom, record it as a customer report unless your team confirmed the path. If an estimator suspects hidden deck rot, record it as a suspected condition and note how it will be handled if found. Good records do not end disputes, but they make your reasoning visible — and a few labeled photos plus a dated measurement and a clean exclusion beat a giant folder of unlabeled images every time.

Records checklist

ESTIMATE FILE — KEEP ON RECORD
[ ] Signed proposal (final version sent to customer)
[ ] Scope statement (internal) + exclusions
[ ] Dated measurement/takeoff + source
[ ] Photos, labeled by area + date
[ ] Material selection (line + color + quantities)
[ ] Labor/access plan + crew-day assumption
[ ] Customer communications (key emails/texts)
[ ] Change orders (terms + approval)
[ ] Payment schedule
[ ] Permit notes / number
[ ] Warranty documents (mfr + workmanship)
[ ] Job-completion notes (actual vs. estimated)

5. Review every customer-facing claim before the proposal leaves

The last step is a review of what the customer will actually read. Most estimate problems are not arithmetic. They are language — a promise that's too big, a hidden condition, a result you cannot guarantee, or a comparison with nothing behind it.

The Federal Trade Commission's standard is plain: advertising and representations must be truthful, cannot be deceptive or unfair, and must be backed by evidence where the claim needs support. The FTC's advertising and marketing guidance applies to far more than billboards — it covers your proposals, brochures, landing pages, and what a rep says at the kitchen table. FTC staff guidance in 2025 specifically cautioned against loose warranty language like "lifetime" or "full coverage" unless the conditions are clearly defined.

What to scrutinize

Run proposal language past these before anyone signs:

• Lifespan claims. If you say a roof or product will last X years, know the basis. Manufacturer-rated service life under stated conditions is a defensible reference; a casual "this'll last 50 years" is not. Tie statements to the actual product line — the manufacturer's published data, e.g. a GAF shingle product page, is the right anchor.
• Warranty. Match the language to the actual manufacturer warranty and your workmanship warranty. Note what voids it. Do not imply system-level coverage you have not registered.
• Insurance. Never imply you control the carrier's decision. You can document damage and communicate with an adjuster; you cannot guarantee approval, and saying otherwise is a representation you cannot keep.
• Energy/savings claims. If you cite a savings or efficiency number, it needs a source and stated conditions. Vague "cut your bills" language invites trouble.
• Urgency. Real deadlines (a permit window, a manufacturer price change) are fine. Manufactured scarcity is the kind of unfair practice the FTC targets.

Don't let code triggers hide in the fine print

Customers and adjusters increasingly know the code. A proposal that ignores code-driven line items reads as either uninformed or evasive, and it sets up a change-order fight later. The most common code triggers that quietly add scope and cost:

• Ice barrier. In regions with a history of ice damming (designated in the code's climate table), the IRC requires an ice barrier on asphalt shingle roofs from the eave to at least 24 inches inside the exterior wall line — and on slopes of 8/12 and steeper, measured at least 36 inches up the slope. The ICC's IRC Chapter 9 (roof assemblies) is the controlling text. If your climate triggers it, it is not optional and it should be a visible line item.
• Drip edge. The IRC requires drip edge at eaves and rakes on shingle roofs, lapped at least 2 inches, with underlayment over the drip edge at eaves and under it at rakes. Leaving it off is a common inspection failure.
• Deck/sheathing condition. Bad sheathing found at tear-off is real, common, and a frequent dispute. Price it as a stated unit cost in the scope so it never becomes a surprise.
• Resilience upgrades. In storm-exposed markets, customers may ask about a sealed roof deck or enhanced deck nailing. The IBHS FORTIFIED Roof program specifies ring-shank deck nailing in a tighter pattern and a sealed roof deck as a secondary water barrier. If a homeowner wants that standard, it is a different — and clearly priced — scope.

Safety language and OSHA

Proposals and any access language should never imply that unsafe or untrained roof access is acceptable. OSHA requires fall protection for construction work six feet or more above a lower level — guardrails, nets, or personal fall-arrest systems — under 29 CFR 1926.501. Your proposal should reflect that you control the work conditions, not the homeowner, and certainly should not invite a customer onto their own roof to "take a look."

Proposal review checklist

PROPOSAL REVIEW — BEFORE SEND
[ ] Correct property address + customer name
[ ] Scope matches internal scope statement
[ ] Exclusions stated plainly (bad deck = unit price)
[ ] Measurement basis + date noted
[ ] Material: exact line + color + quantities
[ ] Code line items present (ice barrier / drip edge / vent)
[ ] Payment terms + schedule
[ ] Change-order process described
[ ] Warranty language matches actual mfr + workmanship terms
[ ] No unsupported lifespan / savings / insurance claims
[ ] No "lifetime/full coverage" without defined conditions
[ ] Photos + records attached
[ ] No placeholder links, stale dates, or internal notes left in

A reviewer should be able to set the proposal next to the takeoff, the photos, and the scope and confirm they agree. When the proposal is tied to the same property record sales and production already use, that comparison takes a minute instead of a phone-call scramble.

How the estimate changes by region and roof type

The five practices hold everywhere, but the content you put inside them shifts with climate and building type. An estimate built for a snow-belt residential gable and one built for a Gulf-coast hip roof are filled out differently even though the process is identical.

Cold climates

In the snow belt, ice damming drives scope. The ice barrier line item is not a nicety — it is code-triggered, it adds material and labor at every eave, and on steep roofs it runs farther up the slope. Ventilation also matters more, because poor attic ventilation is a root cause of ice dams, and a customer who keeps having ice problems after a re-roof will blame the contractor. Build the ice barrier and ventilation language into the scope explicitly, and price the extra eave material rather than absorbing it.

Hurricane and high-wind coasts

Near the coast, deck attachment and water intrusion drive scope. Customers and insurers increasingly ask about resilience standards, and the IBHS FORTIFIED Roof program is the reference point: ring-shank nails in a tighter pattern, with the spacing tightening further within a few feet of gables and at hip corners on homes close to the ocean, plus a sealed roof deck acting as a secondary water barrier. If a homeowner wants that level, it is a different scope with re-nailing labor, taped deck seams, and documentation requirements — price and describe it as its own option, not a vague upgrade.

Hail and high-UV regions

In hail country, impact rating and the difference between repair and replacement come up constantly, and storm timing matters for which roofs are even worth approaching. In high-UV regions, material aging accelerates, which sharpens the value of an accurate roof-age estimate when you decide where to spend outbound effort. This is the kind of regional judgment a targeting tool supports rather than replaces: knowing which roofs in a hail swath are old enough to have likely been worn by the storm helps a canvasser spend time on the right streets, while the actual condition call still happens on the ladder.

Commercial and multifamily vs. residential

Low-slope commercial work changes the labor plan more than the material math. Crane or hoist staging, roof-access coordination, occupied-building restrictions, night or weekend windows, interior protection, and tie-ins to existing membrane all belong in the labor section, and they are exactly the items that turn a thin bid into a loss. Multifamily adds tenant sensitivity and phasing. The estimate for these jobs leans heavily on the labor-and-overhead practice, because the dollars hide in mobilization and sequencing, not in the shingle count. Write the operational plan in plain words first, then price it — a reviewer who can read the crew-day and access assumptions can catch a money-losing schedule before it ships.

What to ask before you sign off on an estimate

Before an estimate becomes a proposal, a reviewer should be able to get a clean answer to each of these. If any answer is a shrug, the estimate is not ready.

• Is the area sloped or footprint, and what pitch factor was applied?
• What is the waste percentage, and does it match the roof's complexity?
• Are starter, drip edge, hip-and-ridge, and ice barrier counted off real edge footage?
• Is the labor priced on a burdened crew-day rate, not the base wage?
• Does the sell price reflect a true margin (divide), rather than only a markup (add)?
• Is bad-deck handling stated as a unit price in the scope?
• Do the warranty and any insurance language match what the company can actually stand behind?
• Is the measurement current, with a source and a date?

Putting the five together: a practical 2026 estimating standard

Every estimate that leaves your office should be able to answer five questions before it goes:

1. What exactly are we promising? (scope + exclusions)
2. What measurements and evidence support the quantities? (dated takeoff, pitch-corrected, waste tied to geometry)
3. What labor, overhead, and risk assumptions support the price? (burdened labor, real markup-to-margin math)
4. What records will explain this estimate later? (the file checklist)
5. What will the customer actually read? (the claim review)

Those questions beat chasing a perfect template. Templates help only when the team fills them with current evidence and specific assumptions. You still need judgment, a review step, and a record system that keeps the estimate connected to the property.

Common estimating mistakes to design out

• Pricing off the footprint. The roof is bigger than the building. Correct for pitch every time.
• A global waste percentage that double-counts starter, ridge, and valley. Pick one method and stick to it.
• Confusing markup with margin. Divide by (1 − margin); don't add.
• Pricing labor on the wage, not the burdened rate. Comp and GL are real costs of the hour.
• A stale measurement that looks precise. Date and source everything.
• Burying bad-deck cost. State it as a unit price up front.
• Warranty and insurance language the company cannot stand behind. Review before send.
• No comparison to actuals. If you never compare estimated to actual, you never get better.

A note on estimating software and aerial measurement

Measurement reports and estimating platforms are genuinely useful — they speed takeoffs and reduce arithmetic errors. They do not replace a field visit where access, layers, penetrations, or structural condition matter, and they do not make a pricing or scope decision for you. Treat the report as one input with a source and a date, confirm whether its area is plan or sloped, and keep the human review steps. The tool that prices the job is not the same as the judgment that wins it profitably.

One more habit ties it all together: review estimated against actual after the job closes. The five practices build a good estimate, but the loop only closes when you compare the crew-days you assumed to the crew-days you spent, the squares you ordered to the squares you installed, and the original scope to the change orders. Do that on a handful of jobs each month and your assumptions stop being folklore and start being calibrated. The estimator who reviews actuals quietly out-prices the one who trusts memory, because next quarter's labor factor is grounded in last quarter's reality. That feedback loop is what turns a process into an edge.

When scope, measurements, labor, records, and claims are handled the same way on every job, the estimate stops being a one-time price document and becomes a working control for the business — one that helps sales sell accurately, production plan correctly, the office understand job performance, and the customer trust what they are buying. That is the whole point of estimating discipline in 2026.

Sources checked: June 18, 2026.

FAQ

What should every roofing estimate include?

Every roofing estimate should identify the property and roof sections, the system or service type, the scope of work with explicit exclusions, the measurement basis and its date, the exact material line and color with quantities, labor and access assumptions, payment terms, the change-order process, warranty language that matches the actual manufacturer and workmanship terms, and your contact and license information. The strongest estimates also attach dated photos and note how bad sheathing will be priced if it is found at tear-off.

Why should measurements be kept separate from pricing in a roofing estimate?

Separating them makes the estimate reviewable. When measurements and pricing blur together, no one can tell whether a number moved because the roof got bigger, the material changed, the waste factor changed, or someone adjusted the margin. Keep the takeoff in its own fields — areas, slopes, edge footage, penetration counts, source, and date — and pricing in separate fields. A manager can then check the measurement and the price independently and approve the estimate with confidence.

How do I correct a roof measurement for pitch?

Multiply the plan or footprint area by the slope multiplier for the roof's pitch. The multiplier equals the square root of 1 plus (rise/12) squared. Common values: 4/12 is about 1.054, 6/12 is about 1.118, 8/12 is about 1.202, and 12/12 is about 1.414. So a 1,000-square-foot footprint on a 6/12 roof is roughly 1,118 square feet of actual roofing. Order and price by sloped area, then add waste; never price off the footprint.

What waste factor should I use for a roofing estimate?

Tie waste to the roof's geometry rather than a flat reflex number. A simple gable with long straight runs usually needs about 5 to 10 percent. A moderate roof with some hips, valleys, and dormers runs roughly 10 to 15 percent. A cut-up roof can need 15 percent or more, and tile can run up to about 20 percent because of breakage. Always calculate waste on the pitch-corrected sloped area, and avoid double-counting starter, ridge, and valley if you price those separately.

What is the difference between markup and margin in roofing job costing?

Markup is added on top of cost; margin is a share of the sale price, and they are not the same number. If a job costs 10,000 dollars and you add 20 percent markup, you sell at 12,000 and your actual margin is only about 16.7 percent. To keep a true 20 percent margin you divide cost by (1 minus 0.20) and sell at 12,500. The rule to remember is divide, don't add — and wire it into your template so no one has to recall it under pressure.

How do I account for labor cost correctly in a roofing estimate?

Price labor on the burdened rate, not the base wage. The loaded cost adds payroll taxes, workers' compensation, general liability, and other employer costs, often in the range of 25 to 35 percent on top of wages, with workers' comp frequently the largest single overhead item for roofers. Write the labor plan in job language first — crew-days, access method, working hours, cleanup, dry-in — then apply your burdened crew-day rate to the realistic number of days, including slower steep-roof hours.

What code requirements commonly add line items to a roof replacement?

The most common are ice barrier, drip edge, and deck repair. In regions with an ice-damming history, the IRC requires an ice barrier from the eave to at least 24 inches inside the exterior wall line, and at least 36 inches up the slope on 8/12 and steeper roofs. Drip edge is required at eaves and rakes. Bad sheathing found at tear-off should be priced as a stated unit cost. In storm markets, customers may also request FORTIFIED-style sealed decks and enhanced nailing, a separate priced scope.

What records should a roofing business keep for each estimate?

Keep the signed proposal, the internal scope with exclusions, the dated measurement and its source, photos labeled by area and date, the material selection with quantities, the labor and access plan, key customer communications, change orders with approvals, the payment schedule, permit notes, warranty documents, and job-completion notes that compare actual to estimated. The IRS expects records that support income and expenses for as long as needed to prove a return, and these same records let you compare estimated to actual costs so future bids get more accurate.

How does a tool like RoofPredict fit into the estimating process?

It sits before the estimate, in targeting and recordkeeping rather than pricing. RoofPredict tells contractors which roofs are likely due — pairing an estimated roof-age range with storm physics modeled per individual home — so mailers and CRM re-engagement focus on worn roofs rather than brand-new ones. It keeps property history, photos, and prior notes attached to the address so each future estimate starts informed. It does not inspect roofs, diagnose damage, certify remaining life, set your price, or decide insurance coverage; those remain judgment calls for your team.