Every registry publishes its document list. What the list does not convey is sequencing, specifically which artefacts have to exist before which others can be produced, and which get assembled at the end by teams who did not realise they needed material collected at the beginning.
The Core Set
| Document | What it establishes |
|---|---|
| Project description / design document | The whole project: boundary, baseline, methodology, activities |
| Evidence of land rights and carbon rights | That the proponent can claim the credits |
| Boundary geometry (GIS) | The spatial extent, cleanly |
| Validation report | Independent assessment that the design conforms |
| Monitoring plan | What will be measured, how, when |
| Monitoring report | What was measured, per period |
| Verification report | Independent assessment that the monitoring conforms |
| Stakeholder consultation record | That affected parties were consulted |
The Sequencing That Trips Projects
Order things actually have to happen
1. Land and carbon rights
Everything downstream assumes these are settled. Unsettled rights stop a project at validation regardless of design quality.
2. Boundary geometry
The design document quotes areas derived from it. Producing the design first means rewriting it.
3. Stakeholder consultation
Must occur before design is finalised, because it is supposed to influence the design.
4. Design document
Assembles the above into the methodology's structure.
5. Validation
Independent assessment of the design.
6. Implementation and monitoring
Per the plan, with evidence collected contemporaneously.
7. Verification
Independent assessment of the monitoring.
The Two Always Assembled Too Late
Stakeholder consultation records. Consultation frequently happens, meaning meetings occur and communities are engaged, but the record is reconstructed afterwards from memory and photographs. Registries want dated records, attendance, what was raised, and how the project responded. Assembled later, the record cannot show that consultation influenced anything, which is the point of requiring it.
Evidence of activity implementation. Discussed at length elsewhere on this site, and it belongs here too: the monitoring report claims activities occurred at a scale, and the evidence has to have been collected while they were occurring.
Carbon Rights Are Not Land Rights
The distinction catches projects in jurisdictions where the framework is still settling.
Holding or controlling land does not automatically confer the right to claim and sell carbon from it. That depends on national law, the tenure instrument, and any agreements with the parties who actually manage the land. In Indonesia, with several tenure categories and an evolving regulatory framework, this deserves specialist review at the start rather than an assumption.
A project that reaches validation with ambiguous carbon rights has spent its design budget on a question that was answerable on day one.
The Living-Document Problem
The design document is written once and referenced for decades, while the project changes, as activities evolve, areas adjust, and parameters get updated.
Registries have processes for revisions, and the failure mode is not using them: a project operating differently from its registered description, with the divergence accumulating quietly until a verification surfaces it all at once.
Keeping the registered description current is unglamorous administration that prevents a specific and expensive category of failure.
Turn climate goals into a verified portfolio
TREEO connects the full carbon cycle, encompassing eligibility, simulation, real time monitoring, and registry ready reporting, thereby combining expert consulting with dMRV technology so the evidence exists before anyone asks for it.
