Understanding drive time between assigned stops

A driver completes one delivery at 10:05 a.m. and reaches the next at 10:38. The route app shows two stop events, but nothing obvious for the 33 minutes on the road between them. Across a sparse route, those gaps total 90 minutes. Understanding drive time between assigned stops means tracing travel that occurs during the assigned route and checking whether the employer's time record includes it, even when no package is handed over during the drive.

A delivery route is more than a set of stop timestamps. It includes necessary movement to reach the next assigned location. The length of that movement can vary with traffic, distance, access and dispatch changes. A candidate should ask how the employer records the whole workday, not infer pay from the number of completed stops. A separate guide compares per-stop and hourly offers; this one checks one role's treatment of travel within an active route.

Mark the route's first required activity

Before looking at stop-to-stop travel, establish when the assigned workday begins. A driver may report to a depot, inspect a vehicle, load parcels and then drive to the first delivery. Another role may use a different reporting arrangement. Ask which activities and travel are recorded as work. The first customer scan is not necessarily the first required task.

Keep ordinary home-to-work travel separate. A trip from home to the first normal reporting site can be an ordinary commute, while travel after required route work begins follows a different analysis. A companion guide examines the initial trip. Here the central question is what happens after the driver has started the assigned route and is moving between destinations chosen by the employer.

Ask whether the role uses a payroll time clock, route app or both. If the driver clocks in at the depot, that timestamp may anchor the workday. If the app begins only at the first stop, ask how the earlier required work and travel are captured. The answer should describe the actual system, not simply say that the driver is “on route.”

Trace travel between assigned stops

Write a simple route sequence: finish Stop A, drive to Stop B, make the delivery, then drive to Stop C. The intervals between assigned stops are part of completing the employer's route, not personal trips inserted into a day off. Note any dispatch-approved change that sends the driver to a pickup, a return point or another delivery area.

The U.S. Department of Labor's hours-worked fact sheet says travel that is part of an employee's principal activity, such as movement from job site to job site during the workday, is work time. That general rule supports counting assigned route travel in the work-time analysis. The exact pay calculation still depends on the role's wage method and all applicable terms.

A route may include long access roads, wrong-turn corrections or traffic delays. Ask how the employer records actual time spent following the assignment, including reasonable rerouting. A planned travel estimate is not a substitute for the workday that occurred. If dispatch changes the destination mid-drive, note the instruction and the resulting route change rather than assuming the original estimate controls payroll.

The driver should also distinguish assigned travel from a personal detour. A meal stop, personal errand or unauthorized trip raises a different time question. Ask how breaks and personal time are entered so the record does not mistake an ordinary delivery drive for a break or a true break for work travel.

Use route drive time as its own measure

Some route dashboards report stops completed, packages handled and miles driven. Ask whether they also show route drive time and whether that number feeds payroll. A dashboard may help dispatch plan work without being the system of record for hours. The candidate needs to know which number determines pay and who checks gaps caused by app or device problems.

Suppose a route has four distant stops. The driver spends 20 minutes from the depot to the first, 30 minutes to the second, 35 minutes to the third and 25 minutes to the fourth. That is 110 minutes of assigned driving before counting any delivery handling or return work. A pay estimate based only on the minutes at doors would miss most of the route.

Traffic and parking can make actual drive time differ from the map estimate. Ask whether payroll uses a scheduled route duration, clocked hours, completed-stop count or a combination. If a driver is paid by a method linked to stops, the employer still needs a way to account for hours worked under applicable wage rules. The route map alone does not establish what time the employee actually spent working.

Do not turn a GPS trace into a legal conclusion. It can corroborate movement but may have gaps, include personal travel or fail to show loading and other work. A useful review pairs the employer's time record with route assignments and the driver's actual sequence. The goal is to identify an omitted work interval, not to reconstruct every second of a day from a phone signal.

Check the time record against route events

The Department of Labor's recordkeeping fact sheet lists hours worked each day and total hours worked each workweek among the basic records covered employers must keep. A route app showing only completed deliveries may not display that full time record. Ask which system preserves clock-in, clock-out, breaks and non-stop intervals.

Compare a sample day in the payroll system with the route app. Does the period from Stop A to Stop B appear within continuous paid time, or does the system pause when a delivery is marked complete? If it pauses, who resumes it, and what happens when the next stop takes 40 minutes to reach? An applicant can ask for a sample explanation without requesting another driver's private statement.

Some systems record a shift continuously but apply separate codes for driving, delivery, depot work and breaks. In that case, the stop-to-stop interval may already be included even though it has no special line on the pay stub. Ask payroll to show how the daily total was derived before assuming the absence of a “drive time” label means the time was unpaid.

If an app loses signal, note the approximate start and end of the gap, the assigned destinations and the dispatch instruction. Ask how to correct a missing segment. The employer should have a process for technical failures that does not depend on a customer scan to prove the driver was on the road.

Work through the 90-minute sparse route

Imagine a driver starts required route work at 8 a.m., completes several stops, and finishes at 4 p.m. The delivery events themselves occupy only a small part of that span. Three long drives between stops total 90 minutes. The first question is whether the payroll record contains the full work period, including those drives and any required depot work, with actual breaks identified separately.

On a sparse route, a stop count can look low even when the workday is full. One driver might make many nearby deliveries in an hour; another might spend the hour reaching the next assigned address. If compensation or performance measures rely on stop count, ask how the employer keeps that measure distinct from the time record. A low count does not erase travel required by the assignment.

Suppose the time system shows 8 a.m. to 4 p.m. with a documented 30-minute unpaid meal break. The 90 minutes of driving between stops may already be inside the recorded work time. Suppose instead it shows only brief paid blocks around customer scans. That record needs an explanation and possibly a correction. The driver should identify the actual intervals rather than assume either display is correct from appearance alone.

Do not add the 90 minutes a second time to an eight-hour shift merely because the pay stub lacks a driving line. Confirm whether continuous clocked time already includes it. The arithmetic should account for each minute once: active work, required travel, actual breaks and release. A useful question for payroll is, “Where are the three stop-to-stop drives in this total?” That asks for a clear, traceable explanation without claiming an underpayment before the underlying record is reviewed.

Change one fact: dispatch asks the driver to skip a planned stop and drive 25 minutes to a new pickup. The drive remains an assigned part of the route sequence even though the original stop was not completed. Record the dispatch change and compare the day total. The fact that one stop disappeared from the app does not mean the travel to the new assignment was personal time.

Handle hourly and stop-linked pay without mixing the decisions

For an hourly role, ask whether the clock runs through assigned travel and how breaks are marked. For a stop-linked arrangement, ask how total work hours are recorded and how the pay method satisfies applicable wage rules. This guide does not compare which offer pays better. It identifies the hours the driver actually spent moving between assigned destinations so the employer's stated method can be checked.

A per-stop amount might compensate several activities within the route, depending on the written terms. It does not tell the driver that only door time counts as work. The Department of Labor's work-time guidance concerns activities and hours, while a pay plan describes how earnings are calculated. Both need to be understood without treating them as the same question.

If the route runs longer because stops are far apart, ask whether the employer adjusts the schedule, pay calculation or both. A driver who regularly spends 90 minutes between sparse stops needs a realistic planned workday. The issue here is not a promise of extra pay for every mile; it is accurate recognition of the required travel and the compensation method that applies to it.

Include travel after the last delivery when work continues

The last customer stop may not end the assigned workday. A driver might have to return undelivered parcels, park the vehicle, complete a scan or check out at the depot. Ask whether the return travel and closeout are captured before the employee is released. A route app may display “complete” before those tasks are finished.

Separate the trip home after final release. Once the employee has completed required closeout at the regular worksite, the homeward trip is ordinarily commuting. If dispatch sends the driver from one assigned site to another before release, that is workday travel and deserves its own record. The boundary is the employer's required work sequence, not the location of the last successful delivery.

If a driver is allowed to end the day at a different site, ask how the employer records the transition and where the ordinary commute home begins. A driver should not invent an end time from the last package scan. Ask payroll for the policy applicable to the actual route arrangement.

Resolve a missing driving interval

Report the date, route identifier, assigned stops on either side of the gap, and approximate start and end times. Include any dispatch change and the time system's current entry. Payroll can then determine whether the drive is already included in continuous clocked hours, hidden under a code, or missing because of an app error.

If a correction is needed, ask which statement will show it and how the adjusted hours or earnings are labeled. Keep the original and corrected records. Avoid storing customer names or addresses outside approved work systems; the route identifier and stop sequence should be enough for the employer to trace the event internally.

The Fort Wayne driver guide hub covers related route and pay questions. For a current opening on the Fort Wayne driver careers page, ask how drive time between stops appears in that role's timekeeping and pay plan. Understanding drive time between assigned stops should leave the driver able to identify a real missing interval without mistaking a sparse route for a short workday.