What is carbon project development?
Carbon project development is the process of taking land from initial feasibility screening through to the issuance of credits by a registry. It spans site selection and eligibility testing, choosing a methodology, writing a project design document, passing third-party validation, implementing the planting or management activity, monitoring outcomes over years, and passing verification. Each stage produces a document or dataset the next stage depends on, which is why a weakness early in the pipeline is expensive rather than merely inconvenient.
Timelines vary widely by project type, geography and standard. What is consistent is the shape: a long front-loaded phase where money goes out and nothing is issued, followed by a crediting period during which verification recurs on a cycle.
What are the stages of a carbon project?
The pipeline below is the common structure across the major standards. Names differ between registries — the substance does not.
| Stage | What happens | Output |
|---|---|---|
| Feasibility | Screen land, test eligibility, size the opportunity | Go/no-go and an indicative volume |
| Methodology selection | Match activity and geography to a registry methodology | Chosen methodology and standard |
| Baseline | Establish what would have happened without the project | Baseline scenario and carbon model |
| Project design | Document design, additionality, safeguards, monitoring plan | PDD |
| Validation | Independent audit of the design against the methodology | Validation report, registry listing |
| Implementation | Planting, management, community engagement | Field records and evidence base |
| Monitoring | Measure outcomes on the methodology's cycle | Monitoring report |
| Verification | Independent audit of claimed outcomes | Verification statement |
| Issuance | Registry issues credits for the verified period | Credits in a registry account |
How do you know if land is eligible?
Land eligibility is the first hard gate, and the one most often failed late. Every methodology sets conditions on what the land was before the project started — typically covering prior land use, historical tree cover, and the date from which the project can claim. Establishing that requires historical satellite imagery, not a site visit, because the question is about the past rather than the present. This is where projects most commonly discover that a parcel they have already invested in does not qualify.
- Historical land cover, evidenced over the lookback period the methodology specifies.
- Land tenure and the right to claim the carbon, which is a legal question as much as a spatial one.
- Exclusion of areas that fail eligibility, mapped precisely rather than estimated.
- Evidence that the activity is additional — that it would not have happened anyway.
FloraScope handles the spatial half of this: satellite land screening and land-use and land-cover mapping, so eligibility can be tested before capital is committed rather than after. See how digital MRV covers the lifecycle.
Where do carbon projects most often stall?
Projects rarely fail because the trees do not grow. They stall at the points where evidence has to satisfy someone external — a validator, a verifier, or a buyer's diligence team. Four recur:
- Eligibility discovered late, after land has been secured on assumptions that historical imagery does not support.
- Baseline disputes, where the counterfactual is not documented well enough to survive audit scrutiny.
- Monitoring gaps, where the data collected does not match what the methodology's monitoring plan committed to.
- Participant traceability at scale, where per-farmer records cannot be reconciled into a defensible whole.
The last of these grows non-linearly with participant count. Our own work spans around 100 farmers in West Bengal and more than 2,000 in Timor-Leste, and the difference between those two is not twenty times the paperwork — it is a different problem requiring a different system.
What does carbon project development cost?
Costs fall into three buckets: development costs before issuance, implementation costs on the ground, and recurring verification costs across the crediting period. Published figures vary so widely by geography, project type and standard that a single number would be misleading, and this page will not invent one. What can be said structurally is that development and verification costs are substantially fixed rather than proportional to project size, which is why small projects struggle and why aggregation into larger programmes is the dominant response.
Digital MRV bears mainly on the third bucket, and on the diligence overhead inside the first. If you want the numbers for a specific project shape, talk to our team rather than working from a generic benchmark.
Which standard should a project use?
The choice of standard follows from the activity, the geography, and who is expected to buy the credits. Flora Carbon AI works across the major frameworks rather than pushing one, because the right answer differs per project. For afforestation, reforestation and revegetation under Verra, see the VM0047 methodology guide. For the two project types we work on most, see agroforestry and blue carbon.