Skip to content
ANR Horizon
Project Development

Building a risk register for a renewable project

How to build and use a practical risk register for solar and wind projects — identifying, rating, owning and reviewing risks from land to build.

By ANR Horizon Editorial Team · · 4 min read

Two people reviewing and signing documents at a desk

Every renewable project faces uncertainty — land that might not be secured, a substation that might be late, a monsoon that might flood the site. A risk register is a simple tool for managing that uncertainty: a structured list of what could go wrong, how likely and serious it is, and what is being done about it. Used well, it helps teams focus on what matters. Used badly, it becomes a document no one reads.

What a risk register contains

For each risk:

FieldPurpose
IDReference
CategoryLand, grid, approvals, technical, commercial, community, HSE
DescriptionWhat could happen, and its cause
LikelihoodHow probable
ImpactHow serious — schedule, cost, performance, reputation
RatingCombined likelihood × impact
MitigationActions to reduce likelihood or impact
OwnerPerson responsible for managing it
Due dateWhen actions should be complete
StatusOpen, mitigating, closed
TrendRising, stable, falling

Writing good risk descriptions

Vague: "Land risk."

Better: "Co-owners of survey number 145/2 may not all consent, delaying the lease for the parcel on which inverter station 3 is planned."

A good description names the cause, the event and the consequence. That makes it possible to plan specific actions.

Rating risks

A simple scale:

  • Likelihood: 1 (rare) to 5 (almost certain)
  • Impact: 1 (minor) to 5 (severe)
  • Rating: likelihood × impact

Define what each impact level means for your project — for example, schedule delays of different lengths, or cost increases of different sizes. Consistency matters more than precision.

Typical risks by category

Land

Right of way

  • Refusal along cable or line routes
  • Route changes after engineering

Grid

  • Substation bay delayed
  • Evacuation line approvals delayed
  • Connectivity milestones missed

See grid connectivity basics.

Approvals

  • Requirements change
  • Dependencies between approvals
  • Conditions not met

Technical

  • Geotechnical conditions worse than expected
  • Resource lower than estimated
  • Equipment quality issues

Supply chain

  • Long-lead equipment delays
  • Price changes

Construction

  • Monsoon disruption
  • Contractor performance
  • Interface gaps

See where renewable project schedules slip.

Community

  • Work stoppages over compensation
  • Local employment disputes

See landowner relations during construction.

Commercial and regulatory

  • Changes in open access charges or banking
  • Offtaker payment risk
  • Change in law

Mitigation strategies

  • Avoid — change the plan so the risk no longer applies (e.g., reroute a line)
  • Reduce — act to lower likelihood or impact (e.g., early record checks)
  • Transfer — shift to a party better able to manage it (e.g., contract or insurance)
  • Accept — monitor and hold contingency

Making the register useful

Keep it current

Update after every significant change. An out-of-date register is worse than none, because it gives false comfort.

Focus on the top risks

Review the highest-rated risks in every project meeting. The rest can be reviewed less often.

Assign real owners

Every risk needs a named person, not a department.

Track actions

Mitigation actions should have deadlines and be tracked like any other task.

Learn

When a risk materialises, record what happened and what would have helped. Use it on the next project.

Risk registers and lenders

Lenders and investors often ask to see the risk register during due diligence. A well-maintained register shows that the project team understands its risks and is managing them. See investor due diligence.

From register to schedule

Risks should feed into planning. High-rated schedule risks might justify contingency in the schedule, earlier starts on vulnerable tasks, or parallel paths. Cost risks feed into contingency budgets.

Common mistakes

  • Generic risks with no specific cause
  • No owners
  • Never updated after the first version
  • Ignoring land and community risks
  • Treating the register as a compliance document

Who should contribute

A register written by one person at a desk will miss risks. The land team knows which parcels are fragile; the engineers know where ground conditions are uncertain; the community liaison knows where tensions are building; the commercial team knows which regulatory changes are coming. A short workshop with each group at the start, and regular input afterwards, produces a register that reflects the real project rather than a template.

How we help

Through project management and project advisory, we help owners build and maintain practical risk registers — with particular depth on land, right-of-way, approvals and community risks — and turn them into actions.

Frequently asked questions

Have a project or land in mind?

Talk to ANR Horizon Group about land, solar, wind or industrial projects — wherever you sit in the process.

Discuss a Project