Mandate & Rollout
One evidence standard. Every sub, supplier and haulier. From day one.
Hub360 works best when it's mandated — not optional. The main contractor, developer or public body sets the standard at contract stage. Subs and hauliers adopt it on site. The result: one consistent, defensible record across the entire supply chain — from first movement to final audit.
Why mandate — not suggest
Optional adoption means inconsistent evidence. Inconsistent evidence means exposure.
When some subs use Hub360 and others use paper, you get two classes of evidence — and the gaps are exactly where disputes, ghost trips and duty-of-care failures live. Mandating a single standard eliminates the inconsistency before it becomes a problem.
- Each sub records movements differently — or not at all
- Disputes default to "your word vs theirs"
- Ghost trips and inflated quantities go undetected
- Duty-of-care gaps appear exactly where paper ends
- Audit and valuation evidence is reconstructed, not captured
- One consistent record from every sub and haulier
- GPS-verified evidence counters any dispute
- Ghost trips and duplicate loads visible immediately
- Full chain-of-custody — closed at both ends
- Audit and valuation packs in <2 minutes, on demand
Financial modelling on Irish public infrastructure projects shows 4–10% of material spend is exposed through paper docket gaps. At 1% improvement on a €23m roads project, the modelled ROI is 138%. Calculate your exposure →
The mandate model
Set top-down. Adopted bottom-up. Enforced through the portal.
The developer, main contractor or public body specifies Hub360 as the movement record standard at contract stage. Subcontractors, suppliers and hauliers adopt it on site. The main contractor sees all records — and all gaps — in real time.
The single most important step. Adding the Hub360 requirement to the sub-contract, LOI or tender before works commence means every party is contractually bound to the same evidence standard from day one.
- Add the clause to your standard sub-contract template
- Include in Letter of Intent where programme is tight
- Reference in tender documents for public procurement
- Written to specify capability — not a named product — procurement-safe
Before the first load moves, every subcontractor and haulier is set up on Hub360. Drivers download the Tipper App. Dispatchers get portal access. The Hub360 team supports onboarding — your team doesn't carry it.
- Drivers: download app, one short walkthrough — live in minutes
- Dispatchers: portal access configured per sub and site
- Hauliers: invited via the portal — no separate system
- Full project archive live from movement one
Mannok: 50+ years of paper-based process replaced across 5 business units — every driver live within 7 days. 150+ hauliers on a single major project.
The digital record is the record. Paper dockets are not accepted alongside Hub360 records — doing so creates two competing systems and undermines the mandate. The app captures what the docket used to, faster and with GPS evidence.
- Brief site managers to direct all movements through Hub360 from day one
- Any load without a Hub360 record is a visible gap in the portal
- Exceptions and non-compliance visible to the main contractor in real time
- One record per movement — clean, consistent, defensible
Practical tip: appoint a single Hub360 lead per site — usually the site manager or QS. They own compliance and are the first point of contact for any sub that needs support.
The Hub360 portal gives the main contractor a live view of all movements across all subs and hauliers. Any movement not on Hub360 is a visible gap — not a hidden one. KPIs, exceptions and non-compliant parties are surfaced automatically.
- Live movement feed — all subs and hauliers, one view
- Exceptions flagged: missing drops, GPS anomalies, late confirmations
- Non-compliant sub or haulier identified immediately
- Read-only access for client, council or auditor on request
For public bodies: councils and authorities get read-only portal access. Contractors create the evidence — you search and export without chasing anyone.
When the QS needs a valuation pack, the auditor requests Article 27/28 evidence, or an FOI lands on a council desk — the export is ready in under 2 minutes. Evidence was captured at source. Nothing is reconstructed.
- QS valuation pack — quantities, dockets, GPS trail per sub
- Article 27/28 bundle — chain-of-custody, facility permits, GPS timestamps
- UK DWTS documentation — WM3, U1 and payload records
- Scope 3 / ESG dataset — per-load CSV/Excel for sustainability reporting
- FOI / audit pack — project archive, tamper-evident change log
In practice
What a mandated rollout looks like on site
How fast it happens
Fully live in 7 days — the exact rollout plan
From first conversation to every driver active on site. The Hub360 team runs the onboarding — your commercial and site teams make two decisions and attend one short kick-off call.
50+ years of paper-based process. 5 business units. 11 sites. 150+ hauliers on a major project. Every driver live within 7 days.
Read the Mannok story →Council mandated Hub360 across contractors on the N2 national road scheme. GPS-verified reuse and chain-of-custody records for TII, Article 27/28 and circular economy reporting.
Read the case study →7 days
To go fully live
From first conversation to every driver and sub active — including 150+ hauliers on a single project
138%
ROI at 1% control improvement
Modelled on a €23m Irish roads project — based on public data and independent audit benchmarks
<2 min
Audit or valuation pack
Article 27/28, QS valuation, DWTS or chain-of-custody — generated on demand from the live archive
The contract clause
Specify the capability in contract. Procurement-safe. Ready to use.
This clause specifies what the system must do — real-time capture, GPS, photos, chain-of-custody, 24-hour export — without naming a specific vendor. It works in sub-contracts, LOIs, tenders and framework call-off agreements across Ireland and the UK.
Hub360 is an example of a system designed to meet the above requirements. We can tailor this clause to your specific scope, sites, waste streams and jurisdiction.
- Sub-contract: as a specific obligation under the works scope or standalone digital evidence schedule
- Letter of Intent: pre-commencement condition — evidence standard agreed before mobilisation
- Tender / ITT: include in Particular Conditions or Method Statement requirements
- Framework call-off: standard condition applied to all call-offs above a set value
- Public procurement (Ireland): specify in Works Requirements — capability-based, not brand-specific
- Public procurement (UK): specify in Works Information or Scope under NEC4/JCT
We can review your sub-contract template and suggest exactly where and how to insert the clause for your project type, waste streams and jurisdiction.
Discuss rollout
Sustainability & circular economy
The mandate also delivers your circular economy and ESG evidence.
A mandated rollout doesn't just close commercial and compliance gaps — it builds the verified evidence base for Green Public Procurement, circular economy reporting, Article 27/28 and Scope 3 automatically. No extra process. The records are already there.
GPS-verified planings reuse, C&D recovery rates and circular economy quantities — captured in the same movement record. One process, multiple reporting outputs.
Per-load datasets exported directly to your ESG or sustainability dashboards. Numbers you can stand over — not estimates calculated from averages.
Questions about rollout
Mandate & rollout — frequently asked
Most rollout discussions cover four things in 30 minutes:
- Your current recording process and where the gaps are
- Which streams to mandate first — and which to phase
- How the clause fits your existing sub-contract template
- Onboarding plan and timeline for subs and hauliers
Start the conversation
Pick one project. Set the standard. See what changes.
We'll map your streams, review your sub-contract clause and walk through what a fully mandated rollout looks like for your project type — in 30 minutes.