A one-page risk and issue summary for an executive shows up to three open risks and active issues that need the sponsor's decision or help. Each row names an owner, a mitigation or next step, a next check date, and the specific ask. The full register stays with the team, and a written rule decides which items make the page.
What belongs on a one-page risk and issue summary?
A one-page risk and issue summary holds up to three open risks or active issues that a sponsor can act on. Each row names an owner, a mitigation or next step, a next check date, and the decision or help being asked for. Everything else stays in the project register.
Only items the sponsor can act on belong on the page. Sort every line in the register into one of three groups:
- Issues: a problem that has already happened and is slowing a deliverable now.
- Risks the sponsor can help move: a possible problem that needs a decision, budget, access, or action from someone outside the team.
- Everything else: items the team can handle alone, and closed items. These stay in the register.
Only the first two groups are candidates for the page. SlideTeam's one-page risk report roundup lists the core parts of such a page as project overview, identified risks, impact assessment, mitigation strategies, and risk owners (SlideTeam). Keep the overview short, so the rows carry the detail.
How do you choose the three rows?
Score each open risk for likelihood and impact on a 1 to 5 scale, multiply the two, and rank the open risks by that score. The page takes the top three that clear a threshold you write down before the first cycle. If more than three qualify, the rest stay in the register.
Simple PM Strategies describes the same method: likelihood times impact, with each rated from 1 (low) to 5 (high), and a focus on risks that are likely to happen and pose a large threat. Use that scale for every open risk at every update so the page reads the same way each cycle. If your team prefers high, medium, and low, write down which scores count as each label before the first cycle, and use that mapping every time.
Write two conditions in your project's terms, then apply them to every open risk:
Put an open risk on the page when its score is at or above [threshold you set], and a sponsor decision, budget, access, or help could change [agreed date or approved budget].
Keep it in the register when the team can reduce it without the sponsor.
Issues have already happened, so rank them above risks by their impact on the deliverable, not by likelihood. When more than three rows qualify, rank by score, then by the earliest next check date, and move the rest to the register. A row returns to the page only when a row above it closes or its score changes.
How do you tell a risk from an issue on the page?
A risk is a possible problem that has not happened yet, and an issue is a problem that has happened and is slowing work now. Show issues and risks as separate groups, with issues first, because an issue needs help today and a risk needs a plan and a trigger.
Mustardseed PMO places risks and roadblocks under one heading, which can make a risk that has not happened read like an active problem. Use two labels so the sponsor can tell them apart at a glance. Mixing them makes both look less urgent or more certain than they are.
Issue: [what has happened], affecting [deliverable]. Help needed: [specific help] by [date].
Risk: [possible problem], which would cause [impact on the deliverable or date].
Trigger: [early sign the team will watch].
Mitigation: [action], owner [name].
What does each row on the page need?
Each row needs these fields: the item in one plain sentence, a named owner, the mitigation or next step, a date for the next check, and the decision or help being asked for. If a field is blank, close the gap before the sponsor meeting rather than dropping the row.
Simple PM Strategies suggests stating each risk as a possible problem with its negative impact, and documenting the steps to mitigate it. The item sentence can follow that pattern: “If [possible problem] happens, it could [negative impact on the deliverable or date].” Name a person, not a team, as the owner. Mustardseed PMO recommends assigning an owner to each risk.
Illustrative example with placeholders only. Replace every bracket with your project's details; no name, date, or option here is real.
| Item | Type | Owner | Mitigation or next step | Next check | Ask of the sponsor |
|---|---|---|---|---|---|
| Issue: approval of [deliverable] is waiting on [reviewer] | Issue | [Owner name] | [Next step] | [date] | Decision on [option A or option B] by [date] |
| Risk: [component] may arrive after [date] | Risk | [Owner name] | [Mitigation action] | [date] | [Approval or access needed], or none this cycle |
| Risk: [item] could move [agreed date] | Risk | [Owner name] | [Mitigation action] | [date] | None this cycle |
List the rows in rank order, highest score first.
How do you write the decision ask for the sponsor?
Open each sponsor ask with the decision or help you need, the date you need it, and what happens if the answer is late. Follow it with your recommendation and the options. Mustardseed PMO also advises pairing each roadblock with a proposed solution and ending with a specific request for leadership to approve.
Use this wording as a starting point, and keep the decision line first:
Decision needed by [date]: [approve option A / choose between option A and option B] for [item].
Recommendation: [option], because [one-sentence reason drawn from the evidence].
If we have no decision by [date], [plain consequence, such as the deliverable moving to a later date].
Evidence: [name of the status report, log, or document attached].
Replace general requests such as “any thoughts?” with the choice itself.
How do you walk the sponsor through the page in the meeting?
Name the decisions first, read each request aloud, and confirm the answer, the owner, and the next check date before moving on. Close by stating what the team does next and when the sponsor will see the updated page. Send the page with its decision requests at the top of the email body before the meeting.
In the meeting, say these lines in order, filling in the brackets:
- Open: “We have decisions for you on [item] and [item]. I will read each request, then confirm the owner and the next check date.”
- Read each request: “Decision needed by [date]: [option A or option B] for [item]. My recommendation is [option], because [reason].”
- Confirm: “Can you confirm that [option] is your decision, and that [owner name] will bring the next update on [date]?”
- Close: “Thank you. The team will [next action] by [date], and [owner name] will send the updated page after that.”
If the sponsor has no answer yet, ask: “What would you need to see to decide by [date]?” Record the answer in the register with the new date.
What do you do with overflow and items that drop off?
Overflow stays in the project register, and the one-page summary carries one line that points to it. Record why an item left the page: it closed, it moved to the team's own list, or the sponsor decided it was not theirs to act on. The register stays the full record.
Add one line at the foot of the page, such as: “Also open and tracked by the team: [project register location].” Remove an item from the page only when [condition, such as its mitigation is in place, the decision has been made, or the item has closed]. Write the reason in the register, so the next update does not add the item back by mistake.
How do you keep ratings consistent across updates?
Write down what each rating means before the first cycle, then check every row against those words at each update. Smartsheet's monthly one-page template uses green, amber, and red, with sample labels of Healthy, At Risk, and Progress Halted (Smartsheet). Use your own definitions in place of those labels.
SlideTeam advises prioritizing the most critical risks and updating the report when risks change. Define each rating in terms of your project:
Red: [the agreed date or budget will be missed unless the sponsor decides the item in the ask].
Amber: [condition, such as a mitigation is in place but not yet confirmed].
Green: [condition, such as the next check shows no change].
Change a rating only when the evidence changes, and write that evidence in the register.
What mistakes weaken a one-page risk summary?
The common mistakes are rows that list tasks instead of risks, rows with no owner, and problems with no proposed solution or request. Mustardseed PMO lists hiding major risks among common mistakes, so keep a major open risk on the page even when the news is unwelcome.
If the page needs several paragraphs to make sense, the rows hold too much detail. Move that detail to the register and point to it from the row. Before you send the page, check that:
- every risk and issue has a named owner;
- every row has a mitigation, a next step, or a request for help;
- every decision request has a date and a recommendation;
- no major open risk has been left off the page; and
- the page holds no more than the top three rows.
Then read the decision requests alone. If the sponsor could answer them without the rest of the page, send the page with the decision requests at the top of the email body.