Project Management

Risk Register Template: ISO 31000, PMI Responses, Scoring

By Vact Published · Updated

A risk register is a table with one row per risk. Each row states what could happen, how likely it is, how much it would matter, who owns it, what response was chosen, and what event would trigger the contingency. The sample below is a seven-row register for a help-center launch, scored on a 1-5 scale for probability (P) and impact (I). It includes two opportunities, because PMI’s response strategies cover opportunities as well as threats.

IDRisk statement (cause, event, consequence)PIScoreResponseOwnerTrigger
R-01Because preview-environment access is not yet granted, screenshots for three articles may be missing, so those articles miss Tuesday’s review339Mitigate: request access Monday and test a screenshot captureProduct leadNo access by Thursday noon
R-02Because only one person knows the build scripts, that person’s absence may stall releases for days248Mitigate: cross-train a second engineerEngineering leadLeave request or resignation notice
R-03Because the translation vendor has one reviewer, its delivery may slip past the content freeze, so the localized launch is delayed2510Transfer (contract delivery terms) plus mitigate (staged delivery)Content managerFirst batch late by 2 days
R-04Because legal review has no fixed turnaround, terms-of-use changes may take over five days, so publication is blocked4312Escalate to the sponsor for a committed slotSponsor (escalated by the project manager)Legal has not started by day 2
R-05A product-marketing contact has offered a co-hosted launch webinar, which may add launch-week sign-ups236Enhance: draft the invitation and agenda nowMarketing leadContact confirms a date
R-06Templates from a previous launch may cut article drafting time by about three days326Exploit: assign the templates to every writer on day 1Project managerTemplates not in the drafting folder by day 1
R-07An office move falls in launch week, so some staff may be offline for a day122Accept: no action; note it on the calendarOperationsNone

Every figure above is invented for illustration. The scales, the response vocabulary and the column set come from the standards and guides described below.

What a risk register needs, and why those columns

Two government sources describe what a register holds. The US Department of Defense’s Risk, Issue, and Opportunity Management Guide (version 2.2, December 2023) describes the register as holding information for each risk “such as risk category, risk statement, likelihood, consequence, planned mitigation measures, the risk owner, WBS/IMS linkage, and, where applicable, expected closure dates and documentation of changes.” It adds that the risk event may be written as an If-Then statement and that the register may also record root cause. HM Treasury’s Orange Book (page updated 29 July 2026) recommends stating each risk as a cause, an event and a consequence, and says treatment plans should specify the rationale, actions, accountable owners, resources, early warning indicators, timescales and the basis of reporting.

The cause-event-consequence form does most of the work in the sample table. “Key developer leaves” is a headline; “because only one person knows the build scripts, that person’s absence may stall releases” says what to cross-train, what to watch and what is at stake. A vague statement cannot be scored consistently, because two people score two different events.

A working template has these columns:

ColumnWhat goes in it
IDA stable number that is never reused
Risk statementCause, event, consequence; opportunities are worded as benefits
CategoryTechnical, resource, schedule, scope, external, organizational
Probability, Impact, ScoreOrdinal 1-5 values and the product (see scoring below)
Response and actionsOne strategy from the lists below, with the specific action
OwnerOne named person or role, not a team
TriggerThe observable event that activates the contingency
ContingencyWhat happens if the trigger fires
Linked workThe activities or milestones affected
Action due date and next reviewTwo separate dates (see the review section)
StatusOpen, mitigating, occurred, closed

The DoD guide’s “WBS/IMS linkage” is the “Linked work” column here: a risk that is not tied to specific work cannot be traced into the schedule. The work breakdown structure guide shows how to produce the work packages to link to.

ISO 31000:2018: the principles behind the register

ISO 31000:2018, Risk management — Guidelines, is the international guidance standard on risk management, first issued in 2009 and revised in 2018. The site of ISO/TC 262, the ISO committee responsible for it, says the 2018 version “places a greater focus on creating and protecting value as the key driver of risk management.” The NC State Enterprise Risk Management Initiative’s summary of the standard lists its eight principles. Risk management should be:

  1. integrated across the entity;
  2. structured and comprehensive, to ensure consistency of processes;
  3. customized to the organization;
  4. inclusive of the knowledge, views and perceptions of key stakeholders;
  5. dynamic in managing risks that change continually over time;
  6. based on the best available information;
  7. developed in light of human and cultural factors; and
  8. subject to continual improvement of the risk management process.

The same summary lists six process elements: communication and consultation; scope, context and criteria; risk assessment (identification, analysis and evaluation); risk treatment; monitoring and review; and recording and reporting.

Six of the principles, and one process element, map directly onto register habits:

ISO 31000 ideaRegister practice
CustomizedDefine your own probability bands and impact descriptions for the project before scoring anything
InclusiveAsk the people doing the work, and the sponsor, which risks they see
DynamicRe-score at every review; add and close rows continually
Best available informationCite evidence in the row: past schedules, vendor history, test results
Human and cultural factorsMake it safe to report bad news; run the pre-mortem below
Continual improvementAt close, compare anticipated risks with the problems that occurred
Recording and reportingThe register itself, with its change history preserved

The Orange Book reaches a similar set from the public-sector side. Its main principles are governance and leadership, integration, collaboration and best information, risk management processes, and continual improvement. Its definition of risk appetite, “the nature and extent of risks that the organisation is willing to take,” explains why scoring thresholds should be agreed with the sponsor and not set by the register’s author alone.

Scoring: probability, impact and the thresholds

The DoD guide gives typical likelihood criteria on a five-point scale:

LevelLabelProbability of occurrence
5Near certaintyabove 80% to 99%
4Highly likelyabove 60% to 80%
3Likelyabove 40% to 60%
2Low likelihoodabove 20% to 40%
1Not likelyabove 1% to 20%

Its consequence scale also runs from 1 (minimal) to 5 (critical) and is defined against cost, schedule and performance baselines. Level 5 on cost is a 10% or greater increase over the baseline objective values; level 5 on schedule is a slip that requires a major rebaseline. The guide says the scale should be tailored: “Programs should establish and document specific criteria, including program-specific dollar and schedule thresholds.” A small project can translate that into its own terms: level 3 on schedule might be “a non-critical milestone slips” and level 5 “the launch date moves.”

Three rules from the DoD guide carry over to any register:

  • Score impact on the worst dimension. If analysis gives a cost consequence of 2, a schedule consequence of 3 and a performance consequence of 2, the risk is characterized as a 3, the maximum.
  • Keep scores whole. The values are ordinal; the guide tells programs to avoid fractional scores such as 2.4, which “incorrectly implies increased fidelity.”
  • Promote certainties. If the probability is approaching 1, the event is an issue rather than a risk and moves to the issue log.

The DoD matrix converts likelihood and maximum consequence into low, moderate or high levels. The sample table uses the simpler product P x I, a common convention, with example thresholds: 15-25 for an action review, 8-14 for close monitoring, below 8 for routine review. These cut-offs are illustrative; agree your own with the sponsor. Add an override: any impact of 5 gets a review regardless of probability, which is why R-03 (score 10) carries a staged-delivery action as well as a contract.

The DoD guide also says the matrix level is not the only ranking input: “programs should consider additional factors to prioritize risks,” including the cost-effectiveness of mitigation, frequency, time frame and interrelationship with other risks.

When money is the unit: expected monetary value

For cost risks, the DoD guide shows how to rank by expected monetary value (EMV), the likelihood multiplied by the cost consequence, then subtract the mitigation cost to see the return. Its Table 2-3 example, reorganized:

RiskLikelihoodCost consequenceRisk-weighted (EMV)Cost to mitigateExpected return
120%$10M$2M$1M$1M (1:1)
270%$10M$7M$1M$6M (6:1)
340%$36M$14.4M$2M$12.4M (6:1)
460%$5M$3M$0.5M$2.5M (5:1)

In the guide’s example, a program may decide to fund risks 2 and 3 ahead of risks 1 and 4. The guide then adds that a risk threatening a key performance parameter “should normally be prioritized over other risks even if it has a lower ROI.” The scores order attention; they are not a forecast.

Response strategies: threats and opportunities

The PMBOK Guide, Sixth Edition, divides the strategies of its Plan Risk Responses process into those for threats and those for opportunities. As summarized by the training firm PMTI, which describes itself as a PMI Premier Authorized Training Partner (strategies for risk response), there are five of each:

Threat strategyMeaningOpportunity strategyMeaning
EscalateMoves ownership to a higher authorityEscalateSame: ownership moves up
AvoidEliminates the threat or its impactExploitMakes the opportunity certain to occur
TransferShifts impact and ownership to a third partyShareGives ownership to the partner best placed to capture the benefit
MitigateLowers probability, impact, or bothEnhanceRaises probability, impact, or both
AcceptTakes no proactive action, or funds a reserveAcceptSame

Escalate and accept apply to both, so there are eight distinct strategies. The DoD guide uses a four-option set for risks, accept, avoid, transfer or control, and asks programs to “consider the accept, avoid, and transfer options, not just the control option.” The Orange Book lists its response options in plain language: avoid by not starting or continuing the activity, take or increase risk to pursue an opportunity, retain through an informed decision, change the likelihood, change the consequences (including contingency planning), or share, for example through commercial contracts. The labels differ and the decision is the same: reduce, remove, hand off, pass up, or knowingly keep.

The sample register uses six of the eight:

  • Mitigate (R-01, R-02). The action reduces probability or impact before the event.
  • Transfer (R-03). A contract with delivery terms moves some financial consequence to the vendor. A late vendor still delays the project, which is why the register pairs the transfer with a mitigating action.
  • Escalate (R-04). The project manager cannot make legal commit to a turnaround, so the decision belongs to the sponsor.
  • Enhance and exploit (R-05, R-06). Opportunities get an owner and an action too. The DoD guide says the likelihood of an opportunity “depends upon the effort and resources expended to achieve the opportunity,” that candidates should be evaluated “for costs, benefits, and potential risks before they are approved,” and that approved ones are tracked in an opportunity register “analogous to the risk register.” It adds that programs may combine the two registers.
  • Accept (R-07). Acceptance is a decision recorded with a name and a reason, not an omission.

Finding the risks

The register is only as good as its entries. The DoD guide lists checklists and trigger questions among its identification methods and says identification should go far enough to understand underlying root causes. Four methods suit a project team:

  • Walk the work breakdown structure. At each work package, ask which assumption the estimate rests on.
  • Review past projects. Their issue logs show which risks occurred.
  • Use a category checklist. Technical, resource, schedule, scope, external and organizational headings prompt entries that a free brainstorm misses.
  • Run a pre-mortem. Gary Klein’s description of the pre-mortem is to brief the team on a plan, ask members to imagine that the plan has failed, and have everyone contribute the threats and hurdles they can think of. His Harvard Business Review article (September 2007) frames the aim as making it safe for knowledgeable people to voice doubts during planning.

Enter the results as drafts and score them together afterward, so that an early score does not anchor the group.

Connect each risk to the schedule

A register row becomes useful when it points at activities. In R-01 the affected activity is screenshot capture for three articles, which feeds Tuesday’s review. Compare two scenarios on the schedule: access on time, and access two working days late. If the screenshots sit on a path with three days of float, a two-day slip does not move the launch; if they sit on the critical path, the launch moves by two days. The critical path method guide explains how to read that float, and the project timeline estimator can run the comparison.

Keep any contingency allowance visible in the plan and state how it was sized. The 1-5 scores order the risks; they do not give a probability of finishing on time. A quantified answer needs schedule risk analysis, which the US Government Accountability Office’s Schedule Assessment Guide (GAO-16-89G, December 2015) says “allows for program management to account for the cost effects of schedule slippage.” The DoD guide likewise says Monte Carlo methods, such as those used in schedule and cost risk analysis, can find the cumulative effect of multiple risks on total project duration or total cost.

Run the register: review rhythm and the issue log

A suggested cadence for a team project, to adapt:

CadenceWhoWhat
Weekly, 10 minutesTeamScan the top five rows; has any trigger fired?
FortnightlyProject manager and risk ownersRe-score all open rows; add and close entries
MonthlySponsor and stakeholdersTop risks, response progress, decisions needed

Record two dates per row. The action due date says when the mitigation task should be done; the next review date says when someone will re-read the row. A risk can stay open after its action is complete: once access is granted in R-01, someone confirms that the editor can actually capture the screenshots before the row closes.

When a risk occurs, the event moves to an issue log with its own owner and resolution plan, and the original row stays, linked to the issue. The DoD guide defines an issue as “an event or condition with negative effect that has occurred (such as a realized risk) or is certain to occur (likelihood of 5).” At project close, compare the anticipated risks with the issues that occurred; the guide says the register “can provide traceability of program risks and can be a source for lessons learned.” The same comparison calibrates the next project’s scales: if every “likelihood 2” risk occurred, the team’s likelihood ratings were too optimistic. The project kickoff checklist is the moment to agree the scales and set up the register.

Tools

A spreadsheet is enough for most teams: one tab for threats and opportunities, one for the issue log, a formula for the score and conditional formatting for the thresholds. The DoD guide notes that many commercial tools are available for risk management, prioritization and reporting. Whichever tool holds the register, the decisive features are traceability to scheduled work, a history of changes and a named owner on every row.

Sources