Concrete work has two features that make a written contract non-negotiable: the product is permanent, and the process is weather-dependent. Most concrete disputes, the crack argument, the “I thought that included the walkway” argument, the rain-delay argument, are contract failures, not workmanship failures. Here’s what a residential concrete contract needs to say.
Scope: what you’re building, and what you’re not
Describe the work in measurable terms: location, dimensions, thickness, reinforcement (mesh, rebar spacing, or fiber), base depth and material, finish type, joint layout, and sealer if included. Then the section that prevents most disputes, exclusions, stated plainly: existing concrete removal priced separately if not listed, no drainage correction beyond stated grading, no sprinkler or utility line relocation, no landscaping repair beyond the work path. Every exclusion you write is an argument you won’t have.
The cracking clause, because concrete cracks
Every concrete contractor knows it: concrete cracks, and control joints exist to decide where. Customers don’t know it, and the contract is where they learn it, before the first hairline appears. Include a plain-language disclosure: minor shrinkage cracking is inherent to concrete, control joints are placed to direct it, and hairline cracks that don’t affect structural integrity are normal and not a defect. Define what your warranty does cover, structural failure, excessive settlement, scaling from a bad mix, and for how long. This one paragraph converts the most common concrete complaint from a warranty fight into an expectation you set.
Weather: delay rights and cold/hot placement limits
You cannot pour responsibly in heavy rain, on frozen subgrade, or in extreme temperature without protective measures, and your contract should say that scheduling is weather-dependent, with dates adjusted as conditions require and the customer notified. Give yourself the explicit right to postpone a pour when conditions would compromise the work. The alternative, pouring into weather to keep a date, produces the slab you’ll be arguing about for years. If cold-weather protection (blankets, accelerators) or hot-weather measures may be needed at extra cost, state how that’s handled.
Payment schedule tied to visible milestones
Residential concrete commonly structures as: deposit at signing (often enough to cover materials), a progress payment at completion of prep or the pour, and the balance at completion. Tie each payment to something the customer can see finished, and state the final payment terms in dates, not vibes. Include your change-order rule in the same section: any work outside the written scope is priced and approved in writing before it’s performed. Concrete’s discovery problems, bad subgrade, buried debris, an old slab thicker than anyone knew, make that clause earn its space regularly.
The boilerplate that isn’t optional
License number where required, proof of insurance on request, who pulls any required permit, a start window rather than a single date, cleanup and haul-off responsibility, how long the quoted price is valid (concrete pricing moves, 15 to 30 days is common), and both signatures with dates. None of it is exotic. All of it is the difference between a professional agreement and a handshake with a dollar amount attached.
Make the paperwork the fast part
A contract this complete sounds like an evening of writing, and that’s exactly why most small outfits skip it, until the dispute that costs more than every evening combined. The fix is templates: your standard scope language, cracking disclosure, weather clause, and payment structure, reused on every job with the specifics filled in. That’s what we’re building with Punchlist for independent contractors and small crews: quotes that carry your standard terms, e-signature on the spot, and change orders from the phone with photos attached. Join the waitlist to get it when it ships.