The document is filed against the batch
Not in a folder named after a month or a contractor. You open the batch and its papers are there, because that is where they were attached when they arrived.
You are probably here because someone asked for one certificate and you are opening four folders to find it.
When someone asks for the document, you open the batch. Not a shared drive where the file might be, under a name someone chose in a hurry.
Not in a folder named after a month or a contractor. You open the batch and its papers are there, because that is where they were attached when they arrived.
Who produced the document and when it was issued stay on the record, so a certificate can be read without asking anyone what it refers to.
When a document is reissued, the previous one stays readable with its date. You can see what was current at the time a claim was made.
A weighbridge ticket belongs to a handoff, a processing certificate to a treatment step. A document with nothing behind it is a document that proves nothing.
An event that should carry a document and does not shows as a gap on the batch, while there is still time to chase it.
The batch and its documents export together, in the order they happened, for an auditor, a customer or a tender.
Which document a handoff, a treatment or an outcome has to bring with it.
The party that produces the document uploads it against the event it supports.
A reissue is appended with its date. Nothing disappears when something is corrected.
Events without their document are listed while the material is still moving.
Batch, events and documents in one structured handover, assembled from what exists.

Documents are retrieved by batch, site or period, so finding one does not depend on remembering how it was named.
Corrections are appended. An auditor can see what the record said on the day the claim was made.
A missing certificate is a known gap during the operation, not a discovery during the audit.
When the request lands, “Can you send the certificate?” — how long does it take?
A document is cheap to attach when it arrives and expensive to find a year later. Choose the next step that fits where you are.
Find answers to common questions and discover the best way to get started.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
REZET Hub is available in English and Spanish, with Portuguese and German coming soon.
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.