Sponsor Workflow
The sponsor workflow turns local project knowledge into a complete RICA Project Information Model. The process begins with framework fit and ends with an operating project record that can support financing, monitoring, purchase review, and investor reporting.
Sponsor
Section titled “Sponsor”Use the workflow to organize evidence before submitting the Project Information Model. The goal is to reduce review friction by making every project claim testable.
Reviewer
Section titled “Reviewer”Use the workflow to identify missing evidence, weak assumptions, unresolved approvals, and conditions that must be resolved before financing.
Investor
Section titled “Investor”Use the workflow to understand whether the project record is mature enough to support credit review and later monitoring.
Workflow Steps
Section titled “Workflow Steps”- Confirm RICA solution-framework fit.
- Define the asset boundary, location, sponsor, operator, local participation structure, and stewardship entity.
- Gather site, stakeholder, legal, technical, market, and environmental evidence.
- Document feasibility studies, consultations, pilots, and unresolved diligence gaps.
- Prepare demand, supply, customer, user, offtake, pricing, and utilization assumptions.
- Develop project scope, components, functional design, engineering design, and operating model.
- Prepare capex, opex, revenue, financing, repayment, cash-flow, and sensitivity models.
- Complete governance, risk, compliance, E&S, quality, procurement, implementation, and O&M sections.
- Map the Project Information Model to the Atlas open project account and upload evidence.
- Submit for RICA review, resolve comments, and maintain updates after approval.
Readiness Gates
Section titled “Readiness Gates”| Gate | Sponsor Output | Reviewer Test | Result |
|---|---|---|---|
| Framework Fit | Solution framework and adaptation problem are identified. | Is the project a RICA asset rather than a general business plan? | Proceed, revise, or reject. |
| Evidence Readiness | Core project, site, stakeholder, and market evidence is uploaded. | Can major claims be independently checked? | Proceed or return for evidence. |
| Financeability | Capex, revenue, opex, repayment, and risk assumptions are complete. | Is the project loan structure supportable? | Proceed to credit review or request revisions. |
| Implementation Readiness | Permits, procurement, WBS, governance, and O&M plan are defined. | Can the project be delivered and monitored? | Approve with conditions or defer. |
| Monitoring Readiness | Atlas mapping, metrics, reporting cadence, and material-event rules are complete. | Will the asset remain visible after financing? | Activate reporting or require setup. |
Common Readiness Blockers
Section titled “Common Readiness Blockers”| Blocker | Why It Matters | Required Action |
|---|---|---|
| Unclear site control | Financing cannot proceed without a lawful asset location or use right. | Upload title, lease, concession, or legal opinion. |
| Unsourced demand claims | Revenue assumptions are not diligence-ready. | Provide buyer evidence, survey data, contracts, or market sources. |
| Weak operator accountability | Investors need a party responsible for performance. | Define operator obligations, KPIs, reporting, and replacement rights. |
| Missing local participation evidence | RICA requires inclusive stakeholder design. | Provide ownership, participation, consent, or benefit-sharing records. |
| No material-event process | Risk changes can become invisible. | Define event triggers, reporting timeline, owner, and escalation path. |
Submission Package
Section titled “Submission Package”The sponsor submission must include the Project Information Model, financial model, evidence register, open issues log, source list, version register, and Atlas evidence mapping. The reviewer may accept a staged submission only when the missing items are listed as explicit conditions.