Browse the public CDM registry's AFOLU project list and a handful of status labels do most of the work: "Registered," "Registration requested," "Late to verify," among others. They sound self-explanatory until you try to use them to judge whether a project is active, abandoned, or simply slow — and the labels alone don't tell you which.
The Labels Worth Knowing
| Status | What it actually means |
|---|---|
| Registration requested | A project has applied but not yet completed the formal registration step |
| Registered | The project has been formally accepted into the CDM pipeline and has an active crediting period |
| Late to verify | A registered project has passed a point in its crediting period where a verification would normally be expected, and none has been filed |
| Withdrawn | The project proponent has formally pulled the project from the pipeline |
"Late to verify" is the one most likely to be misread. It is not a formal determination that a project has failed or been abandoned — it is a registry-level flag that a verification event is overdue relative to the project's own monitoring plan or typical cadence for its methodology. A project can carry that status for reasons ranging from a developer genuinely having stopped the activity, to a slower-than-planned monitoring cycle for a legitimate biological reason (tree growth not yet sufficient to verify meaningfully), to administrative delay in commissioning a verification body.
Why the Distinction Matters
Treating "late to verify" as equivalent to "dead project" would be a mistake in either direction — some projects carrying this status for years do eventually file a verification and resume normal issuance, particularly AR projects where growth-rate-driven monitoring gaps are structurally longer than for other project types. Treating it as a non-issue is also a mistake: a project with no verification activity for an extended period, with no public explanation, is a reasonable candidate for closer due diligence before anyone relies on its registered-but-unverified status as evidence of ongoing performance.
What a Status Label Does Not Tell You
None of these registry status labels say anything directly about data quality, baseline soundness, or whether the project would pass verification if one were filed tomorrow. They describe where a project sits in an administrative pipeline, not whether its underlying carbon claims are sound. A "Registered" project with a clean verification history is not automatically more credible on the substance than a project carrying a "Late to verify" flag for a defensible, documented reason — the status label is a starting point for investigation, not a substitute for reading the project's actual monitoring and verification record.
How to Use the Field in Practice
For anyone screening the registry for research or due-diligence purposes, the practical move is to treat status as a filter for where to look closer, not as a final answer. A project flagged "Late to verify" is worth checking for a public explanation (a monitoring report in preparation, a stated delay reason) before drawing any conclusion about its current state — and a "Registered" project with no recent activity deserves the same scrutiny the status label alone won't prompt.
Turn climate goals into a verified portfolio
TREEO connects the full carbon cycle — eligibility, simulation, real-time monitoring and registry-ready reporting — combining expert consulting with dMRV technology so the evidence exists before anyone asks for it.



