The weighbridge already captures much of the operational truth behind a waste receipt. Preparation means connecting that verified movement to complete reference data, validation, submission and a usable audit trail.
Start with the transaction, not the API
Document the current journey from vehicle arrival to completed ticket. Identify when the customer, carrier, source, vehicle, material, gross weight, tare weight, destination and operator are selected or entered.
Then mark which required reporting fields do not exist, are held only in free text or are added later by another team. Those gaps define the implementation work more accurately than a generic software feature list.
Review reference-data quality
Connected reporting relies on reusable reference data. Duplicate carrier records, obsolete permits, inconsistent site names and loosely controlled waste descriptions create operational friction and submission errors.
Clean active customers, carriers, sites, vehicles, materials and codes before migration or integration. Agree who may create new records and what checks are required so the data does not deteriorate again after launch.
Confirm the technical connection
Record the weighbridge indicator, connection method, workstation, current application, database, network constraints, printer and any interfaces used by accounts or reporting systems. Do not assume that two sites with similar weighbridges have the same integration route.
A safe implementation should use representative test data, preserve ticket continuity, define fallback operation and avoid interrupting the live weighbridge until the connection has been proven.
Test real exceptions
Test first and second weighs, stored tares, multiple waste lines, estimated values where applicable, unfamiliar carriers, missing source details, rejected records and corrections after submission. Include weekend and out-of-hours operating patterns.
Operators should understand what blocks completion, what can be corrected later and who owns each exception. Training should be based on the actual screens and job roles used on site.
Practical checklist
Actions to take
- Map the complete vehicle and ticket workflow
- Inventory hardware, software and database connections
- Clean carrier, site, vehicle and material records
- Define validation rules and operator prompts
- Test common and difficult movement scenarios
- Agree fallback, support and go-live ownership
Common questions
What operators ask
Must we replace the physical weighbridge?
Usually not. The integration question concerns the indicator, connection, workstation, existing software and process; these should be reviewed site by site.
Can existing software be retained?
Yes, where it can provide the required data through a suitable and supportable connection route.
Should old records be migrated?
Selected customer, vehicle, material and historical records may be useful, but the scope should be based on operational value and data quality.
Official sources and review note
This guide was last reviewed on 12 August 2026. Official guidance remains the source of truth and may change as the service develops.
Defra: Digital Waste Tracking service