Digital Waste Tracking: Spreadsheet or Connected Software?

For a receiving-site team, the reporting route is only one part of the job. Someone still needs to establish what arrived, review missing information and follow the reporting outcome.

The government provides a prescribed spreadsheet as well as an API route through compatible software. This guide explains how to compare them against your everyday work, rather than assuming every operator needs the same system.

What does the government spreadsheet route involve?

The official Report receipt of waste guidance explains the current process. Use the supplied template, complete its required fields and upload it. The format must be kept as provided. You can prepare multiple receipts before submitting a workbook, then start a new workbook for the next submission.

A spreadsheet can be a practical reporting route. Agree where the source information comes from, who checks the workbook, who submits it and how the team records the result. An uploaded file should not be confused with a confirmed accepted receipt.

What changes when software is connected?

With an API-connected product, the reporting process sits within a software workflow. The useful comparison is how the team captures, reviews and follows records, including those that need attention.

PaperRoute connects Yard observations, receipt review and the configured reporting connection with the wider customer, collection, driver, document and invoicing work. We check eligible site setup and supported scenarios before live reporting. See the PaperRoute Digital Waste Tracking workflow.

Being connected is not a guarantee that every record is correct or accepted. The information entered and the outcome returned still matter.

Compare the work around each receipt

| Question | With a spreadsheet process | With a connected workflow | |---|---|---| | Where does the load information begin? | Identify the records staff use to complete the workbook. | Check which operational records supply the receipt and what staff still enter. | | Who reviews discrepancies? | Agree the reviewer and how changes reach the submitted workbook. | Demonstrate how the Yard and office review the observed load. | | How do you follow reporting outcomes? | Keep submission results connected to the source records. | Review receipt status and the process for records needing attention. | | What happens during absence? | Make the file, instructions and reporting responsibility accessible to cover staff. | Confirm user access, review ownership and the handover in the system. | | Does the business need wider software? | A reporting workbook does not by itself manage routes, drivers or invoicing. | Check whether the wider platform fits those actual operational needs. |

These are process-review questions, not claims about automatic features in every product.

Three examples worth walking through

A straightforward incoming load

Start with the arriving vehicle and the information supplied. Follow the record through review, submission and the reporting result. Ask who will notice if required information has not arrived with the load.

A load that differs from the booking

The expected materials or quantity may differ from what the Yard observes. Identify which record needs review, how the office confirms the facts and how the final receipt reflects the actual arrival.

A record that needs attention

Use a safe demonstration or approved test environment to review a validation problem. Check how staff find the affected record, resolve the information and confirm the subsequent result. Follow the relevant regulator’s current requirements for reporting and corrections.

Can a business use both routes?

The government guidance allows API and spreadsheet reporting to be used together. Agree when each route will be used and how staff will avoid submitting the same receipt twice. Keep the responsibility for checking the final outcome clear.

If your operation has several legal entities or receiving sites, review registration and organisation details before setup. The names people use internally may not identify the organisation that holds a particular authorisation.

Which option is right for your site?

Review the number and variety of receipts, the people involved, existing systems, the handover from Yard to office and whether the business needs a wider operations platform. Consider actual work and support needs rather than a guessed time saving or a claim that software alone establishes compliance.

A demo can establish whether PaperRoute is a useful fit. Current pricing, setup and agreement details are on the pricing page.

What about the January rollout?

For Scotland, read our Scottish receiving-site preparation page alongside SEPA’s guidance. For Northern Ireland, use the Northern Ireland preparation page and the current DAERA and Assembly updates.

Existing Waste Transfer Notes and other required documents are separate from receipt reporting. The later collector phase is also a separate development; our Phase 2 preparation guide explains that work.

Bring your current process to a demo

Bring a typical load record and explain how the team captures and checks it now. In a free receiving-site demo, we can show the relevant workflow, discuss supported scenarios and review setup and support with you.

Reviewed by the PaperRoute team on 19 October 2026. Check the linked official guidance for current reporting arrangements.