How to keep a useful record of design changes

Record the decision, not every conversation

You do not need a transcript of each meeting. Start one list with a row for every change that could affect the agreed design, scope or price. Give it a short reference, date and plain description.

Add a status such as proposed, investigating, approved or not proceeding. That stops an idea discussed in passing from quietly becoming part of the job.

• What is changing, and what problem is it meant to solve?
• Who provides the next information or decision?
• What is its status, and when will it be checked again?

Point to the information that must move with it

Note the drawing number and revision, specification item and any estimate or programme that may need updating. If revised information has not been issued yet, say so.

Consider a hypothetical bedroom window moved to improve the furniture layout. The row might identify the floor plan, elevations and window schedule, then flag structure, weatherproofing, consent and price. A note saying 'move window' cannot do that work alone.

• Which document still shows the old decision?
• Who will revise it, and when?
• Who needs the revised information before acting?

Check the consequences before approving it

Before marking a change approved, ask the team to consider five things: design, consultant input, approvals, cost and timing. Not every change affects all five, but the record should show they were considered.

Write 'no confirmed effect' only when the right person has checked. If a cost is being prepared or the engineer has not responded, leave that point open. Visible uncertainty is better than a tidy but misleading list.

• Does the change alter another room, detail or product?
• Does a consultant need to review it?
• Does it affect a resource consent or building consent?
• What is the confirmed or estimated cost effect?
• Could it affect a submission, order, inspection or completion date?

Separate the three approvals

A design decision, a contract variation and approval to change consented work are not the same thing. MBIE advises keeping written records of construction decisions and changes. It also says a change to work listed in the building contract is a contract variation that should be put in writing, with price and timeline effects checked.

If the work has building consent, the building consent authority must be told about a proposed variation. It decides whether the change is minor and how it is recorded, or whether a formal amendment is required. Confirm the pathway before carrying out changed work.

Your register can point to these approvals, but it does not replace the notices, signed variations or council records the project requires.

• Design decision confirmed by the client and design team.
• Contract effect agreed using the building contract process.
• Consent pathway confirmed with the building consent authority where relevant.

Use a ten-minute change check

At an agreed checkpoint, sort the register by status. Close fully documented items. Give every open item one next action and one responsible person, then check the latest issued information matches approved decisions.

Keep superseded drawings, but make the current revision obvious. The point is to help the homeowner, designer, consultants and builder act on the same version of the project.

• Are proposed ideas being treated as approved?
• Are approved changes missing from current documents?
• Are cost, programme or consent questions still open?
• Does everyone know which information is current?

Make the record fit the project

A small alteration may need a simple table. A detailed new home may need a formal register managed with drawings, specifications and contract administration. Agree who maintains it and how decisions are authorised before the project becomes busy.

If you want a clearer way to manage decisions through design and construction, bring the question to a conversation with Modal Architecture. We can discuss your project stage and what a sensible record could look like.