VERIGRID
Project readiness, by gate, by document, by rule
VeriGrid is a system of record for Philippines utility-scale solar development. It turns documents into evidence, evidence into gate status, and gate status into a bankability score that a lender can audit.
Philippines document catalog
61 document types across the DOE, ERC, DENR-EMB, NCIP, DAR, BSP, LGU, grid and offtake domains, each with synonyms, expiry behaviour and the gate and HBI dimensions it informs. Uploads that match no known type are stored but never satisfy a gate.
Diligence packet
A point-in-time snapshot of gates, HBI, dimension breakdowns, every current document with its validity and applicability state, and all blockers — sealed with a SHA-256 hash. Any change to a score, rule or reason breaks the hash. Generate it when a lender, IE or acquirer asks; it is the data room, pre-organized.
Required, conditional, recommended, optional
Each document is classified for the project's route (GEAP or bilateral) and phase. Required documents block a gate when missing or expired. Conditional documents activate only when their trigger applies: foreign funding, agricultural land, ancestral-domain overlap, competitive selection. Strongly Recommended documents cap a score when absent. Optional documents never move a number.
Eight-gate readiness model
Gate 0 DOE authority and contract · Gate 1 Sponsor and legal authority · Gate 2 Land and site control · Gate 3 Grid and interconnection · Gate 4 Environmental and social clearance · Gate 5 Revenue and offtake · Gate 6 Financing · Gate 7 Build and operate. Each gate reports Open, Blocked, Capped, Under Review or Complete, with the rule and document behind it. Gate status recomputes on every relevant change.
Heliosity Bankability Index (HBI)
One lender-grade score, 0 to 100, from four dimensions: Operational (30%), Execution (25%), Financial (25%), Technical (20%). A project with several assets takes its worst asset's score, not an average. If a required input is missing, the result is "Incomplete — Missing Inputs." VeriGrid never fabricates a score. Score columns are written only by the backend; no user role can edit them.
Audit and access
Role-based access, immutable audit log of every document upload, status change, override and packet generation. Document version history with supersession chains. Justified human overrides are allowed and recorded with the reason. Single-tenant data isolation enforced at the database layer.