How to write a construction proposal
that wins the job.

A strong construction proposal has eight parts, in roughly the order the client reads them. None are optional.

• Cover and introduction — the client's name, the property address, the date, and two or three sentences restating the project in your own words. "Full renovation of the second-floor bathroom as discussed on March 4" beats a generic opener every time.
• Scope of work — what you will do, broken down by area or trade: demolition, framing, rough plumbing, electrical, finishes. Specific enough that a stranger could tell what is and is not in the job. Name materials and grades where they drive cost.
• Exclusions — what you will not do, stated just as plainly. More on this below, because it is the most underwritten section in the trade.
• Pricing — the number, itemized or summarized. The next section takes a position on which.
• Payment schedule — deposit, stage payments tied to milestones, and balance on completion. A client should never be surprised by an invoice; the schedule they signed told them it was coming.
• Timeline — start date, key milestones, and completion, with the honest caveats: permit approval, lead times, weather.
• Terms — the short version of how you work: how change orders are handled and priced, warranty, what happens if payment is late. Keep it readable; save the boilerplate for the contract.
• Signature block — a place to accept, with a date. A proposal without one is a brochure.

Exclusions win disputes before they start

Every contractor has eaten the cost of something the client "assumed was included." Permits, dumpsters, paint, appliance hookups, landscaping repair after trenching — the assumption is always in the client's favor, and the argument always happens after the money is committed. A written exclusions list settles that argument in advance, in writing, while everyone is still friendly. It deserves the same care as the scope itself: walk the job in your head and write down everything adjacent to the work that you are not pricing.

Exclusions are also where change orders are born. When the client later wants the excluded item after all, you are not renegotiating a vague promise — you are pricing an addition to a documented scope, which is an easier conversation and a better-paid one.

The proposal that arrives complete within a day of the site visit reads as the work of a contractor who will run the job the same way. The one that arrives ten days later, after a reminder call, has already told the client something too. The process below is built to make next-day sending routine rather than heroic.

1. Capture everything on site. Photos of every area, measurements, and the client's own words — especially the throwaway lines ("we'd love to do the deck someday") that become alternates and future work. The proposal will quote these words back; that is what "they really listened" feels like on paper.
2. Draft scope and exclusions the same day. While the visit is fresh, write what is in and what is out. This is the thinking part; everything after it is assembly. Left overnight, the details blur and the exclusions list is the first casualty.
3. Price from your own numbers. Your labor rates, your supplier prices, your markups — applied to the scope you just wrote. If your rates live in a spreadsheet or in your head, this is the slow step; whatever moves them into a reusable form pays for itself on every subsequent bid.
4. Add the payment schedule and timeline. Tie stage payments to milestones the client can verify — "rough-in complete" not "week four" — and give a start date conditional on deposit and permits.
5. Read it once as the client. Would a non-builder understand what they are getting, what they are not, and what they owe when? If any answer is no, fix it before it becomes a phone call.
6. Send it with a way to sign. A document the client can accept from their phone closes faster than a PDF that needs printing. Then put the follow-up on your calendar, because most proposals die of silence, not rejection.

An honest answer: a template solves the smallest part of the problem.

What a template gives you is the skeleton — the eight sections above, in order, so nothing gets forgotten at 9pm. That has real value: if a blank page is what stands between you and sending proposals, take a template and use it. The structure in this guide is one.

What a template cannot hold is everything that actually wins the job. It does not know your labor rates or your supplier prices, so the pricing section is still a spreadsheet exercise. It does not write in your voice, so the intro reads like everyone else's who downloaded the same file. And it cannot know your exclusions, because those come from your scars — the specific things your trade, your region and your history have taught you to fence off in writing. A template with someone else's exclusions is worse than none, because it looks complete while protecting you from the wrong risks.

So the real work is not finding a better template. It is getting your rates, your standard exclusions and your way of describing work into a form you can reuse — so that each new proposal is assembled from your own materials rather than written from scratch. Some contractors build that in documents and spreadsheets; some use purpose-built tools. Either way, that library of your own numbers and language is the asset. The template is just the box it ships in.