Part 4 · Building and finishing

When it starts going wrong

This chapter is short on purpose, and careful about the line between what is established and what is not. If you are here because something is going wrong, start by lowering the temperature.

First: stop escalating

The instinct when a project goes wrong is to confront, threaten, or stop paying immediately. All three feel like taking control. But impulsive escalation and unilateral action can create new problems of their own, and before a consequential step — terminating the contract, withholding a disputed payment — proper legal guidance is the safer first move, because what you may do depends on your contract and your facts.

There is a practical reason too. A dispute still has to be resolved with the same person, and a relationship that has turned hostile makes everything harder to resolve. Meanwhile everything you do in anger becomes part of the record that someone else may later read.

There is also the fear underneath the question, and it deserves a straight acknowledgement: people worry that complaining will cause the contractor to walk off and leave the house open. That fear is real and it is why so many homeowners say nothing for far too long. Handling it calmly and in writing, early, is Lior’s preferred way to keep the issue clear, documented, and less escalated.

Second: document, properly

Documentation is not preparation for war. It is what makes a calm resolution possible, because it creates a record both sides can refer back to.

• Photograph everything, dated, with enough context to show where it is in the house. If you have been keeping the Chapter 12 habit, you already have most of this.
• Write down what happened and when — dates, who said what, what was agreed. Do it the same day, while it is accurate.
• Keep every message. Do not delete a thread because it was unpleasant.
• Keep the paperwork together — contract, change orders, payment records, preliminary notices, everything.
• Record what you have paid and when, against what the schedule said.

Third: put it in writing

Once something is a real problem rather than a question, it should exist in writing. Not an aggressive letter — a factual one.

The second version is clearer to act on and easier for a third party to understand later. It also gives the contractor a clear route to fix the problem, which is what you actually want.

This matters for another reason too: CSLB will ask whether you formally notified your contractor of your concerns, and publishes a sample letter for the purpose. A complaint that begins with a clear written notice is on stronger ground than one that does not. (Source: CSLB, filing a construction complaint, cslb.ca.gov. Verified August 10, 2026.)

Fourth: allow a reasonable opportunity to correct

Where it is appropriate, give them a genuine chance to put it right. Many problems can be corrected once they are clearly identified and the contractor has a reasonable opportunity to respond.

“Where appropriate” is doing real work in that sentence. There are situations where it is not appropriate, and that is a judgment about your circumstances that this guide cannot make for you.

The official routes that exist

If direct resolution does not work, California has established channels. Here is what they are, accurately.

What is not established — stated honestly

This section separates rights the research could verify from claims it could not establish. Three things were checked against official sources and did not turn out the way people commonly assume.

One last piece of perspective

If you are reading this chapter as part of the guide rather than because something is wrong, the useful thing to notice is where the real protection sits.

The checks in Chapters 6 through 10 — checking properly, meeting people, getting comparable proposals, reading the contract, understanding the payment rules — are meant to reduce the chance of reaching this stage. The routes described here are real, and they are formal options available after a problem has developed.

That is the honest hierarchy: pre-hire checks are the first layer of protection; formal remedies are the backup.

Your free documentation log

Start it now, whatever state your project is in. A log started early is easier and more accurate than one reconstructed later from memory.

Still not sure about something? Ask AI Mickey — it knows this guide and where you are in it.

The whole guide, on one page

Before you go on

Many problems can be addressed before a formal route becomes necessary, but some situations do require formal or legal help.

The final chapter covers the closeout stage of a completed project: how to tell when a job is genuinely finished, what to collect before the final payment, and the records you may be glad to have later.