Dispatch and truck movements
Bring assignments and movement records into a shared workflow, with screens built for the people who enter and use the information.
Services / Software for transportation
Custom trucking software built around your operation.
Connect dispatch, drivers, payroll and safety records in software designed for the way your business runs. Work directly with Derek Deppermann, from the first conversation through development.
Book a free discovery callAn example workflow
One operation. Connected work.
- Dispatch records the work
- Drivers and the office stay in sync
- Payroll and reporting use the same records
When another spreadsheet stops helping.
A custom system is worth discussing when the same trip, driver or document has to be entered in several places. Start with the handoff that causes the most trouble: a dispatch update, missing paperwork or a payroll reconciliation. DPM is based in Quincy, Illinois and works with businesses across the United States.
Driver payroll and reporting
Connect operational records to the payroll calculations and reports your business needs. Review the rules and exceptions before building them into the system.
Safety records and follow-up
Keep incidents, corrective actions, supporting documents and due dates connected so the office can see what still needs attention.
Work already built
Experience behind the proposal.
One system supporting about 75 trucks
A flatbed carrier in west-central Illinois uses DPM’s custom transportation system every day. Dispatch, drivers and payroll work in one application covering dispatch, truck movements, driver payroll, live GPS and reporting. DPM designed, built and operates the system that replaced the carrier’s spreadsheets.
Read the transportation case studySafety Director
DPM’s own safety management software connects events, owners, due dates and evidence. Office staff use a browser; drivers have a phone screen for quick reports.
See Safety Director and sample screensScope and delivery
Define the first useful release.
A custom build does not need to replace every tool at once. Existing systems and available interfaces determine what can be connected.
See how development, hosting and backups connect- Map who enters each record and who needs it next.
- Review existing data, exports and integration access before promising a connection.
- Agree on the screens, permissions, reports and acceptance checks in the written scope.
- Plan data migration, deployment and the support needed after launch.
Before you start.
Can you connect the systems we already use?
That depends on their interfaces, permissions and available exports. Bring the names of your systems to the discovery call so the connection can be assessed before it becomes part of the scope.
Is this a ready-made trucking product?
This service is for a custom project. The transportation system and Safety Director show DPM’s experience; their features are not automatically included in a new engagement.
What should I bring to the first call?
Describe one workflow that is difficult today, who uses it, and the software involved. An anonymized example of a form or report is useful; confidential driver or customer records are not needed for the first conversation.
Your next step
Start with the part of your operation that needs to work better.
Discuss the problem with Derek and work out whether a custom project fits.
Explore business automation