Project Management

Risk Register Template: Track, Score, and Mitigate Project Risks

By Vact Published · Updated

A risk register is a living document that catalogs identified project risks, scores their likelihood and impact, assigns owners, and tracks mitigation actions. It is the operational backbone of project risk management — the place where abstract worries become concrete plans.

Use the register to make uncertainty discussable: what might happen, what it would affect, who watches for it, and what action is available.

Risk Register Structure

A practical risk register needs these columns:

ColumnPurposeExample
Risk IDUnique identifierR-007
DescriptionWhat could happen”Key backend developer leaves mid-project”
CategoryRisk domainResource, Technical, External, Schedule
ProbabilityLikelihood (1-5)3 — Possible
ImpactSeverity if it occurs (1-5)4 — Major
Risk ScoreProbability x Impact12
OwnerPerson responsible for monitoringEngineering lead (example role)
Mitigation StrategyActions to reduce probability or impactCross-train second developer, document architecture
Contingency PlanWhat to do if risk materializesEngage contract developer from approved vendor list
StatusOpen, Mitigating, Closed, OccurredMitigating
Last ReviewedDate of most recent reviewEnter the actual review date

Scoring Risks

The following 5x5 matrix is an example scoring system to adapt to your project. The scores are not scientific — they represent the team’s collective judgment and exist to prioritize which risks deserve attention.

Probability Scale:

  • 1 — Rare: Less than 10% chance
  • 2 — Unlikely: 10% to less than 25%
  • 3 — Possible: 25% to less than 50%
  • 4 — Likely: 50% to 75%
  • 5 — Almost Certain: Greater than 75%

Impact Scale:

  • 1 — Negligible: Minor inconvenience, no schedule effect
  • 2 — Minor: Small delay or cost increase, manageable
  • 3 — Moderate: Noticeable schedule slip or budget impact
  • 4 — Major: Significant delay, scope reduction needed
  • 5 — Critical: Project failure, cancellation risk

For this example, flag scores of 15-25 for an action review, 8-14 for close monitoring, and lower scores for routine review. Escalate severe consequences even when the likelihood score is low. Define the thresholds and review frequency with the people accountable for the project.

Identifying Risks

Risk identification is not a one-time activity. Run a dedicated risk identification session at project kickoff, then review and add risks throughout the project lifecycle.

Brainstorming. Gather the team and walk through each phase of the work breakdown structure. At each work package, ask: “What could go wrong here? What assumptions are we making?”

Historical review. Check post-mortem documents from similar past projects. The risks that bit previous teams are likely to appear again.

Checklist review. Use a risk category checklist to ensure coverage across domains:

  • Technical: Architecture decisions, technology maturity, integration complexity
  • Resource: Key person dependencies, skill gaps, vendor availability
  • Schedule: Dependency delays, estimation accuracy, external milestones
  • Scope: Requirements ambiguity, scope changes, stakeholder alignment
  • External: Market changes, regulatory shifts, vendor bankruptcy
  • Organizational: Budget cuts, reorganization, competing priorities

Pre-mortem. Run a hypothetical exercise: “It is six months from now and this project has failed. What went wrong?” Ask participants to write possible causes independently, then compare them and assign follow-up questions. The exercise gives people a concrete way to challenge optimistic assumptions.

Mitigation Strategies

For each high-priority risk, choose one of four strategies:

Avoid. Eliminate the risk by changing the project plan. If a risky technology integration threatens the timeline, substitute a proven alternative. Check what new risks the alternative introduces before treating the original threat as resolved.

Mitigate. Reduce the probability or impact. Cross-training team members mitigates key-person dependency. Building a prototype mitigates technical uncertainty. Mitigation costs time and money upfront but reduces exposure.

Transfer. Shift the risk to a third party. A contract or insurance policy may allocate particular financial consequences to another party. Check the terms and remaining exposure: a vendor failure can still delay your project even when some costs are recoverable.

Accept. Acknowledge the risk and prepare a contingency plan without active mitigation. Some risks are too unlikely or too expensive to mitigate. Acceptance is a valid strategy when the cost of mitigation exceeds the expected loss.

Document the chosen strategy in the register along with specific actions, owners, and deadlines.

Reviewing the Risk Register

A risk register that is created at kickoff and never reviewed is theater. Schedule risk reviews:

  • Weekly in a short risk review or appropriate team meeting: Quick scan of top-5 risks. Any changes in status?
  • Biweekly with the PM and risk owners: Detailed review of all open risks. Update scores based on new information.
  • Monthly at stakeholder reviews: Present top risks with mitigation progress. Stakeholders may surface risks the project team cannot see.

During reviews, ask:

  • Have any risks materialized? Move them to “Occurred” and activate the contingency plan.
  • Have probability or impact changed? Re-score accordingly.
  • Are there new risks? Add them immediately.
  • Have mitigation actions been completed? If a mitigation has reduced a risk’s score below the threshold, the team can reduce monitoring effort.

Tool Options

Spreadsheets work for small projects. Google Sheets or Excel with conditional formatting on risk scores gives a clear visual. Color-code cells: red for 15+, yellow for 8-14, green for below 8.

Jira can track risks as a custom issue type with fields for probability, impact, and owner. This integrates risk tracking into the team’s existing workflow.

Smartsheet and Monday.com offer risk register templates with dashboards and automated reminders for review dates.

Dedicated tools like RiskWatch or ARM (Active Risk Manager) are overkill for most teams but make sense for large programs with hundreds of tracked risks.

Connect a risk to a decision and a trigger

In a sample help-center launch, the risk might be: “If preview-environment access is not granted by Thursday, screenshots for three articles may miss the Tuesday review.” The trigger is the missing access on Thursday. The owner is the product lead. A mitigation action is to request access early and confirm that it works. A contingency is to release the nine completed articles first, if the launch owner approves that scope.

Record the action deadline separately from the review date. A risk can remain open while its mitigation task is complete. After access is granted, verify that the editor can actually obtain the required screenshots before closing the risk.

Model schedule effects explicitly

Connect the risk to the activities and milestones it could affect. Compare a scenario in which access arrives on time with one in which it arrives two working days late. Include review availability and other dependencies in the comparison. A delay does not automatically translate into the same delay at the end of the project if another path already controls the finish date.

Keep any contingency allowance visible in the plan and explain how it was chosen. A likelihood score multiplied by an impact score is a prioritization device, not a calculated probability of finishing on time. Use schedule risk analysis when a quantified confidence level is needed.

Keep an issue log alongside the register

Once the event happens, record the actual issue, its owner, and its resolution plan. Preserve the original risk entry and link it to that issue so that the team can see whether the warning and planned response were useful. At project close, compare the risks you anticipated with the problems that actually occurred. That record can improve the next project’s assumptions and questions.

Sources