Person compares illustrated project reports with a laptop table at a desk.
A documentary review connects the relevant project report with its supporting record.
Diagram text description

Synthetic editorial desk scene with forest images, maps and charts on printed pages and a laptop. No actual project identity, result or registry status can be read from the image.

How do you verify carbon credits when the seller sends a monitoring report and calls the result verified? Follow the evidence for the particular project and period. A developer prepares the project records; an independent validation/verification body, or VVB, evaluates the relevant submission; the programme makes its own decisions; and registry records establish whether units have actually been issued. Earlier design and monitoring documents cannot establish an issued credit on their own.

The distinction matters when a report, invoice and sales summary describe different quantities. A buyer cannot resolve that conflict by selecting the most favourable number. The practical task is to match the project, governing method, monitoring dates and stated quantity, then identify the decision still outstanding. The fictional case below follows one vintage through a document crosswalk and a discrepancy escalation. It illustrates documentary reasoning rather than certifying a project or providing a replacement for programme rules.

First identify the crediting programme and methodology

Start with the programme name, project identity, applicable methodology and its version. Keep these fields attached to the precise monitoring period or vintage being examined. A familiar verifier name is insufficient: an opinion about another project, method version or period does not answer the same question. The first useful output is therefore a defined file boundary, not a general badge of credibility.

Verra's VCS project-development page describes methodology selection, a project description, independent validation, monitoring and independent verification, followed by programme decisions. It says the proponent can request issuance after Verra approves the verification request. That is a VCS process description. Climate Action Reserve describes its own verification activities and documents; those pages do not make Reserve forms requirements for VCS projects.

For an actual transaction, identify which rulebook and methodology version apply to the project and request. These overview pages do not establish every transition rule, sector-specific requirement or version that governs an individual vintage. Where the file lacks that information, retain the gap and ask the project proponent for the applicable document reference. A buyer's assessment should state what it has established rather than silently treating the latest document on a website as the controlling version for an older period.

Who does what: developer, VVB, programme and registry

Responsibility follows the decision being made. The developer produces project data and explanations. The independent body evaluates the relevant design or monitored performance. The programme reviews the submission under its process, while the registry records the resulting unit status. Saying that the verifier issued the credits collapses those separate responsibilities and can hide an unfinished approval step.

ActorDocumentary contributionDistinct limit
Project developer or proponentProject description, monitoring data and calculationsIts own report is not an independent opinion
Approved VVB or verification bodyAssessment report and applicable statementIts conclusion is not programme issuance
Crediting programmeReview and approval decision under its processApproval should not be assumed from a seller's summary
RegistryRecord of issued units and recorded statusA record must match the units and period being discussed

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

Row 1

Actor
Project developer or proponent
Documentary contribution
Project description, monitoring data and calculations
Distinct limit
Its own report is not an independent opinion

Row 2

Actor
Approved VVB or verification body
Documentary contribution
Assessment report and applicable statement
Distinct limit
Its conclusion is not programme issuance

Row 3

Actor
Crediting programme
Documentary contribution
Review and approval decision under its process
Distinct limit
Approval should not be assumed from a seller's summary

Row 4

Actor
Registry
Documentary contribution
Record of issued units and recorded status
Distinct limit
A record must match the units and period being discussed

Follow who produces, audits, approves and records the project evidence.
Follow who produces, audits, approves and records the project evidence.
Diagram text description

The project developer produces the design and monitored result. The VVB independently assesses the relevant design or period. The programme makes its own decision. The registry records issued units when the applicable programme process is complete.

Use that map when requesting clarification. Ask the developer to explain the calculation or document revision it produced; ask the verification body about the scope of its own statement through an appropriate authorised channel. A programme or registry question belongs with the institution that owns the decision or record. A seller can help obtain those answers, but a seller's rewritten spreadsheet does not replace the underlying document. This division also makes it possible to keep a case open without accusing every participant of making the same error.

Validation checks the project design before credits exist

Validation concerns the proposed design and its conformity with the applicable programme requirements. The design file identifies the project boundary, baseline approach, additionality reasoning and monitoring plan that the applicable method requires. Those are questions about what the project proposes to do and how performance will be demonstrated. They are different from evidence that a later period has achieved a stated reduction or removal.

Under the VCS lifecycle described by Verra, the proponent selects an applicable methodology, prepares the project description, and has the project validated by an approved VVB. The page then distinguishes the registration request from later monitoring and verification. A positive design assessment should therefore remain attached to its design version and scope. It cannot be relabelled as a verification of a future annual quantity.

For documentary review, capture the design title, version, assessment date and named project, together with any scope limitation visible in the report. If the monitoring report uses a different boundary or method version, ask how that change was addressed under the programme's process. Do not infer the answer from similar project titles. This check gives the later performance evidence a defined starting point without pretending that validation eliminates all subsequent uncertainty.

Monitoring creates a period-specific evidence record

Monitoring turns the project's implementation into a period-specific account. Verra describes the proponent measuring reductions or removals for a defined monitoring period, completing a monitoring report, and arranging verification by an approved VVB. The monitoring report is the proponent's submission for examination; it is not already the independent conclusion.

Use the applicable programme and method version to tie design and monitored activity together.
Use the applicable programme and method version to tie design and monitored activity together.
Diagram text description

The design is tested for boundary, baseline, additionality and monitoring plan. The period-specific file joins dates, activity data and the calculated report to the exact project and method version. Keep the applicable programme and vintage with both records.

  1. Identify the exact opening and closing dates, the project identifier and the governing methodology reference. Record whether the label “vintage” corresponds to the full dates in the documents rather than assuming that a year in a filename proves coverage.
  2. Connect the period to the underlying activity records and calculation version. Preserve quantities, units, data owners and any stated estimation or missing-data treatment. A copied total without those connections cannot explain a later revision.
  3. Keep changes visible. If the proponent replaces a report or calculation, retain the earlier version and the reason for the change so the verification statement can be matched to the submission it actually covers.
  4. Send the relevant version through the programme's verification process and distinguish the submitted quantity from the quantity in the resulting independent statement.

These are practical file controls, not additional universal programme requirements. A period can contain incomplete records or a calculation correction even where the project design was validated earlier. The consequence is specific: the buyer needs evidence explaining which period and quantity were examined. Neither an attractive project photograph nor the previous year's positive opinion fills a missing year in that chain.

Verification tests the monitoring report and project performance

Verification examines the reported performance and its supporting evidence. Climate Action Reserve's overview describes conflict-of-interest evaluation, planning, desk work and a site visit, assessment of material misstatement risk, review of methods and management systems, and examination of reduction calculations. Its process ends with submission of a verification report, findings and statement to the Reserve. That description belongs to the Reserve; it should not be presented as a universal list of VCS forms or visit requirements.

The Reserve's document page gives the records different functions. The public verification report summarises the assessment and its risk basis. The public verification statement confirms the reported result and verification standard. The List of Findings is private and shared with the developer and Reserve. An outside buyer should not claim to have inspected that private list merely because the public report mentions findings.

For example, a public statement may identify a narrower period than the seller's monitoring summary. That warrants a scope question, not an assumption that the missing months passed the same assessment. Obtain the appropriate public explanation or an authorised clarification of the statement. Where access is limited, state that limitation. A document request should seek the evidence needed for the decision; it should not imply entitlement to confidential findings or invent their contents.

What a verification statement does and does not say

A verification statement is meaningful because it has a defined subject. Read the named project, period, standard, quantity and qualifications together. Its conclusion applies within that scope. Extending it to future performance, a different vintage or every assertion in a marketing brochure changes the claim without changing the underlying evidence.

A period-specific verification statement does not automatically establish issuance, future performance or a buyer claim. Verra's lifecycle makes the next programme step visible: after the VVB concludes verification, the proponent may submit for verification approval, and approval precedes an issuance request. The existence of an independent report cannot substitute for those subsequent decisions.

Read the verification statement within the project and dates it names.
Read the verification statement within the project and dates it names.
Diagram text description

The VVB checks conflicts, plans desk or site work, documents findings and issues a scoped statement. The named project, period and quantity are inside that conclusion. Issuance, future performance and the buyer claim need their own evidence.

The same discipline applies to uncertainty. A statement about assessed historical reductions is not a blanket guarantee of future delivery, permanence, commercial value or suitability for a particular buyer's public wording. Those questions may require other evidence and rules. Conversely, the absence of a document in the buyer's folder does not prove that the project failed verification; it means that the buyer has not established the fact from the material available. The useful output is a bounded conclusion, such as “this statement covers this period and quantity; issuance evidence remains outstanding”, with the open question assigned to its owner.

When are units actually issued and visible in a registry?

Treat programme approval, issuance, transfer and retirement as different documentary statuses. In the VCS lifecycle, Verra approval of the verification request allows the proponent to submit an issuance request for VCUs in the Verra Registry. A pending request is not evidence that the requested number has been issued. Equally, the presence of issued units would not, by itself, identify a buyer's retirement or support that buyer's proposed claim.

Match any registry evidence to the project, period, quantity and status being reviewed. Retain the observation date, because a screenshot or exported record describes what was observed at that time. If the seller says the status has changed, obtain the corresponding current record rather than altering the old screenshot. Keep any private account information within the owner's authorised access.

The primary lifecycle page examined here describes the route through issuance but does not set out a detailed retirement procedure. Accordingly, the worked case does not invent retirement fields, serial numbers or a completed retirement. For a real buyer, the missing question is whether there is appropriate programme-specific evidence of the relevant unit action and its association with the intended use. A verification statement, an approval message and an invoice answer different questions. The diagram separates those gates so an earlier document cannot quietly stand in for the next one.

Programme approval, registry issuance, transfer and retirement require separate records.
Programme approval, registry issuance, transfer and retirement require separate records.
Diagram text description

The VVB statement is specific to an assessed period. Programme approval is a separate decision. Issuance creates the registry units. A transfer records a holder change where applicable. Retirement is a distinct action with its own registry evidence. The stage guide covers the route through issuance.

A document checklist for one credit vintage

Illustrative fictional case: Alder Marsh Learning Project, labelled vintage 2025, uses a fictional Method A version 1 solely to demonstrate document matching. It is not an actual registered project or a claim that this method is approved by Verra or the Reserve. The example follows the VCS stage distinction described above; Reserve forms and confidential findings are not imported into it.

The file contains a project description and design assessment, a monitoring report, an independent verification statement and a registry-status extract. Fictional identifiers below are local teaching labels, not registry identifiers or credit serials. The monitoring report claims a full calendar year, while the statement covers only nine months. That difference changes what can be inferred about the seller's requested quantity.

Fictional recordPeriod or scopeQuantity and status
PD-A1 and design assessment VA-A1Method A version 1; project designDesign evaluated; no achieved annual quantity
Monitoring report MR-A21 January 2025 to 31 December 202512,400 tonnes CO2e reported by proponent
Verification statement VS-A11 January 2025 to 30 September 20259,100 tonnes CO2e within stated verification scope
Registry-status extract RG-A1Viewed 4 November 2026; same fictional projectVerification approval pending; no issued-unit evidence supplied

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

Row 1

Fictional record
PD-A1 and design assessment VA-A1
Period or scope
Method A version 1; project design
Quantity and status
Design evaluated; no achieved annual quantity

Row 2

Fictional record
Monitoring report MR-A2
Period or scope
1 January 2025 to 31 December 2025
Quantity and status
12,400 tonnes CO2e reported by proponent

Row 3

Fictional record
Verification statement VS-A1
Period or scope
1 January 2025 to 30 September 2025
Quantity and status
9,100 tonnes CO2e within stated verification scope

Row 4

Fictional record
Registry-status extract RG-A1
Period or scope
Viewed 4 November 2026; same fictional project
Quantity and status
Verification approval pending; no issued-unit evidence supplied

The numerical gap is 3,300 tonnes CO2e: 12,400 minus 9,100. It cannot automatically be described as rejected emissions, additional verified reductions or an available balance of credits. The records cover different periods, and the file gives no independent explanation for the final three months. The discrepancy is therefore unresolved; the buyer cannot treat the full 12,400 tonnes CO2e as verified, issued or available for its claim.

The Alder Marsh report covers twelve months and its verification statement covers nine.
The Alder Marsh report covers twelve months and its verification statement covers nine.
Diagram text description

The fictional file contains the project description, design assessment, monitoring report MR-A2, verification statement VS-A1 and registry-status extract. MR-A2 reports 12,400 tonnes for January to December 2025. VS-A1 covers 9,100 tonnes for January to September. Ask the proponent for the period reconciliation, the VVB about scope, and the programme and registry for the distinct status records. Approval is pending and issued units are unconfirmed.

The proponent must supply the period reconciliation and identify the report version submitted for assessment. The VVB is responsible for clarifying the scope of VS-A1 or issuing an appropriate revised assessment through the proper process if one is warranted. Programme approval and registry evidence still require their own records. No retirement evidence is present. Keeping all five document types together makes those gaps visible; merely counting the documents would miss the incompatible dates and the pending status.

A practical decision path when the evidence does not match

Continue the illustrative fictional Alder Marsh Learning Project case, vintage 2025: MR-A2 reports 12,400 tonnes CO2e for the full year, VS-A1 covers 9,100 tonnes CO2e through September, and RG-A1 shows approval pending. Method A version 1 and every record label are fictional. The discrepancy remains unresolved, so the buyer holds the proposed claim and does not allocate 12,400 units to a retirement schedule.

  1. Open a discrepancy record containing both document versions, their exact periods and the 3,300 tonnes CO2e difference. Describe the issue as a period-and-quantity mismatch, without guessing whether it arose from an omitted quarter, a revision or an error.
  2. Ask the proponent to reconcile MR-A2 with VS-A1, identify what was actually submitted and provide the relevant supporting or corrected monitoring record. The proponent owns its reported data; a sales team's assurance is not a documentary resolution.
  3. Request clarification of VS-A1 from the VVB through the authorised channel. If additional assessment or correction is needed, the responsible body must address it under the applicable programme process. The buyer cannot extend the statement's end date itself.
  4. Obtain the programme's applicable decision and the corresponding registry evidence after the verification issue is resolved. For the VCS sequence, verification approval and the subsequent issuance request are separate from the VVB's conclusion. A corrected report alone does not establish issued units.
  5. Assess the intended buyer action only against the resulting unit record and appropriate evidence of any retirement. Until that evidence exists, neither a completed purchase nor a verification label is enough to close the claim file.

The open decision is whether the final quarter was assessed and what quantity, if any, the programme subsequently approves and the registry issues. Its consequence remains a hold on the full-year quantity and buyer claim. If the answer establishes only the nine-month scope, retain that narrower conclusion and reassess the proposed transaction. Do not delete the original mismatch: the resolution should explain it, identify the responsible record and preserve the distinction between verified performance, programme approval, issuance and retirement.

Preserve a traceable record and resolve the open decision

An evidence register helps a team see why a case is open and what would close it. Give each project-period file one owner, preserve the original documents, and distinguish a seller's explanation from an independent statement or programme decision. Record the exact document version behind each conclusion. This makes a later correction understandable without rewriting the history of the review.

For the fictional case, the next useful action is specific: obtain the proponent's reconciliation of the full-year monitoring report and nine-month verification statement, then establish the applicable programme and registry outcome. The evidence currently supports neither the full-year verified quantity nor an assertion of issuance or retirement. A pending status should stay pending until its responsible record changes.

This approach also sets a boundary for any record-management tool or adviser. Organising identifiers and questions does not confer the authority to verify project performance, approve a programme request or change a registry status. Choose the next action by the missing evidence and its owner. The final test is whether the proposed conclusion can be traced to the matching project, method, period and status, with unresolved limitations still visible.