Make unanswered decisions visible
Delays in client decisions often begin quietly: an unconfirmed layout, a sample still to be considered or a message nobody regards as final. Work continues until the team reaches a task dependent on that answer. A useful schedule reveals those connections before they become a blockage, without requiring every choice to be settled at the beginning.
Ask your architect for a list of open decisions appropriate to the actual project stage. Distinguish matters requiring your preference from those needing a technical check or external information first. You should not have to resolve a professional uncertainty simply to keep things moving. Your role is to explain needs, choose with adequate information and communicate through the agreed channel. The list should also show when you cannot yet decide and what information or action is missing before a responsible answer becomes possible.
Order choices by dependencies rather than appeal
It is easy to spend time on colors while questions affecting service layouts or dimensions remain unresolved. Ask which choices enable other tasks and which can wait without disrupting planned work. Your schedule should reflect that particular sequence rather than a generic shopping list detached from the current stage of the project.
For each choice, record the next task that depends on it and who needs the answer. Where a selection affects an order, obtain current information from the person managing that purchase. Do not rely on delivery periods remembered from another product or another building project. Choosing early does not solve everything either: some decisions require measurements or checks that are not available yet. With the team’s help, identify the useful decision point by balancing the information available against the consequences of waiting to respond.
Define the information needed for each choice
Every schedule entry should contain a clear question. “Sort out bathroom” is too broad; “confirm the layout from the two reviewed alternatives” explains what is expected. Add the drawings, samples, financial comparisons or explanations required, and identify who will provide them. If essential information is missing, record the gap rather than retaining a date that no longer has a realistic basis.
Ask for alternatives to be presented using consistent criteria. A material choice might involve maintenance and feel; a layout choice might involve use and circulation. A single image will not answer every question. Avoid requesting an unlimited catalog of possibilities: agree a reasonable selection compatible with the project’s technical requirements. Allow time to consider it and raise questions, especially when several people share the decision or need to discuss it remotely before responding.
Assign a person and an agreed response date
Identify who assembles the client’s views and who confirms the final answer. Where a decision is shared, organize your internal discussion before sending conflicting instructions to the team. One person need not make every choice, but there should be a recognisable way to close each issue and distinguish a provisional preference from approval.
Agree dates with the architect and, where appropriate, those coordinating construction or supply. Record why each date matters and what happens if it cannot be met. A simple format is enough: decision, missing information, responsible person, date and status. Avoid filling the schedule with identical reminders that have no clear action attached. When new information changes the conditions, update the entry and tell those depending on it, so they do not continue working from an assumption that is no longer valid or understood by everyone.
Flag a delay before the answer is due
If you will be unable to decide, say so as soon as you know and explain the specific reason: a missing sample, an unclear consequence or a disagreement between decision makers. Ask which tasks are affected and whether the team can assess a temporary alternative. Do not independently turn an interim suggestion into an instruction for execution.
Where the uncertainty is financial, request the comparison needed before approval. Where it concerns use, return to an everyday situation that helps test the options. If people making the decision disagree, communicate shared priorities instead of expecting the architect to guess which message takes precedence. Record the revised date and understood consequences. A current schedule is more helpful than preserving an impossible deadline and assuming other people can absorb the uncertainty without adjusting their own work, purchasing arrangements or coordination with the rest of the team.
Close each decision with a recoverable reference
When approving a choice, identify the option, drawing version, sample or document concerned. Save the confirmation in the agreed place and update its status. Record any reservations: conditional approval should make clear what still requires checking. Ask the team how the decision will be incorporated into the project information and who will communicate it to the people who need to act on it.
Review open matters at intervals suited to the project stage and appointment. You do not need a meeting for every detail if the agreed communication route can resolve it clearly. To prepare an enquiry, bring your outstanding decisions and explain which ones hold up the next step. If a choice changes something already approved, read the guide to recording layout changes. The schedule organises answers, while also recognising when an answer changes the scope of the work and needs a separate assessment.