The team is estimating tasks six months away while next week's supplier decision remains unresolved. Rolling-wave planning details near-term work and keeps later work at a higher level until enough information exists to plan it responsibly. The project still needs an overall direction, constraints and decision points.
APM's glossary describes rolling-wave planning. For a small team, its value is a deliberate boundary between what you can commit to now and what needs more evidence. It is not permission to leave the rest of the project unexplained.
Choose a useful planning horizon
Set the detailed horizon around the next meaningful decision, deliverable or period of reliable information. Avoid choosing a standard number of weeks simply because a template uses it.
Ask which near-term work can be estimated and assigned with credible inputs. For later stages, retain intended outcomes, broad sequence, major dependencies and assumptions. Show ranges and unresolved choices instead of attaching precise task dates to unknown work.
Agree when the next wave becomes detailed
Use a short horizon agreement:
Near-term outcome and detailed work included.
Later outcomes retained in outline.
Information expected before the next planning decision.
Owner obtaining that information.
Date and authority for committing the next wave.
Effect on overall scope, forecast and funding.
The next planning session should have an input requirement, not merely a recurring invitation. If the evidence will not arrive in time, raise that gap while the team still has an option.
An illustrative supplier selection
A small business plans a service-system change. It can detail requirements clarification and supplier evaluation now. The implementation approach depends on the selected supplier and confirmed operating constraints.
The plan keeps the desired operational outcome, latest useful completion window and major transition dependencies visible. It does not invent a detailed configuration schedule before knowing the selected approach.
After the supplier decision, the team plans the next wave with real delivery inputs and available reviewers. The sponsor can then see whether the overall forecast still makes sense or whether an authorised change is required.
Protect the whole-project view
A detailed next fortnight can look healthy while the intended finish becomes implausible. Review the outline beyond the horizon at each commitment point. Check whether assumptions have changed and whether later capacity or procurement windows need early action.
Rolling-wave detail should not delay decisions with long lead times. A future supplier booking may need commitment now even if the associated work is not fully decomposed. Record the uncertainty and appropriate authority for that early choice.
Keep provisional dates visibly provisional
Use clear labels and explain what would make a forecast firmer. Do not export an outline date into a client promise without checking its basis. When a wave changes, preserve the reason and update affected owners.
The small-team planning guide provides the basic structure around this approach. For the connected task, read How to Keep a Project Assumptions Log That Changes Decisions. If your plan is precise in the distant future but vague about the next decision, discuss your project requirements.
