Nexus Materials(placeholder name) — prototype
Seeded from MM Tracker Example TaylorWimpey.xlsx (Taylor Wimpey North Yorkshire, tracker updated 5 Jun 2026). Local JSON only — nothing is saved, no integrations are live.
Options
Routes found for your outstanding balances. We lead with the route — a nearer destination is worth knowing about before anyone has quoted a rate.
You already did this one by hand
West Lane, Ripon → Cat Flatt, 23,933 m³ of subsoil. Three separate cells in the spreadsheet; one route here.
Cat Flatt comments: "Material to be sourced from Ripon" · West Lane, Ripon: 24,527 m³ subsoil exported · Cat Flatt: 23,933 m³ subsoil imported
Marske Sands
4 options found for your 45,100 m³ topsoil export
Enumerated 4 Aug 2026
19km
~28 min drive
- •Fill requirement is subsoil; topsoil accepted only against a revised MMP
- •Takes 2,139 m³ of 45,100 m³ — partial route
No rate captured for either site. Internal transfer — haulage only.
Missing: Chemical testing on the Marske Sands arisings.
Source: Your own division — subsoil fill required, tracker row 19
Guisborough
14km
~22 min drive
- •Inert soils accepted under the restoration permit
- •Capacity comfortably exceeds the outstanding volume
Rate not yet verified. 12 km nearer than the current landfill destination.
Missing: Permit conditions on imported topsoil; Gate fee — operator not yet contacted.
Source: EA permit register (candidate — restoration dataset not yet acquired)
Middlesbrough
12km
~19 min drive
- •Permitted for 17 05 04 soil and stones
- •Nearest permitted receiver to the site
Rate not yet verified.
Missing: Gate fee; Throughput availability for Q4.
Source: EA waste-facility register (synced)
Redcar
8km
~14 min drive
- •Accepts inert soils
Baseline comparator — gate fee plus landfill tax. Always shown so savings are provable once a rate lands.
Source: EA landfill boundaries (OGC GeoJSON, synced) — default comparator
Propsect Farm
4 options found for your 56,685 m³ topsoil export
Enumerated 4 Aug 2026
31km
~41 min drive
- •Same division — no cross-client agreement needed
- •Start date Apr 2027; needs stockpiling or phasing to line up
Internal transfer. Timing, not rate, is the constraint.
Missing: Confirmed earthworks programme for Highfield Farm.
Source: Your own division — 8,528 m³ subsoil fill required, tracker row 21
Sedgefield
17km
~24 min drive
- •Inert topsoil and subsoil sought for land raise
Rate not yet verified.
Missing: Scheme permit reference; Acceptance criteria.
Source: Candidate — restoration dataset acquisition outstanding (spec §6)
Newton Aycliffe
13km
~20 min drive
- •Actively seeking inert fill for a platform build
Rate not yet verified. Closest declared fill demand to the site.
Missing: Direct contact not yet made; Volume confirmation.
Source: Carrier/supplier directory + Companies House enrichment
Aycliffe
15km
~22 min drive
- •Accepts inert soils
Baseline comparator — gate fee plus landfill tax.
Source: EA landfill boundaries (synced) — default comparator
Romanby Grange
3 options found for your 17,839 m³ topsoil export
Enumerated 4 Aug 2026
Thirsk
18km
~25 min drive
- •Inert soils accepted
- •Timing aligns with the Jun 2027 start
Rate not yet verified.
Missing: Permit conditions; Gate fee.
Source: Candidate — restoration dataset acquisition outstanding (spec §6)
22km
~30 min drive
- •Both pre-development — programmes can still be aligned
- •Covers roughly half the outstanding volume
Internal transfer — haulage only.
Missing: Earthworks programmes for both sites.
Source: Your own division — 8,528 m³ subsoil fill required
Northallerton area
26km
~34 min drive
- •Accepts inert soils
Baseline comparator — gate fee plus landfill tax.
Source: EA landfill boundaries (synced) — default comparator
Mocked to show the shape of the Route/Options Engine output (docs/spec-route-options-engine.md §3). In the real build these come from the nexus4 matching engine, the EA waste-facility register and landfill boundaries — with the landfill comparator always included so savings become provable once rates are captured. Restoration routes are shown as candidates because the restoration dataset has not been acquired yet (spec §6, an accepted v1 gap).