Why the structure matters more than the file
Search for a free estimate template and you will find thousands of files. Most of them fail the same way: they are blank boxes with no guidance on what belongs in each one. The file format matters far less than the structure. A well-organized estimate wins jobs because it answers the customer's questions before they ask, and it protects you because the scope and terms are written down.
Below is the full structure, section by section, with what each field is for. Rebuild it in whatever tool you already use. Or skip the rebuilding: EstimateBook generates this exact structure automatically when you describe a job by voice, text, or photo on iOS or Android, and you edit every field before sending.
Section 1: the header
The header identifies both parties and the document itself. It is what turns a number on a page into a business record you can find later.
- Your business name, phone, email, and license number if your trade uses one
- Your logo, if you have one; it makes the document recognizable at a glance
- Customer name, job site address, and their contact details
- Estimate number, so follow-ups and invoices can reference it
- Date issued, which anchors the validity period in the terms
Section 2: job description and scope
Two or three sentences describing the work in plain language: "Replace the bathroom faucet and supply lines, haul away the old fixture." This is the scope the line items price out, and it is the first thing you both point to if there is a disagreement later.
Write it for the customer, not for yourself. If they cannot tell from this paragraph what they are paying for, the estimate is not done.
Section 3: itemized line items
Group lines logically: materials together, labor together, or group by phase of the job. Either works as long as nothing is hidden inside a vague lump sum.
| Field | What it is for |
|---|---|
| Description | One material or task in plain words the customer understands |
| Quantity | How many units: hours, square feet, pieces |
| Unit price | Your price per unit, from your real costs |
| Line total | Quantity times unit price |
Section 4: totals, markup, and tax
Below the line items, show the subtotal, any markup or discount you apply as its own visible line, the tax amount, and the grand total in bold. Tax rules vary by state and province, including what is taxed and at what rate, so verify the rules where the job is rather than assuming.
EstimateBook handles this with regional tax presets for all 50 US states plus DC and 10 Canadian provinces and territories, splitting materials and labor where the rules require it. You should still review the tax line on every estimate.
Section 5: terms
Terms are short sentences that prevent long arguments. Cover how long the estimate is valid, what is excluded from the price, how changes are handled, and your payment expectations such as a deposit or payment on completion.
- Validity: "This estimate is valid for 30 days from the date issued."
- Exclusions: work and materials not included, stated plainly
- Changes: "Additional work is priced and approved before it is done."
- Payment: deposit amount if any, and when the balance is due
An estimate is a starting point for agreement, and every draft, whether from a template or an app, deserves your review before it goes to the customer.
Section 6: acceptance and signature
End with an acceptance block: a line for the customer's signature, printed name, and date. A signed estimate turns your scope and terms into something both sides agreed to, and it gives you a clean trigger to schedule the work.
That is the whole template. To see it filled in with realistic line items and the reasoning behind each number, read the worked estimate example. For the broader method behind the document, start with the guide to writing an estimate.