Probably here because a verifier has been engaged and someone has to produce the evidence by a date already in the diary.

ISO 14064 · Verification

Being right is not enough. Someone else must get the same number.

ISO 14064-1 tells you how to build a GHG inventory. 14064-3 tells someone else how to test it. Which is why the first is built out of records, not totals.

14064-1 quantifies 14064-3 verifies Reasonable or limited
Prepare us for verification Upgrade our inventory evidence
REZET Hub on desktop, tablet and phone: emissions by scope and the source events, methods and quantities behind each figure
The short version

Two standards that only work together.

People say “ISO 14064” and mean one of two quite different documents. Which one you mean changes who is doing the work.

Part 1 · you build it

Requirements for quantifying, monitoring and reporting greenhouse gas emissions and removals: how to set the organisational boundary, identify sources, quantify them and document what you did.

Part 3 · somebody else tests it

Requirements for verification and validation of GHG statements. The verifier plans, assesses risk, gathers evidence, evaluates it and issues an opinion — at either reasonable or limited assurance.

Why that shapes your data

Because the opinion must rest on sufficient, appropriate and reproducible evidence. Reproducible is the demanding word: another competent person, following your method with your records, has to arrive at the same number.

What evidence gathering looks like in practice

Six questions. A batch-level record answers all six.

  • 01WHAT IS INSIDE THE BOUNDARY
  • 02WHICH SOURCES DID YOU INCLUDE
  • 03HOW WAS THE ACTIVITY DATA OBTAINED
  • 04WHICH FACTOR, FROM WHICH VERSION
  • 05CAN ANOTHER PERSON REPEAT IT
  • 06WHAT CHANGED, AND WAS IT RESTATED

The boundary before the arithmetic

Which entities and facilities, on which consolidation approach. A quantity that is correct for the wrong boundary is a finding, not a rounding.

Completeness, and what you left out

What was excluded and on what grounds is part of the statement. An omission that the verifier finds first is worse than an omission you declared.

Primary data beats an estimate

Measured, metered, invoiced or estimated — for each source. The hierarchy is not cosmetic: it determines how much testing the figure attracts.

Method on the record

The emission factor, its source, its vintage and the reason it was chosen. Factors are updated; a figure without its factor version cannot be reproduced.

Reproducibility, literally

The test is whether someone outside your team can follow the same steps to the same result, using what you recorded rather than what you remember.

Corrections, appended

Recalculations happen. What matters is whether the previous value is still readable with its date, so a movement can be explained.

How to get there

Five steps, so the evidence is gathered before it is asked for.

1

Fix the boundary and write down why

Consolidation approach, entities, facilities, period. This is the document the verifier reads first.

2

Grade every source by data quality

Measured, metered, invoiced, estimated. Knowing which is which is more useful than pretending they are all the same.

3

Capture activity data at the event

A quantity recorded where the material moved has an author, a date and a place. One reconstructed from a summary has none of the three.

4

Attach the factor and its vintage to the figure

So the calculation is reproducible without a conversation, which is exactly what reproducible means.

5

Keep restatements visible

A corrected figure keeps its history. The verifier is not troubled by a change; they are troubled by a change that cannot be explained.

Evidence overview in REZET Hub: sources, quantities, methods and the events behind each figure in the inventory
What you get

An inventory that survives the sample.

Activity data with provenance

Quantity, author, place and date recorded at the movement, so the origin of every input is a fact rather than a recollection.

Method attached to every figure

Unit, factor, source and vintage travel with the number, which is what makes a calculation reproducible by someone else.

A trail the verifier walks alone

Read-only access to the evidence, so verification is a review rather than a series of requests to five different people.

When the verifier picks a month and a source and says, “Show me” — what happens next?

Evidence is cheap to keep while the activity happens and impossible to create afterwards without calling it an estimate. Choose the next step that fits where you are.

Prepare us for verification Upgrade our inventory evidence
FAQs

Where to start?

Find answers to common questions and discover the best way to get started.

What does onboarding require?

Start with one material pathway: its origin, destination, people involved and the evidence it needs to support. We then configure locations, roles and the records required at each handoff.

Do we need to change our existing systems?

Not necessarily. REZET Hub is designed to complement existing operational, ERP, reporting and sustainability systems rather than requiring organisations to replace their existing technology stack.

How long does implementation take?

Timing depends on the first pathway, sites, users and integration requirements. We confirm the implementation plan after scoping rather than promising a generic duration before we understand the operating reality.

How is REZET Hub different from traditional reporting?

REZET Hub does not simply tell you what happened.
It helps you decide what should happen next.
Traditional reporting often relies on information entered after an event has occurred. REZET Hub is designed to capture evidence as materials move and responsibility changes, creating a stronger connection between the physical event and its digital record.
It also goes beyond reporting by acting as a sustainability decision-support tool. By analysing each waste stream, REZET Hub can identify alternative recovery, reuse, upcycling or recycling pathways, helping organisations improve circular outcomes and make more informed progress towards their zero-waste goals.

Which plan is right for a first pathway?

Explore is for one user testing one stream at one site. Operate supports a small team managing recurring batches and standard reports at one site. Scale adds multi-site controls and audit-grade Scope 3 outputs. Integrate is for advanced controls, SSO, API and broader organisational support.

Who is REZET Hub not for?

REZET Hub is not a carbon-credit marketplace, a substitute for the physical operator, or a generic reporting tool that can reconstruct missing evidence after the fact. It works best when there is a real material flow and an internal owner prepared to make the record part of operations.

Can we start small and expand later?

Yes. Start with one live pathway, then add users, sites, materials, reporting outputs or integrations as the programme grows. The right starting point is the smallest plan that can support the job properly.

Can we compare supplier with supplier?

Yes, on the record’s own terms. Handoffs are documented between responsible parties, processing events are linked to the relevant operator, and inputs and outputs are reconciled at batch level, so the same figures read supplier by supplier and site by site. Exports can be taken at any time in a structured format, for tenders, contract reviews and disputes.

What does REZET Hub record?

Batch-level material identification, documented handoffs, processing events, responsible parties and input-output reconciliation. The result is a structured trail ready for review and export.

Can the evidence support audits and reporting?

Yes. The evidence pack can support internal reporting, audits, customer requirements and Digital Product Passports. REZET Hub records the evidence; it does not replace the underlying regulatory obligation.

Does REZET Hub sell carbon offsets or credits?

No. Where environmental outcomes are calculated, they stay linked to the underlying material record, methodology and supporting evidence rather than being presented as an offset.

Who verifies the data?

Each responsible party records the handoff it took part in, and the receiving party measures the material independently on arrival and compares it against the sending party’s quantity, so any discrepancy becomes visible. Where the record and the movement disagree, the difference is surfaced as an exception instead of being smoothed over, and the underlying record is tamper-evident and append-only. Auditors and assurance providers come in as guests, on a read-only view of the trail. REZET Hub describes what the evidence contains, not what it certifies

What happens when a record is corrected?

Corrections are appended, not written over the top: every step becomes an event that is added to the record rather than replacing what was there. An auditor drilling into a claim sees the measurement, the actor, the evidence and the correction history behind it, which is why the record is never rewritten for the reader.

Are units and classifications standardised at capture?

Capture begins from a material profile selected at source, with description, quantity and photographic evidence recorded against it; the receiving party then measures the material independently and reconciles the mass. The units and classifications your programme uses are agreed at onboarding, when we configure locations, roles and the records required at each handoff.

Who owns an exception?

REZET Hub surfaces the exception and shows which party recorded which movement; it does not appoint the person inside your organisation who resolves it. REZET Hub works best when there is a real material flow and an internal owner prepared to make the record part of operations.

What does a contractor have to do?

A contractor contributes evidence only where responsibility changes. Working from a scoped link, it sees the one job assigned to it and the quantity handed over, records the outputs, photographs or weighs them and submits. There is no shared login and no second reporting workflow: each party sees only the movements it took part in.

What does this add to our own site team’s day?

At the point of movement, the person handling the material selects the material profile, captures the description and quantity, and captures photographic evidence against it. There is no second reporting workflow: REZET Hub is designed to complement existing operational, ERP, reporting and sustainability systems rather than replace them.

What happens when a handoff is missing?

Evidence is created at material handoffs and processing events rather than reconstructed afterwards, so a handoff that was never recorded stays visible as a gap in the batch trail. Where the record and the movement disagree, the difference is surfaced as an exception.REZET Hub is not a generic reporting tool that can reconstruct missing evidence after the fact: it shows the gap, it does not fill it.

Where did REZET Hub begin?

REZET Hub began inside REZET Global’s circular programmes. Real materials were being recovered and transformed, while evidence sat across spreadsheets, emails, photographs and certificates. REZET Hub was built to keep the digital record in step with the physical work.

Is REZET Hub only for companies working with REZET Global?

No. REZET Hub and REZET Global are separate businesses. REZET Hub can be used independently by organisations and circular operators. REZET Global provides one real-world operating environment in which REZET Hub’s evidence capabilities can be applied.

What languages is REZET Hub available in?

REZET Hub is available in English and Spanish, with Portuguese and German coming soon.

How does this work across different jurisdictions or states?

REZET Hub records the evidence; it does not replace the underlying regulatory obligation, and this page does not set out the rules of any single jurisdiction. Sites are managed as locations within one programme, and framework mapping detail is available on request — we describe what the evidence contains, not what it certifies. Which requirements apply at each site is scoped before implementation.