Illustrative composite case: A prospective investor was reviewing a major infrastructure or development project in Kenya before committing substantial capital. Technical and financial material suggested that the opportunity could be attractive, but the investment team still needed an independent view of whether the project was practically deliverable in its local operating environment.
This project risk assessment in Kenya case study shows how Raven Africa would test the gap between a project that works on paper and a project that can move through access, approvals, mobilisation, construction and reliable operation.
The assessment focused on six delivery questions: whether the site could be accessed; whether land and easement dependencies were controlled; whether approvals were correctly sequenced; whether utility assumptions were realistic; whether contractors and counterparties could perform; and whether stakeholder, community and security exposure could be managed.
Case-study conclusion: the project remained potentially viable, but it was not yet mobilisation-ready. The decision was therefore to proceed conditionally, subject to a defined conditions-precedent matrix and continuing risk monitoring.
For commercial scope, costs and timelines, see Raven Africa's Project & Site Assessment Services in Kenya. This page is intentionally structured as a case study and decision example rather than a duplicate service page.
Project Risk Assessment Case Study Snapshot
| Case type | Illustrative composite infrastructure / development investment in Kenya |
|---|---|
| Decision stage | Pre-investment / pre-financial close |
| Primary decision question | What could prevent the project from moving from paper to construction and reliable operation? |
| Risk domains tested | Land and access, approvals, utilities, contractors, counterparties, stakeholders, community exposure, security and implementation dependencies |
| Illustrative risk posture | Commercially viable in principle, but not yet mobilisation-ready |
| Recommended decision | Proceed conditionally after critical dependencies are verified, assigned and controlled |
Key takeaway: a positive feasibility model does not remove execution risk. The purpose of project risk assessment is to identify the practical dependencies that can delay, reprice or derail delivery before they become expensive problems.
The Investor's Question
The investment team wanted a decision-ready answer to one central question: What could prevent this project from moving from paper to construction and reliable operation in Kenya?
- Is the site legally and physically accessible for construction and operation?
- Are land rights, easements, wayleaves or access routes sufficiently documented and controllable?
- Which permits, approvals or authority decisions sit on the critical path?
- Are power, water, roads, drainage, telecoms and logistics assumptions supported by current evidence?
- Which contractors, suppliers, land intermediaries and local partners are essential to delivery?
- Who are the institutional, county, community, neighbouring and commercial stakeholders?
- Where could grievance, political, security, integrity or reputational exposure delay implementation?
- What should be resolved before financial close, mobilisation and later operational stages?
Evidence a Project Risk Assessment Would Test
The assessment is not limited to a checklist. The evidence reviewed is selected around the investment decision, project stage and consequences of failure. In an infrastructure or development assignment, the review can combine documentary, public-record, counterparty, stakeholder and field evidence.
- Project assumptions: feasibility material, implementation schedules, dependency maps and sponsor representations.
- Land and access: available ownership, lease, easement, wayleave, access-route and neighbouring-use information relevant to mobilisation and operation.
- Regulatory pathway: permits, approvals, agency dependencies, county functions and sequencing assumptions affecting the critical path.
- Infrastructure and utilities: power, water, drainage, roads, telecoms, logistics and connection-capacity assumptions.
- Counterparties and contractors: identity, ownership, capacity, track record, integrity indicators, concentration risk and alternatives.
- Stakeholders: institutions, local leadership, communities, neighbours, commercial interests and potential sources of acceptance or grievance.
- Operating environment: observable site conditions, security exposure, disruption triggers and material inconsistencies between documents and conditions on the ground.
Where physical verification is required, the project-risk review can be supported by Raven Africa's field verification services in Kenya. Where a defined company, contractor or partner requires deeper review, a separate due diligence assessment may be appropriate.
Project Risk Assessment Process
Define the Investment Decision
Identify the decision-maker, project stage, critical assumptions, capital at risk, timetable and consequences of delay or failure.
Map Critical Dependencies
Separate assumptions from verified dependencies across land, access, approvals, infrastructure, contractors, stakeholders and operating conditions.
Verify Site, Land and Access Conditions
Test available land interests, route access, easements, neighbouring uses and practical constraints that could affect mobilisation or operation.
Review Approvals, Utilities and Institutions
Identify critical-path permissions, responsible institutions, current evidence of capacity and dependencies that require written confirmation.
Test Counterparties and Stakeholders
Review essential contractors and partners, then map affected institutions, communities, neighbours and other interests that can influence delivery.
Convert Findings into Decision Controls
Produce a prioritised risk register, conditions precedent, accountable owners, mitigations, engagement actions, escalation thresholds and monitoring indicators.
Illustrative Findings from the Kenya Project Risk Review
1. Site access depended on a third-party route
The project model assumed reliable construction and operating access, but the practical route crossed or depended on interests that had not been fully documented. Access therefore became a condition precedent rather than an operational afterthought.
2. Utility assumptions were ahead of confirmed capacity
The financial and technical model assumed power, water or drainage availability, but the evidence available to the investment team did not yet provide sufficient confirmation of capacity or connection timing. Written provider confirmation and contingency planning were required.
3. Stakeholder mapping was too narrow
A landowner-and-regulator map did not capture neighbouring interests, community leadership, local employment expectations, transport users and institutions likely to influence access, acceptance and implementation. A broader stakeholder assessment was therefore incorporated into the risk treatment plan.
4. Contractor concentration created schedule and integrity exposure
Heavy dependency on one contractor, supplier or intermediary meant that a single failure could affect mobilisation, cost or schedule. The project required capacity checks, contractual remedies and credible alternatives.
5. Regulatory sequencing needed an accountable critical-path matrix
Individual approvals could not be treated as isolated administrative tasks. The project needed a sequenced matrix showing which decisions depended on earlier approvals, who owned each action and when delay should trigger escalation.
6. The project was viable, but not yet mobilisation-ready
The correct outcome was not automatic rejection. It was a sequenced risk-reduction plan identifying what had to be resolved before capital commitment, what could be closed before mobilisation and what required continuing monitoring during delivery.
Illustrative Project Risk Register
| Risk | Illustrative rating | Why it matters | Required treatment |
|---|---|---|---|
| Land / access dependency | Critical | Could prevent mobilisation or reliable operating access. | Document access rights, confirm route position and prepare alternatives. |
| Utility availability | High | Capacity or connection delay could change cost and completion assumptions. | Obtain provider confirmation, validate capacity assumptions and define contingency. |
| Stakeholder acceptance | High | Unmapped interests or grievances could delay access, approvals or implementation. | Build stakeholder map, engagement sequence, grievance controls and escalation triggers. |
| Contractor concentration | Medium–High | Single-party failure could affect cost, schedule or integrity exposure. | Conduct capacity due diligence, strengthen performance protection and identify alternatives. |
| Regulatory sequencing | High | Missed dependency can create a critical-path delay even where individual permits appear manageable. | Create permit matrix, assign accountable owners and monitor deadlines. |
| Security / disruption | Location-dependent | Local conditions can affect staff, logistics, site continuity and stakeholder relations. | Apply site-specific controls, incident triggers and continuing monitoring. |
Interpretation: the rating is useful only when it drives a decision. A critical risk should normally be linked to a clear action, owner, deadline and consequence if the required evidence or control is not achieved.
From Risk Register to Investment Decision
The practical value of the assessment is the conversion of findings into a staged decision framework. For this illustrative case, the risks were separated by the point at which they had to be controlled.
| Decision stage | Examples of required controls | Decision effect |
|---|---|---|
| Before major capital commitment | Access rights, material land dependencies, critical approval pathway, utility-capacity evidence and key-counterparty due diligence. | Determines whether the investment can proceed and on what conditions. |
| Before mobilisation | Site access controls, contractor readiness, stakeholder engagement sequence, logistics plan and unresolved approval conditions. | Determines whether construction activity should start. |
| During construction and operation | Stakeholder grievances, contractor performance, permit changes, security incidents, political or regulatory developments and emerging operational dependencies. | Determines when mitigation, escalation or management intervention is required. |
Material issues that remain dynamic after mobilisation can move into a structured risk monitoring programme with defined triggers and reporting priorities.
Raven Africa Recommendation
The illustrative recommendation was proceed conditionally, not blindly. The project should not move directly from financial attractiveness to mobilisation while access, utility, regulatory, stakeholder and contractor dependencies remained insufficiently controlled.
Major commitment should follow a documented conditions-precedent matrix. Each material risk should have an accountable owner, evidence requirement, target date, escalation threshold and defined consequence if the control is not achieved.
Decision Value of Project Risk Assessment in Kenya
A project risk assessment gives investors and sponsors a bridge between technical or financial feasibility and real-world deliverability. It identifies the dependencies that can delay, reprice or derail a project even where the underlying investment case remains attractive.
In this case-study model, the value was not another descriptive report. It was a clearer investment decision: what must be solved before capital is committed, what must be closed before mobilisation, what can be mitigated during delivery and what requires continuing monitoring.
This distinction also protects search intent: the Project & Site Assessment Services in Kenya page explains the commercial service, while this case study demonstrates how project-risk evidence changes an investment decision.
Project Risk Assessment in Kenya Case Study FAQs
Planning a Major Project in Kenya?
If you need the commercial scope rather than the case-study methodology, Raven Africa supports investors and project sponsors with site, project-area, counterparty, stakeholder and implementation risk assessment before capital is committed and during delivery.
Request Project Risk Assessment View Project Risk ServicesPublication Note
This is an illustrative composite case created to explain Raven Africa's methodology and decision value. It does not describe a named client or make allegations against any identifiable person or organisation.