# Keep selections moving without chasing every decision

Selections process communication tells buyers what has to be decided, who records each choice and which field activity waits on approval. Use the same status terms from the [allowance schedule](/glossary/allowance-schedule/) through purchasing. Record the exact product, review its effects and get the required confirmation before any instruction goes to purchasing or the field.

## What should buyers understand before the first showroom visit?

Selections are construction inputs, not a decorating side project. A faucet choice affects rough plumbing. A tile layout changes quantities, labor and backing. An appliance package affects electrical, ventilation and cabinetry. Buyers need that connection before they start comparing finishes.

Start with an orientation tied to the current plan set, the spec and the [allowance schedule](/glossary/allowance-schedule/). Explain the categories, the decision owners, the approved vendors, the documentation method and the field release points. Say which choices are included, which may create a change and which need compatibility review. For the allowance language itself, send buyers to [the allowance conversation guide](/articles/sales-process/explaining-allowances-to-buyers/).

Do not hand over a calendar full of unexplained dates. A useful schedule tells the buyer which field event follows each decision. "Plumbing approved before rough-in release" means more than a date floating in a spreadsheet.

### Which words need exact definitions?

Define the status terms once and use them everywhere. "Chosen" might mean a buyer voiced a preference. "Approved" means the authorized people accepted the documented item. "Released" means purchasing or the trade received the approved information. "Ordered" means the order was placed. "Received" and "verified" come later. Blur those labels and you hide risk.

## How should the selection schedule follow the build?

Build the schedule backward from field dependencies, not from a sequence of showroom appointments. Cabinet dimensions affect framing and mechanical coordination. Exterior colors may face an architectural review. Long-lead items need attention before the interior finishes that feel more immediate to the buyer.

| Selection record | Required communication | Field control |
| --- | --- | --- |
| Category and location | Which space and plan condition the choice serves | Current plan reference |
| Allowance or specification basis | What the working documents currently include | Approved source document |
| Decision deadline | Why that point matters to the build | Release or installation dependency |
| Buyer approval | Exact item, finish, quantity and known variance | Written authorization |
| Release status | Who received the approved information | Purchasing or trade confirmation |
| Exception status | Substitution, conflict or missing information | Named owner and next action |

A visible schedule changes the weekly conversation. Instead of "Have you picked tile?" the team can say which room, which decision, which document and which downstream activity is waiting.

## What is the clean approval path for each decision?

Every category runs the same basic path, even when the people and the documents differ. The path stops a showroom note, a text message or a job-site conversation from becoming an accidental field instruction.

1. **Prepare the decision.** Confirm the plan location, the spec basis, the allowance category and any known constraints.

2. **Present the options.** Give the buyer enough context to compare fit, availability and the effect on related work.

3. **Record the exact choice.** Capture model, finish, quantity, location and the supporting document or image.

4. **Review the effect.** Check compatibility, scope, allowance variance and field timing with the responsible roles.

5. **Get written approval.** Keep the approval attached to the same record the team will release.

6. **Release and confirm.** Send the approved information to purchasing or the trade, then record receipt.

7. **Close the loop.** Update the buyer-facing status and name the next decision.

If the choice changes scope, route it through [change-order communication](/articles/sales-process/change-order-communication/). The selection tracker should reference that record instead of carrying a loose note about an expected adjustment.

## How do you communicate missed deadlines and substitutions?

State the condition before the consequence. Name the missing decision, the affected work, the available response paths and who has to decide. Do not issue a generic warning that the whole build could slip. Explain the actual dependency the team can verify.

Handle substitutions with the same discipline. Record why the original item is unavailable or unsuitable, what the proposed replacement changes and which related selections need another look. A visually similar item can carry different dimensions, installation needs or maintenance requirements.

When the field uncovers a conflict, stop the affected release and mark the record as an exception. Do not overwrite the original approval. Keep what was approved, document the conflict and create a new reviewed decision. That record matters when the buyer later asks why a room differs from an early selections sheet.

### How should weekly updates handle selections?

Use a short block with four headings: approved this week, waiting on buyer, under builder review and coming next. Link to the controlled record instead of restating every detail in an email. The [weekly buyer update method](/articles/sales-process/weekly-buyer-updates/) keeps selections beside field progress and upcoming access needs.

## Where can AI agents support the selection team?

We run Claude and Codex agents that compare meeting notes with the tracker, draft reminders from approved deadlines, flag incomplete records and prepare a weekly status summary. A person sets the rules and reviews every output.

No agent approves a product, calculates an unverified effect, changes the controlling spec or sends a field release on its own. Document the roles and review gates first through the [AI operations stage](/process/ai-operations/). The [AI guide for builders](/guides/ai-for-home-builders/) explains where reviewed assistance belongs.

For the full sales sequence around these handoffs, see the [sales-process library](/articles/sales-process/).

## What do builders ask about selection approvals?

### Should buyers have direct access to the full internal tracker?

Give buyers a view of selection decisions, approvals and upcoming work. Keep purchasing notes, private trade details and internal controls in the internal selection record.

### What counts as a completed selection?

A completed selection has the required product details, review and approval for its next controlled action. A stated preference alone does not authorize purchasing or field release.

### Who should own the master selection record?

Assign one accountable role to maintain the master selection record and its version history. Design, estimating, purchasing and field roles approve the information each governs.

### How should a site conversation be handled?

Record a selection discussed on site as a request or a note. Use the normal review and written approval path before anyone issues purchasing or field instructions.