Puro.earth dMRV Connect (Beta) (Beta)

An Audit Package is a collection of Audits for a specific Facility. Audit Packages are shared with reviewers, such as Auditors or Issuing Authorities, to evaluate compliance of the Frameworks or Models against defined requirements.

An Audit Report records the outcome of a review for an Audit Package. Reviewers publish Audit Reports based on their permissions. Publishing an Audit Report indicates that the associated Audit Package and by extension the Audit—has been formally reviewed.

An Audit represents the review of a single compliance Framework Instance or Model by an Auditor Organization. It describes what is being audited, who is auditing, and where it is in its process.

Batches represent units of carbon stored within a Monitoring Period. When an Evidence Request is configured as type BATCH, submissions can be organized by batchItemId, allowing the grouping of related Evidence files and Expected Field Values together. This enables efficient data entry where common field values are specified once per Batch rather than repeated for each individual submission.

A Document Instance represents a Document applied to a specific Monitoring Period. Document Instances can contain Evidence Requests, Templates, Expected Fields to structure the collection of compliance data.

A Document represents a specific compliance requirement. It contains one or more Evidence Requests for a given collection period. Documents can be mapped across Frameworks, allowing the same data to satisfy different requirements.

Evidence represents the files submitted to an Evidence Request. Each Evidence is tied to an Evidence Request and Evidence Template.

An Evidence Request prompts the submission of files (Evidence) and/or structured data (Expected Field Values) for a Document Instance. Requests can be STANDARD (single submission) or BATCH (requiring one submission per batch in the Monitoring Period). Evidence Requests can be assigned to users, include a due date, and track status.

Evidence Templates define the expected format for CSV file submissions. Templates specify column headers, data types, and validation rules that uploaded files should conform to. Files that don't match the template structure are flagged in the platform for review rather than rejected by the API.

Expected Field Values are the actual value entries for Expected Fields, capturing the specific numbers, text, dates, or boolean value submitted in Evidence Requests. These values form the dataset used in reporting and analysis.

Expected Fields are configurations for the data inputs for a Document Instance. Each field specifies its data type—text, numeric, date, or boolean—and can include validation constraints like min/max values or date ranges to ensure accurate data capture.

A Facility represents a physical or operational location where environmental activities occur. Facilities serve as the primary unit for reporting, linking Monitoring Periods, Audit Packages, Documents, and Evidence Requests.