APOPO Carbonscope Carbon readiness and land recovery
APOPO Carbonscope
From field records to verified carbon credits

Community anchored carbon registry

Carbonscope links mapped land boundaries, field records, and supporting documents into a single audit trail. Conservative estimates can appear early, but credits only become issued and tradable after independent verification and formal issuance. Retirement permanently removes credits from trading and creates a traceable retirement record.

Evidence first Community anchored Conservative estimates Issued then traded then retired
Records are evidence first, publishing is opt in, and credit states remain explicit across draft, review, issued, traded, and retired.

Live platform totals

Figures appear when the relevant modules and tables are configured.

Not available yet
Projects registered
Not available yet
Boundaries mapped
Not available yet ha
Area with saved geometry
Not available yet
Evidence documents stored
Not available yet tCO2e
Credits available
Not available yet tCO2e
Credits retired

Dashboard preview

A single view across projects, boundaries, documents, and credit states.

Projects registered
primary
Not available yet
Area with saved geometry
success
Not available yet
ha
Evidence documents stored
secondary
Not available yet
Credits retired
secondary
Not available yet
tCO2e

What you are seeing here

This is a public preview of the workflow. Records and estimates can exist early. Issued credits only appear after independent review and issuance, and retirement is the final state.
Core
Readiness 30%
This is a completeness signal. For example, Land readiness increases when a footprint exists, versions are saved, and scope is clearly selected. It is not a verification result.
Estimates are not issuance Audit trail by default Clear credit states
If you are logged out, these may route to sign in depending on your guards. Logged in, they open the actual modules.

Measured outputs

Not yet published
No published metrics yet
This panel stays empty until definitions, scope, and evidence links exist for the module.

Land scope and boundary versioning

Boundaries anchor every claim. Save a versioned footprint and supporting polygons. The platform can enforce “primary footprint” rules to keep scope explicit.
Core
Readiness 35%
This is a completeness signal. For example, Land readiness increases when a footprint exists, versions are saved, and scope is clearly selected. It is not a verification result.
Versioned polygons Primary footprint Overlap checks
If you are logged out, these may route to sign in depending on your guards. Logged in, they open the actual modules.

Measured outputs

Not yet published
No published metrics yet
This panel stays empty until definitions, scope, and evidence links exist for the module.

Evidence packs that support review

Documents are linked evidence with metadata and traceability. They attach to projects, sites, boundaries, MRV records, and exports.
Core
Readiness 25%
This is a completeness signal. For example, Land readiness increases when a footprint exists, versions are saved, and scope is clearly selected. It is not a verification result.
Linked evidence Publish is opt in Export ready packs
If you are logged out, these may route to sign in depending on your guards. Logged in, they open the actual modules.

Measured outputs

Not yet published
No published metrics yet
This panel stays empty until definitions, scope, and evidence links exist for the module.

Credits, lots, trading, and retirement

This tab is where the platform separates estimates from issued credits. Trading only applies to issued lots. Retirement permanently removes lots and generates verifiable outputs.
Preview
Readiness 15%
This is a completeness signal. For example, Land readiness increases when a footprint exists, versions are saved, and scope is clearly selected. It is not a verification result.
Issued only after review Ledgered ownership Retirement is final
If you are logged out, these may route to sign in depending on your guards. Logged in, they open the actual modules.

Measured outputs

Not yet published
No published metrics yet
This panel stays empty until definitions, scope, and evidence links exist for the module.

Integrity and change control

Governance is implemented through rules. Versioning, role separation, approval gates, and the ability to flag or freeze questionable records keep the registry defensible.
Integrity
Readiness 20%
This is a completeness signal. For example, Land readiness increases when a footprint exists, versions are saved, and scope is clearly selected. It is not a verification result.
Change control Review gates Fraud resistance
If you are logged out, these may route to sign in depending on your guards. Logged in, they open the actual modules.

Measured outputs

Not yet published
No published metrics yet
This panel stays empty until definitions, scope, and evidence links exist for the module.

Lifecycle inside the platform

From field work to issued and retired credits, with clear state gates.

1
Define project
Create a project and define reporting scope.
2
Map boundaries
Save a primary footprint and versioned boundary history.
3
Log activities
Capture what was done on the land and when it occurred.
4
Attach evidence
Upload documents and link them to scope and records.
5
Monitoring cycles
Add repeat MRV records so changes are traceable over time.
6
Independent review
Verifier checks completeness and evidence linkage.
7
Issuance
Only after approval are credits minted into lots.
8
Trade and retirement
Issued credits can be traded and then retired permanently.

Integrity controls

Controls that keep evidence, estimates, and issued credits aligned.

Changes create new versions with timestamps and authorship.

Footprint scope uses enforced rules so it cannot silently fork.

Key outputs must reference the records and evidence behind them.

Operators create records, reviewers approve, admins control issuance.

Uncertainty reduces quantities rather than inflating them.

Community and partners

Projects begin with mapped scope and structured records. Review roles can then audit evidence linkage and determine readiness for issuance and market actions.

APOPO
Public profile available
Cambodia Mine action enabled recovery, agricultural livelihoods, and community anchored evidence systems
  • Mapped land scope and versioned boundaries
  • Evidence packs that are reviewable and exportable
  • Risk and readiness signals that improve over time
Cooperatives and farmer groups
Partner pathway open
Cambodia and region Local organisations documenting stewardship, implementing practice change, and maintaining records
  • Private by default with controlled sharing
  • Guided templates for evidence and monitoring
  • Clear steps from onboarding to issuance readiness
Reviewers and verifiers
Partner pathway open
Cambodia and region Independent review of records, risk interpretation, and issuance readiness decisions
  • Read only review views and audit trails
  • Checklist based gating and traceable findings
  • Clear outcomes: request changes, approve, or reject

How the system works

A structured sequence from field work to issued credits, with clear separation between estimates and issued units.

Map the scope

Define projects, create sites, and save boundaries so records are anchored to a specific area and period.

Record and link evidence

Capture activities and monitoring data, then attach documents and logs so review is possible.

Estimate conservatively

Early estimates can be produced where inputs allow. Estimates are not issuance.

Verify, issue, trade, retire

Independent verification enables issuance. Issued credits can be traded. Retirement permanently removes credits from trading.

Measurement principles
A consistent approach across partners and sites, designed to mature into verification readiness.
Definitions are explicit
Each indicator has a definition, scope, and version. Changes are tracked so comparisons remain meaningful.
Evidence is linked
Field records, photos, GPS, and documents attach to indicators so claims can be reviewed and reproduced.
Conservative by default
When uncertainty exists, values are discounted or held back rather than inflated.
Integrity controls
Audit trails, approvals, and change logs reduce silent edits and keep reporting defensible.