Divide the remaining miles by a realistic average speed. That gives driving time. Then add the time likely to be spent fueling, inspecting, loading, unloading, and taking a break that is not already covered by another qualifying stop.
Run three comparisons
- Driving time must fit the drive clock.
- The whole elapsed trip, including stops and off-duty breaks, must fit the remaining 14-hour window in the basic case.
- Expected on-duty time must fit the 60/70-hour cycle balance.
The trip works only when every applicable clock works. For example, 300 miles at a 50 mph average needs six driving hours. Add 35 minutes for fuel and 30 minutes at a dock, and the basic 14-hour comparison needs 7 hours 5 minutes of room. If a separate 30-minute break becomes due, the timeline needs another half hour.
For the cycle comparison, count driving plus other on-duty work. An automatically planned off-duty break uses elapsed time on the 14 but not cycle time. If the same qualifying break is logged on-duty-not-driving, it uses cycle time too. That duty-status difference matters when the cycle is the tightest clock.
Plan the end of the day, not just the destination
A result with ten minutes left may fit the arithmetic and still be a poor plan. Traffic, parking, a slow fuel island, or a customer delay can use that margin quickly. Know where you can stop before committing to a close run, and recalculate when the distance or stop time changes.
This method covers the basic property-carrier case. Sleeper splits, exceptions, recaps, and carrier rules require information that a simple trip form does not have. The ELD remains the record to follow.
Recheck the plan after a long customer delay or route change. The miles may be unchanged while the 14-hour margin has disappeared. A quick recalculation is most useful before leaving the last reliable parking option.