Practical guide
What should a portfolio value review include
Use a recurring portfolio review to resolve material value questions, with a focused agenda, a compact decision brief and explicit ownership of the response.
Wovex
Summary
A portfolio value review should include the decisions required, material changes in expected or observed value, evidence gaps, dependencies and the options available within current constraints. Present the interpretation behind the figures, not only a status summary. Use a short decision brief to connect each significant issue to its evidence, alternatives, accountable decision and follow-up. End with named actions and the next evidence point, preserving why the choice was reasonable at the time.
Define the decisions before assembling the pack
Start with what the portfolio board or executive team can decide at this review. It may need to reshape an initiative, change the sequence of work, resolve a dependency or require better evidence before making a wider commitment.
Separate those decisions from information supplied for awareness. A meeting that reads every project update aloud may leave little time for the issues that could change the portfolio’s value or feasibility.
APM places portfolio management within strategic objectives and delivery capacity. Use that context to include the organisation’s ability to absorb and use change, alongside the expected benefits. A strong forecast is not actionable if the enabling capacity is unavailable.
Prepare evidence for material exceptions
Agree the scope, reporting date and basis of the information before the meeting. Identify significant movements since the previous review, not merely the current colour of each initiative.
For each material issue, show what was expected, what is observed or forecast now, why the position changed and how reliable the interpretation is. Include costs, disbenefits and dependencies where they affect the choice. Keep financial treatments and unlike measurement units distinguishable.
Missing evidence can itself require a decision. A gap may be acceptable for an early discussion but material to a claim that a benefit has been realised. Explain its consequence and the action needed instead of presenting a blank cell without context.
The Teal Book describes portfolio benefits review as part of the continuing portfolio cycle. The agenda and brief below are illustrative working tools, not prescribed governance requirements.
Use a focused illustrative board agenda
The following 45-minute agenda shows how time can be directed towards decisions. Adapt its duration and participants to the actual portfolio and authorities.
Time | Review purpose |
|---|---|
0–5 minutes | Confirm decisions required, scope and outstanding actions from the last review. |
5–15 minutes | Examine material value movements, including changed forecasts and significant observed results. |
15–25 minutes | Resolve evidence gaps, shared claims and dependencies that could alter the interpretation. |
25–35 minutes | Compare realistic responses against capacity, commitments and strategic priorities. |
35–45 minutes | Confirm decisions, rationale, action owners and the next evidence or escalation point. |
Circulate the supporting detail early enough for people to challenge it. Bring the relevant benefit, operational or finance contributor into the discussion when the issue requires their knowledge or authority. Attendance alone does not transfer accountability.
Keep the review connected to existing investment, finance and delivery governance. If the forum cannot authorise a proposed change, record what must be escalated and to whom.
Put one material issue into a one-page decision brief
This compact example concerns a fictional service rollout. It is short enough to use as a starting format for a one-page brief; expand the supporting evidence separately.
Brief field | Illustrative decision content |
|---|---|
Decision required | Whether to start the next rollout phase before the operational support roster is ready. |
Approved and current expectation | The agreed service improvement remains the objective; the current forecast assumes support that is not yet available. |
Evidence available | The first phase is operating, with incomplete evidence from one service group and an identified support-capacity gap. |
Material uncertainty | Whether the next phase can sustain adoption and service quality under the current staffing arrangement. |
Options and trade-offs | Proceed with the current risk, defer the phase or change the support arrangement and sequence. |
Proposed response | Defer this phase pending a credible support plan, while continuing the first phase and checking the missing evidence. |
Authority and action | Confirm the decision with the authorised forum; assign the support plan to a named operational owner in the actual record. |
Next check | Review the support plan and completed evidence before authorising the next phase. |
The proposal is an example, not an automatic best answer. A real brief needs the costs, timing, alternatives and named people relevant to the decision. Make disagreement visible where it changes how the choice should be understood.
Handle variance, uncertainty and changed expectations explicitly
Distinguish a forecast revision from a revision to the agreed commitment. Explain the reason and which periods or benefits are affected. A more realistic forecast can improve the review even when the expected value falls.
Do not use a combined total to hide incompatible units, overlap between initiatives or evidence of different quality. A shared benefit should not be counted again merely because several projects contribute to it.
For the detailed comparison of options, use the portfolio prioritisation guide. For constructing a supported realised-benefit claim, use the measurement and reporting guide. This page organises the board conversation rather than selecting dashboards or replacing those methods.
Close with ownership and a usable record
Before ending, confirm the decision made, the principal reason, any conditions, the action owner and the next check. Record a deliberate decision to gather evidence as clearly as a decision to proceed.
At the next review, ask what happened to those actions and whether the new evidence changes the conclusion. Avoid repeatedly carrying forward an unresolved issue without an owner or escalation route.
Reporting tools can help organise the pack, but the review is complete only when people understand the response and who will carry it out. Keep the decision and its evidence retrievable so later reviewers can understand the judgement made at the time.
Sources and context
The agenda and decision brief are Wovex guidance, not a mandated board process. The service-rollout example is fictional. Apply the actual decision authorities, evidence requirements and review rhythm of the organisation.