California Home Improvement Contract Example: An Annotated Contractor Walkthrough

Before you read the example

Everything on this page is fictional. The contractor, homeowner, project facts, dates, amounts and descriptions are invented to illustrate structure and workflow.

This is not a contract, legal form or legal advice, and it is not a substitute for the current statute, CSLB guidance or project-specific legal review.

Real jobs vary. Depending on the kind of work, the buyer and how the sale happened, a different statutory framework or exception may govern, so the contractor has to settle which rules fit the actual transaction before anyone signs. Check the current text of B&P §7159, CSLB's home improvement contract guidance, the B&P §7159 statute guide, the contract template guide and the 15-point contract checklist.

Fictional project snapshot

These values exist only for this walkthrough, so leave them out of any real agreement.

Annotated example: how the contract information fits together

1. 01

   1. Contractor and customer information

   Example

   Example Remodeling Co. (fictional) and Jordan Homeowner (fictional), with the contractor's license field represented by a fictional placeholder.

   Why it matters

   These fields tie the agreement to a specific licensed business, a specific customer and one project record.

2. 02

   2. Project and location

   Example

   Kitchen remodel at a fictional California residence.

   Why it matters

   Nobody should have to wonder which house, or which room, the contract covers.

3. 03

   3. Contract price

   Example

   $48,500 project price. Any finance charge, if one existed, would be identified separately.

   Why it matters

   Later on you'll reconcile this number against the payment schedule and any changes, so it needs to be unambiguous from day one.

4. 04

   4. Scope of work

   Example

   Remove existing cabinets and counters; install new cabinets, counters and sink; patch and paint affected wall areas; appliances excluded unless later added by written change.

   Why it matters

   Notice the exclusion. Saying what isn't included is often what prevents the argument later.

   Review California contract requirements →
5. 05

   5. Significant materials and equipment

   Example

   Shaker-style cabinets, quartz countertops and an undermount sink, with project selections tracked in the supporting materials schedule.

   Why it matters

   When the cabinets arrive, someone will compare them to what was sold. Specific material detail makes that comparison easy.

6. 06

   6. Start and completion timing

   Example

   Expected start January 12, 2027; expected completion March 20, 2027. Both dates are fictional.

   Why it matters

   Dates aren't a separate topic. They have to make sense alongside the scope, the sequencing and the payment stages.

7. 07

   7. Down payment illustration

   Example

   For this $48,500 fictional project, the walkthrough uses a $1,000 down payment under the general California cap, while recognizing that actual exceptions and transaction facts must be checked.

   Why it matters

   Under the general rule you compare $1,000 with 10% of the contract price and use whichever is smaller. On a price this size, that is the $1,000 figure, subject to any statutory exception that applies.

   Review the down-payment guide →
8. 08

   8. Progress-payment illustration

   Example

   Five fictional later stages totaling the remaining project price: demolition and rough-in $7,500; cabinet delivery and installation $12,000; countertop stage $9,000; finish work $9,500; final stage $9,500.

   Why it matters

   Don't copy the numbers. Copy the logic: on a real job, each payment should line up with the work, services, materials or equipment its stage represents.

   Review the progress-payment guide →
9. 09

   9. Notice and disclosure checkpoints

   Example

   Before signature, the workflow flags insurance status, CSLB information, change-order information, mechanics-lien material and the applicable cancellation paperwork for review.

   Why it matters

   The example shows where notice work happens. It deliberately avoids pretending one generic notice package fits every transaction.

10. 10

    10. Mechanics lien warning

    Example

    The contract package includes a checkpoint for the required mechanics-lien warning and the project's related lien-release workflow.

    Why it matters

    Both the warning and the payment paperwork end up in the paper trail between contractor and customer.

    Review the mechanics-lien guide →
11. 11

    11. Cancellation paperwork

    Example

    The example leaves the cancellation notice as a transaction-specific checkpoint to confirm before signature rather than assuming a universal deadline.

    Why it matters

    California has more than one cancellation framework, and which one applies depends on the circumstances.

    Review the cancellation-rights guide →
12. 12

    12. Change-order example

    Example

    Customer requests under-cabinet lighting after the original agreement. The contractor documents the changed scope, price and timing in a written change order before the changed work begins.

    Why it matters

    A quick yes on the phone is easy to forget. A signed change order leaves a record both sides can point to.

    Review the change-order guide →
13. 13

    13. Signatures and customer copy

    Example

    Contractor and customer complete the signing step, dates are recorded and the completed signed customer copy is delivered before the covered work begins.

    Why it matters

    Signature lines on a page don't finish the job. Someone has to sign, date the signatures and get the customer a copy, in the right order.

14. 14

    14. Attachments and incorporated documents

    Example

    The fictional record references a kitchen plan and materials-selection schedule only if those documents are actually made part of the agreement.

    Why it matters

    If a plan or schedule matters, the contract should say how it fits. Otherwise it's just paper in a folder.

15. 15

    15. Contract record and audit trail

    Example

    The signed agreement, later change order, signing history and supporting project records stay connected to the same fictional project.

    Why it matters

    If a question comes up months later, a connected record shows what was agreed and what changed along the way.

Illustrative progress-payment schedule

This schedule is fictional and educational. It is not a recommended payment schedule for a real project.

Notice how the stages follow the order a kitchen actually comes together. On a real contract, build the schedule from the actual work, services, materials and transaction requirements instead. Review the progress-payment guide →

What an example can show — and what it cannot decide

The example shows the structure. ContractBuilderAI turns your actual project details into a guided contract workflow.

Use the example with the California resource library

From fictional example to your project

Instead of retyping a sample, you'd start from your own job in ContractBuilderAI. Enter the real project information, get draft assistance for scope and materials, set up payment stages, work through review checkpoints, handle change orders, send for e-signature and keep the audit trail.

ContractBuilderAI helps organize the workflow. The contractor remains responsible for the final agreement and for confirming which requirements apply to the project.

Primary sources

• California Legislature — Business and Professions Code §7159
• Contractors State License Board — What Is a Home Improvement Contract?
• Contractors State License Board — Contracts and Binding Agreements

Building California contracts should not start from a blank page.

ContractBuilderAI is opening a California private beta on November 1, 2026 for licensed home improvement contractors.