How to Run a Risk Workshop on a Megaproject

Define what the workshop must produce

Focus the workshop on a defined package, phase or upcoming decision. A whole megaproject may need several focused sessions and an integration review. Name a decision sponsor, facilitator and recorder before issuing the invitation.

Write the purpose in a sentence: we need to decide whether to proceed with this option, and we need to understand these exposures first. Agree the required outputs: a causal risk description, evidence gaps, accepted owners, proposed responses and decisions needing escalation. Confirm who can authorize follow-up work.

Prepare the evidence and the room

• Send the scope boundary, objective, decision date and specific questions in advance.
• Provide the current schedule, estimate basis, interface list, assumptions and existing risks, with version dates.
• Invite design, procurement, construction, commissioning, operations and relevant contractors according to the scope.
• Ask participants for concerns and supporting evidence before the session, including a private route for sensitive concerns.
• Agree consequence criteria, escalation thresholds and the distinction between risks, issues and actions.
• Prepare a visible register and an issues list so discussion stays captured without forcing every topic into a risk row.

Check the participant list for missing authority and missing experience. If a key interface owner cannot attend, identify what can be assessed provisionally and what must wait for their input. Do not turn their absence into assumed agreement.

Agree how interview findings will be used before the conversation starts. Bring the risk and supporting evidence into the shared analysis without casually exposing a confidential source. Use the interviews to widen the evidence, then give the team a chance to test the resulting assessment.

Use a suggested agenda, then adapt it

The suggested agenda below runs for two hours. Reduce the scope or schedule further sessions if the group cannot examine the evidence properly. Protect time for decisions and ownership instead of spending the whole meeting listing concerns.

• 0-15 minutes: confirm the decision, scope, current plan and assessment criteria.
• 15-35 minutes: identify uncertainty individually, then compare observations across functions.
• 35-65 minutes: write causal risk statements, examine evidence and combine genuine duplicates.
• 65-90 minutes: prioritize the exposures requiring action or further analysis; retain material disagreement.
• 90-110 minutes: develop responses, triggers, owners, resource needs and decision requests.
• 110-120 minutes: read back commitments, unresolved questions and the follow-up date.

Facilitate the uncertainty, not the loudest opinion

Begin with silent individual reflection so the first speaker does not define the whole risk picture. Ask each function what information it is waiting for and what another function assumes it will provide. When a concern appears, ask what causes it, what is uncertain and which objective it affects. Record issues separately when the event has already happened.

Challenge evidence respectfully. Ask what supports the assessment, what would change it and whether a response is actually within the named owner's control. Keep conflicting assessments visible until the relevant evidence or authority resolves them. If a specialist safety, environmental or technical question exceeds the session's competence, assign a review through the established specialist process.

Prioritization should identify what needs a decision, not eliminate inconvenient risks. Use the project's agreed criteria consistently. Capture why a risk was deprioritized and when it will be reconsidered. For a response, test feasibility, timing, resources and the exposure left if it succeeds.

Print and complete one worksheet per priority risk

Use the checklist below as a completion guide. Write the answers in the project's controlled register or on a printed copy, keeping the risk identifier consistent across the meeting notes, schedule and action log.

• Risk identifier / package / objective: ________________________________________
• Cause / uncertain event / consequence: ____________________________________
• Evidence / assumptions / information still missing: _________________________
• Current controls / assessment basis: ______________________________________
• Accountable risk owner / acceptance date: __________________________________
• Response / action owner / due date: _______________________________________
• Resources or authority required / decision deadline: _________________________
• Observable trigger / monitoring owner: _____________________________________
• Residual exposure / escalation route: ______________________________________
• Review date / completion evidence / linked records: _________________________

Convert the workshop into delivery commitments

Circulate the recorded decisions, actions and unresolved points promptly using your project's document-control process. Ask owners to confirm their commitments and correct misunderstandings. Transfer approved response work into the schedule and funding process. Mark proposed actions as proposed until the responsible authority accepts them.

At the next review, check evidence of progress, new information and fired triggers. Close actions only against their completion conditions. Keep a short learning note: what the workshop revealed, what it missed and which information would have improved the decision. Use that note to adjust the next session's scope and participants.