Plan when you don't have all the facts

Identify the one thing you can do next

A plan built on missing facts is not a guess. It is a set of commitments deliberately kept small enough to adjust as facts arrive. The method is called progressive elaboration, defined by the Project Management Institute (PMI) in the PMBOK Guide 7th Edition (2021) as iterative planning where detail increases as information becomes known. You do not need all the facts to start; you need a minimum viable plan.

The minimum viable plan has four components: an objective, the next physical action, an owner for that action, and a review cue. David Allen’s Getting Things Done methodology (2015 edition) established this structure for managing tasks when the full picture is unclear. Write these four items down before you do anything else. If you cannot name the next physical action, you have not yet found the starting point.

Build an assumption log before you build a schedule

When key facts are missing, write down what you are supposing. The PMBOK Guide 7th Edition (2021) defines an assumption log as a documented list of planning suppositions with an assigned validation owner and deadline. Every supposition that could block progress must have a validation window: a date before which the supposition must be confirmed or discarded. That date is the last moment you can afford to be wrong.

For example, if you are planning a home renovation and suppose a permit takes two weeks, write that belief in the log. Assign someone to call the permit office and set a deadline one week before you need to order materials. If the permit takes six weeks, you have caught it early enough to re-sequence the work.

How to handle uncertainty in project plans with triggers

Fixed dates are brittle when facts are missing. A trigger-based decision point activates a next step when a specific condition is met, not when a calendar date arrives. The Federal Emergency Management Agency (FEMA) Comprehensive Planning Guide 101, Version 3 (2023) describes three condition types:

• Time-based: “If we have not received supplier confirmation by Friday, escalate to the backup vendor.”
• Event-based: “When the site inspection passes, release the construction deposit.”
• Threshold-based: “If costs exceed the estimate by a predetermined margin, pause and re-budget.”

Write conditions for each supposition you logged. If a supposition is invalidated, the condition activates your Plan B. FEMA CPG 101 (2023) states that Plan B activation should happen when a critical supposition is invalidated or a dependency fails. Do not wait for a meeting to determine what to do next; the condition makes the choice automatic.

Planning with incomplete information: map dependencies and flag unknowns

A dependency is a task that must finish before another task can start. The PMI Practice Standard for Scheduling, 3rd Edition (2019) recommends identifying all tasks that must complete before a milestone and flagging any with unvalidated suppositions. Draw a simple line from the dependent task to the task it depends on. If the upstream task relies on a supposition that has not been validated, mark it red.

Red items are your highest risk. They are the reason you might have to rework the plan. Validate them first. The PMBOK Guide 7th Edition (2021) states that supposition validation should happen at every major review point and at least monthly for active projects. If you have only one hour to work on the plan, spend it on red dependencies.

Set a contingency reserve for time and money

No plan with incomplete information is accurate. The PMI Practice Standard for Project Risk Management (2019) recommends a contingency reserve of 5-15% of total estimated effort or cost, varying with project complexity and uncertainty. If your plan is highly uncertain, use the higher end. This reserve is not slack for poor estimates; it is a buffer for facts you cannot know yet.

For household plans, the same logic applies. FEMA (Ready.gov,2024) recommends keeping cash in small bills sufficient for several days of essential purchases. The amount varies by household size and location, but the principle is the same: hold a reserve for the unknown.

Review when conditions fire, not on a fixed calendar

A plan with missing facts must be reviewed whenever a trigger condition is met, not just every week. FEMA CPG 101 (2023) states that trigger-based decision points are pre-agreed conditions that, when met, activate a specific next step without requiring a new meeting. This prevents over-planning while keeping critical dependencies visible.

Still, some reviews should be calendar-based. FEMA (Ready.gov,2024) recommends a household emergency plan review every six months and an emergency kit check every three months for food and water expiration and every six months for batteries. Use these as a floor, not a ceiling.

The progressive elaboration planning method in practice

When you do not have all the facts, follow this sequence:

1. Write the objective and the next physical action.
2. List every supposition that could block that action.
3. Assign a validation owner and a deadline to each supposition.
4. Define a condition that activates a backup step if the supposition fails.
5. Identify critical dependencies and mark those with unvalidated suppositions as red.
6. Set a contingency reserve of 5-15% for time and cost.
7. Review the plan when a condition fires, and at least every six months.

This sequence works for a household move, a travel itinerary, a freelance project, or a life event like a divorce or bereavement. The structure is the same; only the specifics change.

Why this method avoids over-planning

Over-planning happens when you fill in details that will likely change. Progressive elaboration keeps detail low for far-term work. The PMBOK Guide 7th Edition (2021) calls this rolling wave planning: near-term work is planned in detail, far-term work is kept at a high level. You do not need to know every step of a six-month renovation on day one. You need to know the first week’s steps and the suppositions that govern the rest.

What to do with the plan once it is built

A plan that sits in a binder is not a plan. FEMA (Ready.gov,2024) states that emergency plans must be shared with all household members and practiced annually. For project plans, the PMBOK Guide 7th Edition (2021) recommends gate reviews at the end of each phase to validate suppositions before authorising the next phase. Share the plan with everyone who has a role in it. Test the conditions. Drill the backup steps.

Plan when you don’t have all the facts: the one thing to remember

Plan what is needed, not what you wish you knew. The missing facts will arrive. Your job is to build a structure that catches them when they do.