Risk and stakeholder log

Learning objectives

• Maintain one living register of risks and stakeholders.
• Act on high-severity risks regardless of composite score.
• Plan stakeholder engagement two-way, not broadcast-only.

Risk fields

• ID
• Description / cause / event / effect
• Category
• Probability and impact
• Exposure or priority
• Preventive action and contingency
• Trigger
• Owner and due date
• Status
• Residual risk after action

Stakeholder fields

• Role and unit
• Influence and impact on project
• Interests and concerns
• Desired participation
• Key message and channel
• Frequency and owner
• Feedback captured
• Commitment and readiness
• Next action

Copy-friendly log template

• One row per risk and per stakeholder
• Update at every phase gate and after any change
• Escalate high-severity items on their own, not by average
• Attach evidence links to actions and decisions

Garment-factory example

The register tracks operator workload, buyer sample approval slippage, chemical safety at wash, supplier fabric delay and data-quality risk. Chemical safety is escalated immediately even though its probability is low.

Method

1. Assign every risk an owner and a due date.
2. Refresh after each phase gate.
3. Ask stakeholders for feedback and record it.

Common mistakes

• Listing 'management' generically as a stakeholder.
• Manipulating scores to avoid escalation.
• One-way communication with no feedback loop.