Pre-validation evidence readiness

Find the evidence gaps before your validator does.

We review your PDD against the applicable methodology and show you what is supported, what is unclear, and what still needs action before validation starts.

Independent review designed to complement your existing project team and consultants.

Article6 Carbon

Evidence readiness assessment

Illustrative
RequirementBaseline justification
PDD reference§ 3.2.1
EvidenceCalculation workbook + annex
AssessmentNeeds clarification
ActionReconcile assumption and cite source
Every finding is tied back to a requirement and the evidence used to assess it.

The hidden risk

A finished PDD can still contain evidence gaps.

A requirement may be addressed in the document while the evidence behind it is incomplete, difficult to trace, or inconsistent with the supporting files.

01

Claim without a clear source

The PDD makes a material claim, but the supporting evidence is not identified clearly enough for a reviewer to trace it.

02

Evidence that is hard to find

The support exists somewhere in annexes, calculations, maps, or supporting documents, but a reviewer has to hunt for it.

03

Requirement without enough support

The methodology requirement is discussed, but the justification or supporting evidence is incomplete.

04

Documents that do not reconcile

The PDD and its calculations, maps, annexes, or supporting files do not tell exactly the same story.

These are the gaps that become clarification requests, rework, and additional review cycles during validation.

What we do

We find those gaps before validation does.

Article6 independently reviews the PDD and supporting documentation to identify where evidence is strong, where it is unclear, and where something still needs to be resolved.

You get a practical list of issues your team can work through before they become questions from an external reviewer.

Find it earlier. Fix it on your schedule. Enter validation better prepared.

How we do it

We map each methodology requirement to the evidence behind it.

For every applicable requirement, we create a traceable path through the project documentation.

01

Methodology requirement

02

PDD reference

03

Supporting evidence

04

Assessment

05

Risk

06

Required action

Illustrative review record

Evidence map

Sample data

Review path

  1. 01PDD uploadedProject documentation received
  2. 02Methodology requirements checkedApplicable criteria reviewed
  3. 03Evidence mappedSources traced to requirements
  4. 04Risks identifiedGaps rated by review priority
  5. 05Actions recommendedResolution guidance prepared

Requirement review

Applicable methodology

Medium risk
Requirement
Baseline scenario justification
Evidence reviewed
PDD Section 3.2; supporting documentation
Assessment
Additional support recommended
Action
Provide stronger supporting evidence before validation.

That makes it possible to see not just that an issue exists, but exactly why it was raised and what evidence would resolve it.

Structured analysis. Human-reviewed conclusions.

What you get

A traceable Evidence Map and a clear readiness assessment.

Every applicable requirement is tied back to the relevant part of the PDD and supporting evidence, so your team can see exactly what supports each conclusion.

Evidence Map

A structured record connecting methodology requirements to the relevant claims, evidence, assessment, risk, and next action.

Priority findings

The issues most likely to create clarification, rework, or delay during validation.

Required actions

Clear guidance on what needs to be added, clarified, reconciled, or documented.

Resolution criteria

A practical description of what “resolved” looks like for each finding.

A record your team can keep using

Turn expert knowledge into project knowledge.

The Evidence Map preserves the reasoning and source trail behind the PDD in a structure other members of the team can follow. If people move on, the project retains a usable record of the work.

✓where key evidence came from
✓why a requirement was considered addressed
✓which supporting documents were relied on
✓what was changed or clarified during review

Not a black-box score. Every finding is traceable.

See the output

Review the evidence before you send us anything.

Project boundary definition

Medium
Evidence reviewed
PDD Section 1.4; project boundary map
Finding
Boundary description is present, but the map does not identify all included facilities.
Recommended action
Reconcile the map and narrative before submission.

Monitoring parameter sources

High
Evidence reviewed
Monitoring plan; equipment specification sheet
Finding
The monitoring plan names the parameter but does not show the source of the measurement factor.
Recommended action
Add the source and explain how the factor will be verified.

Stakeholder consultation record

Low
Evidence reviewed
Consultation minutes; attendance register
Finding
Meeting records are included, though responses to material concerns are not traceable.
Recommended action
Link each material concern to a response or resolution note.

Illustrative findings for demonstration only. Not from a real client project.

How to get started

Start with your PDD.

Upload the current version through our secure form. We will review the project scope, confirm the applicable methodology and version, and let you know if we need any additional documentation before beginning the assessment.

Submitting your PDD is only the first scope-review step. It does not commit you to purchase the service.

Required PDF, up to 150 MB.

Evidence supporting the PDD may be PDF, Word, Excel or PowerPoint. Up to 9 supporting files, 150 MB each. Maximum package size 750 MB.

Your documents are transmitted securely and stored privately.

Article6 provides independent pre-validation evidence readiness assessments designed to complement project developers, consultants, and VVBs. We do not perform validation, make registry decisions, or guarantee acceptance by Verra or any validation and verification body.