Rollups And Disclosure

Rollups translate project-level metric values into portfolio, loan-book, and note-level views. They should preserve the line back to underlying project records rather than turning metrics into unsupported headline claims.

Rollup Principles

Principle	Meaning
Approved values first	Investor-facing rollups should use platform-approved values unless clearly labeled otherwise.
Period alignment	Rollups should compare values from the same reporting period or disclose mixed-period coverage.
Unit consistency	Values should not be combined across incompatible units.
Coverage visibility	A rollup should show how many projects reported the metric and how many were missing.
No silent extrapolation	Estimated or extrapolated values should be labeled.
Traceability	A note or portfolio value should be traceable back to project-level records.

Project To Portfolio

At portfolio level, Atlas can sum approved values across projects where the unit and period are aligned. Coverage is as important as the headline total. A portfolio with strong values from two projects and no data from eight projects should not be presented as if all ten projects reported.

Project Loans And Note Pools

Project loans carry exposure to operating projects. Where a note purchases project loans, note-level monitoring can roll up approved project metrics from the underlying projects or purchased loan pool. This should preserve the pool composition context: geography, framework mix, sponsor mix, reporting coverage, and evidence status.

Impact Metrics And Financial-Dimension Metrics

Not every project metric belongs in a note-level impact metrics table. A metric such as Distributions to Nature is important to the RICA model, but it is a financial-dimension money flow. It may belong in stewardship, waterfall, or financial-distribution reporting rather than the same impact rollup surface as hectares, tonnes, or tCO2e.

Caution

A note-level impact table should not mix ecological physical outcomes and financial distributions without clear labeling. If the product needs both, use separate sections or badges that explain the dimension and reporting basis.

Disclosure Language

Disclosure should avoid overclaiming. Use clear qualifiers:

Situation	Preferred Language
Approved and complete	“Platform-approved reported value for the period.”
Missing project coverage	“Reported by 6 of 9 projects in the pool.”
Estimated value	“Sponsor estimate based on stated method.”
Mixed assurance	“Includes platform-reviewed and self-reported values.”
Historical correction	“Restated value supersedes prior submission.”