How to review risks across projects and decide what to escalate
Review risks across projects, trace shared dependencies to their sources, and give each urgent decision an owner, a deadline, and a concrete proposal.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a process to review risks across projects is
When you review risks across projects, you look for decisions that project teams cannot make on their own. A project risk register lists uncertain events that could affect one project. A portfolio risk review connects those entries to the suppliers, people, approvals, or milestones they share. It gives you a shortlist of decisions, such as which work takes precedence when two launches need the same specialist in the same week.
Start from the project updates you can verify and choose a window that reflects the decisions coming up. Keep risks, issues that have already happened, and gaps in reporting visible. A delay can already be an issue for one project while the effect on a second project remains uncertain. The review should show both states, what each team can do, and who has the authority to settle any conflict.
What it does for the business
- Allocate scarce capacity before work collidesA cross-project view reveals when several teams assume they can use the same person, equipment, or supplier slot. You can ask the resource owner to verify availability and assign a sequence before teams make commitments that rely on the same capacity.
- Bring procurement a specific requestGrouping exposure by the underlying supplier or deliverable tells procurement which order, shipment, or acceptance date to confirm. One conversation can then inform several project plans, and the buyer can use the linked milestones to explain which delivery date matters most.
- Give leadership a choice it can makeA decision brief shows what happens if you move a milestone, reduce scope, or move people from another project. An approver can choose among practical responses in the meeting and leave each affected team with a clear account of the tradeoff.
- See whether the response is workingKeeping the previous review and the evidence behind it lets you distinguish implemented changes from new proposals. You can ask the risk owner for proof that an agreed response has taken effect before changing the rating or releasing contingency capacity.
How to build a process to review risks across projects, step by step
Set the review boundary and decision window
A risk ranking is useful only when readers know which projects and dates it covers.
What to do
- List the projects included in the review, their owners, stable identifiers, and approved milestone dates. Use the portfolio boundary agreed with the person who commissioned the review.
- Record the reporting cutoff and review window. Distinguish the date each status report was issued from the date the underlying information was last confirmed.
- Mark stale or missing project updates and list which milestones or dependencies those gaps prevent you from checking. Ask the relevant owner for the specific update you need.
- Find the agreed scoring rules, escalation threshold, and people authorized to change dates, scope, or resources. Use the prior pack you intend to compare against and record its date.
Why
A recent report for one team and an old report for another can make a shared dependency look settled when only one side has confirmed its plan. Start with a clear inventory so the reader can see where the comparison is sound. Defining authority early also helps you route a staffing conflict to the resource owner and a change in business scope to the person who can approve it.
Trace risks and issues to shared dependencies
When several projects rely on the same event, trace the common cause and keep each project's consequence visible.
What to do
- Write each risk as a cause, an uncertain event, and a business consequence. If a delivery is already late, record that issue and identify any downstream consequences that are still uncertain.
- Use stable identifiers to link the same supplier deliverable, approval, technical dependency, or resource across projects. Verify that similar names refer to the same item before grouping them.
- Create one portfolio exposure for the common cause and retain the source entries underneath it. Record where the consequence differs, such as a missed acceptance test for one project and a later release for another.
- Check milestone dates and actual available capacity to establish overlaps. If two teams name the same test engineer but one has no schedule, ask for the missing dates before asserting a clash.
Why
Separate project registers tell you what each team faces. A single shared exposure gives you a place to decide how to handle the common cause and preserve the local effects. Grouping every risk from the same supplier would obscure unrelated deliverables, so check the actual dependency before tying several project outcomes to it.
Rank risks by the decisions they require
A risk belongs high in the queue when a decision made now can change its consequence.
What to do
- Apply the supplied likelihood and impact definitions, then compare the ratings with the escalation threshold. Where no scale exists, give a plain explanation of the consequence and when someone needs to act.
- Distinguish inherent risk, the exposure before controls, from residual risk, the exposure after controls in effect. Check whether a proposed mitigation has actually been implemented before using it to lower the rating.
- Find the latest point when each feasible response can still work. A substitute supplier may require a decision before the missed delivery itself would affect the project.
- Compare findings with the selected prior pack. Separate changes supported by updated evidence from risks entering the first review, and label proposed dates so they cannot be read as commitments.
Why
A ranking should help you use the decision window. The most severe potential consequence may have a response already underway, while a smaller shared risk needs a decision today to preserve an option. Adding ranks from different projects would hide that timing and could make one underlying dependency look like several independent problems.
Write the decisions that need an owner
A risk summary becomes actionable when it tells the approver what they can decide and what that decision changes.
What to do
- For each priority exposure, write the consequence in operational terms and say which teams or milestones it affects. Cite the exact rows or passages that support it.
- Lay out viable responses and the cost in capacity, time, or scope. For a specialist conflict, compare resequencing one project with narrowing its testing scope if both responses are feasible.
- Name the risk owner responsible for tracking the exposure and the person authorized to choose the response. If they are different people, give each a clear action.
- State the recommended decision, the source of its deadline or the proposed date, and what remains uncertain. Explain which work is blocked while the decision is open.
Why
An escalation can stall even when everyone agrees on the severity. The person receiving it may lack authority, or the requested fix may take capacity already promised elsewhere. A decision brief makes the tradeoff explicit and lets the approver ask the teams affected by the recommendation before assigning the work.
Check the escalation queue and hand it off
An escalation stays useful when the person taking it can check the evidence and repeat the next step.
What to do
- Have a reviewer trace priority decisions to their source milestones, dependency records, and owner assignments. Recheck any timing or capacity comparison that would change the recommended action if it were wrong.
- Count projects, source risks, and shared portfolio exposures separately. Show the total project scope next to the count covered and identify which projects are stale or missing.
- Put decisions within the review window at the top. Keep closed and unchanged items in the supporting register so teams can trace prior decisions without crowding the current queue.
- Make sure the handoff names the next person to act and identifies unanswered questions. Keep a copy of the dated review to compare with the next set of updates.
Why
The first people to use the pack are likely to challenge a date, an owner, or a claim about shared capacity. Visible sources help them resolve the disagreement quickly. Coverage also affects the conclusion. A short escalation list means more when every project supplied current inputs than when several reports are still outstanding.
Common mistakes
- Treating silence as current statusCarry the last confirmed update with its date and ask for missing evidence before promising a milestone.
- Counting a shared dependency several timesKeep the local entries visible and group the common cause once for portfolio decisions.
- Treating an issue as an uncertain eventRecord what happened and assess the uncertainty in its consequences separately.
- Lowering the rating on the strength of a planWait for evidence that the response is operating before you revise the residual rating.
- Escalating with no choice or timingName the person who can make the decision and the date when a response becomes harder or unavailable.
What a good result looks like
- The reviewed projects, cutoff, missing inputs, and decision window are clear.
- Each major shared exposure links to the affected project entries and the source dependency.
- Consequences and escalation reasons are concrete and follow the agreed rules.
- The priority queue gives each decision an approver, a choice, timing, and evidence.
- The register records owner commitments, proposed actions, and changes from the selected prior review.
And then what? Using the result
- Put the highest-priority choices on the next portfolio meeting agenda and invite the people who can make them.
- Record each approved change in the relevant project plans and confirm the new dates or scope with the affected owners.
- Give procurement one source-linked request for a shared delivery decision and agree when the answer is needed.
- Ask risk owners for implementation evidence and revisit the residual ratings when they supply it.
- Preserve the dated pack and use it to compare coverage and exposure at the next review.
When to run it
- Before a planning or funding meetingUse the register to connect resource requests to the projects affected and show which choices need to be made together.
- When teams depend on the same supplier or specialistReview the shared delivery or capacity assumptions before teams commit to dates that may be incompatible.
- After a milestone slipsIdentify which downstream teams still have options and which decisions move to an earlier date.
Questions people ask
How do you review risks across projects?
Set the portfolio boundary and decision window, match shared dependencies, rank the exposures that require action, and give each decision an approver and a deadline. Show missing coverage and retain the evidence for each source risk so owners can verify the impact on their own projects.
What belongs in a portfolio risk report?
Include the scope and cutoff, a register of exposures and affected projects, and a short decision queue with consequences, owners, timing, and evidence. Keep closed and unchanged entries available in the supporting register for comparison.
How do you rank portfolio risks without a scoring scale?
Rank them by the concrete consequence, the evidence supporting it, and how soon a choice must be made to preserve an option. State the reasons in words and ask for missing evidence if it would change the order.
How do you handle a risk shared by several projects?
Create one portfolio entry for the common cause and link each affected project's underlying entry. Give the common response an owner while preserving any local actions the project teams need to take.
What is the difference between a risk and an issue?
A risk is an uncertain event that could affect a project, and an issue is a condition or event that has already occurred. An issue can lead to further risks, which you can track as separate uncertain consequences.
When should you escalate a project risk?
Escalate when the agreed threshold is met or the response requires a decision beyond the project owner's authority. Include the choice, who can make it, and the latest date when the response remains feasible.
More jobs in Ops
Review risks across projects, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac