Risk control is the unglamorous half of the job: watching triggers, updating scores, and escalating before the issue has a name. If your register only moves when a crisis arrives, you are doing issue management with extra columns.
Risks become issues. Say it when they do.
A risk is uncertain. An issue has happened. The moment the vendor misses the drop, that row leaves the risk register and enters the issue log with an action, an owner, and a date. Keeping it in the risk list so the 'risk count' looks stable is theatre.
Define triggers in advance. 'If the third-party API sandbox is not available by 15 June, raise as an issue and activate the mock-service fallback.' Triggers turn monitoring into a binary check instead of a vibe.
Watch leading indicators, not just the disaster. Slippage on a predecessor task, a sudden silence from a vendor, or a sponsor who stops reading the pack are often the first movement. By the time the milestone is missed, you are writing an incident report.
A control cadence that survives busy weeks
Put risk review on the same calendar as status, not as an optional extra. Ten minutes on the top five risks in the weekly meeting beats a monthly two-hour archaeology session. If the meeting is always 'too full,' the project is telling you something about its real priorities.
Update three fields every review: score, response status, and next action. If none of those changed, write 'no change — trigger still X.' Silence in the register is how people assume someone else is watching.
Escalate residual risk that no longer fits the PM's authority. A risk that now threatens the business case belongs with the sponsor, not in a footnote. Escalating early with a proposed response is competence. Escalating after the damage is a status surprise.
Reporting without wallpaper
Leadership does not need all twenty-eight rows. They need movement: new high risks, scores that worsened, responses that stalled, and decisions they must make. A heatmap with no narrative is interior decoration.
Be specific about what you want. 'Risk 12 requires a decision by Friday: accept a two-week delay or fund a second test environment.' That sentence is why the register exists.
If the same top risk has sat unchanged for six weeks, either the response is working and you should say so, or the response is fictional and you should stop pretending. Stale top risks are a credibility leak.
Summary & next steps
Promote risks to issues when they land. Use triggers, not vibes. Review on a standing cadence, report movement and decisions, and escalate residual risk that exceeds your authority.
Next: risk workshops — how to run a room that surfaces real risks instead of polite generalities.