Reconcile batched yardage against what shipped
Each night, WebRun opens CommandBatch and Dispatch360, totals batched versus delivered yardage by job and mix design for the day, finds any load or ticket that does not reconcile, and writes the variances to a Google Sheet with the likely cause so plant and dispatch can resolve them.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I reconcile batched versus delivered concrete yardage?
WebRun catches the yardage that quietly slips. Each night it totals batched yardage in CommandBatch against delivered yardage in Dispatch360 by job and mix, finds every load that does not reconcile, and writes the variances to a Google Sheet tagged short pour, returned, overbatch, or missing ticket, so plant and dispatch can resolve them.
- Short pours and overbatching are caught the same night
- Lost or unmatched tickets stop slipping through
- A daily variance record supports accurate billing and yield
Built for ready mix producers · plant managers · controllers · dispatch managers
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.dispatch360.comin a real browser with your saved login - no setup, no API keys. -
1
CommandBatch - total batched yardage
commandalkon.com
WebRun opens CommandBatch to total batched yardage by job and mix. - Open CommandBatch and sum yardage batched during the day by job and mix design
- Capture ticket numbers and plant for each batched load
- Note any batch adjustments or wash-outs
Done when Batched yardage is totaled by job and mix with ticket references.
-
2
Dispatch360 - total delivered yardage
dispatch360.com How to Automate Dispatch360
WebRun opens Dispatch360 to total delivered yardage by job and mix. - Open Dispatch360 and sum delivered yardage for the same day by job and mix
- Match delivered tickets to their batched counterparts
- Flag tickets present in one system but not the other
Done when Delivered yardage is totaled and matched to batched tickets.
-
3
Google Sheets - write the variances
google.com How to Automate Google Sheets
WebRun opens Google Sheets to write the batched versus delivered variances. - Write each variance to a reconciliation sheet with batched, delivered, and difference
- Tag a likely cause: short pour, returned concrete, overbatch, or missing ticket
- List clean jobs briefly so the sheet shows the full day at a glance
Done when Every variance is logged with figures and a likely cause.
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
Does it change any yardage figures?
No. WebRun only reads totals from CommandBatch and Dispatch360 and writes the variances to a Google Sheet. Plant and dispatch decide how to correct anything, so no source record is edited.
What kinds of variances does it catch?
Short pours, returned concrete, overbatching, and tickets present in one system but not the other. It tags each variance with a likely cause so the right person can resolve it fast.
How are the two systems matched?
By job, mix design, and ticket number for the same day. WebRun lines up batched loads in CommandBatch against delivered tickets in Dispatch360 and flags anything that does not pair up.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.