What to Do When a Homeowner Keeps Changing Their Mind Mid-Job

You are three weeks into a kitchen renovation. The layout was agreed. The units were ordered. The electrician has already done first fix to the approved plan. Then the homeowner says: "Actually, I've been thinking — can we move the island to the other wall?"

This is not unusual. It is one of the most common frustrations in domestic building work, and nearly every tradesperson has a story about a customer who changed their mind repeatedly. The temptation is to get annoyed. The professional response is to have a process.

Why customers keep changing their minds

The customer is not trying to make your life difficult. Most of the time, they are changing their mind because:

• They are seeing the space for the first time. A kitchen that looked fine on paper feels different when the walls are stripped back and the old units are gone. The room looks bigger or smaller than they expected. Sightlines change. Ideas that made sense in theory do not work in reality.
• They are getting input from others. A partner, a parent, a friend who "knows about these things" has an opinion. The customer is caught between what they agreed with you and what someone they trust is now suggesting.
• They saw something on Pinterest or Instagram. This is increasingly common. Halfway through the project, they see a design they prefer and want to incorporate it.
• They underestimated the decisions involved. A kitchen involves hundreds of small choices — handles, tiles, socket positions, lighting, splashback material. Decision fatigue is real, and some customers cope by deferring choices and then changing them later.

None of this is malicious. Understanding why customers change their minds makes it easier to handle professionally rather than taking it personally.

The process that protects you

The variation process is the same four steps whether it is one change or twenty:

1. Customer requests the change. They tell you what they want. You listen and confirm you understand the request.
2. You price it. Work out the cost — materials, labour, any additional time — and present it clearly. Include the impact on the timeline.
3. Customer approves in writing. A text message, an email, or approval through your contract app. Not a nod on site.
4. You do the work. Only after approval. Not before.

This process works because it makes each change a conscious decision by the customer. They see the cost. They see the time impact. They decide whether it is worth it. Most customers, when they see the actual cost of moving the island to the other wall, either go ahead knowing the price or stick with the original plan. Either outcome is fine for you.

For the detail on how "can you just" requests fit into this process, see our guide on handling extras without losing money.

Setting expectations at the start

The best time to handle mid-job changes is before they happen. When you go through the contract with the customer at the start of the job, explain the variation process:

"Changes during the project are completely normal — I expect them. Here is how they work: you tell me what you want to change, I price it, and you approve it before I start. That way there are no surprises on either side."

This sets the tone. The customer knows that changes are welcome but that they have a cost. When the first change request comes, you can refer back to this conversation. It is not a new policy — it is what you agreed at the start.

A written contract with a variation clause formalises this. The clause states that any changes to the agreed scope will be priced separately and require written approval before work begins. One sentence in a contract saves hours of difficult conversations later.

What to do when changes affect the timeline

Changes do not just cost money. They cost time. And time impacts other customers, other commitments, and your scheduling for weeks ahead.

When pricing a variation, always include the time impact. "Moving the island means re-routing the plumbing and electrics. That adds three days to the timeline and pushes the completion from Friday to the following Wednesday."

The customer needs to know this before they approve. If they only find out at the end that the project overran by a week because of their changes, they will blame you. If they approved each change knowing the time impact, the extended timeline is their decision.

Keep a running total. After several changes, send a summary: "We have agreed three variations so far. The original price was £12,000 and the variations total £1,800, bringing the project total to £13,800. The completion date has moved from 14 March to 21 March." This keeps the customer informed and removes any surprise at the final bill.

The customer who will not stop changing things

Most customers make a handful of changes during a project. Some make dozens. When changes become constant, it is worth having a direct conversation:

"I want to make sure you're happy with the result, and I'm happy to accommodate changes — that's what the variation process is for. But we've had twelve changes in the last two weeks, and each one has a knock-on effect on the schedule and the budget. Can we set a cut-off point for changes on each section of the work? Once the kitchen layout is signed off, we lock it in. We can still make changes to things that haven't been started."

This is reasonable. It is not refusing to accommodate the customer. It is asking them to commit to decisions in a structured way so the project can progress. Most customers will respect this if it is framed as being in their interest — because it is. Constant changes extend the timeline and increase the cost, neither of which the customer wants.

Keeping records

Every change request and approval should be recorded. If you are using a contract app, this happens automatically. If not, keep a text thread or email chain for each variation.

At the end of the project, you should be able to show:

• The original scope and price
• Each change that was requested
• The price quoted for each change
• The customer's written approval
• The final total, broken down into original scope plus variations

This paper trail is your protection. If the customer disputes the final bill, you have a clear record of every decision they made. Without it, you are relying on memory — and memory is unreliable on both sides.

For the broader picture on managing scope changes across a project, see our guide on handling scope changes on building projects.

The bottom line

Customers changing their minds is not a problem if you have a process for handling it. Price every change. Get written approval. Keep records. Be consistent.

The trades who get burned by mid-job changes are the ones who absorb them quietly and then resent the customer. The trades who thrive are the ones who say "absolutely — here's what that costs" every single time.

TradeContract tracks every change in the chat and gets written approval before you lift a finger — so you get paid for every extra and the customer always knows the cost upfront. Try it free.