Manage house-building changes before they become surprises

Give every change a clear path

Changes can arise from household preferences, missing information, site discoveries or product availability. The existence of a change does not by itself show that a project is badly managed. The important question is whether the team identifies it, assesses the consequences and obtains the decisions required before implementation. This guide offers an editorial method for keeping that process understandable. It does not interpret a construction contract, decide who must pay or determine the legal notice needed in a particular jurisdiction. Have those matters explained by an appropriate adviser using the actual agreement and current local rules.

New Zealand's MBIE guidance says proposed variations to consented work should be raised with the building consent authority, which determines how they are handled. That is a specific regulatory context, not a universal Commonwealth procedure. Your own project may involve different authorities and approval mechanisms. Start by recording the applicable jurisdiction, the relevant approvals and the people authorised to communicate with each authority. Then connect that regulatory route to the contractual route. A household's enthusiasm for a change, a designer's technical view and a builder's price are separate pieces of the decision; none should silently stand in for the others.

Distinguish a request from an instruction

A homeowner should be able to ask about an option without accidentally creating confusion about whether work is authorised. Agree the language and channel used for enquiries, pricing requests and formal instructions. Mark a proposal as under review until the appropriate person approves it through the agreed process. This is an administrative habit, not a claim that labels alone determine contractual meaning. Ask your adviser how your communications interact with the actual contract. The safest practical approach is to avoid ambiguity and promptly correct a message if someone has understood it differently from what you intended.

Create a change register with a unique reference and a short description. Record who raised it, when, why and what part of the house it affects. Link the original question, photographs, drawings and correspondence. A list entry should help someone unfamiliar with the conversation understand the issue. Avoid vague descriptions such as kitchen change when several unrelated decisions are involved. Separate the appliance selection, cabinet alteration and service modification if they need different reviews. The register should remain manageable, but it must be precise enough to track the consequence of each decision through design, cost, time and delivery.

Explain the reason before choosing a solution

Write down what problem the proposed change is intended to solve. A product might be unavailable, a site condition might differ from an assumption or the household may have reconsidered how a room will be used. Those triggers call for different discussions. If the reason is unclear, the team may price an attractive alternative without resolving the underlying problem. Ask whether retaining the original design remains possible and what information would help decide. The household should understand why a change is needed before becoming attached to the first solution presented.

Distinguish a necessary response from an optional improvement without prejudging legal responsibility. A builder may propose an alternative that improves sequencing; a designer may identify a performance issue; the household may request a different finish. Record each person's explanation accurately. Do not use the change register to assign blame before the facts are established. Where responsibility is disputed, keep the factual description and seek advice through the appropriate route. A clear account of the trigger, existing requirements and proposed response helps the team assess options even when the commercial position has not yet been agreed.

Ask for a complete technical review

Identify the drawings, specifications and products affected. Ask the relevant professional who else needs to review the proposal. A change in one room can affect structure, services, enclosure or compliance elsewhere. Do not assume that something visually small is technically minor. Equally, do not burden every simple choice with an invented approval chain. The project team should explain the review proportionate to the actual change. Record the reviewer, the information considered and any conditions attached to acceptance. A response that says acceptable subject to further detail is not the same as a completed design instruction.

If an alternative product is proposed, obtain the exact product information rather than relying on a generic claim of equivalence. Ask which requirements must be met and who assesses them. Appearance, dimensions, installation, maintenance and compatibility can all matter. The manufacturer may be able to provide technical information, but that does not necessarily settle its suitability for the whole design. Keep promotional descriptions separate from the evidence used by the professional reviewer. Once a proposal is accepted, update the project documents so the actual selection is visible to those ordering, installing and later maintaining it.

Understand approval and documentation requirements

Ask the team whether the change affects an existing permission, consent, inspection plan or other authority record. The answer should come from the relevant professional and authority process, not from an online generalisation. A change may require information beyond a revised drawing, and timing can matter. Record who will contact the authority, what will be submitted and what evidence of the decision will be retained. Do not assume that a verbal site conversation has resolved every documentation requirement. Ask for the written record appropriate to the process and keep it with the change.

The household should be told what work is affected while the review is underway. Avoid interpreting this guide as a universal instruction to stop an entire site for every question. The builder and advisers need to manage the actual programme and applicable obligations. Your role is to ensure the proposed change is not treated as fully authorised merely because other work continues. Identify the affected area, the current status and the decision needed. This makes it easier to preserve progress elsewhere without losing control of the unresolved issue or creating pressure to accept an incomplete proposal.

Request the whole cost and time effect

Ask for a written explanation of the proposed commercial adjustment in the format required by the agreement. Understand what it includes and excludes. A change can involve more than the price difference between products: design work, cancellation, rework, delivery or altered sequencing may be relevant. Whether those amounts are payable is a contractual and legal question, not something this guide decides. The practical purpose of the request is to make the proposal intelligible before the household commits. If the adjustment is provisional, record the basis and what remains to be established.

Ask how the change affects the programme and the dates dependent on it. Avoid accepting a statement such as no problem as a substitute for a clear discussion where timing matters. A product available from stock today may require a different installation sequence; an apparently simple revision may need a further review. Record the builder's stated effect and any qualifications. Update the household's own arrangements when appropriate, including accommodation or deliveries. If the cost or time position is disputed, seek advice promptly and preserve notices and correspondence. Do not let an unresolved issue vanish from the forecast simply because nobody has agreed its final value.

Keep approval authority clear

List who can approve household expenditure and who can issue instructions under the project agreements. Those may be different roles. If a designer administers part of the process, understand the limits of that appointment. If the homeowners are making decisions jointly, establish how one agreed response reaches the team. Conflicting messages can create avoidable uncertainty. A contractor should not have to infer which household member's latest text overrides another person's email. Keep significant approvals in the agreed record and identify the reference so everyone can connect the decision to the proposal being accepted.

Before approval, check that the decision package is complete enough for the commitment. Does it describe the scope, identify technical acceptance, explain any authority requirement, state the commercial position and make the time effect understandable? The detail needed varies, but the questions remain useful. If urgency prevents a fully resolved proposal, obtain appropriate advice about the available options and their risks. Do not invent a casual emergency exception to the contract or local rules. Record what was decided, by whom and on what basis, including any outstanding qualification that the team has expressly acknowledged.

Communicate the approved change to the workface

An approval in the homeowner's inbox does not automatically reach the person performing the work. Ask who updates the drawings, orders, schedules and site instructions. Identify superseded information and confirm that affected participants receive the revision. This is particularly important where a product has already been ordered or part of the work completed. The team needs to reconcile the approved decision with physical progress. A change register marked approved is still incomplete if nobody has translated it into the current documents and delivery instructions.

Ask for confirmation appropriate to the work rather than a blanket assurance that everyone knows. A revised cabinet drawing, updated product schedule or recorded site instruction may provide the relevant link. The form depends on the project. Keep implementation status separate from approval status: approved, ordered, installed and checked are different states. If the change is later abandoned or replaced, preserve that history so an old approval does not reappear as a live instruction. A disciplined record protects both the household and the professionals from having to reconstruct the sequence after memories and messages have diverged.

Learn from the pattern of changes

Review changes periodically to see what they reveal about the project. Repeated late selections may indicate that the household needs earlier information or a simpler decision process. Repeated clashes may point to a coordination gap. A series of unavailable products may call for procurement discussion. Do not reduce the review to counting changes or blaming whoever raised them. Some changes prevent a worse outcome. Focus on whether the process identifies issues early enough and whether the cause can be addressed before similar decisions affect more work.

Consider an illustrative request to move a bathroom fitting after service locations have been established. A useful process asks why it is being moved, identifies the exact proposal, obtains technical and commercial review, checks any approval consequence and communicates the agreed revision. It does not assume that the change is free, unlawful or impossible. At project completion, reconcile the register with final drawings, invoices and handover information. Close abandoned proposals explicitly and identify any unresolved matters for appropriate advice. The resulting record should explain the house that was actually delivered, including the decisions that shaped it, rather than leaving future owners to decipher fragments of correspondence.

Make rejected proposals easy to recognise

A household may investigate several alternatives before choosing one. Keep rejected or deferred proposals visibly separate from the approved change. An attractive sketch can reappear weeks later in a message and be mistaken for a live instruction if its status is unclear. Record the decision and a brief reason, particularly where the alternative was rejected for an interface, procurement or approval consequence. This saves the team from repeating the same assessment and helps explain the project to a new participant. Do not delete the context when it remains relevant to understanding the final choice.

Use a status that reflects the decision accurately. Deferred means the question may return; rejected means the proposal is not proceeding; withdrawn means its originator no longer requests it. Define the labels if necessary. If a rejected option is revived, treat it as a new review against the project's current information. Costs, availability and physical progress may have changed. An earlier assessment should not be reused automatically as if the house were still at the same stage. This small administrative discipline prevents an old possibility becoming an accidental commitment merely because its documents remain easy to find.

Reconcile the change register with the finished house

Near completion, review approved changes against the final information pack and the work actually delivered. Ask whether product schedules, drawings and operating documents reflect accepted substitutions. Identify changes that were approved but not implemented, and obtain a clear explanation of their final commercial and contractual status through the appropriate adviser. Keep unresolved matters visible. The aim is not to reopen every decision but to ensure that the project record tells a coherent story. A final invoice or a set of keys does not by itself explain which proposed changes became part of the house.

For each significant implemented change, retain the decision reference and the evidence needed for future understanding. A maintenance provider may need to know the installed product; a future designer may need the approved layout; an owner may need the reason for a special operating instruction. Preserve those useful records without passing private contractual correspondence indiscriminately to others. Ask the team which documents belong in the house information pack and which should remain in the household's private project archive. Change control has done its job when the finished house and its records agree, including a transparent account of matters still requiring resolution.

Sources & review notes

Primary sources checked 2026-11-12. Practical examples and working methods are editorial guidance. Confirm project-specific requirements with the named authority; source pages can change.