How to Get Customer Decisions on Time: Selections, Deadlines, and What They Block

Several project records can look similar. They do different jobs.

The decision record asks a question and preserves the answer. It does not change the agreement.

That distinction matters. "Which grout color do you want?" can be a decision. "Add a second shower niche" changes the work. That goes through a change order before the changed work starts.

A project update is different again. "Cabinets arrived today" needs no answer. Put news like that in the customer update, not in Decisions needed.

A useful decision request has five parts.

One decision should contain one answer.

"Bathroom selections" is too broad. Tile can be decided while the vanity is still open. If they live in one request, you cannot tell what has actually been settled.

The Blocks field is what turns a reminder into a production record.

"Needed by October 19" tells you when an answer was due.

"Blocks waterproofing and tile layout" tells you why it mattered.

If a disagreement later develops about why the work moved, the useful history is not merely that the customer had an unanswered question. It is that the question was posted on a date, needed by a date, and identified the work waiting behind it.

There is no universal number of days before construction when every selection should be due.

Work backward from the work that needs the answer.

For a field decision:

For something that must be purchased:

The needed-by date is the point where waiting longer starts to threaten the work behind it. It is not simply the day you would like an answer.

Michael C. Stone, a builder and remodeler with more than six decades in the industry and author of Profitable Sales: A Contractor's Guide and Estimating Construction Profitably, recommends prioritizing selections according to the job schedule. He also argues against putting decisions off when they can reasonably be settled earlier.

That does not mean asking the customer to choose everything on day one.

Example

The date is an illustration. The method is the rule.

Do not make a customer solve a design problem you can narrow for them.

Use Pick one when there is a short list of real choices:

"Back wall is easier to reach. Side wall keeps the niche farther out of the direct spray."

Michael C. Stone's selection method in Profitable Sales, Chapter 5, is to help an indecisive customer by narrowing the question and often presenting two useful choices at a time instead of an overwhelming list.

That does not mean every Clamp decision must contain exactly two options. Two is Stone's sales method, not a software rule or industry benchmark.

Use Open answer when you genuinely need information rather than a choice you can predefine:

Or:

If replacing it would alter the signed scope, the answer is not authorization to install a new window. It tells you to prepare a change order.

Use the smallest record that actually has the authority you need.

Stone discusses unsettled selections and allowances in Estimating Construction Profitably, Chapter 15. He recommends getting selections settled before contracting where practical, and using clearly defined allowances when a decision genuinely cannot be made before the contract.

The allowance does not replace the decision record. One says what money the agreement carries. The other records what the customer eventually chose.

And neither replaces a change order.

A change, however small, gets its own signed change order before the changed work.

If removed work is part of that change, the credit follows the change order guide. If the customer is selecting within a signed allowance, follow the allowance terms already in the proposal.

Do not turn an overdue decision into an argument. State the record.

Clamp emails the customer once, when you post the decision, with its needed-by date. It does not send reminders after that, so the follow-up is yours: send it before the date if the answer is close to holding up work, and again when the date passes.

If the schedule has already been affected:

Do not invent a universal penalty such as "every customer delay moves the project one day."

Your contract decides how customer-caused decisions affect contractual time, notices and any related cost. Have that language reviewed for your state.

The operational record should establish: when the question was posted; when the answer was needed; what it blocked; who owed the answer; when the answer arrived; what actually changed in the schedule.

Then update the jobsite schedule to reflect what really moved.

An overdue decision is also different from an overdue change order. If the customer has chosen something that requires a change to the agreement, the next blocker is the signed change order, not merely the customer's portal answer.

A customer answer is not always the end of the record.

After the answer comes in, review it and resolve the decision with a short note that states the final result.

Or:

The resolution note should be the clean answer a person can understand later without rereading the whole discussion.

Withdraw a decision when the question no longer matters:

If the customer changes their mind after the decision is resolved, first ask whether the new answer changes the agreement.

That protects the history.

This is the published 5×8 bathroom. The dates below are illustrations showing the decision process, not standard selection lead times.

Decision 1: niche location

The contractor posts:

The customer chooses Back wall.

Resolution:

No price or scope changed. No change order is needed.

Decision 2: faucet becomes a change order

The signed job carries the agreed faucet or allowance terms. The customer answers with a different fixture that changes what is being purchased and raises the sold price.

The portal answer records what they want. It does not authorize the change.

The contractor replies:

The decision has done its job. The contractual change now belongs in the change order.

Decision 3: grout color goes overdue

The grout color is posted with a needed-by date and:

The date passes without an answer. Clamp now shows the decision as overdue.

The contractor sends:

When the answer comes in, resolve it and update the jobsite schedule for whatever actually moved.

The useful record is not "the customer was late."

It is: