How to automate dispatch for a lumber or truss yard
Lumber and truss yard dispatch runs on phone calls, texts from superintendents, delivery tickets and a whiteboard. What your yard ERP already does for load planning and proof of delivery, where the manual work still sits, and how to automate it with a dispatcher approving every load.

In brief
To automate dispatch for a lumber or truss yard, start with your ERP's own delivery tools: Epicor BisTrack lists load planning, route scheduling, driver manifests, delivery texts and photo proof of delivery, and DMSi's Agility Mobile P.O.D. app sends customers automatic delivery notices and invoices an order once it's marked delivered. Then automate what those tools don't cover well: turning calls, emails and texts from the job site into delivery requests, confirming the site is ready the day before, checking truss loads against Texas size limits, and catching ticket-to-invoice mismatches. Keep the dispatcher approving every load.
- Turn on your ERP's delivery tools first: BisTrack and DMSi Agility both cover proof of delivery and customer notices.
- The manual work left is intake, date changes, site-ready calls, size checks and ticket-to-invoice matching.
- Texas legal limits without a permit include 8 feet 6 inches wide and 14 feet high; oversize loads need a TxDMV permit first.
- Start with intake: drafted delivery requests that a dispatcher approves.
What dispatch looks like at most yards
A superintendent texts the salesperson: "Need the trusses Thursday, gate code 4412." A builder's office emails a PDF with three lots and two dates. A contractor calls the counter to push a lumber package a day. Somebody writes it on the whiteboard, somebody else types the delivery ticket, and the dispatcher builds tomorrow's loads from memory and a printout.
It works because the dispatcher is good. But it breaks in predictable ways: a text that never made it to dispatch, a truck sent to a site that wasn't ready, a load that went out short and got invoiced full. Those are the problems worth automating. Assigning trucks and drawing routes is usually the part your software already does.
What your yard ERP already does
Use what you own first. Two widely used lumber and building material systems both have delivery tools.
Epicor BisTrack. Epicor's pro dealer page says BisTrack supports load planning, route scheduling and driver manifests, with GPS, SMS and email delivery notices, and mobile delivery tools that capture photos and signatures. For truss and component plants, Epicor's truss page lists manufacturing scheduling, field scheduling that lines deliveries up with job site readiness, and its Journey Planner for routes and delivery tracking.
DMSi Agility. DMSi's Agility Mobile P.O.D. release says inside reps see delivery status in real time, drivers see schedule changes as they happen, and customers get automatic notices when a load is on the way or delivered. Photos and signatures upload to the system. Drivers can fix quantities found wrong during unloading, and Agility invoices the order once it's marked delivered.
If you run one of these and aren't using its delivery module, turn that on before you build anything. That's the honest first step, and for some yards it's enough.
Where the manual work still sits
Even with a good delivery module, these steps are usually still done by a person typing or calling:
The dispatch steps that stay manual
| Step | What happens today | What automation can do |
|---|---|---|
| Intake | Calls, texts and emails get retyped into a delivery ticket | Read the message, find the order and job, draft the delivery request |
| Date changes | A text to a salesperson who forwards it, or doesn't | Catch "push it to Friday" in any channel and flag the ticket |
| Site ready check | The dispatcher calls the super the afternoon before | Send a confirmation the day before and log the answer |
| Size check | The yard lead eyeballs the truss package | Compare load dimensions to legal limits and flag anything that needs a permit |
| Driver notes | Gate codes and drop spots in someone's phone | Pull them from the job's history onto the manifest |
| Ticket vs. invoice | Someone in billing notices a short load weeks later | Compare what was delivered to what will be billed and flag differences |
Intake is the biggest. The whole schedule is only as good as the requests that made it in. Our automated dispatching guide explains why intake is the step most teams still do by hand.
What's different about truss loads
Truss and component deliveries add three things a lumber package doesn't.
The plant schedule drives the date. A truss package can't ship until it's built, so a delivery date promised by sales has to match production. Automation can compare the promised date to the plant schedule and flag the gap the day it appears, not the day before delivery.
Size. Long trusses can make an oversize load. Texas lists its legal limits without a permit: 8 feet 6 inches wide for trucks, 14 feet high, 59 feet for a semitrailer in a two-vehicle combination, and a 4-foot rear overhang. TxDMV says loads over legal size need an oversize permit and an authorized route before they travel. A check that compares each truss package's dimensions to those limits, at the time the load is built, is simple and catches the expensive mistake.
Handling at the site. The Structural Building Components Association points people to its BCSI-B1 Summary Sheet for unloading and storing trusses and protecting them from weather and damage at the job site. If you include it in your job site packet, automation can make sure it's attached to every truss delivery, every time.
How the automated version works
- A request comes in by email, text or the counter. The system reads it and matches it to the customer, the job and the open order.
- It drafts the delivery request: date, items, site address, gate code and drop notes from the job's history. Anything it isn't sure about is marked for the dispatcher.
- The dispatcher approves it and builds loads in the ERP's own planner, as today.
- The day before, the system sends the job contact a confirmation and logs the reply. "Not ready" goes straight to the dispatcher.
- The driver delivers and captures proof in the ERP's mobile app.
- After delivery, the system compares the delivered quantities to the invoice and flags any difference for billing.
Every step that changes a schedule or a bill goes past a person first. We explain why in human-in-the-loop automation. For texts to customers, confirm who should get them and that they want them before you start.
When this isn't worth it
Fair warning: if you run one or two trucks and one dispatcher handles everything by phone without errors, you probably don't need this. Turn on your ERP's delivery app and stop there. Automation pays off when requests come from many people in many channels, the dispatcher is the bottleneck, or re-deliveries and short-load credits are showing up every week.
How to start
- Pull 20 delivery requests from last month, in whatever form they arrived: texts, emails, calls written on paper.
- Count how many had a missing detail, a date change, or a site that wasn't ready.
- Count re-deliveries and short-load credits for the same month.
- Start with intake only: drafted delivery requests the dispatcher approves.
- Measure deliveries per dispatcher per day and time from request to scheduled, before and after. Our guide to measuring the ROI of office automation shows how.
Common questions
How do you automate dispatch for a lumber or truss yard?
Turn on your ERP's delivery tools first, like Epicor BisTrack's load planning and delivery app or DMSi Agility's Mobile P.O.D. Then automate intake from calls, texts and emails, day-before site confirmations, truss size checks and delivery-to-invoice matching, with a dispatcher approving every load.
Does Epicor BisTrack handle dispatch?
Epicor says BisTrack supports load planning, route scheduling and driver manifests, with GPS, SMS and email delivery notices and mobile photo and signature capture. Its truss page also lists field scheduling and the Journey Planner.
What does DMSi Agility's proof of delivery app do?
DMSi says Agility Mobile P.O.D. shows reps delivery status in real time, shows drivers schedule changes, sends customers automatic notices, uploads photos and signatures, lets drivers fix quantities at unloading, and invoices the order once it's marked delivered.
When does a truss load need a Texas oversize permit?
When it goes over Texas legal limits. TxDMV lists 8 feet 6 inches wide, 14 feet high, 59 feet for a semitrailer in a two-vehicle combination and a 4-foot rear overhang without a permit. Loads over legal size need a permit and an authorized route before travel.
What part of yard dispatch should we automate first?
Intake. Turn texts, emails and calls into drafted delivery requests the dispatcher approves. The schedule is only as good as the requests that reach it.
Will automation replace our dispatcher?
No. The dispatcher still approves every load and handles exceptions. Automation removes the retyping and the reminder calls so they can plan.
Is this worth it for a small yard?
Maybe not. With one or two trucks and few errors, your ERP's delivery app may be enough. It pays off when requests arrive from many people in many channels or re-deliveries show up every week.
Sources
- Epicor, BisTrack for pro dealers
- Epicor, BisTrack for truss and component manufacturing
- DMSi Software, DMSi releases proof of delivery mobile app, Dec. 8, 2021
- Texas DMV, Texas size and weight limits
- Texas DMV, Oversize/overweight permits
- SBCA, Proper storage and shipping of trusses (archived Jan. 2025)
Automated dispatching: how to automate dispatch for service and delivery teams
Human-in-the-loop automation: why a person should approve every step
Packing lists and bills of lading without retyping