A construction change order moves the price, the schedule or both. Custom builders who record each approval with a name and a date close the dispute before it starts.
A construction change order is a written amendment to a signed construction contract. It records a change to the scope of work, the cost, the schedule, or all three, and it takes effect once both parties approve it. On commercial projects those parties are usually the owner, the general contractor and the architect. On a custom build they are the builder and the family who will live in the house.
That second case is where the paperwork tends to come apart. A homeowner choosing finishes is not administering a contract. They ask a question during a Saturday walkthrough, get an answer, and assume the matter is settled. The builder assumes the same thing. Neither writes anything down, because in the moment there is nothing that looks like a transaction. It was a conversation.
Six months later the kitchen goes in with the wrong handles, and both sides remember that conversation differently.
Custom building runs on choices made after signing. Finishes, fixtures, a layout tweak, an upgrade the client saw somewhere, the request that arrives while everyone is standing in the half-built kitchen. Each of those is a change order in everything but name, and each one moves a price, a date, or both.
On a commercial project that event has a shape. There is a template, a contract administrator, and a numbered document that goes round for signature. On a custom build the same event arrives as a text message on a Tuesday evening.
The gap is not effort. It is that nobody has decided where these things live. In a small team the process is often whoever remembered to send a confirming email, and that person is not always in the room. Decisions get made over WhatsApp, agreed by nodding on site, and stored in somebody's memory. When that somebody leaves, the history of the project leaves with them.
Tracking it by hand costs twice. Someone has to notice the decision, write it up, price it, chase the answer, and file the result somewhere the site team will look. That is not a workflow. It is a part-time job nobody was hired for, done in the evening, by the person least able to spare the hour.
An undocumented approval costs money at the exact moment it is questioned. Between the materials, the labor and the second visit, a wrongly ordered kitchen costs several thousand euro before anyone mentions goodwill.
The damage is rarely one large dispute. It is the slow version: a change here, a misremembered agreement there, each one absorbed rather than argued, each one quietly taken out of the margin on that project.
An approval given in WhatsApp comes apart because the message carries the answer but not the thing it answered. The chat holds a yes. It does not hold the specification, the price, the deadline, or the version of the drawing everyone had in mind.
That is why the tool that fixes this is not a better chat. It is a place where the choice itself carries its price, its deadline and the name of whoever approved it, so the approval and the thing approved cannot drift apart.
The failure is predictable. A client asks about an upgrade on a Tuesday evening. Someone answers with a number. Nobody records which of the three quotes that number belonged to. When the invoice arrives, both sides are arguing about a message instead of reading a record.
Chat is fine for the question. The answer belongs somewhere it can be produced again.
A recorded sign-off carries four things: what changes, what it costs, what it does to the schedule, and who approved it on which date. Anything less is a note. With those four, the change order stops being a story two people tell differently and becomes a document that answers for itself.
The mechanics are ordinary. Each choice becomes its own item. The client opens it, sees the specification, the drawing, the price impact and the deadline, and approves it. Their name and the date attach to that approval and stay attached. The site team works from the approved version, and only that version.
The value shows up twice, and the second time is the one nobody plans for. The first is at the moment of the change, when the price is agreed before the order goes to the supplier instead of after. The second is at handover, when a client questions an invoice line eighteen months later and the answer is a document rather than an argument about who said what in March.
| Approval in a conversation | Recorded sign-off | |
|---|---|---|
| Where it lives | A phone call, a site visit, an email thread | The project record, attached to the decision it belongs to |
| Who can find it | Whoever was in the room | Anyone on the project, years later |
| What it proves | What each side remembers | The exact specification that was approved |
| What the client saw | A verbal description | The spec, the drawing, the price and the deadline |
| Cost when questioned | Rework, a second visit, an argument | An approval with a name and a date on it |
A homeowner should not need training to approve a choice they have already made. That objection comes up in every conversation with custom builders, and it is fair: the people signing off on a kitchen are not going to learn software for the privilege.
So the approval has to be one action. A notification arrives, it opens on the one thing that needs deciding, and it closes. No login maze, no manual, no second system to remember. The work of structuring the decision sits with the builder. The act of approving it stays as small as it can be.
It also has to survive the site. Custom building happens in half-finished rooms, not at desks. When a client asks whether the island can move three feet left, the useful version is logging it, pricing it and sending it for approval before anyone has left the room.
Ziggu records each decision inside the project it belongs to, with its price, its deadline and the approval that closed it. The team runs the build. The client sees and signs off on the parts that involve them, and both are looking at the same record.
Across four countries, more than 2,500 companies use Ziggu to run roughly 30,000 active projects, with more than 42,000 clients logging in to follow their own. The tools that carry this work are decisions and approvals, and the same problem seen from the messaging side sits in what replaces WhatsApp for client communication on site.
The first change order that closes without an argument makes the case on its own.
