A woman compares an unbranded dossier with a landscape image and printed map and report pages at a desk.
Review the evidence for the specific project and units being offered.
Diagram text description

A synthetic editorial scene shows a woman reviewing unbranded dossier, landscape and map materials beside an open notebook. It illustrates document comparison, not a real project identity, verified climate result, eligible serial range, customer claim or assessment approval.

High quality carbon credits need evidence that connects a credible climate outcome with the specific units being offered and the purpose for which they will be used. A respected programme, attractive project photograph or high price cannot establish that whole chain. Each can point towards useful questions, but the answer must come from the applicable rules, project records and unit history.

A practical review separates programme controls, category or methodology scope, project-period findings and exact issued units. It then asks whether the buyer’s proposed wording accurately describes the evidence and use. This guide turns those layers into concrete review questions, compares a fictional dossier containing conflicting records and provides a filled unit-quality decision record. The example withholds a conclusion rather than pretending that a missing document has been resolved.

Start with the statement you need to support. “The programme is eligible,” “these serials meet the applicable conditions” and “our company has achieved a climate outcome” are different statements. Defining the statement and its unit, period and evidence scope makes the review more useful than assigning a broad quality score to a project name.

Four layers behind a credit-quality claim

Separate the four credit-side evidence layers before interpreting a label. Programme evidence concerns governance, tracking, transparency and independent review requirements. Category evidence concerns the approved activity or methodology scope and its conditions. Project evidence concerns implementation and findings for the relevant monitoring period. Unit evidence concerns the exact issued quantity, serials and current status. These questions are related, but an answer at one layer is not automatically an answer at the next.

The ICVCM Core Carbon Principles describe a quality threshold covering programme controls and substantive climate and safeguard requirements. ICVCM’s Assessment Framework page describes separate assessments of carbon-crediting programmes and categories. Use that architecture to identify what an assessment statement actually covers, then match it to the offered project and units.

Programme, category, project and issued-unit evidence are separate cards; buyer claims require a separate review.
Match each statement to its own evidence layer.
Diagram text description

Programme rules and eligibility, approved category or method scope, project-period findings and exact issued-unit serial status answer different questions. A buyer claim then needs its own evidence and wording review. Do not inherit a project or unit conclusion from a programme label, or infer a buyer claim from the quality of a credit.

Ask for the precise programme name, methodology and version, project identifier, credited period and serial scope. Record conditions or exclusions attached to the status being asserted. A general logo or a statement about a programme’s wider portfolio does not identify those details.

Keep buyer wording as another review. Even strong unit evidence cannot establish whether a company has described its gross emissions, reductions or retirement correctly. A credit-quality review should therefore say which layer has support, which remains unresolved and which further evidence belongs to the buyer’s own statement.

Does the project pass an additionality test?

Additionality asks whether the credited activity would have occurred without the incentive created by carbon-credit revenue. The existence of a working project is not enough. A credible conclusion needs a supported counterfactual and the tests required by the applicable methodology, rather than an assumption that every activity receiving credit revenue depends on it.

Compare the without-credit baseline with the credited activity and the role of the incentive. Relevant evidence may concern the activity’s circumstances, applicable requirements, implementation decisions and the method’s specific additionality tests. A project narrative should explain the causal argument; the supporting records must make that argument reviewable. Treat a missing baseline justification as an open question, not as a favourable default.

A without-credit baseline and credited-activity case are compared; observed activity alone does not establish additionality.
A real activity still needs a supported without-credit comparison.
Diagram text description

Review a credible baseline for what would occur without the credit incentive and compare it with the credited activity. Examine the relevant methodology tests and evidence of the incentive rather than treating project existence as proof. Neither a persuasive narrative nor a single investment document establishes the whole conclusion.

Be careful with a single persuasive document. An investment paper mentioning credit income can be relevant without establishing that the activity could not proceed otherwise. Conversely, one profitable period does not by itself settle every methodology-specific test. Assess the evidence in its proper context and record the reasoning.

For a buyer, the useful question is specific: which test applies to this activity and period, what evidence supports it, and what finding addresses any contradiction? Request the missing record or explanation before accepting an additionality conclusion. Do not substitute a project’s popularity, location or apparent environmental benefit for the counterfactual that the method requires.

Are the credited tonnes conservatively measured?

Trace the credited tonnes from the applicable methodology through monitored activity, leakage treatment, uncertainty and independent findings. The ICVCM principles call for robust, conservative quantification. A reported gross benefit is not automatically the eligible net quantity: the relevant boundary, deductions and programme requirements must be understood before it is matched to an issuance.

Check that the monitoring report identifies its method and version, period, data sources and calculation basis. Examine the treatment of missing observations, sampling, measurement uncertainty and material displacement outside the project. Where deductions or adjustments are required, retain how they affect the net result. Do not infer that no deduction was needed because a promotional summary omits it.

Then read the independent verification findings for that same scope. Establish which project, period, method and quantity the statement covers, and whether qualifications or unresolved findings affect the offered units. A verification heading on a document is not a substitute for reading the conclusion and its limitations.

If the monitoring and verification records disagree, stop the inference at that gap. Ask for the reconciled calculation, corrected document or period-matched finding and preserve both versions. A larger reported number does not become more credible by being repeated across several sales documents. The important result is the supported quantity under the applicable method, with its uncertainty and review limits visible.

How durable is the climate outcome?

Durability depends on what physically happened and what could undo the climate outcome. Avoiding an emission and removing carbon from the atmosphere are different mechanisms. The permanence question must fit that mechanism and any storage involved. The ICVCM principles require permanence or measures that address and compensate reversal risks; they do not justify treating every credited tonne as an identical physical asset.

Mechanism or conditionQuestion to investigateEvidence to request
Avoided emission relative to a baselineWas the credited release genuinely avoided under the supported counterfactual?Baseline, monitoring and method-specific findings
Removal followed by storageWhere is the carbon stored, for how long, and how is that supported?Storage mechanism, monitoring obligations and applicable durability requirements
Outcome exposed to reversalWhat could release stored carbon and what happens if it does?Risk assessment, monitoring and the programme’s response or compensation provisions

Table 1, shown one row at a time. Every field is retained.

Row 1

Mechanism or condition
Avoided emission relative to a baseline
Question to investigate
Was the credited release genuinely avoided under the supported counterfactual?
Evidence to request
Baseline, monitoring and method-specific findings

Row 2

Mechanism or condition
Removal followed by storage
Question to investigate
Where is the carbon stored, for how long, and how is that supported?
Evidence to request
Storage mechanism, monitoring obligations and applicable durability requirements

Row 3

Mechanism or condition
Outcome exposed to reversal
Question to investigate
What could release stored carbon and what happens if it does?
Evidence to request
Risk assessment, monitoring and the programme’s response or compensation provisions

Use these distinctions to assess the actual project rather than rank every avoided-emission or removal activity in one category. Storage duration, reversal exposure, monitoring responsibilities and remedies can differ substantially within a broad project label.

Check who remains responsible after issuance and what evidence shows that obligations are being met. A stated buffer, insurance arrangement or replacement mechanism needs its terms and applicability reviewed; its name alone does not establish the protection for the units offered. Record any gap in duration, monitoring or response evidence as a condition on the quality conclusion rather than hiding it inside a generic permanence score.

Can emissions move outside the project boundary?

A project can show a local benefit while related activity or carbon loss shifts elsewhere. That displacement can weaken the net climate benefit attributed to the project. Review the leakage pathways relevant to the activity and the treatment required by its methodology instead of assuming that the drawn project boundary captures every consequence.

For example, protecting one area would raise a different evidence question if the affected activity simply moved beyond it. The schematic illustrates that possibility; it is not a claim that a particular project caused displacement. Ask which activity could shift, where the effect could occur, how it is monitored or estimated and how material leakage enters the calculation.

A reported local benefit sits inside a project boundary while displaced activity lies outside; the method must assess the net effect.
Check displacement outside the credited boundary.
Diagram text description

A project can show a local reduction while related activity or carbon loss shifts elsewhere. Assess the relevant displacement pathway under the method, examine monitoring evidence and apply required leakage treatment. The schematic illustrates a risk to investigate, not a measured leakage value or a universal deduction.

Connect the answer back to the credited quantity. A method may require deductions or other treatment; retain the supporting data, assumptions and independent findings. “Outside our site” is not a sufficient reason to disregard an effect that the method is intended to assess.

Do not impose one invented leakage percentage across unrelated activities. If the relevant pathway or deduction cannot be established, identify that uncertainty and request the specific evidence needed. The quality question concerns the supported net benefit, not simply whether the project’s own monitoring area looks improved in isolation.

Can the same unit be counted twice?

Unit tracking needs an exact identity. Match the issued serial scope to its programme, project, credited period and quantity, then inspect the current registry status and relevant history. The ICVCM principles distinguish double issuance, double claiming and double use. A unique identifier is important, but the review must also ask what happened to the unit and how it will be used.

Retain issuance, holding and any transfer history, then verify retirement when the intended use requires it. A purchase invoice or promise to retire later is not the same evidence as an actual registry retirement event. Check the recorded quantity, beneficiary or purpose and the reference connecting that event to the proposed use.

Exact serial issuance leads through holding and transfer history to retirement and a checked beneficiary or claim reference.
Trace the exact serial through its status and intended use.
Diagram text description

Match issued serials with the project and credited period, inspect holding and any transfer history, and verify retirement status and its beneficiary or purpose for the intended use. A registry record supports unit tracking; it does not by itself settle additionality, quantification or the truth of a company claim.

Keep project quality separate from registry status. Retirement helps establish that a unit has been taken out of circulation for a recorded purpose; it does not independently prove additionality, resolve a monitoring discrepancy or validate a company’s wider climate statement. Those questions require their own evidence.

If the seller offers a range of serials, review that range rather than a convenient example unit from the same project. Check that the period, method applicability and status evidence cover the offered scope. Where the evidence cannot be matched, withhold the unit-use conclusion and ask for the exact record. An apparently complete project page should not conceal an unresolved serial-level question.

What do safeguards say about the project?

Safeguard evidence should describe what happened to people and ecosystems around the project, with dated consultation, impact assessment, monitoring and grievance-response records. A photograph of a community meeting can provide context without showing who participated, what concerns were raised or whether the response addressed them. Positive benefit language also needs evidence tied to the project and period.

Read the findings and responses together. Identify affected groups, relevant environmental or social risks, how concerns could be raised, which complaints remain open and what action followed. A policy document can establish a procedure without establishing that it worked in this case. Ask for the project-level record when the conclusion depends on implementation.

Keep different claims distinct. Evidence of consultation does not by itself prove a promised income benefit, biodiversity outcome or absence of harm. For each benefit being communicated, identify the indicator, baseline where relevant, monitoring period and evidence of the result. Missing evidence should narrow the statement.

Also consider whether the activity risks locking in emissions or practices incompatible with the transition described in the applicable framework. A carbon-crediting claim should not distract from unresolved safeguard concerns or long-term consequences. Record significant issues and the evidence needed to address them rather than allowing a strong-looking carbon number to outweigh a critical social or environmental gap.

Compare a fictional project dossier

The following dossier is entirely fictional. Pine Ledger is an invented programme, Willow Reach an invented forest-conservation project, and all document names, quantities and serials are teaching identifiers. The offered package concerns project WR-47 and a claimed 2024 outcome. No real programme, project or credit is being assessed or approved.

Fictional recordWhat it actually saysQuestion raised by comparison
Offer O-24WR-47; 2024; 950 credits; proposed serials FIC-WR-2024-1001 through 1950Does issuance and quality evidence cover this exact range?
Monitoring report MR-24Calendar 2024; methodology WR-M version 2.0; reports 950 t CO2e net benefitIs there independent verification for this period, method and quantity?
Verification statement VS-23Calendar 2023; WR-M version 1.0; covers 700 t CO2eThis statement covers a different period and method from MR-24
Registry material suppliedA project-level summary, without a serial-level issuance extract for O-24The offered units are not yet linked to a demonstrated issuance record

Table 2, shown one row at a time. Every field is retained.

Row 1

Fictional record
Offer O-24
What it actually says
WR-47; 2024; 950 credits; proposed serials FIC-WR-2024-1001 through 1950
Question raised by comparison
Does issuance and quality evidence cover this exact range?

Row 2

Fictional record
Monitoring report MR-24
What it actually says
Calendar 2024; methodology WR-M version 2.0; reports 950 t CO2e net benefit
Question raised by comparison
Is there independent verification for this period, method and quantity?

Row 3

Fictional record
Verification statement VS-23
What it actually says
Calendar 2023; WR-M version 1.0; covers 700 t CO2e
Question raised by comparison
This statement covers a different period and method from MR-24

Row 4

Fictional record
Registry material supplied
What it actually says
A project-level summary, without a serial-level issuance extract for O-24
Question raised by comparison
The offered units are not yet linked to a demonstrated issuance record

The discrepancy matters because VS-23 cannot establish that MR-24’s 2024 result under version 2.0 was independently verified. Nor does the project summary connect the offered serial range to a supported issuance. Do not subtract 700 from 950 and call only the difference unverified: the records cover different periods, so that subtraction would conceal the actual scope mismatch.

Request the complete MR-24 calculation and findings, a period-and-method-matched verification statement, and the registry issuance extract linking the offered serials to WR-47 and the credited period. Check any methodology transition conditions and whether unresolved findings affect the quantity. If a CCP-related status is asserted, obtain the exact programme/category applicability evidence separately; a seller’s badge does not close these dossier questions.

The defensible disposition is hold pending those records. That does not establish fraud or prove that the project lacks a climate benefit. It states that the supplied package cannot support the offered unit-quality conclusion. If a corrected document arrives, retain the earlier version and confirm that the correction resolves the underlying period, method and unit link rather than merely changing a filename.

Additionality and safeguards are also unassessed in this fictional package. A repaired verification mismatch would not silently answer those separate questions. Record what has been resolved and what still prevents a complete conclusion.

Use CCP labels as a threshold, not a shortcut

Use a CCP-related statement at its stated scope. The ICVCM architecture requires both an eligible programme and approved category conditions for the label’s application. Programme eligibility alone does not make every methodology, project, credited period or offered unit within the programme applicable to that statement.

Check the current status and conditions against the exact programme and category or methodology, including the relevant version and scope of the offer. Then link the project and serial evidence. Preserve the date and source of the status observation so a later reviewer can see what was relied on. Do not treat an old screenshot, a broad programme logo or a seller’s summary as a substitute for the applicable record.

The Assessment Framework page also describes a rule architecture for maintaining and interpreting the framework. That is a reason to read relevant conditions and changes rather than treating a label as a timeless statement detached from its scope. This guide does not establish any actual programme, category or unit’s current eligibility.

A threshold can support a consistent review without replacing it. In the fictional Willow Reach case, even a properly matched programme/category status would not make the mismatched verification statement cover the offered 2024 serials. Keep the framework-status question and the dossier-resolution question in separate fields until each has evidence.

Reject seductive but weak quality signals

Weak signals can be useful prompts, but they do not prove a climate outcome. A high price can reflect many commercial factors; a compelling image can show a real place without establishing a baseline or credited quantity. Translate each signal into the evidence question it cannot answer.

Signal presentedUseful follow-upWhat remains unproved by the signal alone
High price or provider promiseReview the contract, exact units, responsibilities and supporting dossierAdditionality, delivered unit identity and verified climate outcome
Project photograph or tree countRequest monitoring, quantification and safeguard evidence for the relevant periodNet credited benefit, durability or absence of harm
Programme or quality badgeCheck exact programme/category status, conditions and unit applicabilityCoverage of every project, version, vintage or offered serial
Marketplace rating or retirement promiseRead the rating’s scope and obtain the actual registry record for the intended useCurrent ownership/status, completed retirement or truthful buyer wording

Table 3, shown one row at a time. Every field is retained.

Row 1

Signal presented
High price or provider promise
Useful follow-up
Review the contract, exact units, responsibilities and supporting dossier
What remains unproved by the signal alone
Additionality, delivered unit identity and verified climate outcome

Row 2

Signal presented
Project photograph or tree count
Useful follow-up
Request monitoring, quantification and safeguard evidence for the relevant period
What remains unproved by the signal alone
Net credited benefit, durability or absence of harm

Row 3

Signal presented
Programme or quality badge
Useful follow-up
Check exact programme/category status, conditions and unit applicability
What remains unproved by the signal alone
Coverage of every project, version, vintage or offered serial

Row 4

Signal presented
Marketplace rating or retirement promise
Useful follow-up
Read the rating’s scope and obtain the actual registry record for the intended use
What remains unproved by the signal alone
Current ownership/status, completed retirement or truthful buyer wording

Use the answer to refine the review rather than replacing one proxy with another. A detailed rating may contain useful analysis, but its scope, date and unresolved questions still matter. A contract can establish an obligation while leaving the climate evidence unproved. A registry record can establish an event while leaving project-quality questions open.

Avoid a weighted average that lets several attractive features compensate for a fatal evidence gap. If the offered serials cannot be identified or the verification covers another period, say so directly. The next step is the missing evidence or a bounded decision, not another round of promotional material.

Record a defensible quality decision

This filled decision record continues the entirely fictional Willow Reach dossier. Reviewer Lena Shaw and the review date of 18 February 2025 are invented scenario details, separate from the publication dates of real framework guidance. The record documents a hold, not approval of a real or fictional credit.

Decision fieldFilled fictional entryEvidence limit or conditional action
Programme and categoryPine Ledger; forest-conservation category asserted in O-24Programme eligibility and category applicability not established; seller statement is insufficient
Methodology/versionWR-M version 2.0 for MR-24Resolve transition and applicability; VS-23 uses version 1.0
Project and periodWillow Reach WR-47; calendar 2024Period-matched independent findings required
Unit and serial scope950 offered credits, FIC-WR-2024-1001 through 1950Offered range only; exact issuance and status not established
Evidence inspectedO-24, MR-24, VS-23 and project-summary registry materialVS-23 covers 2023; no serial-level issuance extract supplied
Other quality questionsAdditionality, durability, leakage and safeguards not established by this packageObtain the applicable evidence and record findings separately
Reviewer and dateLena Shaw; 18 February 2025Fictional review identity and scenario date
DispositionHold unit-quality conclusionRequire matched verification, registry linkage and resolution of critical open questions
Proposed buyer claimA compensation statement is contemplated; no supporting retirement or buyer inventory evidence suppliedBuyer wording remains unsupported and needs a separate review

Table 4, shown one row at a time. Every field is retained.

Row 1

Decision field
Programme and category
Filled fictional entry
Pine Ledger; forest-conservation category asserted in O-24
Evidence limit or conditional action
Programme eligibility and category applicability not established; seller statement is insufficient

Row 2

Decision field
Methodology/version
Filled fictional entry
WR-M version 2.0 for MR-24
Evidence limit or conditional action
Resolve transition and applicability; VS-23 uses version 1.0

Row 3

Decision field
Project and period
Filled fictional entry
Willow Reach WR-47; calendar 2024
Evidence limit or conditional action
Period-matched independent findings required

Row 4

Decision field
Unit and serial scope
Filled fictional entry
950 offered credits, FIC-WR-2024-1001 through 1950
Evidence limit or conditional action
Offered range only; exact issuance and status not established

Row 5

Decision field
Evidence inspected
Filled fictional entry
O-24, MR-24, VS-23 and project-summary registry material
Evidence limit or conditional action
VS-23 covers 2023; no serial-level issuance extract supplied

Row 6

Decision field
Other quality questions
Filled fictional entry
Additionality, durability, leakage and safeguards not established by this package
Evidence limit or conditional action
Obtain the applicable evidence and record findings separately

Row 7

Decision field
Reviewer and date
Filled fictional entry
Lena Shaw; 18 February 2025
Evidence limit or conditional action
Fictional review identity and scenario date

Row 8

Decision field
Disposition
Filled fictional entry
Hold unit-quality conclusion
Evidence limit or conditional action
Require matched verification, registry linkage and resolution of critical open questions

Row 9

Decision field
Proposed buyer claim
Filled fictional entry
A compensation statement is contemplated; no supporting retirement or buyer inventory evidence supplied
Evidence limit or conditional action
Buyer wording remains unsupported and needs a separate review

Use explicit acceptance conditions rather than a single score. Here the reviewer needs evidence that corresponds to the offered project, method, period and serials, plus findings on the outstanding quality dimensions. If CCP-related wording is intended, its applicability must be supported at the relevant programme/category and unit scope. The record does not promise that supplying one document will satisfy every condition.

A rejected scope or unresolved critical contradiction should remain visible rather than being averaged away. When evidence arrives, record its identity and date, the question it resolves and the revised disposition. Preserve the previous decision so another reviewer can understand why the conclusion changed. Claim approval remains separate even if the unit-quality review later advances.

Separate a good unit from a good company claim

A strong issued credit can still appear in a misleading company statement. Review what the buyer says about its gross emissions, own reductions, credit purchase and retirement. These facts need their own evidence and should not be collapsed into a broad assertion that the company’s activities no longer create emissions.

Match the intended use to the actual units and retirement record, including beneficiary or purpose and reporting period where relevant. A seller’s delivery document is not automatically evidence of retirement for that buyer. Likewise, a retired credit does not establish that the buyer’s inventory is complete or that its reduction figure is accurate.

Keep inventory and credit records distinguishable. Preserve gross emissions and the evidence for reductions, then describe the credit-related action on its supported basis. Do not use a unit-quality label to imply an assurance conclusion about the company or a blanket entitlement to any compensation wording.

For the fictional Willow Reach offer, the record withholds a unit conclusion and lacks retirement and buyer evidence. A compensation claim therefore cannot be supported by the supplied package. This is a practical separation of evidence questions, not a finding about a real transaction or a universal rule approving one phrase. Review the actual proposed wording under the requirements and context that apply to it.

Keep project, unit and claim evidence connected

Keep programme, project, unit and claim records connected without pretending that record organization performs the substantive assessment. A useful evidence structure helps a reviewer identify the document supporting a statement and find the unanswered question. It does not establish a credit-quality service, independent verification or a guaranteed approval outcome.

Assign responsibility for each layer. The supplier can provide the exact offer and dossier; programme and registry records establish their respective stated scopes and events; the buyer must supply evidence for its own inventory and intended use; a reviewer must assess the fit between the evidence and the conclusion. One convenient folder should not blur those responsibilities.

Use a clear issue record with the project and serial scope, document reference, discrepancy, owner, requested evidence and current disposition. Retain prior versions when a report or offer changes. A colleague should be able to understand why the Willow Reach example is on hold without relying on a verbal explanation.

Test the structure with the statement that matters most. If the reviewer cannot find which period was verified or which units a registry extract covers, improve that link first. A polished summary is valuable only when it preserves the specific evidence and limits behind its conclusions.

Make the next review specific to the unit

Make the next review specific to the statement and units under consideration. High-quality credit evidence connects programme and category conditions, a credible project outcome, exact issued-unit history and the intended use. A familiar logo, a high price or a complete-looking folder cannot replace a missing link.

If the gap concerns quantification, obtain the relevant method, monitoring and independent findings. If it concerns identity or use, trace the exact serials and registry event. If it concerns buyer wording, review the buyer’s own inventory, reduction and retirement evidence separately. Programme shortlists, credit calculations, lifecycle and expiry questions deserve focused work on their own terms.

Before recording a conclusion, state what the evidence supports, what remains unknown and which condition changes the disposition. The fictional dossier demonstrates a useful hold: it identifies the mismatched period and method, requests the missing unit linkage and leaves broader quality and claim questions open.