UK & Northern Ireland
DWTS‑ready workflows for UK earthworks & waste — from paper tickets to digital traceability in weeks.
This blueprint shows how Hub360 (incl. Tipper) supports UK compliance: DWTS staging & submission, DoWCoP packs, U1 guardrails, and WM3‑assisted e‑dockets — for facilities and operators.
Executive summary
Capture → Validate → Transmit → Reconcile → Report
Position Hub360 as DWTS‑ready for the UK: field capture in Tipper; validations for WM3/U1/permits; DWTS payloads per receiver; reconciliation to weighbridge; monthly Duty of Care and DoWCoP packs.
Regulatory timeline (UK)
What’s coming and when
End‑to‑end workflow
From the field to DWTS & monthly packs
Field e‑dockets in Tipper: GPS/time, vehicle reg, photos, signatures, EWC/LoW, weighbridge import.
On‑device checks for WM3 fields, permits/licences, U1 counters, DoWCoP flags; block or warn as configured.
DWTS payload assembled and queued per receiving site; per‑receiver credentials and rate limits.
Auto‑match loads with weighbridge tickets/invoices; exception inbox for issues.
Duty of Care packs, DoWCoP Verification Report, U1 usage, monthly registers and CSV/Excel exports.
Printable, pre‑numbered dockets; scan‑to‑record with OCR; supervisor approves.
DWTS field map
WTN/Consignment → Hub360 → DWTS
Proposed field mapping and validations for UK DWTS and earthworks use‑cases (incl. DoWCoP & U1 counters).
| Domain | Field (business meaning) | Hub360 field (proposed) | Required | Validation | DWTS equivalent |
|---|---|---|---|---|---|
| Parties | Producer name / site | producer.name, producer.site_id | Yes | From client/org master | Producer details |
| Parties | Carrier (CBD ref/licence) | carrier.name, carrier.licence_no | Yes | Licence format + expiry | Carrier details |
| Parties | Broker/Dealer (if any) | broker.name, broker.reg_no | Conditional | Present if declared | Broker/Dealer |
| Receiver | Receiving site (permit/licence) | receiver.name, receiver.permit_no | Yes | Permit format + status | Receiver site |
| Waste | EWC/LoW code | waste.code | Yes | WM3 code list | Waste code |
| Waste | Description | waste.description | Yes | Non‑empty | Description |
| Waste | Form/State (solid/sludge/liquid) | waste.form | Yes | Enum | State |
| Waste | Hazardous flag | waste.hazardous | Derived | From code/H properties | Hazardous? |
| Movement | Quantity | movement.quantity | Yes | Positive number | Quantity |
| Movement | Units (t/m³) | movement.unit | Yes | Enum | Unit |
| Movement | Container/vehicle type | transport.container_type | Optional | Enum | Container |
| Transport | Vehicle reg | transport.vehicle_reg | Yes | Alphanumeric regex | Vehicle |
| Transport | Driver signature | signatures.driver | Yes | Presence | Signatures |
| Transport | Producer signature | signatures.producer | Conditional | Presence if required | Signatures |
| Locations | Origin (address/site) | origin.address, origin.site_id | Yes | Non‑empty | Origin |
| Locations | Destination (address/site) | destination.address, destination.site_id | Yes | Non‑empty | Destination |
| Time | Date/time of transfer | timestamps.transfer_at (UTC+offset) | Yes | ISO 8601 | Timestamp |
| Docs | Weighbridge ticket ref | docs.weighbridge_ref | Conditional | Match to import | Supporting docs |
| Compliance | Carrier/Receiver documents | docs.licences[] | Yes | In‑date | Attachments |
| Export | Annex VII (if export) | exports.annex_vii_ref | Conditional | Present if export | Export fields |
| DoWCoP | MMP/QP/Mass balance | dowcop.* | Project‑level | Completeness checks | Verification pack |
| U1 | Registration, window, counters | u1.* | Site‑level | Guardrail alerts | Exemption usage |
DoWCoP
Material reuse: MMP, mass‑balance and verification
Records: MMP ID, QP ID, scope of reuse, source & receptor locations, specs. Mass‑balance ledger with running totals by material/class, linked to each load. Verification Report compiles photos, test certs, ledger totals, plan and sign‑offs.
U1 exemption
Use‑of‑waste controls with counters & alerts
Counters track tonnage by EWC and time window per site. Alerts warn at 80% and block at 100% (role‑based override with reason). Each load links to the U1 registration entry and shows remaining allowance.
Roles & permissions
Who does what
API & integrations
DWTS Connector (UK) and data flows
Weighbridge import (CSV/API); document stores (SharePoint/OneDrive/Google).
POST /dwts/loads (queue per receiver), GET /dwts/acks (webhook). Retry & dead‑letter queues; payload hash, ack ID and status.
Map DWTS errors to user‑readable fixes (e.g., invalid LoW code, missing permit).
Pilot SOW (template)
4–6 weeks to DWTS‑ready
1–2 depots/sites; ≤10 vehicles; one workflow (e.g., soils/waste for a highways job).
- ≥80% loads captured digitally
- Admin time per load ↓ ≥30%
- Monthly Duty of Care/DoWCoP pack generated in <2 minutes
Fixed pilot fee credited to year‑1 subscription on adoption.
- Configured e‑dockets; WM3 assist; U1 counters
- DoWCoP ledger & Verification export
- DWTS staging queue & exception inbox
- Training and end‑of‑pilot metrics
FAQ
Quick answers for UK & NI
Do we have to wait for DWTS to go live to start?
No. Capture digitally now; Hub360 stages DWTS payloads and submits when the receiving site is live. You can still export PDF/CSV packs meanwhile.
How does Hub360 help with DoWCoP?
We maintain a mass‑balance ledger, link each load, and generate a Verification Report with photos, test certs and sign‑offs.
Can we control U1 limits?
Yes — per site and EWC. Counters warn at 80% and block at 100% with role‑based overrides and reasons.
What about hazardous classifications (WM3)?
On‑device code lists and validations flag missing fields or hazardous indicators so loads can’t be submitted with gaps.
Will this work with subcontractors?
Yes. Subbies use the same app; their loads feed your archive with your branding and permissions.
How quickly can we run a pilot?
Typical pilot is 4–6 weeks with clear success criteria; fixed pilot fee credited to the first year if adopted.