Drawing of Stakeholder map

Risk Management, Risk Analysis, Templates and Advice

  • Concise, focused guide that cuts through the clutter
  • Step-by-step instructions for creating a project plan in under a day
  • Master essential skills like work breakdowns and task sequencing
  • Real-world troubleshooting for 20 common scheduling challenges
  • Rapidly get up to speed if you're new to Microsoft Project
  • Includes glossary, support resources, and sample plans
The cover of the book 'Essential Microsoft Project: The 20% You Need to Know'
by | reviewed 17/11/2026

20 Most Common Project Risks – Free Excel Risk Register

Example data from the Excel template. Use the arrows to view the register and dashboard; select an image to enlarge it.

Want a head start on your risk management? Use these 20 common project risks to spot gaps in your own register and find practical actions to tackle them. The free Excel template comes pre-filled with example ratings, suggested owners, mitigation actions and contingency plans.

What is included in the risk register?

  • 20 of the most common project risks that can affect schedule, cost, quality, scope, suppliers, approvals, resources and stakeholders.
  • Example likelihood, impact and severity ratings for each risk.
  • Suggested risk owners, including project sponsor, project manager and team manager roles.
  • Mitigating actions to reduce the likelihood or impact of each risk.
  • Contingency actions to use if the risk happens.
  • Progress and status fields for tracking risk actions during project delivery.
  • Excel .xlsx and legacy .xls download options.
Quick index: the 20 common project risks

Select a risk to open its mitigating and contingency actions in the completed register below.

  1. Project purpose and need is not well-defined. View actions for risk 1
  2. Project design and deliverable definition is incomplete. View actions for risk 2
  3. Project schedule is not clearly defined or understood. View actions for risk 3
  4. No control over staff priorities. View actions for risk 4
  5. Consultant or contractor delays. View actions for risk 5
  6. Estimating and/or scheduling errors. View actions for risk 6
  7. Unplanned work that must be accommodated. View actions for risk 7
  8. Lack of communication, causing lack of clarity and confusion. View actions for risk 8
  9. Pressure to arbitrarily reduce task durations and or run tasks in parallel which would increase risk of errors. View actions for risk 9
  10. Scope Creep. View actions for risk 10
  11. project conflicts not resolved in a timely manner. View actions for risk 11
  12. Business Case becomes obsolete or is undermined by external or internal changes. View actions for risk 12
  13. Delay in earlier project phases jeopardizes ability to meet fixed date. For example delivery of just in time materials, for conference or launch date. View actions for risk 13
  14. Added workload or time requirements because of new direction, policy, or statute. View actions for risk 14
  15. Inadequate customer testing leads to large post go live defect list. View actions for risk 15
  16. Legal action delays or pauses project. View actions for risk 16
  17. Customer refuses to approve deliverables/milestones or delays approval, putting pressure on project manager to 'work at risk'. View actions for risk 17
  18. Theft of materials, intellectual property or equipment. View actions for risk 18
  19. Acts of God for example, extreme weather, leads to loss of resources, materials, premises etc. View actions for risk 19
  20. Stakeholder action delays the project. For more on the damage stakeholders can do see our case studies of real world projects that faced costs running into millions, because of stakeholder actions. View actions for risk 20

Completed risk register with 20 project risks you need to manage

Explore the example risks below. Each card shows the likelihood, impact, severity, owner and status. Select View actions to read the mitigating action, contingency action and progress.

These ratings and owners are examples. Adjust them for your own project.

Understanding the ratingsMitigation vs contingency

01

Project purpose and need is not well-defined.

Likelihood
Medium
Impact
High
Severity
High
Status
Open
View actionsHide actions for risk 1

Mitigating action

Before the risk happens

Complete a business case if not already provided and ensure purpose is well defined on Project Charter and PID.

Contingency action

If the risk happens

Escalate to the Project Board with an assessment of the risk of runaway costs/never-ending project.

Progress on actions

Business case re-written with clear deliverables and submitted to the Project Board for approval.
02

Project design and deliverable definition is incomplete.

Likelihood
Low
Impact
High
Severity
High
Status
Open
View actionsHide actions for risk 2

Mitigating action

Before the risk happens

Define the scope in detail via design workshops with input from subject matter experts.

Contingency action

If the risk happens

Document assumptions made and associated risks. Request high risk items that are ill-defined are removed from scope.

Progress on actions

Design workshops scheduled.
03

Project schedule is not clearly defined or understood

Likelihood
Low
Impact
Medium
Severity
Medium
Owner
Project Manager
Status
Open
View actionsHide actions for risk 3

Mitigating action

Before the risk happens

Hold scheduling workshops with the project team so they understand the plan and likelihood of missed tasks is reduced.
Share the schedule and go through upcoming tasks at each weekly project progress meeting.

Contingency action

If the risk happens

Revisit the schedule with the project team.
'Relaunch' the project schedule.

Progress on actions

Workshops scheduled.
04

No control over staff priorities

Likelihood
Medium
Impact
Medium
Severity
Medium
Owner
Project Manager
Status
Open
View actionsHide actions for risk 4

Mitigating action

Before the risk happens

The Project Sponsor will brief team managers on the importance of the project. Soft book resources as early as possible and then communicate final booking dates asap after the scheduling workshops. Identify back ups for each human resource on the project.

Contingency action

If the risk happens

Escalate to the Project Sponsor and bring in back up resource.

Progress on actions

Project Sponsor has agreed to hold briefing. Now making arrangements for a meeting room.
05

Consultant or contractor delays

Likelihood
Medium
Impact
High
Severity
High
Owner
Project Manager
Status
Open
View actionsHide actions for risk 5

Mitigating action

Before the risk happens

Include late penalties in contracts.
Build in and protect lead time in the schedule.
Communicate schedule early.
Check in with suppliers regularly. Query '90% done'. Ask again and again if they need anything else.

Contingency action

If the risk happens

Escalate to Project Sponsor and Contracts Manager. Implement late clauses.

Progress on actions

Lead time from each contractor built into the project schedule. Late penalties agreed to and contracts signed.
06

Estimating/or scheduling errors

Likelihood
Medium
Impact
High
Severity
High
Owner
Project Manager
Status
Open
View actionsHide actions for risk 6

Mitigating action

Before the risk happens

Break this two risks 'cost estimating' and 'scheduling errors'.
Use two methods of cost estimation, and carefully track costs and forecast cost at completion making adjustments as necessary.
Build in 10% contingency on cost and scheduling.
Track schedules daily and include schedule review as an agenda item in every project team meeting.
Flag forecast errors and/or delays to the Project Board early.

Contingency action

If the risk happens

Escalate to project sponsor and Project Board.
Raise a change request for changes to budget or schedule.
Pull down contingency.

Progress on actions

Contingency agreed by Project Board.
07

Unplanned work that must be accommodated

Likelihood
Low
Impact
High
Severity
Medium
Owner
Team Manager
Status
Open
View actionsHide actions for risk 7

Mitigating action

Before the risk happens

Attend project scheduling workshops.
Check previous projects, for actual work and costs.
Check all plans and quantity surveys.
Document all assumptions made in planning and communicate to the project manager before project kick off.

Contingency action

If the risk happens

Escalate to the Project Manager with plan of action, including impact on time, cost and quality.

Progress on actions

Team managers attending scheduling workshops.
08

Lack of communication, causing lack of clarity and confusion.

Likelihood
Medium
Impact
Medium
Severity
Medium
Owner
Project Manager
Status
Open
View actionsHide actions for risk 8

Mitigating action

Before the risk happens

Write a communication plan which includes: the frequency, goal, and audience of each communication.
Identify stakeholders early and make sure they are considered in the communication plan. Use most appropriate channel of communication for audience e.g. don't send 3 paragraph email to Developers, have a call instead.

Contingency action

If the risk happens

Correct misunderstandings immediately. Clarify areas that are not clear swiftly using assistance from Project Sponsor if needed.

Progress on actions

Communication plan in progress.
09

Pressure to arbitrarily reduce task durations and or run tasks in parallel which would increase risk of errors.

Likelihood
Low
Impact
High
Severity
Medium
Owner
Project Manager
Status
Open
View actionsHide actions for risk 9

Mitigating action

Before the risk happens

Share the schedule with key stakeholders to reduce the risk of this happening.
Patiently explain that schedule was built using the expertise of subject matter experts. Explain the risks of the changes. Share the Dennis Lock quote at Why you should never arbitrarily reduce task durations.

Contingency action

If the risk happens

Escalate to Project Board with assessment of risk and impact of the change.
Hold emergency risk management call with decision makers & source of pressure and lay out risk and impact.

Progress on actions

Awaiting completion of the schedule.
10

Scope Creep
(the adding of features and functionality without assessing the impact on time, costs, and resources, or without customer approval).

Likelihood
Medium
Impact
High
Severity
High
Owner
Project Manager
Status
Open
View actionsHide actions for risk 10

Mitigating action

Before the risk happens

Document the project scope in a Project Initiation Document or Project Charter and get it authorised by the Project Board. Refer to it throughout the project and assess all changes against it also ensuring alignment of any changes with the Business Case.

Contingency action

If the risk happens

Document each and every example of scope creep NO MATTER HOW SMALL in a change request and get authorisation from the Project Board BEFORE STARTING WORK. This includes ZERO COST changes.

Progress on actions

Scope clearly defined in the PID.
11

Unresolved project conflicts not escalated in a timely manner

Likelihood
Low
Impact
Medium
Severity
Medium
Owner
Project Manager
Status
Open
View actionsHide actions for risk 11

Mitigating action

Before the risk happens

Hold regular project team meetings and look out for conflicts. Review the project plan and stakeholder engagement plan for potential areas of conflict.

Contingency action

If the risk happens

When aware immediately escalate to Project Board and gain assistance from Project Sponsor to resolve the conflict.

Progress on actions

Project team meetings scheduled.
12

Business Case becomes obsolete or is undermined by external or internal changes.

Likelihood
Low
Impact
High
Severity
High
Status
Open
View actionsHide actions for risk 12

Mitigating action

Before the risk happens

No ability to reduce likelihood, but make sure early warning is given by reviewing the business case on a regular basis with the Project Board.

Contingency action

If the risk happens

Initiate escalation and project close down procedure.

Progress on actions

Project close down procedure confirmed with Project Board.
13

Delay in earlier project phases jeopardizes ability to meet fixed date. For example, delivery of just in time materials, for conference or launch date.

Likelihood
Medium
Impact
High
Severity
High
Owner
Project Manager
Status
Open
View actionsHide actions for risk 13

Mitigating action

Before the risk happens

Ensure the project plan is as accurate as possible using scheduling workshops and work breakdown structure. Use Tracking Gantt and Baseline to identify schedule slippage early.

Contingency action

If the risk happens

Consider insurance to cover costs and alternative supplier as a back up.

Progress on actions

Awaiting completion of the schedule.
14

Added workload or time requirements because of new direction, policy, or statute

Likelihood
Low
Impact
Medium
Severity
Medium
Status
Open
View actionsHide actions for risk 14

Mitigating action

Before the risk happens

No ability to reduce likelihood.

Contingency action

If the risk happens

Consider insurance and use Project Board to get advance notice if possible.

Progress on actions

Project Board reviewing insurance options.
15

Inadequate customer testing leads to large post go live snag list.

Likelihood
High
Impact
High
Severity
High
Owner
Project Manager
Status
Open
View actionsHide actions for risk 15

Mitigating action

Before the risk happens

Ensure customer prepares test cases/quality checks and protect testing/quality assurance window.

Contingency action

If the risk happens

Raise risk immediately and raise issue if it is clear testing inadequate. Customer could extend testing & bring in additional resource.

Progress on actions

Customer preparing test cases.
16

Legal action delays or pauses project.

Likelihood
Low
Impact
Medium
Severity
Medium
Status
Open
View actionsHide actions for risk 16

Mitigating action

Before the risk happens

Ensure all contracts signed before starting the project. Follow all regulatory requirements and complete stakeholder management plan.

Contingency action

If the risk happens

Escalate to Project Board who will notify legal department. Follow instructions from legal.

Progress on actions

Contracts issued.
17

Customer refuses to approve deliverables/milestones or delays approval, putting pressure on project manager to 'work at risk'.

Likelihood
Medium
Impact
Medium
Severity
Medium
Owner
Project Manager
Status
Open
View actionsHide actions for risk 17

Mitigating action

Before the risk happens

Ensure customer decision maker with budgetary authority is identified before project start and is part of the Project Board. Communicate dates for sign-off points up front.

Contingency action

If the risk happens

Escalate to Project Board and recommend action e.g. to stop the project.

Progress on actions

Customer project manager is confirming their sponsor / senior supplier.
18

Theft of materials, intellectual property or equipment.

Likelihood
Low
Impact
High
Severity
High
Owner
Project Manager
Status
Open
View actionsHide actions for risk 18

Mitigating action

Before the risk happens

Follow security procedures, ensure Non-Disclosure Agreements, & compliance certificates are in place. Verify all physical security measures in place. Secure insurance.

Contingency action

If the risk happens

Notify appropriate authorities e.g. police, Project Board and initiate internal investigations.

Progress on actions

NDAs issued. Security certificates confirmed for contractors.
19

Acts of God for example, extreme weather, leads to loss of resources, materials, premises etc.

Likelihood
Low
Impact
High
Severity
High
Owner
Project Manager
Status
Open
View actionsHide actions for risk 19

Mitigating action

Before the risk happens

Check insurance is in place. Familiarise project team with emergency procedures. When cost effective put back up systems in place e.g. generators.

Contingency action

If the risk happens

Notify appropriate authorities. Follow health and safety procedures. Notify stakeholders and Project Board.

Progress on actions

Public Liability Insurance confirmed along with additional premises insurance at site B.
20

Stakeholder action delays project.

Likelihood
Low
Impact
High
Severity
High
Owner
Project Manager
Status
Open
View actionsHide actions for risk 20

Mitigating action

Before the risk happens

Identify stakeholders, analyze power and influence and create a Stakeholder Engagement Plan. Project Board to authorise the plan. Revisit the plan at regular intervals to check all Stakeholders are managed. Consider getting insurance.

Contingency action

If the risk happens

Notify appropriate authorities and follow internal procedures e.g. for activist demonstrations.

Progress on actions

Download this risk register of common project risks

Common mistakes when using a risk register

A risk register is only useful if it is actively reviewed and updated. Avoid these common mistakes when adapting this example for your own project.

  • Copying risks without tailoring them. Use the 20 risks as prompts, then rewrite them so they match your project, suppliers, stakeholders and constraints.
  • Confusing mitigation with contingency. Mitigation is action taken before a risk happens; contingency is the backup plan if it happens.
  • Leaving risks without owners. Every important risk needs a named owner who can monitor it and progress actions.
  • Using ratings once and never reviewing them. Likelihood, impact and severity should change as the project changes.
  • Recording vague actions. A good action should say what will be done, who will do it and when it will be reviewed.
  • Not escalating high risks. High risks that threaten cost, schedule, scope or benefits should be visible to the project sponsor or project board.

Help using this risk register

The risk register includes likelihood, impact, severity, owners, mitigating actions and contingent actions. These guides explain how to use those fields properly.

How to use a risk register in Excel

Learn what each column means, how to add risks, assign owners and keep the register useful.

Likelihood, impact and severity

Understand how likelihood and impact combine to produce a Low, Medium or High severity rating.

Mitigation vs contingency

See the difference between action taken before a risk happens and the backup plan if it happens.

Download a complete risk register of common project risks

Download the template, review the example risks, then edit the descriptions, scores, owners and actions so they fit your own project. The .xlsx version is recommended for most users.

Excel download (.xlsx) - FREE Risk Register of Common Risks

Excel 1997 - 2003 download (.xls) - FREE Risk Register of Common Risks

MindMap download - FREE MindMap of Common Project Risks

Video - How to edit the risk register

Related risk management templates and guides

How to Use a Project Risk Register in Excel

Likelihood, Impact and Severity in a Risk Register

Mitigation vs Contingency in Project Risk Management

The Top 50 Business Risks and how to manage them!

Checklist of 30 Construction Risks

Download a Risk Register template

Overall Project Risk Assessment Template

Simple Risk Register Template

Frequently asked questions

What are common project risks?

Common project risks include unclear scope, poor communication, supplier delays, scheduling errors, inadequate testing, lack of resources, late approvals, stakeholder action and changes that undermine the business case.

What should be included in a project risk register?

A project risk register should include the risk description, likelihood, impact, severity, owner, mitigation action, contingency action, action progress and status. Some organisations also include trigger points, residual risk and review dates.

What is the difference between mitigation and contingency?

Mitigation is action taken before a risk happens to reduce its likelihood or impact. Contingency is the backup action used if the risk actually happens.

Can I use this risk register in Excel?

Yes. The template is provided as an Excel download and can be edited for your own project. The .xlsx file is the best option for most users, while the .xls file is included for older versions of Excel.

Should I use all 20 risks on my project?

No. Use the list as a starting point. Delete risks that do not apply, rewrite risks that need more context and add risks that are specific to your project, organisation, supplier or stakeholder environment.

Resources used in this article

Lock, D. (2007) Project Management Ninth Edition, Aldershot, England and Brookfield, Vt: Gower Publishing Limited