Certifications PMP CertificationWorld’s top PM cert CSM — Certified ScrumMasterTop agile cert CAPMEntry-level PM cert PRINCE2UK & Europe standard View All Certifications ?
PM Guides Agile GuideComplete breakdown Scrum GuideRoles, ceremonies, artifacts EVM GuideAll formulas explained View All Guides ?
Career & Salary PM Salary 2026By country & level How to Become a PMStep-by-step roadmap 50 Interview QuestionsWith strong answers
PM Software Monday.com ReviewTop pick 2026 ClickUp ReviewBest value Best Free PM ToolsNo trials, truly free View All Software ?
Free Tools & Templates EVM CalculatorFree, no signup Gantt Chart MakerBuild & export free PMP Eligibility Checker30-second result Free PM Templates30 templates — Excel, Word, PDF
Get the Free PMP Guide ?
Free Template · Updated March 2026

Free Risk Register Template
Excel, Sheets & PDF

I built this risk register based on how I actually managed risks on real projects in the UAE. Projects worth hundreds of millions of dollars. It has 15 pre-filled example risks across 8 categories, automatic colour-coded scoring, a 5x5 heat map, dropdown validation and residual risk tracking. Download it free in Excel and open it in Google Sheets in one click.

By Syed Mujeeb Rehman, PMP
📅Updated March 2026
📊3 sheets · 15 example risks
🔓Free — no signup
What's Inside

Three sheets: Risk Register (15 pre-filled risks, auto-scoring, dropdowns), Risk Matrix (5x5 heat map with risks plotted), and Instructions (step-by-step guide). Scores calculate automatically. RAG colours update instantly. Fully editable.

1–4
Low
5–9
Medium
10–16
High
17–25
Critical

Risk score = Probability (1–5) × Impact (1–5) — colour updates automatically

Download Free Template

Excel (.xlsx) · Works in Google Sheets too

RISK REGISTER
R-001 · Scope Risk · CRITICAL
R-002 · Resource Risk · HIGH
R-003 · Vendor Risk · MEDIUM
R-004 · Scope Risk · LOW
+ 11 more pre-filled risks…
.XLSX Google Sheets FREE
  • 15 pre-filled risks across 8 categories
  • Auto-scoring: Prob × Impact = Score
  • RAG colours update automatically
  • 5x5 probability-impact heat map
  • Dropdown validation on all key fields
  • Residual risk tracking (post-response)
  • Risk count summary row
  • 30 blank rows for your own risks
  • Step-by-step instructions sheet
⬇ Download Free (.xlsx) Open in Google Sheets →
15
Pre-filled example risks included
3
Sheets: Register, Heat Map, Instructions
4
Auto-colour bands: Low to Critical
Free
No account or payment required
01 — Template Contents

What's Inside — All 15 Columns Explained

Every column in this register has a reason. I did not add anything that does not earn its place on a real project. Here is exactly what each column captures and why it matters.

ColumnWhat It CapturesNotes
IDUnique risk identifier (R-001, R-002…)Pre-filled. Use it to cross-reference risks in status reports and steering committee packs.
CategoryRisk type: Scope, Resource, Schedule, Budget, Quality, Technical, Stakeholder, ExternalDropdown menu. Select from 10 categories.
Risk DescriptionClear statement of the risk event and its potential impactWrite as "If [event], then [consequence]." This format forces clarity.
Risk OwnerPerson accountable for executing the response planDo not default every risk to the PM. Ownership must match expertise.
Probability (1–5)Likelihood of the risk occurringDropdown: 1=Rare, 2=Unlikely, 3=Possible, 4=Likely, 5=Almost Certain
Impact (1–5)Severity if the risk materialisesDropdown: 1=Negligible to 5=Catastrophic
Risk ScoreProbability × Impact — auto-calculatedColour updates automatically: Green, Yellow, Orange, Red
RatingLow / Medium / High / CriticalAuto-colours based on score threshold
Response StrategyAvoid / Mitigate / Transfer / Accept / EscalateDropdown menu
Response ActionSpecific steps to execute the responseName who does what and by when. Vague actions get ignored.
Contingency PlanWhat to do if the risk materialises despite the responsePlan this in advance. Do not improvise under pressure on a live project.
Residual ProbProbability after response actions are in placeShould be lower than original probability if the response is effective.
Residual ImpactImpact after response actions are in placeSome risks can only reduce probability, not impact. Know the difference.
Residual ScoreResidual Prob × Residual Impact — auto-calculatedShows remaining risk exposure after mitigation. This is your true risk position.
StatusOpen / In Progress / Closed / CancelledDropdown. Open risks are highlighted in violet so nothing gets missed.
02 — Risk Scoring

How Risk Scoring Works in This Template

The risk score calculates automatically as Probability × Impact. Both are rated on a 1 to 5 scale. The score ranges from 1 to 25 and maps to a colour-coded rating that updates the moment you change either input. No formulas to set up. No manual colouring. It is all done for you.

Probability Scale (Column E)

1 — Rare: Less than 10% chance. Theoretically possible but very unlikely. 2 — Unlikely: 10 to 30% chance. Has happened on similar projects but not expected here. 3 — Possible: 30 to 60% chance. Could easily go either way. Flag every Possible risk for active attention. 4 — Likely: 60 to 80% chance. Expected to happen unless you actively manage it. 5 — Almost Certain: More than 80% chance. At this point you are dealing with an issue, not just a risk.

Impact Scale (Column F)

1 — Negligible: Minor disruption, easily absorbed within normal project operations. 2 — Minor: Small schedule or cost impact manageable within existing contingency. 3 — Moderate: Noticeable impact on one or more project constraints. Sponsor needs to be aware. 4 — Major: Significant impact on schedule, budget or scope requiring formal change control. 5 — Catastrophic: Project failure, major financial loss, reputational damage or regulatory breach. On my UAE projects, anything at Impact 5 went straight to the steering committee.

💡
PMP exam tip and real project advice: The residual risk score after mitigation is just as important as the original score. If your response reduces a Critical risk scoring 20 down to a High scoring 12, that is progress. But it is still High. Some risks will always carry a residual score above your acceptable threshold. That means you need a contingency plan regardless of how good your response is. I have seen teams assume a risk is handled because they assigned a response. The residual score tells the real story.
03 — Response Strategies

The Five Risk Response Strategies

Choosing the right response strategy is one of the most important decisions a PM makes. I have seen experienced project managers default to Mitigate for every single risk. That is lazy risk management. Here is when to use each strategy properly.

Avoid
Change the project plan to eliminate the risk entirely. Remove the risky activity, change the approach or scope it out completely.
Best for: High-probability, high-impact risks where a viable alternative approach exists.
Mitigate
Reduce the probability of the risk occurring, reduce the impact if it does, or both. The most commonly used strategy and the right one when you cannot avoid the risk.
Best for: Risks you cannot avoid but can reduce through proactive, planned action.
Transfer
Shift the financial consequence to a third party through insurance, warranty clauses, fixed-price contracts or outsourcing. Transfer does not eliminate the risk. It moves who bears the cost.
Best for: Financial or technical risks where a vendor or insurer is better placed to absorb the impact.
Accept
Acknowledge the risk and decide not to act unless it materialises. Active acceptance means you prepare a contingency plan. Passive acceptance means you do nothing and deal with it if it happens.
Best for: Low-scoring risks where the cost of responding exceeds the cost of the risk itself.
Escalate
Raise the risk to the programme manager, sponsor or organisational level because it is beyond the project manager's authority or scope to manage alone. Always document the escalation. Record who it was raised to and when. On my UAE projects, regulatory risks and major supplier risks went straight to the client and steering committee. The PM should never sit on a risk that is above their authority level.
Best for: Risks affecting multiple programmes, requiring executive decisions or needing an organisational-level response.
04 — FAQ

Risk Register — 5 Common Questions Answered

A risk register is the central document that records all identified project risks. It captures probability, impact, response plans, owners and current status. It is created during the Identify Risks process in PMBOK and updated continuously throughout the project lifecycle. I used a risk register on every single project I managed in the UAE. It should be reviewed at every steering committee meeting and weekly with your team. A risk register that is never updated is worse than not having one. It creates a false sense of security.
A complete risk register needs: unique risk ID, risk category, clear risk description, risk owner, probability score (1 to 5), impact score (1 to 5), overall risk score (probability × impact), risk rating (Low, Medium, High or Critical), response strategy, specific response actions, contingency plan, residual probability and impact after responses are applied, and current status. This template includes all 15 fields. Everything I just listed is in there.
Risk score = Probability × Impact. Both are rated 1 to 5. Probability: 1=Rare (less than 10%), 2=Unlikely (10 to 30%), 3=Possible (30 to 60%), 4=Likely (60 to 80%), 5=Almost Certain (more than 80%). Impact: 1=Negligible, 2=Minor, 3=Moderate, 4=Major, 5=Catastrophic. The score maps to: 1 to 4 Low (green), 5 to 9 Medium (yellow), 10 to 16 High (orange), 17 to 25 Critical (red). This template calculates and colours the score automatically. You just enter the two numbers and everything else updates.
The four PMI strategies for threats are: Avoid (eliminate the risk by changing the plan), Mitigate (reduce probability or impact), Transfer (shift to a third party through insurance or contracts), and Accept (acknowledge and monitor, with or without a contingency plan). A fifth strategy, Escalate, is used when the risk is beyond the PM's authority to manage. For opportunities (positive risks), the equivalent strategies are Exploit, Enhance, Share and Accept. See our full risk management guide for a detailed breakdown of all strategies with examples.
Review the full register at every steering committee meeting, typically fortnightly. Risk owners should update their specific risks weekly. At minimum, review every risk at each project phase gate to confirm scores and response status are still accurate. New risks can emerge at any point. I always ran a risk identification session at the start of each new phase. Closed risks should stay in the register marked as Closed. Never delete them. They form part of your audit trail and are invaluable for lessons learned at project closeout.