Information Requirements
Information requirements define the evidence, records, and decisions that must be present before a RICA Project Information Model can support financing review, project delivery, and later Atlas monitoring.
Use this page at the start of a project to decide what information is required, where it belongs, who is responsible, and what level of review is needed. The requirements should be updated when project scope, financing path, clearances, stakeholders, or operating assumptions change.
Requirement Register
Section titled “Requirement Register”| Requirement ID | Required Information | Related Chapter | Owner | Reviewer | Evidence Location | Status |
|---|---|---|---|---|---|---|
| IR-001 | Project identity, sponsor authority, site, currency, and decision gate. | Project Profile | REPLACE: Owner | REPLACE: Reviewer | pim.yaml and 00-project-profile.md | REPLACE: Status |
| IR-002 | Location, boundary, land access, and site context. | Project Profile / Project Scope | REPLACE: Owner | REPLACE: Reviewer | assets/maps/ and evidence register | REPLACE: Status |
| IR-003 | Feasibility evidence for the preferred option. | Feasibility Evidence | REPLACE: Owner | REPLACE: Reviewer | Feasibility reports and evidence register | REPLACE: Status |
| IR-004 | Demand, supply, users, offtake, or service need. | Demand, Supply, and Offtake | REPLACE: Owner | REPLACE: Reviewer | Market evidence, user records, agreements | REPLACE: Status |
| IR-005 | Technical design basis, drawings, quantities, and specifications. | Engineering Design | REPLACE: Owner | REPLACE: Reviewer | assets/drawings/ and technical notes | REPLACE: Status |
| IR-006 | Governance, ownership, stakeholder, and community arrangements. | Governance and Ownership | REPLACE: Owner | REPLACE: Reviewer | Agreements, minutes, consent records | REPLACE: Status |
| IR-007 | Financial model, assumptions, sources, and sensitivity cases. | Financial Model | REPLACE: Owner | REPLACE: Reviewer | data/financial-model.xlsx and assumptions register | REPLACE: Status |
| IR-008 | Risk, mitigations, clearances, safeguards, and material open issues. | Risk / Clearances / Safeguards | REPLACE: Owner | REPLACE: Reviewer | data/risk-register.csv, permits, safeguards records | REPLACE: Status |
| IR-009 | Implementation, procurement, quality, commissioning, and handover records. | Implementation / Procurement / Quality / O&M | REPLACE: Owner | REPLACE: Reviewer | Workplan, contracts, test records, handover files | REPLACE: Status |
| IR-010 | Monitoring setup, operating metrics, and Atlas mapping. | Operations and Maintenance | REPLACE: Owner | REPLACE: Reviewer | Monitoring plan, metric definitions, Atlas fields | REPLACE: Status |
How To Use
Section titled “How To Use”Start with the rows above, then add project-specific requirements. A protected cultivation project may need greenhouse design loads, irrigation water quality, crop plan, grower agreements, and offtake evidence. A social forestry project may need plot records, stewardship obligations, harvesting controls, and benefit-sharing evidence.
Each requirement should be specific enough that a reviewer can decide whether it has been met. Avoid vague requirements such as “market study complete” unless the expected evidence, reviewer, and decision use are clear.
Atlas Mapping
Section titled “Atlas Mapping”Atlas can use the requirement register to show which project information is complete, which evidence is still missing, and which items are ready for financing review or operating handover. Keep requirement IDs stable once they are shared with reviewers.