Fraley & Schilling needed a way to close a compliance workflow gap in its ELD system without adding more work from driver training, reminders, and back-office follow-ups. It found the answer in a custom driver app.
Do drivers sometimes forget to self-certify their electronic logs? Do some fail to include their trailer and bill of lading numbers in their logs? Of course. The only question is how often.
Each of these mistakes is harmless on its own. But if they’re repeated daily by hundreds of drivers, hours-of-service “form and manner” violations multiply during roadside inspections.
Violations from seemingly minor mistakes are detrimental to CSA scores and can result in costly fines, damage reputations, and increase insurance rates. Corrective measures typically add extra work and communication between office staff and drivers.
Rushville, Indiana-based Fraley & Schilling found a solution in a custom driver mobile app.
Built on the Eleos Technologies platform, the app streamlines routine workflows, communication, and daily tasks for drivers.
The fleet worked with partner ASR Solutions to develop the integration between Eleos and the TMW Suite TMS used by the company.
How the Custom App Helps With Compliance
For compliance steps, such as certifying logs and updating trailer and shipping details, drivers use the fleet’s in-cab ELD platform from a separate provider.
But Fraley & Schilling needed a way to close a compliance workflow gap in its ELD system without adding more work from driver training, reminders, and back-office follow-ups.
To do this, the fleet used the Eleos platform’s Action Request feature to set up critical messages and tasks that drivers have to acknowledge in the app and complete.
What an Action Request Does
An Action Request is a pop-up that takes over the screen and requires a driver to respond before proceeding. Unlike regular messages or to-do items, it cannot be ignored.
Action Requests can be deployed to collect yes/no responses, acknowledgments, signatures, and form completions, depending on how a fleet structures its workflow.
They can be triggered by location-based events, for example. A fleet can configure a window to appear when a driver stops or crosses a geofence in a designated area, such as a customer facility or a severe-weather zone.
Fleets can choose whether to allow drivers to snooze a non-urgent request or to require immediate action before drivers can access other features in their app.
Making Log Certification Unavoidable
To ensure log compliance, Fraley & Schilling created an Action Request to eliminate the need to call or message drivers about uncertified logs from previous workdays.
The automated process is triggered when the fleet’s ELD system reports that a driver has uncertified logs. Through integration with the ELD, the custom app triggers an Action Request that appears as soon as the system confirms the driver is stopped.
Once the driver confirms they are safely stopped, the workflow automatically logs them out of the ELD. To resume, the driver must complete the standard ELD login process, which prompts them to certify any remaining log records.
Once they went to this process, Fraley & Schilling reduced its daily backlog of uncertified logs from 25-50% in August 2025 to 10-20% today, says Nicky Cupp, director of continuous improvement.
Preventing Trailer and Shipping Document Violations
Fraley & Schilling also uses an Action Request to ensure drivers enter their trailer and bill of lading numbers into the ELD system.
When a driver picks up a load and submits the required arrival form in the app, the Eleos platform checks whether the driver has entered the trailer and shipper details into the ELD and whether those details match the data in the fleet’s back-office system.
If the data doesn’t match, drivers receive an immediate Action Request to enter or correct the ELD information.
Instead of discovering mistakes after an inspection, the system automatically detects issues and prompts drivers to correct them. Follow-up checks are conducted if the mismatch isn’t resolved within the set timeframe.
Improving the First Days on the Job
Drivers’ first encounter with Action Requests occurs during orientation training.
They are introduced to the Fraley & Schilling app during training at the fleet’s terminal in Knoxville, Tennessee.
At the end of the orientation, an Action Request prompts them to complete a short digital form indicating when and where they plan to pick up their tractor before their first dispatch.
This information is shared with the maintenance and operations teams via email. Upon receipt, they can prepare the equipment for each driver’s schedule and needs. This communication is especially helpful for accommodating drivers who arrive outside normal business hours to pick up their trucks.
Before this process, the fleet sometimes didn’t have trucks fully prepared for drivers upon their arrival, especially when they showed up after hours. In these instances, the fleet often had to pay for a driver’s hotel expenses.
Why Better Driver Workflow Matters
Fraley & Schilling was able to address multiple issues through a single, consistent workflow tool that does more than just communicate with drivers.
By safely prompting drivers to take immediate action, the company is preventing avoidable CSA violations, reducing manual follow-up, and improving the job experience.
Credit: Source link
