Course Preview

Risk Registers and Contingency Planning

A risk register is a living record of uncertainties that could affect an objective. Contingency planning connects important risks to preapproved actions, triggers, owners, and resources so a team can respond when prevention is not enough.

itEngineering leadership and delivery management | OpenSkills.info

Course pathWalk it in order

Look it upDip in anytime

Go furtherLeaves this page

Don't Panic — Risk Registers and Contingency Planning

A risk register is a structured list of everything that could go wrong with your project — except it is not really a list. It is a decision system. Each entry connects an objective to an uncertain event, assigns an owner, and specifies what happens next. The register exists so that when uncertainty arrives, you are not improvising from scratch.

Most people mistake the document for the process. Having a spreadsheet with fifty rows of risks does not mean you are managing risk. It means you have a spreadsheet. The actual work is the conversation that forces clarity: what matters, who owns it, what changes now, and what happens if it occurs.

The cause-event-effect structure is the idea everything else hangs from. Name the cause. Name the uncertain event. Name the effect on the objective. This separation is not academic — it tells you where prevention acts, where monitoring acts, and where contingency acts. A risk statement that bundles all three into "supplier risk" is a worry, not a management tool.

Here is the thing that surprises most people: the score does not matter as much as you think. Inherent risk is your exposure before controls. Residual risk is what remains after. The residual number is the one that drives decisions — accept, treat, escalate, or change the objective. If your controls are rated effective but you cannot show evidence, the score is fiction.

The register is not the finish line. A contingency plan that has never been exercised is an assumption dressed as preparedness. Run a tabletop. Find the gaps before the event finds them for you. And if your register has entries with no owner, no trigger, and no due date, you do not have risk management. You have a document that describes risk management.

The Practice Reference walks through building one entry from context to contingency card. The Cheatsheet gives you the field-by-field structure. The Slides map the control loop. Start with whichever answers the question you actually have.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources