Write risks as owned work, not weather
Draft engineering project risks with a clear event, consequence, trigger, owner, and planned response.
The move: write the risk in a way that creates action. Good risk management is not a list of things that might go wrong. It is a management system for uncertainty. In an engineering firm, uncertainty usually hits one of five objectives: safety, quality, schedule, fee, or client trust. The risk statement should make that impact visible before it happens. Use this structure: If [specific event] happens, then [specific consequence] because [cause]. Trigger: [early signal]. Owner: [person]. Response: [planned move]. This structure makes the difference between monitoring and hoping. The owner is not a blame marker. The owner is the…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in