Home / Guides / Project Risk Management
Guide

Project Risk Management

A practical guide to managing uncertainty across project objectives, decisions, dependencies, and change.

By Adrian M. FenwickReviewed August 3, 2026

Project risk management supports delivery decisions from concept through closure. It should address both individual risks and the overall uncertainty affecting scope, schedule, cost, quality, benefits, resources, stakeholders, and transition to operations.

Start before the plan is fixed

Early risk work should challenge assumptions, options, dependencies, estimates, procurement strategy, capability, and stakeholder expectations. Waiting until a detailed schedule exists limits the ability to avoid or redesign exposure.

Integrate with project controls

Link risks to assumptions, decisions, milestones, changes, issues, actions, dependencies, and contingency. The risk process should inform planning and governance rather than operate as a separate monthly spreadsheet.

Typical areas

  • Scope and requirements
  • Schedule logic and dependencies
  • Resources, skills, and decision capacity
  • Suppliers and contracts
  • Cost uncertainty and funding constraints
  • Quality and technical performance
  • Stakeholder alignment and approvals
  • Transition and benefits realization

Review at decision points

Reassess risk at gates, major changes, procurement decisions, design freezes, testing, implementation, and handover. Closure should include residual operational risks and lessons.

Avoid overlap with cost estimating

Related but separateRisk Guides explains how to identify, own, treat, and monitor project uncertainty. Detailed estimating, contingency calculations, earned value, and lifecycle cost methods belong on the separate Cost Guides site.
Use with judgmentRisk methods support decisions; they do not remove uncertainty. Record assumptions, limits, and acceptance authority.

Connect risks to the project lifecycle

Risk priorities change from concept through planning, procurement, delivery, testing, transition, and closure. Early stages often contain scope, assumption, approval, and feasibility uncertainty. Later stages may emphasize integration, quality, readiness, supplier delivery, handover, and benefits realization.

Integrate risk with project controls

The register should inform schedule decisions, change control, procurement strategy, contingency use, governance gates, and stakeholder communication. Risks should not sit in a separate spreadsheet that is reviewed after key decisions have already been made. Opportunities can also be recorded when uncertainty may improve time, cost, quality, or benefits.

Project review prompts

  • Which milestone or deliverable is affected?
  • What schedule or cost assumption is most uncertain?
  • Are interface and transition risks visible?
  • Does the response have time to work before the decision point?
  • Who owns the risk after handover?