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 the walkthrough. Do not reuse them in a 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

   Identity fields connect the agreement to the licensed business, customer and project record.

2. 02

   2. Project and location

   Example

   Kitchen remodel at a fictional California residence.

   Why it matters

   The agreement needs to make clear which project and property the parties are talking about.

3. 03

   3. Contract price

   Example

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

   Why it matters

   The price should be clear enough to reconcile with the payment schedule and later changes.

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

   A useful scope shows both the promised work and important boundaries.

   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

   Material detail helps connect what was sold to what will be ordered and installed.

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

   Timing belongs in the same project story as scope, sequencing and 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

   The general rule compares $1,000 with 10% of the contract price and uses the smaller amount, subject to applicable statutory exceptions.

   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

   The point is not these particular amounts. Each real payment should connect to the work, services, materials or equipment represented by the applicable stage.

   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

   A sample should show where notice work happens without 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

    The warning and payment documentation are part of the contractor/customer paper trail.

    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 uses different cancellation frameworks in different 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

    Project changes need their own visible approval trail rather than disappearing into texts, calls or field notes.

    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

    Signing and delivery are workflow events, not just blank signature lines.

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

    Supporting documents should have a clear relationship to the main contract rather than floating separately.

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

    A coherent record helps show what the parties agreed to and what changed over time.

Illustrative progress-payment schedule

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

On a real contract, the payment schedule must be built around the actual work, services, materials and transaction requirements. 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

ContractBuilderAI is designed to replace retyping a sample with a guided project workflow. Contractors enter the real project information, use draft assistance for scope and materials, organize payment stages, review checkpoints, manage change orders, use e-signature and retain an 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.