From fragmented reporting to a governed operating system

At this scale, portfolio visibility was critical. C-level executives and senior management relied on recurring reports to understand project health, development stage, critical milestones and risks across the portfolio.

There was no shortage of information. The problem was that much of it was distributed across spreadsheets, presentations and country-level reporting processes. As the portfolio grew, a seemingly simple management question became increasingly difficult to answer:

What is the current, governed truth of our portfolio?

Country teams maintained their own spreadsheets, which were consolidated into management reports. Each team understood its projects well, but no governed information model connected the local perspectives. Even the corporate list of projects could vary between reports — one spreadsheet contained one perimeter of projects, another a slightly different one.

Project identification itself was inconsistent: development names in some reports, the legal names of SPVs in others, and in some cases an incomplete connection between the two. A single project might involve the project SPV, a joint venture around shared grid infrastructure, a battery component, one or several intermediate holding companies, and the corporate ownership structure above them. Those relationships could not be reliably represented in flat spreadsheets.

Leadership monitored critical dates — Ready-to-Build, Notice to Proceed, Commercial Operation Date, Provisional Acceptance. But those dates could differ depending on which spreadsheet or reporting cycle was being reviewed, and when a milestone changed, the previous commitment was frequently overwritten.

If the expected COD moved from June to September, management could see September. What they could not easily see was: What was the previous commitment? When did it change? Who changed it? Why? How much has the project drifted from plan over the last reporting cycles?

Resolving those questions meant contacting country heads, who contacted local teams, who reconstructed what had happened. The organization had the data. What it lacked was the history and accountability surrounding the data.

We wrote about this exact pattern in Who Changed That Date?

Risks were reported through a non-standardized framework that ultimately became management presentations and quarterly PDF reports. Descriptions, categories, scoring approaches and mitigation actions evolved from quarter to quarter — so the organization could understand the risks reported at a point in time, but not which risks had disappeared, which had deteriorated, which mitigation commitments remained outstanding, or which projects were becoming progressively more exposed.

A quarterly report provided a snapshot. Leadership increasingly needed a timeline.

The natural first response was to implement a commercial project-management platform. The experience revealed something important: the organization did not primarily have a project-management-tool problem. It had an information-model problem.

Generic software could represent projects, tasks and additional fields. But each new business requirement became another custom field — the digital equivalent of continuously adding columns to a spreadsheet. Relationships between projects, SPVs, joint ventures and holding companies; shared infrastructure between projects; country-specific permitting processes; historical baselines; milestone versioning; standardized risk management; land securization across hundreds of individual plots — all remained difficult to express, and the application became increasingly difficult to govern.

The organization commissioned a bespoke platform. What was expected to be a relatively short development initiative became a much deeper exercise in business discovery: the people who best understood the processes were also the people developing real projects across 6 countries, so requirements emerged progressively, and processes that appeared simple at portfolio level proved considerably richer in the teams managing them every day.

Iteration by iteration, years of operational knowledge were translated into a structured information model — and several fundamental problems were finally solved:

The bespoke application was designed around a sophisticated information model. Users, however, had spent years working in Excel — and updating dozens of projects through traditional application forms could feel slower than opening a spreadsheet and editing cells directly.

That friction was important, because even the best-designed corporate data model generates limited value if operational teams do not continuously maintain it.

Navorda was created by combining the business knowledge accumulated during this transformation with several additional years of experience working directly with renewable energy development organizations. One design principle became fundamental: do not fight Excel — industrialize what people love about it.

Teams work in structured grids and datasets with much of the speed and flexibility they associate with spreadsheets. But underneath that familiar experience, every data point belongs to a governed information model. A project is a project. An SPV is an SPV. A permit is a permit. A land plot is a land plot. A risk is a risk. The relationships between those objects are explicitly managed rather than hidden inside cells, formulas and naming conventions.

Users drill down from the portfolio to a country, from a country to a project, from a project to its permits, its land plots and its corporate structure, from a milestone to its historical baselines, from a risk to its owner and mitigation actions. And something important happened almost invisibly: everyday project management started generating leadership reporting automatically. Teams maintain operational reality; leadership consumes that same reality.

When a critical milestone changes, Navorda retains the current expectation, the previous ones, when the change occurred, who made it, and the associated context. That changes the nature of management conversations: