Key takeaways
- Every selection is a build instruction, so an uncontrolled selection is a variation that was never priced, approved or programmed.
- Margin leaks in selections come from rework, downtime and out-of-sequence trade attendance, not from the selection item itself.
- A selections register with a named owner, a due date and a written confirmation status turns client decisions into a schedulable input.
- The clause that matters is not the size of the deposit but when a selection becomes binding, when the client may change it, and who bears the cost of change.
- Decisions left open past the point where the builder must order or book trades are the most expensive kind of open item on a residential job.
Selections are usually treated as a client service: a showroom visit, a colour board, a set of choices that get made somewhere between contract signing and lock-up. On the builder’s side of the table they are something else. Each selection is a build instruction. It determines what gets ordered, what gets installed, and when the trade that installs it can be on site. When that instruction is late, unclear or changed after the fact, the cost does not appear as a line item. It appears as downtime, rework, out-of-sequence attendance and a client who believes the price they signed is still the price they owe.
That is the margin leak. It is rarely one big mistake. It is a series of small, individually defensible decisions — a verbal confirmation here, a supplier order placed on an assumption there, a trade stood down because the tile was not chosen — that together erode the margin you priced into the job. The work of managing selections is the work of turning client decisions into schedulable inputs before they become variations.
This article covers the selections process and its commercial impact. It does not cover how to price a variation once it exists, how to quote a job in the first place, or how to sequence trades on the programme. Those are separate problems. The problem here is the handover point: how a client’s choice becomes a confirmed instruction, and what it costs when that handover is not controlled.
Why a selection is a build instruction, not a preference
When a client chooses a tap, a tile, a benchtop or a door handle, they are not expressing a preference. They are specifying a product that has a lead time, an installation method, a substrate requirement and a trade that installs it. The choice determines whether the waterproofing detail in the wet area still works, whether the cabinetmaker can build to the confirmed dimension, and whether the electrician roughs in for the appliance the client eventually buys.
Builders who understand this treat the selections register as part of the construction documentation, alongside the drawings and the specification. Builders who do not treat it as documentation end up discovering selections on site, in real time, from the client’s mouth. By then the rough-in is done, the sheeting is on, and the cost of the decision has multiplied.
The mechanism is simple. A selection made before the relevant trade is programmed costs the difference in product price. A selection made after the trade has attended and left costs the difference in product price plus the cost of bringing the trade back. A selection made after the substrate is closed costs the difference plus the rework plus the delay to every trade behind it. The item itself may be trivial. The timing is what makes it expensive.
The four places margin leaks out of a selections process
Margin does not leak evenly. It leaks at predictable points, and each one has a different fix.
Open selections that never close
An item that is discussed but never confirmed is an open item. On a well-run job, open items have owners and dates. On a leaking job, they sit in an email thread and everyone assumes someone else is chasing. The client thinks they have decided because they said so in passing. The builder thinks the client has not decided because nothing is in writing. The trade cannot order. The programme starts to compress.
Selections that change after the order
Once a supplier order is placed or a subcontract is let on a confirmed selection, a change is not a selection anymore. It is a variation with a cancellation cost, a restocking cost and a programme consequence. If the contract does not make clear when a selection becomes binding, the builder wears that cost or fights about it.
Selections that were never priced
Some selections look like inclusions but are not. A client choosing a tap from the specified range is within contract. A client choosing a tap outside the range is a change to the scope, and if it is accepted without pricing, the builder has just donated the difference. This is where an uncontrolled selections process overlaps with the variation process, which is why the two need to be linked rather than run separately.
Selections that are confirmed verbally and ordered on assumption
Verbal confirmation feels efficient. It is not. If the client later changes their mind, or denies the conversation, the builder has no record and no basis to recover the cost. The supplier has an order, the trade has a booking, and the builder has an argument.
The mistake that costs the most. Allowing a trade to be booked or a supplier order to be placed on a selection that has not been confirmed in writing. Everything downstream — the cancellation fee, the rework, the downtime, the client dispute — flows from that one decision, and it is almost always made to save a day.
The selections register: what it contains and who owns it
A selections register is not a colour schedule. It is a control document. At minimum, each entry needs the selection item, the trade or supplier it affects, the date by which the decision must be made for the programme to hold, the person responsible for chasing it, the current status, and the date the client confirmed it in writing.
The decision-by date is the part most builders skip, and it is the part that protects the margin. A date that is tied to the programme — before the rough-in, before the cabinetmaker measures, before the tiler is booked — tells the client exactly what is at stake. A date that is tied to a calendar month tells them nothing and gets ignored.
Ownership matters as much as content. If the site supervisor owns selections, they will chase them when they are already late, because chasing is not their primary job. If the client owns them without a builder-side owner, nothing happens until the builder asks. The register needs one person on the builder’s side who is accountable for the status of every line, and that person needs the authority to escalate before the date passes, not after.
How a selection moves from a client idea to a build instruction
- Register the itemThe builder lists the selection, the trade it affects and the date it must be decided by.
- Present the optionsThe client is shown the specified range, the inclusions and the effect each option has on the contract sum.
- The client decidesA choice is made in writing, with the date recorded against the register entry.
- The builder confirmsThe decision is checked against the specification, priced if it changes the scope, and confirmed back to the client in writing.
- The trade is bookedThe confirmed selection is issued to the supplier or subcontractor so it can be ordered and programmed.
- The selection is closedThe register entry is marked closed and the signed confirmation is filed with the contract documents.
Setting the rules before the client needs them
The time to agree how selections will be managed is at contract signing, not when the first item is late. The contract and the pre-start documentation should answer four questions in plain language.
- When does a selection become binding on the client?
- When may the client still change it, and what does that change cost?
- What happens if the decision-by date passes?
- Who bears the cost of a delay caused by an open selection?
These are contractual questions, and the answers sit in your own contract documents and in the disclosure documents the client receives. The builder’s job is not to draft the law; it is to make sure the client has actually read and understood the mechanism before they are under pressure to choose a tile. A client who knows that a late change costs them money and time makes different decisions from a client who believes everything is negotiable until it is installed.
This is also where the selections process connects to the broader client relationship. The way you communicate about a delayed decision is the same way you communicate about a delayed payment or a defect. Builders who handle selections well tend to handle the rest of the project well, because the underlying skill is the same: converting a conversation into a written, dated, actionable record. The PointCPD article on dealing with neighbours and site access covers that skill in more depth.
Running the selections meeting so it produces decisions
A selections meeting that ends with “we’ll think about it” has failed. The purpose of the meeting is to close items, not to present options. That means the builder running the meeting needs to know, for each item, what the specified range is, what the upgrade costs, what the lead time is, and when the decision is needed. If any of those are missing, the meeting produces conversation instead of decisions.
Practically, the meeting should be structured so that the items with the earliest decision-by dates are dealt with first, while the client is fresh. Items that affect the same trade should be grouped, so the client understands the cumulative effect of their choices on that trade’s programme. Any item that changes the specified scope should be flagged as a potential variation at the meeting, priced before the client leaves the room if possible, and confirmed in writing afterwards.
The output of the meeting is not a set of preferences. It is a set of register entries with dates and confirmations. If the client cannot decide on an item, the register records that the item is open, the date it must close, and the consequence of it not closing. That record is what protects the builder when the consequence arrives.
Checks that keep selections from leaking margin
- Every selection has a named person responsible for chasing it.
- Every selection has a decision-by date tied to the programme, not to a calendar month.
- The client has been told in writing what happens if the date passes.
- Any selection that changes the specified scope has been priced before it is accepted.
- The confirmation the client signs matches what was actually ordered.
- The supplier or subcontractor has received the confirmed selection in writing.
- Closed selections are filed with the contract documents, not left in an email thread.
Connecting selections to variations without doubling the work
Selections and variations are not the same thing, but they meet at a specific point: when a client chooses something outside the specified scope, or changes a selection after it has become binding. At that point the selection process hands over to the variation process.
The efficient way to manage this is to make the handover automatic. A selection entry that is outside the specified range should trigger a variation notice, not a conversation. The notice should describe the change, state the effect on the contract sum and the programme, and require written acceptance before the change is ordered. If the client accepts, the selection is updated and the variation is recorded. If the client does not accept, the selection stays within the specified range and the register reflects that.
Builders who run selections and variations as separate systems end up doing the work twice and losing the connection between them. Builders who link them find that the selections register becomes the early warning system for variations. The PointCPD article on spotting scope creep deals with what happens once the variation is triggered; the selections register is what triggers it early enough to be priced properly.
Worked example: a builder in western Sydney
A builder in western Sydney is running a knockdown-rebuild. The contract includes a specified range of floor tiles, and the client has a decision-by date for the tile selection that falls before the screed is laid. The register entry is owned by the builder’s office administrator, and the site supervisor has a copy of the date in the programme.
Two weeks before the date, the administrator sends the client a written reminder with the specified range, the lead time for each option, and the effect on the programme if the decision slips. The client does not respond. One week before the date, the administrator calls, then confirms the call in writing. The client says they are still deciding.
The date passes. The screed is due. The builder issues a written notice that the tile selection is now on the critical path, that the tiler’s booking will be released if the selection is not confirmed by a stated date, and that re-booking the tiler after release will be a variation. The client confirms a tile from the specified range the next day. The tiler attends as programmed. No margin is lost.
Now consider the same job with no register. The supervisor assumes the client will choose before the screed, because that is what usually happens. The screed is laid. The client chooses a tile that requires a different substrate preparation. The tiler arrives, cannot proceed, and leaves. The substrate is reworked. The tiler is re-booked at a later date, which pushes the wet area and delays the cabinetmaker. The client believes the tile choice was within their rights and disputes the extra cost. The builder absorbs the rework, the downtime and the supervision time, and the relationship with the client is damaged. The margin on the job is gone, and the builder cannot point to a single decision that caused it — only to a process that did not exist.
What to do on the next job
Start the register before the contract is signed, or at least before the pre-start meeting. List every selection the job requires, the trade it affects, and the date it must be decided by. Give every line an owner on the builder’s side. Put the decision-by dates into the programme so the supervisor can see them coming.
At the pre-start meeting, explain the mechanism to the client: what a selection is, when it becomes binding, what happens if the date passes, and how changes are handled. Get their acknowledgement in writing. Then run the selections meetings to close items, not to present options, and confirm every decision in writing the same day.
Finally, review the register weekly alongside the programme. An open item with a date inside the next fortnight is a risk to the programme and to the margin. Treat it the same way you would treat a late delivery or a trade shortage. The cost of chasing a selection early is a phone call. The cost of chasing it late is the margin on the job.
For builders who want to go deeper into the commercial side of running a residential building business, the PointCPD course catalogue includes modules on project management and margin control, and the guide to how NSW builder CPD works explains how those modules fit the annual requirement. If you are new to the platform, start at the PointCPD home page.
Questions builders ask
What is a selections register and why does it matter?
A selections register is a control document that lists every client selection, the trade it affects, the date it must be decided by, the person responsible for chasing it, and the status of the decision. It matters because it turns a client’s preferences into schedulable build instructions with dates attached. Without it, selections are discovered on site and become unpriced variations.
When should the client make their selections?
Each selection should be decided before the trade or supplier that depends on it needs to order or attend. That date is set by the programme, not by a calendar month. The builder should work backwards from the relevant trade’s start date and give the client a decision-by date that protects that sequence.
What happens if a client misses a selection deadline?
The contract and pre-start documents should state the consequence in plain language. Typically the builder issues a written notice that the selection is now on the critical path, that a trade booking may be released, and that re-booking or rework will be treated as a variation. The client should have acknowledged this mechanism before the deadline passed.
How do selections relate to variations?
A selection within the specified range is not a variation. A selection outside the range, or a change after the selection has become binding, is a variation. The selections register should trigger a variation notice automatically at that point, so the change is priced and accepted in writing before it is ordered.
Can a builder charge for a selection change after the order is placed?
Whether the builder can recover the cost depends on the contract terms and on when the selection became binding. If the contract makes clear that a confirmed selection is binding and that later changes are variations, the builder has a basis to recover cancellation, restocking and programme costs. If the terms are silent, recovery is much harder.
Who should own the selections process on a residential job?
One person on the builder’s side should be accountable for the status of every register line, with the authority to escalate before a date passes. On many jobs this is an office administrator or contract administrator rather than the site supervisor, because the supervisor’s primary role is on site. The supervisor still needs visibility of the decision-by dates through the programme.
Sources
- Flood risk management manual · NSW Government
- Construction begins on NSW’s first 3D-printed social housing project · NSW Government · 2024-11-11
- Managing the risk of falls in housing construction: code of practice · Safe Work Australia
- Model Code of Practice: Managing psychosocial hazards at work · Safe Work Australia
Published 18 September 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
