Find the consequential unknowns
An unanswered question matters when its answer changes the work. Can the first area be released before the whole building is ready? Does a specialist need uninterrupted access? Which design information is needed before procurement can proceed? Start with those questions rather than an exhaustive list of every uncertainty. Assign responsibility and a deadline for each significant unanswered question, then separate confirmed commitments from the assumptions used to keep planning moving.
Make the method visible
Ask the team to describe the proposed sequence in plain language before translating it into activities. Identify work areas, trade handoffs, access limits and shared equipment. A short execution sketch often reveals disagreements that a polished bar chart conceals. Record why a particular sequence was chosen so a later reviewer can distinguish an unavoidable dependency from a strategy the team could change.
Issue a basis people can challenge
A useful planning basis names scope boundaries, calendars, milestones, resource assumptions and unresolved decisions. Keep it concise enough to discuss at a coordination meeting. Do not bury an important access assumption in a large appendix that nobody uses. Review the basis alongside the programme when the project changes; otherwise the narrative can describe one strategy while the schedule quietly models another.
Bring it to the next conversation.
- Identify one assumption that changes the sequence.
- Identify who can confirm it and set a deadline.
- Keep the decision with the issued planning basis.
From the Hexifyer team. Examples are illustrative and do not identify client projects. Project requirements and professional responsibilities are agreed for each engagement.