Write a risk register entry that drives action

The current register entry says, 'Subcontractor may be late.' It appears in every review but never changes behavior. ISO 31000 action loop: identify the uncertainty, analyze consequence, evaluate urgency, treat it, monitor triggers, and communicate ownership. Common trap: writing risks as worries. A worry says what might go wrong; a risk entry says how the team will know and what it will do. Objective Protect June integration readiness and customer demo confidence. Risk is uncertainty on objectives. Naming the objective prevents generic fear. Cause and consequence If SubK misses two weekly interface drops, lab integration slips and demo margin falls…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in