Skip to main content
← All consultations
RULE CHANGE · Tier 5 — Operational policies, procedures, templates, guidanceOPEN FOR COMMENT

Verification Report Template v1.0

New normative template under MCC-100 v2.2 cl. 0154 and MCC-400 v1.1 art. 64

Opened 25 August 2026Closes 8 September 2026 · 14-day notice (floor 14)9 days left

What is being consulted on

The structure and minimum content of the verification report, including the monitoring period, the verified quantification, adjustments with reasons, the recommended issuance volume, the project-specific buffer rate and the SD contribution assessment.

Decision by
Programme administration under FD-2026-08-24 item 3, with Board oversight (MCC-001 cl. 0083)
After closing
Every material comment receives a written response; the closing protocol is published here; the decision cites the proposal by its hash; on adoption the text is published at /transparency/documents with a version bump and this consultation is linked from it.
Proposal SHA-256
a044bf7bbb3572f3b7c2ef79622e24aad2bacf89d1f50c12f5e2678be6e398ed
Source file
MCC_Verification_Report_Template_v1.0_DRAFT.md

Proposal text hash a044bf7b…e6e398ed

MCC Verification Report Template

Document type: Normative template (MCC-100 cl. 0153) Version: 1.0 — DRAFT for adoption Prepared: 25 August 2026, programme administration Adoption route: amendment under FD-2026-08-24 signature authority, or first constituted board meeting. Not adopted until recorded in the decision record and listed on /transparency/documents. Related: MCC-100 v2.2 cl. 0146–0162, 0186 · MCC-400 v1.1 Arts. 49–65, 94–105 · MCC-800 v1.1 · MCC-850 v1.2 · Buffer Pool Management Policy v1.0 · Corresponding Adjustment and Double Counting Prevention Policy v1.0 · Annex B Monitoring Report Template · MCC Validation Report Template v1.0


Purpose and use

A verification report is the VVB's account of what a project actually achieved in a monitoring period, and how many units may be issued for it. It is the first of the seven mandatory prerequisites for issuance (MCC-100 cl. 0162(1)): the Registry will not advance an issuance request unless the verification record carries a POSITIVE typed opinion, the quantum on the record covers the request, and the vintage falls inside the monitoring period. The report is public once the workflow completes (MCC-400 Art. 65).

The verification report contains everything a validation report contains (MCC-400 Art. 64) plus the monitoring period, the verified quantification, every adjustment to the developer's figures with reasons, the recommended issuance volume and the SD contribution assessment.

How to use it. Complete every section in order; keep headings; state "Not applicable" with a reason where relevant. Numbers in this report are the numbers the Registry will issue against — they must match the verification record entered on the platform (quantifiedCredits, bufferPercentage, netCredits, opinionType) exactly.


R.0 Report identification

Field Entry
Report reference / version / date
Validation and verification body · MCC accreditation number · status
Engagement reference in the MCC Registry [verification record id]
Project name · MCC project code · developer
Host country · host-country position on the Registry [use case · authorisation / not applicable · notification status]
Applicable MCC methodology and version · family
Monitoring Report verified [MR version · period · Registry document id · SHA-256]
Validation report relied on [reference · opinion · date]
Monitoring period [start – end]
Vintage(s) [calendar year(s) inside the monitoring period]
Verification number in the crediting period [1st / 2nd / …]; site visit required for the first verification of each crediting period (Art. 53(b))

R.1 Scope statement (cl. 0154(a); cl. 0152)

What was verified, against which documents (Monitoring Report version, PDD as validated, methodology version, programme documents), what was excluded, and whether the Programme Administrator directed a site visit on risk grounds (Art. 53(c)).

R.2 Audit team and independence (cl. 0154(e)–(f); Arts. 45–48, 0150)

Team table as in the Validation Report Template. Reference the COI declaration filed in the Registry for this engagement. Rotation: state which verification cycle this is for this body on this project; rotation is required every three cycles (cl. 0150). Statement of independence in full.

R.3 Methodology and procedures applied (cl. 0154(b); Section 9)

Engagement plan (Art. 50); document review (Art. 51); site visit or approved remote assessment (Arts. 53–55) with what was independently measured or observed; sampling design and achieved sample; data sources traced to origin (telemetry, logs, laboratory results, satellite products, vessel records); interviews.

R.4 Findings by assessment section (cl. 0152, cl. 0154(c))

For each: requirement, evidence examined, assessment, findings (cross-referenced to R.6), conclusion Conforms / Conforms with conditions / Does not conform.

R.4(a) Monitoring data completeness, accuracy and source verification

Coverage of every parameter required by the methodology; gaps and the treatment applied to missing data (methodology rule cited); calibration and maintenance evidence; independent confirmation of a sample of values.

R.4(b) Quantification calculations and conservative application

Recalculation by the VVB of baseline, project and net figures; conservativeness of every assumption; uncertainty treatment.

R.4(c) Leakage deductions

R.4(d) Permanence status and reversal assessment

Reversal events in the period (Registry reversal records), buffer draws, monitoring of reversal-risk indicators over the applicable horizon. For flow-based families (F03, F04): "Not applicable — flow-based crediting", with the justification.

R.4(e) Environmental and social safeguards implementation

Incidents, grievances (Registry grievance records — any RECEIVED/ACKNOWLEDGED/UNDER_INVESTIGATION/ESCALATED grievance blocks issuance, cl. 0162(6)), corrective actions.

R.4(f) Sustainable development indicator tracking and scoring

Against the SD Contribution Framework v1.0; the indicators reported, evidence, and the VVB's score.

R.4(g) Corresponding adjustment status

The position recorded on the Registry (D8): for contribution-basis units, confirm no corresponding adjustment is claimed and the host-country authority has been notified; for CA/compliance use, the LoA and its expiry.

R.4(h) Buffer pool contribution calculation

The canonical family rate (F01 20 %, F02 25 %, F03 15 %, F04 10 % per FD-2026-08-24 D6, F05 30 %), applied ex-ante, rounded up; reconciled to the Registry's buffer ledger.

R.5 Verified quantification (Art. 64(b)–(d); Arts. 59–60)

Item Developer's figure VVB adjustment Reason (clause) Verified figure
Baseline
Project
Leakage
Gross verified reductions / removals / conservation units
Buffer contribution (rate · units)
Net units recommended for issuance

State the unit basis explicitly (tCO₂e for F01/F02/F05; for F04 under MCC-M008, 1 MCU = 100 kg verified recovered gear). Show the step-by-step recalculation in Annex 2. The verified gross figure is what goes on the Registry as quantifiedCredits; the rate as bufferPercentage; the net figure as netCredits.

R.6 Findings register (Arts. 56–58)

As in the Validation Report Template. No positive opinion with an open Major non-conformity; Minor non-conformities from the previous engagement must be closed (Art. 58).

R.7 AI-assisted analysis record (Arts. 94–105; MCC-850)

As in the Validation Report Template, including satellite or model outputs used by the AI Analysis Layer, their confidence values (0–100), and every point of concurrence or difference.

R.8 SD contribution assessment (Art. 64(e))

The scored assessment against the SD Contribution Framework v1.0 for the period, with evidence.

R.9 Verification opinion and statement (cl. 0154(d); Art. 63(f); cl. 0162(1))

Select one and state it in full; the typed opinion entered on the Registry must be identical.

POSITIVE. [Body] has verified the Monitoring Report [version] of project [name, code] for the period [start–end] against MCC-100 v2.2, [methodology] and the documents in R.1, and states that the net quantity of [N] [units] is verified for issuance, after a buffer contribution of [B] units at [rate] %.

POSITIVE WITH CONDITIONS. …is verified for issuance subject to: [conditions]. Note: the Registry issues only against a POSITIVE opinion; conditions that must precede issuance mean the opinion is not yet positive.

NEGATIVE. …cannot be verified for issuance, for the reasons in R.4 and R.6.

R.10 Recommended issuance (Art. 64(d))

Vintage Gross verified Buffer units Net for issuance Serial basis
[family · credit type · country · vintage; demo flag must be false]

R.11 Peer review statement (Arts. 61–62)

As in the Validation Report Template.

R.12 Signature and accreditation (cl. 0154(e))

Lead auditor; authorised signatory; accreditation number; Registry filing (document id, SHA-256, in-platform attestation, date).

Annexes

  • Annex 1 — Documents examined (title, version, Registry id, SHA-256)
  • Annex 2 — Recalculation workings, parameter by parameter
  • Annex 3 — Site-visit or remote-assessment record
  • Annex 4 — Sampling record
  • Annex 5 — Findings correspondence (exported from the Registry)
  • Annex 6 — COI declaration reference and screening result

Change log. v1.0 DRAFT (2026-08-25): first template. Drafted from MCC-100 v2.2 cl. 0146–0162 and 0186, MCC-400 v1.1 Arts. 49–65 and 94–105; unit basis and buffer rates per FD-2026-08-24 D6; host-country position per D8; figures aligned to the Registry's verification record fields.

Public comments 0 received · 0 answered

No comments have been submitted yet.

Submit a comment

Your name, organisation and comment are published. Your email address is not published; the programme uses it only to respond to you about this comment.