27 Risk Categories for Project Managers + Free Checklist

27 risk category examples for project managers, with a free risk category checklist tool

Every project carries some possibility that things will not go as planned, and treating risk as one vague threat leaves teams unprepared for the specific problems they are likely to face. Sorting risk into categories gives project managers a repeatable lens for spotting trouble before it escalates into missed deadlines, budget overruns, or failed deliverables, and it builds a shared vocabulary among stakeholders.

Key takeaways

  1. Categories turn vague risk into a checklist. Grouping risks into technical, management, commercial and external families gives project managers a repeatable way to spot trouble early.

  2. Identify before you list. Start from the project’s purpose, goals and constraints, then combine techniques such as Delphi, SWOT and root cause analysis.

  3. Real projects show the cost. The Sydney Opera House finished at 14 times its estimate, and NASA lost a Mars orbiter over a units mismatch at a team interface.

  4. Score, own and review every category. Rate likelihood and impact, give each category an owner, build a risk breakdown structure and revisit it at every milestone.

Score your project with the free Risk Category Checklist

This guide walks through twenty-seven practical risk category examples drawn from real project environments, spanning technical, commercial, and external threats alike. You will also find methods for identifying which categories matter most to your project, along with a framework for grouping them into a risk breakdown structure and a free checklist tool to score your own project. Read on to see how these categories apply directly to your next initiative.

How to Identify Risk Categories

Four steps to identify project risk categories: purpose and need, goals and outcomes, project constraints, and assessment techniques

Spotting the right project categories starts before you ever open a risk register. Project managers who understand why the work exists, what constraints bind it, and which techniques surface hidden threats are far better positioned to build a category list that actually reflects their environment. The four areas below form a practical starting sequence for that identification work.

Purpose and Need

Identifying risk categories begins with a clear sense of purpose. Once you know exactly what the project is meant to accomplish, it becomes much easier to determine which risks genuinely threaten that outcome. Understanding the underlying reason for the work first allows you to approach specific tasks with a clearer view of where things could realistically go wrong later.

Project Goals, Objectives & Outcomes

Clear goals give risk identification a target to measure against. This means understanding what the final product or result should look like, along with any subgoals that support the larger objective. Teams documenting these outcomes should provide concrete examples so stakeholders can apply the same thinking later, ensuring the product or process remains user-friendly and lets people complete tasks with minimal friction.

Project Constraints

A project’s constraints shape which risks are even possible to encounter. Recognizing these boundaries helps you determine what can be changed or adapted when obstacles appear. Ask direct questions such as whether the task must be finished by a fixed date or whether specific regulations apply, so you understand exactly what restrictions govern the project before risks are assessed.

Risk Assessment Techniques

Before naming risk categories, examine whether your organization already maintains a defined set of them through its documented process assets. Several proven techniques exist for surfacing risks that would otherwise stay hidden until they cause real damage to the schedule or budget. Combining more than one of these methods, rather than relying on a single approach, typically produces a far more complete and reliable risk picture overall.

These proven techniques tend to work best when combined together:

  • Delphi Technique: Gathers anonymous input from a panel of experts across multiple rounds to reach consensus on likely risks without groupthink skewing the results.
  • Root Cause Analysis: Traces a known problem back through its contributing factors to identify the underlying driver rather than just the visible symptom.
  • SWOT Analysis: Examines strengths, weaknesses, opportunities, and threats together so risks are considered alongside the project’s competitive position.
  • Documentation Reviews: Checks prior project plans, contracts, and lessons learned for recurring risk patterns that a new project is likely to repeat.
  • Brainstorming and The Risk Register: Captures raw team input quickly, then organizes it into a structured, trackable log for ongoing monitoring.
  • Impact Matrix and Simulation: Scores risks by probability and severity, then models potential outcomes to prioritize where mitigation effort should go first.

27 Risk Category Examples

With the identification techniques covered, it’s time to look at risk categories in action. The list below breaks down twenty-seven real-world examples project managers regularly encounter, from technical and budgetary risks to supplier, regulatory, and environmental threats. Use it as a reference to check your own project against categories you may not have considered yet.

The 27 project risk category examples, color coded by technical, management, commercial and external group

1. Scope

Scope risk emerges when a project fails to deliver what it originally promised, creating a ripple effect across deadlines, budgets, and stakeholder trust. This failure can stem from causes ranging from unclear contract terms to shifting client expectations midway through delivery. Left unmanaged, it forces teams into constant rework rather than steady forward progress toward the original objective.

Every scope risk deserves consideration, whether it has already been quantified or not. The category spans a wide range, from gradual scope creep to outright defects in delivered software or hardware. Common contributors include insufficiently specified requirements, unforeseen changes to the legal or regulatory framework, and integration problems that surface only once components are combined.

Scope risk in practice

Real-life example

The FBI’s Virtual Case File

The FBI spent about $170 million over roughly 40 months on a case management system it never accepted. The Justice Department’s inspector general traced the failure mainly to requirements that kept changing after September 11, along with poorly defined specifications, unrealistic schedules and weak oversight.

Source: DOJ Office of the Inspector General, Audit 05-07 (2005)

By the numbers

$170M

spent on the system by late 2004, with no usable release

Source: DOJ Office of the Inspector General, Audit 05-07 (2005)

Project manager takeaway

Freeze a baseline, then route every new requirement through change control before anyone builds it.

2. Estimates & Assumptions

Few projects get off to a perfectly accurate start, and few would ever launch at all if absolute certainty were required before beginning. That reality is exactly why estimates and assumptions function as critical variables in producing timely, realistic project outcomes. Every schedule and budget is built on a foundation of educated guesses that must be actively managed rather than ignored.

Making any estimate necessarily requires relying on assumptions, and an assumption that later proves false behaves exactly like a risk that has been realized. Estimate buffering helps absorb both of these pressures without derailing the schedule entirely. Documenting assumptions alongside estimates as the project unfolds gives teams an early warning system when reality starts to diverge from the original plan.

Estimates & assumptions risk in practice

Real-life example

Most big-project estimates miss

Oxford professor Bent Flyvbjerg’s research on large projects found that only a small minority meet or beat both their schedule and cost estimates, and almost none also deliver every promised benefit. The pattern points to optimistic assumptions made at the start rather than bad luck later.

Source: Bent Flyvbjerg via Thought Economics

By the numbers

8.5%

of projects meet or beat both their time and budget estimates; only 0.5% also deliver the promised benefits

Source: Bent Flyvbjerg via Thought Economics

Project manager takeaway

Write each assumption next to the estimate it supports, and give it an owner who checks it at every milestone.

3. Budget

Budget risk, also known as cost risk, arises when the money allotted to a project or activity turns out to be inaccurately estimated from the start. The consequences ripple outward quickly once funding runs short. Teams often discover the gap only after committing resources, which limits their options for correcting course without affecting other parts of the schedule.

The practical fallout from budget risk includes delayed project completion, premature handover before work is truly finished, and an inability to deliver the quality originally promised to the client. In some cases, teams knowingly ship a compromised version of the deliverable simply to stay within the remaining funds, trading long-term satisfaction for short-term financial compliance.

Budget risk in practice

Real-life example

The Sydney Opera House

The Sydney Opera House was estimated at A$7 million and finished in 1973 at A$102 million. Guinness World Records lists it as the largest proportional cost increase for a building project.

Source: Guinness World Records

By the numbers

14x

final cost compared with the original estimate

Source: Guinness World Records

Project manager takeaway

Track cost variance monthly and agree a contingency release rule with the sponsor before work starts.

4. Technical & Architectural

Technical and architectural risks jeopardize an organization’s overall functionality and performance at a structural level, rather than affecting one isolated feature. These risks typically surface due to the failure of the software and hardware tools and equipment used on a specific project. A weak architectural foundation tends to produce cascading problems that become more expensive to fix the longer they go unaddressed.

Technical & architectural risk in practice

Real-life example

England’s National Programme for IT

The NHS National Programme for IT set out to build national care records systems. Delays in developing and deploying those systems led to the programme being dismantled in September 2011, with the Department of Health forecasting total costs of £9.8 billion and MPs warning the figure would keep rising.

Source: Computer Weekly

By the numbers

$1.52T

accumulated software technical debt in the US, part of $2.41 trillion in poor-quality software costs

Source: CISQ, Cost of Poor Software Quality 2022

Project manager takeaway

Run an architecture review before the build phase and test integration early with a thin working slice.

5. Technology

Technology risk, often called information technology risk, describes the possibility that a technological failure disrupts the firm’s ability to operate normally. Companies face a wide range of exposures here, including information security incidents, cyberattacks, password theft, service disruptions, and other issues that can halt work without warning. Modern project environments depend so heavily on connected tools that even a brief outage can stall an entire team.

Any technology risk that materializes can produce financial, reputational, regulatory, and strategic consequences all at once, rather than staying contained to a single department. This makes an effective technology risk management strategy essential for anticipating problems before they escalate. Regular security audits, patch management, and access controls all reduce the likelihood that a single vulnerability becomes an organization-wide incident.

Technology risk in practice

Real-life example

The CrowdStrike update outage

On July 19, 2024, a faulty security software update crashed Windows systems worldwide, grounding flights and disrupting hospitals, banks and retailers. Many teams lost days to manual recovery of each affected machine.

Source: TechCrunch, July 20, 2024

By the numbers

8.5M

Windows devices affected, according to Microsoft

Source: TechCrunch, July 20, 2024

Project manager takeaway

Ask vendors how they stage updates, and keep a tested manual workaround for every critical tool.

6. Interface

Interface risk arises whenever a project’s success depends on the interaction between two or more stakeholders, systems, or teams working across a shared boundary. When separate contractors are engaged in the design of the same or adjacent development, physical interfaces become common points of friction. Miscommunication at these handoff points is often where small errors compound into larger delivery problems.

Interface risk in practice

Real-life example

The Mars Climate Orbiter

NASA lost the Mars Climate Orbiter in 1999 after ground software supplied data in English units where navigation expected metric. The review board also pointed to a small, overloaded navigation team and weak cross-checking between NASA’s Jet Propulsion Laboratory and its industrial partner, Lockheed Martin.

Source: NASA Mishap Investigation Board release, Nov 10, 1999

Project manager takeaway

Write an interface control document for every handoff and verify units, formats and owners on both sides.

7. Performance

Performance risk is the possibility that a product, service, program, or project fails to deliver as much value as the situation or environment genuinely requires. This risk applies broadly, covering internal projects, outsourced work, and product or service purchases made from another company entirely. Establishing clear performance benchmarks early makes it far easier to detect this risk before it affects end users.

Performance risk in practice

Real-life example

The HealthCare.gov launch

HealthCare.gov went live on October 1, 2013, and suffered outages and malfunctions at launch and for weeks after. The HHS inspector general named the absence of clear leadership as the most critical problem and found warning signs had been ignored before go-live.

Source: HHS Office of Inspector General (2016)

By the numbers

~2 months

for the reorganized team to return the site to high consumer use

Source: HHS Office of Inspector General (2016)

Project manager takeaway

Define measurable performance targets and load test against them before you commit to a launch date.

8. Quality & Process

Quality and process risks tend to surface from inefficient application of process customization or from hiring staff who have not received adequate training for the work at hand. These gaps rarely announce themselves immediately, instead accumulating quietly until output quality begins to slip. The result is a compromised process that produces inconsistent outcomes and erodes overall quality across the project.

Quality & process risk in practice

Real-life example

Alaska Airlines flight 1282

On January 5, 2024, a door plug blew out of a Boeing 737-9 shortly after takeoff. Investigators found the four bolts meant to hold it in place were missing, and the NTSB tied the cause to inadequate training, guidance and oversight of factory workers.

Source: NTSB press release, June 24, 2025

By the numbers

4

retaining bolts missing from the door plug

Source: NTSB press release, June 24, 2025

Project manager takeaway

Make every critical process step verifiable, and audit that the documented process is the one people follow.

9. Project Schedule & Dependencies

Project schedule and dependency risks are associated with unexpected linkages or missing inputs that significantly affect the project’s timeline from one phase to the next. These dependencies primarily influence project deliverables and the underlying work itself, which is why they are typically grouped alongside risks associated with scope changes. Mapping dependencies visually early in planning helps surface these linkages before they cause delays.

Schedule & dependency risk in practice

Real-life example

Berlin Brandenburg Airport

Berlin’s new airport finally opened on October 31, 2020, nine years later than first planned. It cost about €6 billion, roughly three times the original budget.

Source: Associated Press, Oct 31, 2020

By the numbers

9 years

late: planned for October 2011, opened October 2020

Source: Associated Press, Oct 31, 2020

Project manager takeaway

Map external dependencies, such as approvals and inspections, on the schedule with owners and buffers.

10. Logistics

Logistics risks include transportation, warehousing, shipping, and inventory management, along with risks tied to leadership at every level of the supply chain and logistics function. Projects involving ports, shipping, or other maritime operations may also face specialized staffing risks. In these cases, maritime recruiters helping organizations source personnel with the required industry experience can materially reduce the risk of critical roles going unfilled during a project.

Logistics risk in practice

Real-life example

The Ever Given in the Suez Canal

In March 2021 the container ship Ever Given wedged across the Suez Canal for six days. Shipping data firm Lloyd’s List estimated that roughly $9.6 billion of goods were held up for every day of the blockage.

Source: Al Jazeera, March 25, 2021

By the numbers

$9.6B

of ship traffic held up per day, a rough Lloyd’s List estimate

Source: Al Jazeera, March 25, 2021

Project manager takeaway

Identify single shipping routes and suppliers in your plan, and price an alternative before you need it.

11. Resourcing

Risks tied to recruiting people for a project can shift with changes in staff turnover levels across an organization’s broader workforce. When key contributors leave unexpectedly, delays follow if replacement personnel cannot be sourced quickly enough to keep the schedule intact. This makes workforce planning an ongoing task rather than a one-time exercise completed at project kickoff.

Resource risk is the possibility of failing to complete a task due to a genuine lack of available resources. Financing, bridging loans, time, skilled workers, and anything else required to reach a specific goal all count as resource types worth tracking. This category of risk generally arises from inefficient management of a company’s resources, including its people and its budget allocations.

Every project will have different categories. Healthcare organizations, for example, link their risk categories to strategic objectives, as this HIROC healthcare project guidance on risk identification shows, which is why the examples that follow move from project-level risks to wider organizational ones.

Resourcing risk in practice

Real-life example

US air traffic control staffing

A 2023 audit by the US Department of Transportation’s inspector general found that 20 of the FAA’s 26 most critical air traffic facilities were staffed below the agency’s 85 percent threshold, raising the risk of delays across the system.

Source: DOT Office of Inspector General (2023)

By the numbers

25M

new project professionals needed worldwide by 2030

Source: PMI Talent Gap report

Project manager takeaway

List the roles only one person can do today and plan cross-training or backup before the project needs them.

12. Funding

Funding risk is different from budget risk. A budget can be estimated correctly and still fail the project if the approved money does not arrive when the work needs it, a pattern that shows up repeatedly across healthcare and other regulated environments where funding cycles are rigid. Grants, annual appropriations and staged releases of capital all create points where work can stall while teams wait for the next tranche.

Like budget risk, funding gaps can force a project to be handed over prematurely, deliver a lower-quality result, or offer a version that falls short of what was originally promised to the client. Healthcare organizations in particular track this closely because funding shortfalls there can directly affect patient care outcomes.

Funding risk in practice

Real-life example

The 2025 US government shutdown

Federal funding lapsed from October 1 to November 12, 2025, the longest shutdown in US history. Work that depended on new appropriations had to wait until Congress acted, leaving contractors and grant-funded projects with paused activities.

Source: Ballotpedia

By the numbers

6+ weeks

of lapsed federal funding

Source: Ballotpedia

Project manager takeaway

Check when each funding tranche is released and what work stops if one arrives late.

13. Communication

Communication risk covers the inability to exchange information reliably with other entities, whether those entities are people, software systems, or entire processes within the organization. If every party held identical information at all times, there would be no need for communication and, consequently, no communication risk to manage in the first place. People are not all-knowing, which is exactly why this category matters on distributed teams.

Communication risk in practice

Real-life example

Hawaii’s false missile alert

In January 2018 a false ballistic missile alert went out to phones across Hawaii, and residents waited 38 minutes for a correction. The FCC found human error, two supervisors who misunderstood each other, and no standard way to retract the message.

Source: NPR, April 11, 2018

By the numbers

56%

of the budget at risk on a failing project is tied to ineffective communication

Source: PMI Pulse of the Profession (2013)

Project manager takeaway

Agree who confirms critical messages, which channel they use, and how a wrong message is corrected.

14. Contractual

Any legal agreement signed during a project can pose financial risk if the other party fails to honor it, such as a vendor accepting payment without completing the agreed work. This exposure grows in proportion to how many external parties a project depends on for critical deliverables.

A contract risk definition generally breaks down into two scenarios:

  1. Buyer Non-Compliance: There is a possibility of incurring losses due to the buyer’s failure to comply with the contract terms, excluding cases where the buyer is simply unable to pay.
  2. Poor Transaction Performance: Losses may result from the transaction’s poor overall performance. Sellers face the most exposure with fixed-price contracts and the least exposure with cost-type contracts.
Contractual risk in practice

Real-life example

Hertz versus Accenture

Hertz hired Accenture in 2016 to build a new website and apps. After go-live dates slipped from December 2017 into 2018, Hertz ended the engagement and in 2019 sued for the $32 million it had paid plus remediation costs. Accenture said the claims were without merit.

Source: TechSpot, April 2019

By the numbers

~9%

of annual value lost on average to poor contract management

Source: World Commerce & Contracting

Project manager takeaway

Tie payments to accepted deliverables and define acceptance criteria inside the contract itself.

15. Internal Procurement

Internal procurement risk is associated with how well procurement functions inside an organization, spanning supplier management, logistics, and vendor relationships that ultimately feed into the buying decisions made by purchasing departments. Weak procurement processes tend to surface only once a shipment is late or a budget line runs over. These risks tend to trace back to a handful of recurring root causes worth tracking closely.

These procurement risks tend to occur for a few common reasons:

  • Overstated or Understated Need: Purchasing requests that misjudge actual demand lead to either wasted spend on excess inventory or costly last-minute shortages.
  • Unrealistic Timescales and Schedules: Overly aggressive deadlines strain suppliers and internal teams alike; applying critical chain or critical path methods helps recalibrate expectations.
  • Poorly Designed Requirements: Vague or incomplete specifications during the request phase often force expensive rework once the wrong items or services arrive.
Procurement risk in practice

Real-life example

Scotland’s ferries 801 and 802

Two island ferries ordered from Ferguson Marine in 2015 were almost four years late by 2022, with costs reaching at least £240 million. Audit Scotland found the contract went ahead even though the yard could not provide the mandatory refund guarantees.

Source: Audit Scotland, March 2022

By the numbers

2.5x

the original contract cost, according to Audit Scotland

Source: Audit Scotland, March 2022

Project manager takeaway

Never waive a procurement safeguard to keep a schedule; escalate the decision and record why.

16. Suppliers & Vendors

The risk associated with suppliers and vendors covers any exposure tied to how a supplier or vendor operates or organizes its own business, since problems on their end can directly harm the client organization’s activity. A vendor’s financial instability, quality control lapses, or capacity constraints all count as legitimate sources of this risk and deserve regular monitoring throughout the relationship.

Supplier risk in practice

Real-life example

The 2021 chip shortage

A global shortage of semiconductors forced carmakers to idle plants throughout 2021. AlixPartners forecast that the shortage would cut auto industry revenue by $210 billion that year.

Source: AlixPartners, Sept 23, 2021

By the numbers

7.7M

vehicles of lost production forecast for 2021

Source: AlixPartners, Sept 23, 2021

Project manager takeaway

Rank suppliers by how hard they are to replace, and hold extra stock or a second source for the top few.

17. Subcontracts

Subcontract risk covers the exposures created by bringing outside parties into delivery through formal subcontracting arrangements. A common practice in the software development industry involves using non-standard subcontract conditions prepared directly by the contractor rather than a neutral template. In such subcontracts, many of the requirements skew harsh, which is exactly why contractors regularly build risk allowances into their bid pricing from the outset.

Subcontract risk in practice

Real-life example

Boeing and Spirit AeroSystems

Spirit AeroSystems, spun off from Boeing in 2005, built 737 fuselages under contract. On July 1, 2024, Boeing agreed to buy Spirit back, saying it would let the company fully align its production systems with its safety and quality priorities.

Source: Boeing press release, July 1, 2024

By the numbers

$8.3B

total transaction value, including Spirit’s net debt

Source: Boeing press release, July 1, 2024

Project manager takeaway

Give subcontracted work the same quality checks and visibility you apply to work done in house.

18. Client Stability

Whenever a new business relationship or transaction with a customer begins, a series of risks accompanies that relationship from day one. Identifying and assessing the potential risks a customer may pose is critical to protecting the engagement long term. Doing this work up front helps reduce the likelihood that unexpected events later cause the broader working relationship or delivery system to malfunction.

Client stability risk in practice

Real-life example

The collapse of Carillion

UK construction and services giant Carillion went into liquidation in January 2018. A parliamentary report found about 30,000 suppliers, subcontractors and other short-term creditors were owed roughly £2 billion, many of them paid on 120-day terms.

Source: The Construction Index, May 2018

By the numbers

£2B

owed to suppliers, subcontractors and short-term creditors

Source: The Construction Index, May 2018

Project manager takeaway

Watch client payment behavior and financial news, and shorten payment terms when warning signs appear.

19. Partnerships

Partnership risk is faced whenever a partner proves unable to carry out their agreed responsibilities within a joint arrangement. This inability can stem from financial strain, shifting priorities, or simple capacity constraints on the partner’s side of the relationship. Regardless of the cause, the effects reach the financial position, creditworthiness, or overall ability to perform of everyone involved in the partnership.

Partnership risk in practice

Real-life example

Boeing’s Starliner crew flight

NASA’s commercial crew partnership with Boeing reached its first crewed Starliner flight on June 5, 2024, planned for about eight to ten days. Thruster problems and helium leaks led NASA to return Starliner empty in September 2024, and the two astronauts came home on a SpaceX capsule in March 2025.

Source: NASASpaceFlight.com, March 2025

By the numbers

286 days

the astronauts spent in space instead of about 10

Source: NASASpaceFlight.com, March 2025

Project manager takeaway

Agree in advance what happens if a partner cannot deliver, including a fallback partner or option.

20. Legislation

Legislative risk refers to the possibility that regulations or legislation enacted by government bodies will significantly impact the prospects of one or more companies, and the projects they run, within that jurisdiction. These changes can reduce the value of a planned deliverable or investment almost overnight. Legislative risk can arise directly from government action or indirectly through shifts in the demand patterns of a company’s own customers.

Legislation risk in practice

Real-life example

The EU’s AI Act

The EU AI Act entered into force in 2024 and phases in obligations over several years: banned AI practices from February 2, 2025, and duties for general-purpose AI models from August 2, 2025. Project managers delivering AI features in Europe must plan for these dates.

Source: DLA Piper, August 2025

By the numbers

7%

of global annual turnover, or €35 million, the maximum fine for banned practices

Source: DLA Piper, August 2025

Project manager takeaway

Track pending laws in your delivery markets and assign someone to translate each one into requirements.

21. Market Rates

Market rate risk is the possibility that prices set by the wider market move against the project after the budget is approved. Interest rates, exchange rates, material prices and labor rates can all change during delivery for reasons no single organization controls, raising the cost of the same scope of work.

Investors call the broader version of this exposure market risk, or undiversifiable risk, because it affects all asset classes at once and is genuinely difficult to predict. Projects cannot diversify it away either, so project managers rely on hedging tools such as fixed-price supply contracts, price escalation clauses and currency hedges, and they test the business case against higher rates before committing.

Market rate risk in practice

Real-life example

Ørsted’s Ocean Wind projects

On October 31, 2023, Ørsted stopped developing its Ocean Wind 1 and 2 offshore wind projects in New Jersey. The company cited supplier delays and rising long-dated US interest rates that weakened the business case.

Source: Ørsted company announcement, Oct 31, 2023

By the numbers

DKK 28.4B

in impairments recognized by Ørsted in its nine-month 2023 report

Source: Ørsted company announcement, Oct 31, 2023

Project manager takeaway

Run your business case at higher interest, material and labor rates to see where it breaks.

22. Business Continuity

Business continuity risk appears whenever data is lost, services become unusable, or productivity suffers because access to critical systems or services disappears unexpectedly. In other words, if something renders one or more essential business processes inoperable for any meaningful length of time, the entire company can be put at financial risk. Recovery planning and regular backups are the most direct defenses against this category.

Business continuity risk in practice

Real-life example

The CDK Global cyberattacks

Cyberattacks on June 18 and 19, 2024, forced CDK Global to shut down most of its systems. Thousands of car dealerships that relied on CDK’s dealer management software fell back to manual processes for days.

Source: Help Net Security, June 2024

By the numbers

15,000+

dealerships in North America use the CDK platform

Source: Help Net Security, June 2024

Project manager takeaway

Document how the team keeps working if a core platform is offline for a week, and rehearse it.

23. Regulations

Regulation risk refers to the possibility that a change in laws or regulations will materially impact security, business operations, an entire industry, or a market in the future. When a government or regulatory body updates the rules, business costs can rise sharply and without much warning. The attractiveness of an investment can decrease as compliance overhead grows heavier for affected organizations.

Beyond rising costs, regulatory shifts can dramatically change the competitive landscape within a given business sector almost overnight, forcing companies to reassess their positioning. In extreme cases, such modifications can completely dismantle a company’s existing business model, forcing a full strategic pivot. Monitoring pending legislation before it takes effect gives project teams meaningful lead time to adjust.

Regulatory risk in practice

Real-life example

A record GDPR fine for Meta

On May 22, 2023, Ireland’s Data Protection Commission fined Meta €1.2 billion for transferring EU users’ personal data to the US in breach of the GDPR, and ordered it to suspend those transfers within five months.

Source: Hunton Andrews Kurth, May 2023

By the numbers

€1.2B

the largest GDPR fine announced to date at that time

Source: Hunton Andrews Kurth, May 2023

Project manager takeaway

Add compliance sign-off as a gate in the plan for any change that touches regulated data.

24. Weather

Weather risk describes a company or organization’s exposure to environmental factors that could lower its profits or threaten its ability to operate at all. Anything that plausibly threatens a company’s capacity to achieve its financial goals falls under this category, including severe storms, seasonal disruptions, and climate-related delays affecting physical sites, construction schedules, or supply routes tied to the project.

Weather risk in practice

Real-life example

Hurricane Helene and IV fluids

Hurricane Helene damaged Baxter’s North Cove plant in Marion, North Carolina, which makes about 60% of US IV solutions. Baxter temporarily closed the plant on September 29, 2024, and began allocating IV products to hospitals.

Source: American Hospital Association

By the numbers

27

separate billion-dollar weather and climate disasters in the US in 2024

Source: NOAA Climate.gov

Project manager takeaway

Check whether a key supplier or site sits in one weather-exposed location, and plan a backup.

25. Facilities

Facility risk is the possibility that a physical facility, such as a data center, fails and causes a loss or a disruption to software development and other project activity. This, in turn, can bring the entire development process to a standstill until the facility issue is resolved. Redundant infrastructure and documented failover plans meaningfully reduce how long such a standstill actually lasts.

Facilities risk in practice

Real-life example

The OVHcloud Strasbourg fire

On March 10, 2021, fire destroyed OVHcloud’s SBG2 data center in Strasbourg and partly destroyed SBG1. Power was cut to the whole site, and OVH told customers with production systems there to activate their recovery plans.

Source: The Register, March 10, 2021

Project manager takeaway

Keep backups in a different facility from production, and test a restore before you rely on it.

26. Reporting & Briefings

Reporting and briefing risk is the possibility that sponsors and decision makers act without the analysis, forecasts and data they need about the project’s financial and operational risk factors. When status reports arrive late, show only the planned dates, or skip the formal briefing step, decisions get made without the full context that a proper briefing would have surfaced. Treating the briefing as a mandatory checkpoint, rather than an optional formality, helps keep decision makers genuinely informed.

Reporting risk in practice

Real-life example

Crossrail

Crossrail Ltd announced in August 2018 that London’s new central rail section would not open in December 2018 as planned. The National Audit Office later found the plan used since 2015 was aspirational and did not reflect key interdependencies, while the sponsors had few levers to act.

Source: National Audit Office, Completing Crossrail (2019)

By the numbers

4 months

between the delay announcement and the planned opening date

Source: National Audit Office, Completing Crossrail (2019)

Project manager takeaway

Report forecast dates with confidence levels, not just plan dates, so sponsors see trouble early.

27. Security

Security risk pertains to any exposure related to security breaches, natural disasters, or physical safety concerns affecting people, facilities, or data connected to the project. This category sits close to technology risk but extends further into physical protections, access controls, and emergency response planning. Treating security as a distinct category, rather than folding it into technology risk, keeps physical and digital protections both properly staffed and funded.

Security risk in practice

Real-life example

The Target data breach

Attackers entered Target’s network in 2013 through access granted to a small refrigeration and HVAC vendor, then moved on to payment systems. A US Senate report said Target missed several automated alerts during the attack.

Source: GovInfoSecurity on the US Senate report

By the numbers

30%

of breaches involved a third party in 2025, double the year before

Source: Verizon 2025 Data Breach Investigations Report

Project manager takeaway

Limit vendor access to what they need, segment networks, and make someone responsible for acting on alerts.

Grouping Risk Categories

Once you have identified the individual risks facing a project, grouping them into broader families makes the resulting list far easier to manage and communicate to stakeholders. The four groupings below offer a practical starting structure, though every organization should adapt the categories underneath each one to reflect its own operating environment and risk appetite.

How the 27 categories in this guide map to the four groups. The checklist tool uses the same mapping.

GroupWhat it coversTypical ownerCategories in this guide
TechnicalWhat is built and how: requirements, design, tools, quality and protectionTech lead, architect, QA leadScope, Technical & Architectural, Technology, Interface, Performance, Quality & Process, Security
ManagementHow the project is planned, staffed, funded and reportedProject manager, sponsor, PMOEstimates & Assumptions, Budget, Schedule & Dependencies, Resourcing, Funding, Communication, Reporting & Briefings
CommercialMoney and agreements with outside partiesProcurement, contract manager, financeLogistics, Contractual, Internal Procurement, Suppliers & Vendors, Subcontracts, Client Stability, Partnerships, Market Rates
ExternalForces outside the organization that the team cannot controlSponsor, compliance, facilities, continuity leadLegislation, Business Continuity, Regulations, Weather, Facilities

Technical Risk Categories

Technical risk categories: communication, quality assurance and architecture

Technical risks cause an organization’s entire functioning and performance to fail when left unmanaged over time. These risks develop due to the failure of software and hardware tools and equipment used on a specific project. The risk within this category may stem from capacity, suitability, usability, familiarity, reliability, system support, and overall deliverability of the tools involved.

This category typically groups together the following three related risk areas:

  • Team Communication: Breakdowns in how technical information flows between developers, testers, and stakeholders often produce defects that surface far later than they should.
  • Quality Assurance: Gaps in testing coverage or review rigor allow avoidable defects to reach production, undermining confidence in the broader technical solution.
  • Architecture: A poorly planned technical foundation makes every subsequent change more expensive and increases the odds of cascading system failures.

Management Risk Categories

Management risk categories: resourcing, budgeting and other projects

Management risk results from inefficient resource management across a project, which is exactly why appropriate management planning is always necessary to keep consequences contained within acceptable limits. When leadership fails to anticipate resourcing or budgeting needs early, the resulting gaps tend to surface at the worst possible moments during delivery, forcing reactive decisions rather than planned ones throughout the project.

Management risk generally groups these three related areas together for tracking:

  • Resourcing: Insufficient staffing or the wrong skill mix on a project team directly limits how much quality work can realistically get done.
  • Budgeting: Underfunded plans force difficult tradeoffs later, often at the exact moment when flexibility is needed most to keep delivery on track.
  • Other Projects: Competing priorities across an organization’s broader portfolio can quietly pull resources away from a given initiative without formal notice.

Commercial Risk Categories

Commercial risk categories: contractual, partnerships and suppliers

Commercial risks broadly cover all non-political risks facing a project, including completion and financing risks that may exist during the development or construction phase specifically. From a company’s perspective, commercial risks include non-payments by private sector buyers due to default, insolvency, or a refusal to accept the deliverable developed under the original contract terms.

These commercial pressures harm project costs and revenue streams directly, and they can put a project’s overall commercial viability in genuine jeopardy if left unaddressed for too long. Tracking commercial risk alongside technical risk gives leadership a fuller, more accurate picture of whether a project remains genuinely worth continuing under its current terms and funding arrangement.

Commercial risk commonly includes these three closely related categories:

  • Contractual: Legal exposure from agreements that go unfulfilled can create financial losses that ripple well beyond the immediate transaction in question.
  • Partnerships: A partner’s inability to deliver on its commitments directly affects the financial position and credibility of everyone else involved in the arrangement.
  • Suppliers: Vendor instability or capacity shortfalls upstream can stall delivery timelines regardless of how well the core project team is performing.

External Risk Categories

External risk categories: weather, regulations and facilities

External risks often include economic events that arise from outside the corporate structure entirely, beyond the direct control of any single organization or project team. These events are largely impossible for a company to control or predict with high accuracy, which makes lowering the associated exposure genuinely difficult. Economic, natural, and political factors make up the three broad types of external risk.

External risk is generally broken down into these three distinct areas:

  • Weather: Severe or unseasonal conditions can delay physical work, disrupt supply routes, or damage facilities tied directly to the project.
  • Regulations: Sudden shifts in law or policy can raise compliance costs or invalidate assumptions the original project plan was built on.
  • Facilities: The loss or disruption of a physical site, such as a data center, can halt project activity until service is restored.

Risk Breakdown Structure Template

Risk breakdown structure example with project risks split into technical, management, commercial and external categories

A risk breakdown structure, or RBS for short, is a hierarchical chart that divides project risks into higher-level categories, organized from broad groupings down to specific threats. It is an essential tool in a project manager’s repertoire, forcing every identified risk into a defined place within the larger structure rather than sitting in an unsorted list.

A risk breakdown structure allows project managers to categorize risks into larger groups with lower-level components that can be assigned specific actions during execution. This provides a clear path forward when analyzing possible problems without requiring extensive planning at the very start of a project, so teams can map new risks into it quickly as they emerge.

Free Risk Category Checklist Tool

Use the free checklist below as a ready-made RBS template. Tick each of the 27 categories that applies to your project, rate its likelihood and impact from 1 to 5, and add an owner. The tool ranks your top categories, builds a risk breakdown structure by group, and lets you copy the result or download it as a CSV for your risk register. An example project is loaded so you can see how it works.

Video: Risk Categories and the Risk Breakdown Structure

This short video explains how project managers use risk categories and how they roll up into a risk breakdown structure.

Risk Categories and the Risk Breakdown Structure, by David McLachlan (about 3 minutes).

Facts Worth Checking

Ten common beliefs about project risk, checked against published data.

#You may hearWhat the data saysSource
1Most failed projects fail for technical reasons.One in five projects is unsuccessful because of ineffective communication, about half of all failures in that study.PMI Pulse of the Profession (2013)
2A careful estimate will usually hold.Only 8.5% of projects meet or beat both their schedule and cost estimates.Bent Flyvbjerg via Thought Economics
3Landmark projects keep costs under control.The Sydney Opera House cost more than 14 times its original estimate.Guinness World Records
4Vendor risk is the vendor’s problem.Third-party involvement in breaches doubled to 30% in the 2025 DBIR.Verizon 2025 Data Breach Investigations Report
5Weather risk only matters on construction sites.One damaged plant in North Carolina makes about 60% of US IV solutions.American Hospital Association
6Contract risk ends once the contract is signed.Poor contract management costs organizations almost 9% of annual value on average.World Commerce & Contracting
7Software defects are a small, local cost.Poor software quality cost the US an estimated $2.41 trillion in 2022.CISQ, Cost of Poor Software Quality 2022
8Interest rates are a finance issue, not a project issue.Rising interest rates helped end two offshore wind projects and DKK 28.4 billion in impairments followed.Ørsted company announcement, Oct 31, 2023
9Regulatory fines are too small to change plans.The EU AI Act allows fines of up to €35 million or 7% of global turnover.DLA Piper, August 2025
10There will always be enough people to staff projects.PMI estimates the world needs 25 million new project professionals by 2030.PMI Talent Gap report

Sources checked November 2026. Figures come from the organizations linked and may be updated by them.

Conclusion

Sorting project risk into clear categories, from scope and budget through technology, contractual, and external threats, gives teams a shared language for spotting trouble early rather than reacting after damage is done. The twenty-seven examples covered here span nearly every situation a project manager will encounter, and the identification techniques and grouping structure tie them into one coherent, repeatable system.

Start by mapping your own project against these categories, noting which ones carry the highest likelihood or impact for your specific situation. Build a risk breakdown structure around what you find, then revisit it regularly as the project evolves. Treating risk categorization as an ongoing habit, rather than a one-time exercise, keeps your team prepared for whatever the project introduces next.

Frequently Asked Questions About Risk Categories

What is the difference between a risk category and a risk register?

A risk category groups similar types of threats together, such as budget, technology, or contractual risk, so patterns become easier to recognize across a project. A risk register, by contrast, is the detailed log where individual risks are recorded, scored, and tracked over time. Categories organize the register, but the register captures the specific, actionable entries your team actually monitors.

How many risk categories should a project actually track?

No fixed number fits every project, and most teams draw from a broader list, like the twenty-seven examples covered here, to build a shorter set that matches their own environment. Smaller projects might track six to ten relevant categories, while complex or regulated initiatives often need considerably more. The goal is genuine relevance, not simply matching someone else’s checklist.

Who is responsible for identifying risk categories on a project?

The project manager typically owns the overall risk identification process, but the most reliable categories emerge from input across the whole team. Technical leads flag architecture and technology risks, procurement staff surface supplier and contractual concerns, and finance flags budget exposure. Involving multiple perspectives during identification consistently produces a more complete and accurate risk picture than one person working alone.

How often should risk categories be reviewed during a project?

Risk categories and the risks within them should be reviewed at every major milestone, and ideally during regular status meetings as well, since new threats can emerge as a project evolves. A category that seemed minor at kickoff, such as a specific vendor relationship, can become significant once circumstances shift. Treating review as continuous rather than one-time keeps the risk breakdown structure genuinely useful.

Can risk categories overlap with each other?

Yes, and overlap is common rather than a sign of a flawed framework, since many real-world risks touch more than one category at once. A vendor failure, for example, can trigger supplier risk, budget risk, and schedule risk simultaneously. When this happens, log the risk under its primary driver and note the secondary impacts so mitigation efforts address the full picture.

What are the four main groups of project risk categories?

Many project managers group categories under four headings: technical, management, commercial and external. Technical covers scope, design, technology and quality; management covers estimates, budget, schedule, people and communication; commercial covers contracts, suppliers, partners and clients; external covers laws, regulations, weather and facilities. These four groups make a practical top level for a risk breakdown structure.

How do I use the free Risk Category Checklist?

Open the checklist on this page, tick each category that applies to your project, and rate its likelihood and impact from 1 to 5. The tool multiplies the two into a score, ranks your top categories and builds a simple risk breakdown structure by group. Copy the result as text or download a CSV, then log the individual risks in your risk register.

Suggested articles:

Scroll to Top