Skip to content

Framework Metric Assignment

RICA solution frameworks create the initial metric set for a project. A protected cultivation project, a biochar project, and a wetland restoration project should share a common reporting discipline, but they should not all report the same operating and impact metrics.

When a project selects one or more RICA solution frameworks, Atlas can seed a default metric set from those frameworks. If more than one selected framework uses the same metric, the project receives the metric once.

After project creation, the metric set becomes project-owned. Changing the project’s framework labels should not silently add or remove project metric assignments. Additions, retirements, and changes should be explicit and traceable.

Framework defaults reduce reporting burden and prevent sponsors from inventing a new metric vocabulary for each project. They also preserve comparability for investors by ensuring projects in the same solution framework start with similar evidence expectations.

ActionStandard Treatment
Add metricRecord the metric, effective start date, target where relevant, and reason.
Retire metricStop future reporting while preserving historical submissions.
Change targetRecord the new target and reason without rewriting prior approved values.
Change cadenceTreat as an explicit reporting agreement change. Monthly is the default.
Add project-specific metricLabel it clearly as project-specific so it is not confused with common RICA metrics.

Sponsors should confirm that each assigned metric is measurable with the project’s operating systems. Reviewers should test whether the assigned metric set matches the selected frameworks, the Project Information Model claims, the O&M plan, and the evidence available through the open project account.