What to bring into a portfolio review—and what to leave out.
Start with the decisions
Build the review around sites that need a decision, not a tour of every task. Show the opening date, the next major milestone and the blocking issue. Keep the detailed project plan available when a question needs more context.
Separate progress from confidence
A site can have many completed tasks while its opening date remains uncertain. Ask whether the remaining dependencies support the target date. Record the assumption behind the forecast so a change is easier to explain.
Leave with an owner and a date
For each issue discussed, agree the next action, accountable owner and review date. Carry unresolved decisions into the next meeting with their history intact. This turns the portfolio review into a working tool rather than another reporting exercise.
