Find your verification pathway.
The route from production data to an independent opinion, stage by stage. Ten stages before a verifier sees anything, then a review that runs inside the platform against a model that can no longer move.
Verification usually starts too late.
It begins after the numbers are already assembled — in spreadsheets that moved between people, from sources nobody can re-trace. The verifier’s first job becomes reconstructing how you got there, and the cost of that is measured in rounds, not hours.
traditional process
to verification
the ten stages below
From raw data to a verifiable footprint.
Every verification follows the same lifecycle. These are the ten stages and the data each one asks for — the work that has to exist before a verifier can form an opinion.
-
Stage 1: Project Governance & Study Setup
Define project scope, assign team roles, select your target standard, and configure the study parameters that will govern your entire verification journey.
-
Stage 2: Product Definition & Functional Unit
Specify exactly what you are measuring — the product, its functional unit, reference flow, and the declared unit that verifiers will audit against.
-
Stage 3: System Boundary & Scope
Draw the line around your system — which lifecycle stages, processes, and inputs are included. Document cut-off criteria and any exclusions with justification.
-
Stage 4: Activity Data & Supply Chain
Collect and validate primary data from your facility and suppliers. Score data quality, flag gaps, and document every source for the audit trail.
-
Stage 5: Emission Factors & Background Data
Match each activity to the right emission factor. Select from 40,000+ factors or use supplier-specific data. Document selection rationale for every choice.
-
Stage 6: Allocation & Multifunctionality
Handle co-products, recycling loops, and multi-output processes. Apply allocation rules per your target standard and document every decision.
-
Stage 7: Carbon Footprint Calculation & LCIA
Run the carbon model. Review results by process, lifecycle stage, and hotspot. Compare against benchmarks and validate with sensitivity checks.
-
Stage 8: Interpretation, Sensitivity & Uncertainty
Stress-test your results. Run Monte Carlo simulations, scenario analysis, and contribution analysis to ensure your numbers are defensible.
-
Stage 9: Reporting, Documentation & Disclosure
Generate the complete documentation package — background report, public summary, data quality statement, and standard-specific annexes.
-
Stage 10: Verification, Assurance & Maintenance
Hand off to your verifier with a structured workspace. Track review comments, resolve findings, and maintain your verified footprint over time.
The model is the record.
Your product becomes a connected system in the System Builder: inputs carrying Scope 2 and Scope 3 emissions, process steps, direct emission nodes for Scope 1, and outputs.
Every input needs an emission factor. Match it from the marketplace — Ecoinvent, IPCC, US EPA and EPD International, over 40,000 factors — or use supplier-specific data, and record why you chose it.
Build with AI is the other way in: a description and up to five documents produce a full connected system in 30–60 seconds. Every node it creates arrives Draft, because nobody has reviewed it yet.
- Incomplete — no data yet.
- Draft — has data, nobody has reviewed it.
- Reviewed — a person checked it. Green is your quality gate, not the platform’s.
Where primary data comes from.
Send a Request for Carbon Attestation from Relations. Your supplier builds their own system, issues a Carbon Receipt, and transfers it — it becomes an EAC on your side, and the input’s source switches from a reference factor to their actual number. Dependent values recalculate.
The transfer is irreversible, and sharing is Private, Public or Restricted.
A receipt is not proof of verification. One can be issued at any point in the lifecycle and carries whichever status applies — the default is Self attested. The six statuses are: Not registered, Self attested, Pending verification, Under verification, Revisions requested, and Verified on CarbonSig. A transferred receipt or EAC is not a verified input unless its status says so.
Find the gaps before a verifier does.
The System Status Report reads the whole system and returns a health summary, the gaps and what to do next, in 30–90 seconds. Then Analyze computes the result — Net Emission = Sources − Sinks − Credits — with intensity per unit, a Sankey view for tracing where the mass sits, and a bar chart for comparing processes.
The model is frozen before a verifier sees it.
Registering a finished model creates a locked, read-only copy with its own identifiers. The original stays editable; the registered snapshot cannot move. That is what makes a review mean something — and it is the product’s own reasoning, not ours:
“A verifier cannot issue an opinion on a system whose inputs are still mutable.”
Snapshots lock again at every round boundary, so the version a verifier reviewed is always the version their findings refer to.
A review that leaves a record.
Request verification and the engagement appears in the Verifier Hub — a dedicated verifier account with its own Engagements workspace, and account-level Standards and Requirements libraries.
The verifier works in a read-only environment. They raise a finding pinned to the exact node through its Model → Product → Node path, tick requirements as they go, and send a revision request. Your model unlocks for that round, you reply to each finding, and you resubmit. The round counter advances and the snapshot locks again.
When the review is complete the verifier issues a formal opinion, and the status becomes Verified on CarbonSig.
The record persists. Findings stay visible at every verification status — during the review and after the opinion — so the review history is still readable once the engagement closes.
Comments from earlier rounds stay locked, so the record for a closed round cannot be changed afterwards.
A registered system or engagement can be downloaded as an XLSX file for offline reporting and record keeping — on the Registered page for every status except Revision Requested, and in the Verifier Hub for every status except Pending Acceptance.
Two end states, and they are not the same. Verified means you recorded an off-platform verification yourself. Verified on CarbonSig means an accredited third party issued an opinion inside the platform, against the standard you report to.
The Verifier Hub is designed to align with ISO 14064-3, ISO 14067, the GHG Protocol and CBAM.
CarbonSig is a pre-verification platform. All carbon calculations should be independently verified by an accredited third party.
Start with the product you need verified.
Tell us what you make and your standard. We'll show you the stages that apply, and what your verifier will ask for.