Name the decision, not just the delay
A plan can become vague when someone says, “We’re waiting on a decision.” Before rearranging the week, write down the specific question that needs an answer. Is the team choosing between two approaches, approving a budget, or deciding whether the project will happen at all? Each situation blocks a different amount of work.
Next, identify who can make the decision and what information they need. If you are responsible for providing that information, preparing it may be your immediate priority. If the decision sits with someone else, your job may be to make the question clear and then plan around the wait. Keep these details in the project notes so you do not have to reconstruct them each time you review your tasks.
Divide the work into three groups
Make a short list of work related to the project and sort it into three groups: work that is useful under any likely outcome, work that makes the decision easier, and work that depends on a particular answer. This is more helpful than treating the whole project as either active or blocked.
For example, if a team has not chosen a format for a guide, gathering existing material and identifying the intended audience may be useful either way. Sketching the trade-offs between formats might help the team decide. Building a detailed layout for one format, however, may be wasted effort if the team chooses another. The aim is not to avoid every possible revision; it is to notice when you are committing substantial time to an assumption.
Give the first two groups clear next actions, with a reasonable limit on preparation. Once you have enough material to support a decision, more preparation may not add much value. Put answer-dependent tasks on a separate list marked with the decision they require, rather than leaving them among tasks you could do today.
Set a follow-up point and a planning assumption
A pending decision needs a place in your plan, but it does not necessarily need a large block of reserved time. Record when you expect to check for an answer and what you will do if none has arrived. That might mean sending a concise follow-up, raising the question in an existing meeting, or moving to another approved task. A follow-up point keeps the decision visible without making you monitor it constantly.
If you must schedule work before the answer arrives, label any assumption explicitly. For instance: “If approved by Thursday, begin the draft on Friday; otherwise, use Friday for the next project.” This is a conditional plan, not a prediction. It shows what can change while protecting time for work that is ready to move.
Be cautious about holding multiple large time blocks open for a decision with no clear timing. If the answer comes later, you can reassess the schedule then. Until that happens, assign most available time to commitments you can actually advance.
Reopen the plan when the answer arrives
When a decision is made, do not simply reactivate every task you parked. Check what the answer changes: the goal, the scope, the order of work, and any commitments made while you waited. Some preparatory work will still be useful; some may need a quick update. Remove tasks that no longer apply so they do not linger as misleading reminders.
Then choose the next concrete step and give it a realistic place in your schedule. If the decision creates a new deadline or affects other people’s work, communicate the updated plan to those involved. A brief note stating the answer, the next action, and any changed timing is often more useful than forwarding a long discussion.
Planning around uncertainty is not about finding a way to keep every project moving at full speed. It is about doing the work that remains worthwhile, keeping the unresolved question visible, and leaving yourself a straightforward way to continue once you know more.
