top of page

Waste stream and vendor evidence register

Writer: Anil Khatwani
Anil Khatwani
Oct 15
5 min read

Record the waste stream, the vendor’s actual role and the receiving facility before deciding what a document supports. A company name can connect several sites and services. It does not make every attachment applicable to every consignment, date or downstream operation.

The eight-page pack provides instructions, four reusable blank sheets and three fictional worked pages. Use the editable DOCX for maintained records or the matching PDF for printing. These are manual forms without formulas, automatic checks, scoring or notifications. They organise evidence and decisions; they do not authenticate records or assess a vendor’s legal status.

Download the editable waste stream and vendor evidence register (DOCX).

Download the print waste stream and vendor evidence register (PDF).

Start with the stream and the question

Give each stream a stable ID tied to its generating site and process. Record its description and the source version supporting it. Link the responsible specialist’s classification decision, applicable basis, scope and date. Keep an unresolved classification visible. An everyday material name is not a substitute for that decision, and a collector change need not create a new stream.

Define the selected period and intended use. The same file may be adequate for confirming receipt but inadequate for a recycling statement. Write that question before requesting more documents. Retain quantity references, original values, units and measurement bases where needed, while keeping any numerical reconciliation in its own controlled schedule.

Give each vendor role its own evidence card

Record the vendor’s business identity and the particular facility or service point. Identify whether the record concerns collection, transport, receipt or a specified downstream operation. If one organisation performs several roles, preserve the separate evidence links. Where subcontractors or later receivers are involved, add their identities rather than extending the first contractor’s name along the route.

On the evidence card, transcribe the document’s stated site, stream, activity and dates with a precise locator. Distinguish issue date, service dates and any stated validity dates. Record exclusions explicitly. A schedule describing available services and a record describing an event that occurred answer different questions.

Keep the required authorisation or permission review separate. Link the relevant specialist’s decision and supporting records where supplied; otherwise record that assessment as outstanding or outside the defined review. A match between a document and a consignment is a documentary finding. It does not establish lawful handling, treatment suitability or a complete compliance assessment.

GRI 306-2(b)/(c) addresses processes for checking third-party handling of own-activity waste against contractual or legislative obligations, and processes for waste-data collection. Its guidance recognises different handling roles. These are narrow reporting context; this register is independently designed.

Connect each consignment to the event it records

Use one consignment ID across the dispatch reference, collector record, receiving record and any later operation record. Preserve event dates separately from document issue dates. Keep the intended destination and the receiving facility actually named by the evidence in distinct fields. Ask for clarification if they differ; do not silently replace one with the other.

The consignment sheet records which vendor card was examined and the outcome of that comparison. Use plain results such as “site and service dates match the stated scope” or “no supplied schedule covers this date”. Record the downstream evidence question separately. Do not turn a collection receipt into a treatment record or describe missing evidence as a measured zero.

Replay two facilities and three consignments

All organisations, people, records and dates in this case are invented. The review covers three consignments of stream S7, paperboard trimmings from Rowan Packing’s line P2. Fictional specialist decision CL7 assigns an internal non-hazardous reporting category to the exact description in SR7 v1. That stipulated decision must not be applied to real paperboard or changed process conditions.

Harbour Collection is identified as the collector. Meridian Materials is the receiver, with East facility E1 and West facility W1. Meridian’s commercial schedule A-E v1 names E1, S7 and receiving plus pulping services for 1–30 June 2026. A-W v1 names W1, S7 and receiving services only for 1–31 July. These schedules are not permits and do not report completed operations.

The retained event extracts identify C11 as dispatched and received at E1 on 20 June. C12 is dispatched and received at W1 on 28 June. C13 is dispatched and received at W1 on 4 July. The collection list links Harbour to all three consignments. No quantities are supplied because this exercise tests record applicability, not waste totals or recovery rates.

For C11, A-E matches the stated facility, stream, receiving role and date. Receiver record OP11 separately reports pulping for C11 at E1 on 22 June. Reviewer Kavya can record those documentary relationships, attributed to the supplied sources. This desk exercise has not independently observed the operation or assessed its performance.

For C12, the E1 schedule cannot cover the W1 receipt merely because Meridian issued both. The W1 schedule starts on 1 July, after C12’s 28 June event. Neither supplied schedule supports the requested service-scope match. Keep the receipt itself recorded: the missing applicable schedule does not erase the documented receipt or establish an unlawful event.

For C13, A-W matches the stated W1 receiving service and 4 July date. No downstream operation record is supplied for C12 or C13. OP11 names C11 and E1 only, so it cannot be extended to either West consignment. C13 therefore has a supported receiving-scope match and an unresolved downstream question at the same time.

Fictional Meridian Materials record review. C11 at East E1 on 20 June matches A-E and has receiver-reported operation OP11. C12 at West W1 on 28 June has no matching supplied service schedule. C13 at West W1 on 4 July matches A-W receiving scope. Both West downstream operation questions remain unresolved.
Original fictional case. All three receiving records remain linked. A-E and A-W are commercial service schedules, not permits or completed-operation records. OP11 reports C11 pulping at E1 only. The exercise makes no quantity, performance or permission assessment.

Record a bounded disposition and its next check

At the 8 July 2026 cut-off, Kavya records separate decisions for service-scope matching, receiving evidence and downstream evidence. Authorisation assessment is not performed in this exercise for any consignment. No whole-vendor pass or fail follows from these rows. The classification reference remains linked to S7 rather than copied into a claim that all vendor activities are approved.

Follow-up F1 asks the procurement custodian for existing W1 service-scope evidence covering 28 June. F2 asks the vendor-record custodian for any downstream records specifically linked to C12 and C13. Both have a proposed review date of 15 July in the fictional case. The register records these requests for the approved workflow; it does not send them or confer permission to share files.

If another record arrives, append a dated review event with its source version and exact effect. A retrospective explanation should retain its actual issue date. It might resolve a particular site or period question without establishing an operation. Preserve the previous conclusion and identify dependent summaries that need review instead of replacing every status with “complete”.

Test the worked copy by removing OP11. C11’s receiving-scope match remains, but its operation evidence becomes unavailable. Remove A-W instead: the C13 receipt remains, while its schedule match becomes unresolved. Changing the vendor’s display name should not repair either gap. These manual tests show which record supports each conclusion.

Use the register alongside the existing guides

The waste-register guide explains stream identity, classification and destination. The vendor-record reconciliation guide deals with duplicate entries and weight differences. This download supplies the reusable cards and linked decisions for those preparations, with a different worked example and no quantity arithmetic.

Use the source document and approval register for controlled versions and access. Keep confidential records in authorised storage and share only approved extracts. Remove the fictional pages before live use. This optional aid provides no waste-handling instructions, legal opinion, certification or independent assurance.

Source checked 15 October 2026: Global Reporting Initiative, GRI 306: Waste 2020, Disclosure 306-2(b)/(c) and related guidance. No source organisation endorses these original forms or fictional example.

 
 
 

Comments


bottom of page