Tepia builds custom dispatch software for trucking companies that assigns loads using live hours of service from your ELD provider, automates check calls and captures signed bills of lading from the driver's phone. Builds connect to Samsara, Motive or Geotab, EDI tenders from shippers and QuickBooks or NetSuite.
A trucking dispatch system has to match every load to a driver who has the hours, the right trailer and a realistic way home.
Tepia pulls remaining drive and duty hours from your ELD provider, so planners see who can legally take a load before they call.
Read: Trucking Company App Development
Drivers photograph signed bills of lading and lumper receipts in the app, and Tepia files each one against the right load.
Read: Telematics Integration with Samsara, Geotab and Motive
Shipper tenders arrive as EDI 204 messages and status goes back as 214s, so planners stop rekeying loads from email.
Read: ELD and Hours of Service Integration
Driver settlements calculate from completed loads, miles and accessorials, so payroll stops depending on paper trip sheets.
Trucking figures Tepia keeps in view when scoping dispatch software.
The American Trucking Associations reports trucks move about 72 percent of US freight by weight, more than any other mode.
CVSA's 2025 Roadcheck found hours of service caused about 32 percent of driver out of service violations, the top category.
ATRI research found drivers were detained at about 39 percent of stops in 2023, hours that dispatch has to plan around.
A planner at a regional truckload carrier starts the day with tenders from shippers, a board of trucks spread across three states and a list of drivers who each have a different number of hours left on their clock. Every assignment is a trade off. The closest truck might be pulling a dry van when the load needs a reefer, the driver with the most hours may be due home tonight, and the strongest lane might leave a truck stranded with no reload. Tepia builds dispatch software around those decisions, not around a generic job list.
Once a load is assigned, the work shifts to execution. Planners chase check calls, confirm pickup and delivery appointments, log detention when a receiver keeps a driver waiting, and collect paperwork before the load can be billed. Owner operators and company drivers follow different settlement rules, and a team truck needs two drivers’ hours tracked against one tractor. These details are where spreadsheets and whiteboards start to fail, and where Tepia focuses the first version of a custom system.
Tepia scopes the board around how your planners work today. Most carriers end up with a core like this:
| Feature | Who uses it | Why it matters |
|---|---|---|
| Tender inbox with accept and reject | Customer service and planners | Answers shipper tenders inside their response deadline |
| Driver and truck availability by location and hours | Planners | Shows who can legally and practically take the next load |
| Equipment matching for dry van, reefer and flatbed | Planners | Prevents sending the wrong trailer type |
| Automated check calls from GPS | Customer service | Updates shippers without phone tag |
| Appointment and detention tracking | Planners and billing | Records arrival and departure times to support detention claims |
| Driver app with document scan and messaging | Drivers | Sends signed paperwork the moment a load delivers |
| Driver settlement rules | Payroll | Handles per mile, percentage and flat rate drivers correctly |
| IFTA mileage by state | Compliance | Builds fuel tax reports from GPS miles |
Tepia adds a home time planner to most trucking builds, because a driver who repeatedly misses home time is a driver who leaves. Planners see each driver’s requested days off on the same board as the loads, and the software flags any assignment that would make that date impossible.
Under FMCSA rules, a property carrying driver gets 11 hours of driving inside a 14 hour window after 10 consecutive hours off, plus a 60 or 70 hour limit across 7 or 8 days. Tepia does not recreate the logbook, because your ELD provider remains the legal record. Instead, the dispatch software reads remaining drive, duty and cycle time from Samsara, Motive or Geotab through their APIs and projects whether a driver can reach the receiver within those limits, including the 30 minute break.
The driver app carries the rest: load details and stops, truck specific navigation, a document camera that crops and flattens paperwork, messaging with dispatch, and large buttons for arrived, loaded and empty. Tepia builds it offline first, since a rural grain elevator or a mountain pass loses signal, and syncs everything when coverage returns. Read more on ELD and hours of service integration and driver app development.
Trucking dispatch lives between other systems, and Tepia builds those connections early so planners never enter a load twice:
When a shipper tenders through a web portal instead of EDI, Tepia can parse structured emails or call the portal’s API. See our telematics integration work for the device side.
Typically Discovery runs 1 to 3 months, development and QA 2 to 6 months, and launch about a month. See our process.
Many carriers already run a trucking TMS for accounting and compliance. If it handles your freight well and the pain is a weak driver app or poor visibility, Tepia will usually recommend keeping it and building around it through its API or database exports. A full replacement makes sense when:
Compare options on trucking company app development and build or buy software, then talk to Tepia about your fleet.
A paragraph or two with information on your product/service or describes a problem your product/service is designed to solve.
CEO
Senior Project Manager
VP & Operations Manager
