Change Orders in Custom Cabinetry: Get Every Small Change on Paper

The Morgans signed off on their kitchen drawings in March: fourteen cabinets, a tall pantry, an island, quartz countertops from a separate fabricator. In week three, Mrs. Morgan texts a photo from Instagram: "Could the island have one of these waterfall ends?" The designer, standing in a showroom with another client, replies "should be fine!" In week four, Mr. Morgan calls the shop and asks to move the sink twenty centimetres to the left so it's centred under the window. The foreman hears about it in passing.

On install day, the plumbing rough-in doesn't match the new sink position, the island needs an end panel nobody ordered, and the invoice doesn't include either. The Morgans remember being told it was fine. The shop remembers a text and a hallway conversation. Somebody is going to eat the cost, and somebody is going to be unhappy about it.

Every cabinet maker I've talked to has a version of this story. The problem isn't that clients change their minds; in custom work, that's normal and often good. The problem is that changes arrive through every channel except the one where they'd be priced, drawn, and approved. That's something AI is surprisingly good at fixing.

How big the problem is

There's no precise study of change orders in small cabinet shops, but the broader construction data is clear about where rework comes from.

Custom cabinetry is especially exposed. A change that sounds small ("can it be a bit deeper?") ripples into the drawings, the cut list, the CNC program, the material order, the hardware, the countertop template, and sometimes the plumber's or electrician's work. If one of those links doesn't hear about the change, it shows up as rework on site.

How changes arrive, and what they need to become

The left column is how people naturally talk. You won't change that, and you shouldn't try too hard: clients who feel they can casually mention ideas are clients who are engaged with the project. The right column is what the shop needs. The gap between them is pure information work.

The change capture flow

The second step is where the value is. The hardest part of change management in a small shop isn't pricing or paperwork. It's noticing that a message contains a change at all, especially when it's the fourth paragraph of a friendly email about the delivery date. A language model reads every message on the project with the same attention, which no busy designer can.

What the model is looking for

It helps to see what "spotting a change" means in practice. The model reads each message against the approved drawings and specification and sorts it roughly like this:

The model will get some of these wrong, mostly by flagging too much. That's the right way to be wrong: a designer dismissing a false alarm takes seconds, while a missed change costs a day on site. After a few weeks, the corrections tell you which phrasings your clients use, and the flags get sharper.

What a change note contains

The first line is underrated. When a dispute comes up six weeks later, being able to show the client their own message, next to the change note they approved, ends most arguments before they start.

The appliance trap

One kind of change deserves special mention because it causes so much rework: appliance swaps. A client switches to a different fridge, oven, or dishwasher model mid-project, often because of a sale, and mentions it in passing.

This is a good job for AI in two steps. First, the model spots the change ("we went with the Bosch after all"). Second, it pulls the new model's specification sheet and extracts the installation dimensions, ventilation clearances, and hinge requirements, then compares them with the opening in your drawings. The output is a short note for the designer: "New fridge needs 5 mm more width and 50 mm more depth for ventilation than the opening allows." The designer checks it and decides. That comparison takes a person twenty minutes of PDF hunting; it takes the software seconds.

What undocumented changes cost

That box doesn't include the rework: the wrong-sized cabinet built twice, the install day that runs into a second day, the plumber called back. Those costs are often larger than the unbilled changes themselves.

Start with a change audit

The best first step isn't building anything for live projects. It's looking backwards.

Take the message threads, emails, and notes from your last twenty finished projects and let a model go through them looking for change requests. Then compare what it finds with the change orders you actually issued and invoiced. The gap between the two lists is your number. It tells you, in your own currency, whether a change capture system is worth building, and it usually turns up a few surprises that settle the question.

Tools it has to fit

Cabinet shops run design and production software like Cabinet Vision, Microvellum, KCD, Mozaik, or 2020 Design, often alongside a CRM or project tool. The change capture system doesn't replace any of that. It reads the project's communication, produces change notes, and tracks approval. Updating the drawings and the CNC output stays with your designers, in the software they already use.

The communication channels need some housekeeping. Change capture only works if project messages are in places the system can read: a shared inbox per project, a business messaging account rather than a designer's personal phone, call notes in the CRM. That's a good habit regardless of AI, because it's also what lets someone else pick up a project when the designer is on holiday.

Questions cabinet makers ask

Won't formal change orders annoy clients?

Clients are annoyed by surprises on the final invoice, not by a short note that says "here's what that change costs, reply yes to go ahead". Most appreciate knowing the price before they commit, and the note is quick to approve.

What about changes decided on site during install?

Those are the most important ones to capture, because they're the easiest to forget. An installer's thirty-second voice memo ("client wants the filler on the left, not the right, added a panel") can become a draft change note automatically, to be priced back at the office.

Can it price changes by itself?

For standard items with a price in your book, it can propose a price. Anything custom, structural, or unusual goes to an estimator. The model's job is to make sure the estimator sees every change, not to replace their judgment.

Is this worth it for a two-person shop?

Try the change audit first. If it finds a few thousand in unbilled changes per year, a lightweight version pays for itself quickly. If it finds almost nothing, your current process works, and that's worth knowing too.

The rule of thumb

If it isn't written down and approved, it isn't a change. It's a future argument. Software can make sure every "can we just…" gets written down; you decide what it costs.

If you'd like to know what your last twenty projects would reveal, get in touch and I'll help you run a change audit. Change requests aren't unique to cabinetry: architects lose design decisions the same way, and construction site notes are where many of these changes first get mentioned.