# Set selection deadlines the field can actually use

A useful selection deadline is tied to the date a verified decision has to reach purchasing and the field, not a vague week on a buyer calendar. Build each deadline backward from the earliest field need: rough-in information, approval, pricing, ordering, delivery and checks. Then show the consequence of a missed decision before it disrupts the job.

## Why do selection deadlines belong in the construction schedule?

Selections are production inputs. A plumbing fixture sets rough-in locations. An appliance package changes electrical service, cabinet openings and ventilation. A tile pattern changes takeoffs, substrate prep and labor. Treat those choices as a design-side checklist and their effect on the field disappears.

The construction schedule shows when work is expected. The selection schedule shows when each approved decision has to be in hand to support that work. Those are different dates. If the site needs a fixture spec for rough-in, the deadline cannot sit at the install date.

Start with the current plan set, the specifications and the [allowance schedule](/glossary/allowance-schedule/). The [allowance schedule review](/articles/process-and-documents/allowance-schedule-explained/) covers how to reconcile categories before release. Use the same category names in every document. If the plans say "primary bath," the tracker does not say "owner suite bath" unless the cross-reference is unmistakable. Small naming mismatches become real ordering errors.

### Which date does the buyer see?

The buyer decision date, with an explanation of what it protects. Internal procurement dates stay visible to the team. A buyer does not need every purchasing [handoff](/process/handoff/). They do need to know the published deadline gives you time to verify compatibility, document cost changes, secure approval and release the item.

## What does every selection line contain?

More than category, vendor and due date. The tracker keeps an appointment apart from a decision, a decision apart from an approval and an approval apart from a released order. "Done" is too loose for a field document.

| Field | What it answers | Job-site use |
| --- | --- | --- |
| Selection category | What decision is being made? | Matches plans, specifications and allowance labels |
| Decision owner | Who has to act? | Keeps an unassigned choice from aging |
| Buyer deadline | When is the complete decision due? | Protects review and release work |
| Field need date | When must verified information or material be on site? | Ties the choice to rough-in or installation |
| Status | Proposed, approved, ordered, received or checked? | Shows the real state without guessing |
| Dependency | What other work relies on this decision? | Exposes cabinet, electrical, plumbing or finish effects |
| Exception note | What changed and who approved it? | Preserves the project record |

Attach the controlling document or approval record. The superintendent should never have to dig through an email thread for a model number while a trade waits. The tracker points to the current approved information. It does not become a second, unofficial specification.

## How do you calculate a defensible deadline?

Work backward from the field need date through your real handoffs. Lead time alone is not enough. A product may need shop drawings, finish confirmation, deposit approval, delivery coordination or a damage inspection on arrival.

1. **Name the field event.** The rough-in, blocking, framing, cabinet, finish or installation activity that depends on the choice.

2. **Define what the field needs.** Often a dimensioned cut sheet before the physical item.

3. **Confirm the ordering path.** Who checks availability, compatibility, pricing and substitutions before release.

4. **Add review gates.** Buyer approval plus any design, engineering or builder review.

5. **Set the buyer decision date.** Early enough to finish the verified path without an optimistic delivery assumption.

6. **Check the date against the job.** Revisit it when the construction schedule, a plan revision or product status changes.

For custom work, define what complete means. "Choose appliances" is not complete while cabinet openings lack approved model numbers. "Choose tile" is not complete while pattern, grout, edge treatment and room allocation stay open.

## What happens when a buyer misses a deadline?

The process describes the next review. It does not threaten the buyer with a generic delay. Confirm what is missing. Identify the affected work, the available alternatives and the approval needed to proceed. The governing documents decide contractual consequences. The selection tracker records the operating facts.

Never quietly move a date and bury the original commitment. Record the requested date, the revised date, the reason, the affected dependency and who approved the change. A proposed substitute is a new decision, with its own compatibility and cost review.

### How does the buyer update read?

Concrete. The cabinet release is waiting on the approved appliance schedule. The field need date is approaching. The missing model information affects opening dimensions. Here are the available next actions. That beats "the project may be delayed" every time.

## How are deadline changes communicated?

One current schedule and one change record. The current view helps the buyer act. The change record tells the office and the field why a date moved. Email can notify people. The project source holds the approved status.

Weekly updates call out only the decisions that need attention, with links to the full record. A dedicated [builder schedule update](/articles/process-and-documents/builder-timeline-communication/) shows which field milestone moved. The selection notice explains which decision connects to that movement.

AI agents compare a selection tracker with meeting notes, flag missing model numbers and draft reminders from approved data. People confirm the field need date, interpret the project documents and approve every buyer-facing message. That split follows the review rules in [AI operations](/process/ai-operations/).

Selection deadlines work best inside a documented operating system. The [build process guide](/guides/writing-down-your-build-process/) shows how to connect plans, approvals, field handoffs and revisions. The [process and documents library](/articles/process-and-documents/) holds the related working records.

## Which selection deadline questions come up most?

### Should every project use the same selection deadlines?

Same method, different dates. Calculate each one from the project plans, the procurement path, the current field schedule and the known review steps.

### Is a selection appointment the same as a deadline?

No. An appointment is an activity. A deadline is when complete decision information has to enter your review and release process.

### Who should own the selection tracker?

One role. Buyers, design, purchasing and field roles stay responsible for their own recorded inputs and approvals.

### What if a product becomes unavailable after approval?

Open an exception record. Confirm the field effect, review substitutes and update the schedule after approval.