What to Include in a Contractor Estimate

There are two documents a contractor might send. One is a number and a sentence. The other is a document that answers the questions a customer was going to ask anyway, and closes the gaps a dispute would later find.

They take different amounts of effort and they win at different rates. Here's what belongs in the second one.

The header items that seem obvious

Your business name, license number where you're required to display it, address, phone, and email. The customer's name and the job address, which is often not their mailing address and causes confusion when it isn't stated. A date, a unique estimate number, and an expiry date.

The expiry date is the one people leave off. Material prices move, your schedule fills, and a customer resurfacing four months later expecting the same number is a conversation you can avoid with one line. Thirty days is common.

Scope, written as what you will do

This is the most important section and usually the thinnest. Scope should describe the work in enough detail that someone who wasn't at the walkthrough could read it and know what's being done.

"Bathroom remodel" is not scope. "Remove existing tub, tile surround, vanity, and flooring. Install new fiberglass tub unit, tile surround to ceiling height, 36 inch vanity, and luxury vinyl plank flooring. Relocate existing GFCI outlet to left of vanity" is scope.

Write it in the order the work will happen. It reads naturally, it doubles as a rough sequence for the customer, and it makes gaps easier to spot while you're writing.

Line items grouped the way a customer thinks

Somewhere between one lump sum and a four-page itemization of every fastener is the level that actually helps. Group by phase or by area, whichever matches how the customer experiences the job. Demolition, rough-in, materials by type, finish work, cleanup.

A lump sum asks for complete trust and gives a comparing customer nothing to compare. A hyper-itemized list reads as padding and nobody finishes it. Grouped categories show where the money goes without turning the document into a spreadsheet.

Where you're offering choices, present them as options with their own prices rather than burying an assumption. A customer who can see what the upgraded fixture costs makes the decision themselves, which is faster and produces fewer revisions than guessing on their behalf.

Exclusions, which prevent more arguments than inclusions

What is not in the price causes more disputes than what is. Customers assume generously, and silence reads as included.

• Permits and fees, if the customer is handling them
• Painting or finishing, if you're leaving the surface ready but not finished
• Appliances, fixtures, or materials the customer is supplying
• Work by other trades that has to happen before or after yours
• Repair of conditions found once existing material is removed
• Disposal, if it isn't included
• Restoration of landscaping or driveways affected by access

Exclusions feel negative to write and they're the cheapest insurance in the document.

Assumptions, especially about what you couldn't see

Every estimate rests on things you believe to be true and could not verify. Say them.

That the subfloor is sound. That the panel has capacity. That the walls are framed at standard spacing. That there's no asbestos or lead in material of that age. That access will be available during working hours.

Each assumption should say what happens if it turns out to be wrong. "Priced assuming existing decking is sound. Replacement, if required, billed at X per sheet, quoted before proceeding" converts a future argument into a signed agreement made in advance.

Schedule, payment, and warranty

Give a realistic start window and duration rather than a specific date you may not hold, and note what would move it: permit timelines, material lead times, weather, the customer's own decisions.

Payment terms should state the deposit, any progress payments and what triggers them, and the final payment condition. Milestones tied to observable events work better than calendar dates, since dates slip for reasons that have nothing to do with completion. Note that some jurisdictions cap deposits on residential work, which is worth checking once for where you operate.

Warranty deserves its own short section. What you cover, for how long, and what's excluded. Manufacturer warranties on materials are separate from your labor warranty and customers routinely conflate them.

Photos, if you have them

An estimate that references what you actually observed is more persuasive than one that doesn't, and it isn't close. A line noting the water staining visible in the crawlspace photo, or the slope shown in the yard photos, tells the customer their specific job was looked at rather than plugged into a template.

It's also documentation. Conditions photographed before work started have settled more disputes than any clause.

What this is really doing

Every section above is doing two jobs at once. It's making the estimate more persuasive, because a customer comparing three bids is largely comparing which contractor understood their job. And it's making it more defensible, because nearly every dispute traces back to something that was assumed rather than written.

The reason estimates don't look like this is time. Nobody writes exclusions and assumptions at nine at night after a full day on site. Which is the actual argument for having the scope drafted from your walkthrough notes and photos before you sit down, so the work in front of you is reviewing and adjusting rather than starting from an empty page and cutting the sections that felt optional.