When the Storm Passes, the Paperwork Begins
A hailstorm crosses a solar farm at two in the morning. By sunrise, the site team is photographing shattered panels; by the afternoon, the insurance team has a new claim on its hands. Policies to check, brokers to notify, surveyors to schedule, estimates to assemble — and that's one incident, at one site, held by one of more than 300 legal entities in the portfolio.
For the insurance team at one utility-scale green energy producer, this was spreadsheet territory. Every claim lived as rows in a workbook: dates, amounts, assessor names, status notes. Every claim actually meant two parallel financial stories — Material Damage to the assets themselves, and Loss of Profit for the generation revenue lost while they were down — each with its own estimates, broker assessment, surveyor assessment, and payments.
The spreadsheets worked the way spreadsheets always work: right up until they didn't.
Where the Model Broke
The problems compounded with scale. With claims spread across hundreds of entities, there was no single view of open exposure — answering "what's outstanding across the portfolio?" meant consolidating workbooks by hand. Claims drifted between informal states, so a missing surveyor report or an unassessed Loss-of-Profit figure might surface only when settlement stalled. Supporting documents — policies, surveyor reports, broker correspondence, payment advices — lived in inboxes and shared drives, attached to the claim only by memory.
And when an auditor or a renewal negotiation needed the full history of a claim, reconstructing it was a project in itself.
The Decision: Process First, Software Second
The mandate from finance leadership was specific: don't digitize the spreadsheet — enforce the process. Every claim should move through the same stages, in the same order, with the same data requirements, and leave a complete trail.
That became the design: a strictly linear 13-stage claim lifecycle built on DocQ, from first intimation through assessment and approvals to final payment. Each stage gate carries mandatory fields — a claim physically cannot advance with an unassessed financial track or a missing report. Claims can be withdrawn cleanly at any point until they're paid, and both financial tracks — Material Damage and Loss of Profit — live on the same claim record, always in sync.
AI at the Intake
The documents that used to scatter across inboxes now flow into the platform, where AI does the filing. Incoming claim documents are classified automatically — surveyor report, broker assessment, payment advice — and DocQ's extraction pulls the figures that matter straight into the claim record: assessed amounts, deductibles, dates, references.
The insurance team stopped re-typing numbers out of PDF reports. More importantly, the numbers on the claim and the documents behind them are now the same thing, attached to each other, permanently.
One Portfolio, One Picture
Today the team works from a claims workspace, not a workbook folder. Every open claim shows its stage, its two financial tracks, its documents, and its history. Portfolio questions — open exposure, stage bottlenecks, settlement progress — are answered by the platform rather than assembled by hand.
The spreadsheets are gone. What replaced them isn't just a database — it's the claims process itself, enforced by the system that records it.
