Automated M2X Weight-Restriction Routing
Every morning, WebRun opens M2X, reads each planned load's gross weight and route, checks it against weight-restricted roads and bridges, logs any load that would breach a limit to a Google Sheet, and posts a routing warning to dispatch in Slack before trucks roll.
How do I automatically route livestock loads around weight-restricted bridges?
Every morning WebRun opens M2X, reads each planned load's gross weight and route, and checks it against weight-restricted roads and bridges. It logs any conflict to a Google Sheet with a suggested detour and posts a routing warning to dispatch in Slack, so no loaded livestock truck heads toward a bridge it cannot legally cross.
- Overweight loads are caught before they reach a posted bridge
- Dispatch gets suggested detours, not just a red flag
- Only the trucks that need re-routing show up on the warning
Built for livestock haulers · cattle transporters · fleet dispatchers · bulk haul operators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.m2xgroup.comin a real browser with your saved login - no setup, no API keys. -
1
M2X - read load weight and planned route
WebRun opens M2X to read load weight and planned route. - Open M2X and list today's planned loads with an assigned route
- Read the gross vehicle weight and the pickup and delivery locations for each
- Compare the route to known weight-restricted roads and bridges
- Note any load whose weight exceeds a posted limit on its route
Done when Every planned load has been checked against weight-restricted roads and bridges on its route.
-
2
Google Sheets - log weight-restriction conflicts
WebRun opens Google Sheets to log weight-restriction conflicts. - Open the Route Conflicts sheet
- Add a row for each load that would cross a weight-restricted structure, with the truck, weight, and restricted point
- Note the suggested alternative road where one is known
- Mark loads with no clear detour for a dispatcher to review
Done when The sheet lists every routing conflict with its restricted point and a suggested detour where available.
-
3
Slack - warn dispatch about at-risk routes
WebRun opens Slack to warn dispatch about at-risk routes. - Post a routing warning to the dispatch channel
- List the affected trucks and the restricted bridge or road first
- Link the Google Sheet so a dispatcher can re-route before departure
Done when Dispatch has a Slack warning naming every load that needs a re-route today.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it re-route my trucks in M2X automatically?
No. WebRun only reads the planned weight and route from M2X and flags conflicts to a Google Sheet and Slack. A dispatcher decides the actual detour and updates the route, so nothing is changed in M2X on its own.
How does it know a bridge is weight-restricted?
It checks each planned route against the weight-restricted roads and bridges you configure for your operating area, so a loaded truck over the posted limit is caught before it leaves the yard.
What if a load is under every limit on its route?
Loads that clear all posted limits on their route are left off the warning list, so dispatch only sees the trucks that genuinely need a re-route that morning.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.