The FMCSA 14-Hour Rule With Worked Driver Logs

A driver comes on duty at 05:30, spends four hours at a shipper's dock waiting for a late load, takes a half-hour lunch, and still shows two hours of driving left on the ELD at 19:30. Dispatch reads that two-hour balance, promises the consignee an early arrival, and the truck rolls on. At 19:31 the driver is already in violation, because the clock that expired was not the driving clock. It was the 14-hour window.

The 14-hour rule is short, but it is the limit that most often surprises planners, because it runs on elapsed time rather than on hours worked. Once you can read where a window starts, what never pauses it and which narrow exceptions stretch it, you can plan loads that finish inside it, bill the shipper for the hours it consumed, and stop selling capacity that the driver cannot legally use.

• What this guide covers: the regulatory text of 49 CFR 395.3(a)(2), two worked driver logs (one plain, one with a 7/3 sleeper split), the exceptions that extend the window, and what a missed window costs.
• What it adds for India: how the Occupational Safety, Health and Working Conditions Code, 2020 now governs motor transport working hours, and why its spread-over is a different instrument from the US window.

What 49 CFR 395.3(a)(2) actually limits, and what it leaves alone

The 14-hour rule limits driving, not working. Under 49 CFR 395.3(a)(2), a property-carrying driver may not drive after a period of 14 consecutive hours after coming on duty following 10 consecutive hours off duty. Inside that period the driver may drive up to 11 hours under 395.3(a)(3)(i). After the 14th hour the driver may still do paperwork, fuel or unload, but may not drive.

Three words in the text do most of the work. "Consecutive" means the window is a block of wall-clock time; it does not stop for lunch, a nap in the cab or a breakdown. "Coming on-duty" means the window opens with the first on-duty activity, which is often a pre-trip inspection rather than driving. "Following 10 consecutive hours off-duty" ties every window to the reset that came before it, so a short rest does not open a new one.

On-duty time is defined broadly in 49 CFR 395.2. It includes time at a shipper's facility waiting to be dispatched, time inspecting or servicing the vehicle, time loading or unloading or attending a vehicle being loaded, and time giving or receiving receipts for shipments. That is why a dock wait which looks like idle time on a yard screen is window time on the driver's log.

Federal hours-of-service rule 49 CFR 395.3(a)(2) bars a property-carrying driver from driving after 14 consecutive hours following the first on-duty moment that comes after 10 consecutive hours off duty; the electronic logging device record is the evidence, and only qualifying sleeper berth periods of at least 2 hours are excluded from the window.

Where the window starts: the first on-duty minute after 10 hours off

The window opens at the first change to on-duty status after a qualifying reset, and every later decision is measured from that minute. A driver who logs on duty for a 15-minute pre-trip at 05:15 and does not start driving until 06:30 has already used 75 minutes of the 14 hours. The window end is fixed at 19:15 regardless of when the wheels first turned.

Which records fix that start time matters when a planner, a safety manager and a roadside inspector all read the same day. The table below sets out the records that establish each element of the window and who should own a correction when they disagree.

Carriers must keep records of duty status and supporting documents for at least 6 months from receipt under 49 CFR 395.8(k)(1). Gate logs and appointment confirmations are the supporting documents that let a carrier prove when the window was consumed by a facility rather than by the driver, which matters for both an audit and a detention invoice.

Worked log one: a regional run that loses two hours at a shipper

A long dock wait does not reduce the 11 hours of driving, but it can make them unreachable. The log below follows one driver on a single regional day. The times and the load are illustrative; the arithmetic follows the rule text.

At 19:30 the driver has used 9 of 11 driving hours and all 14 window hours. The remaining 2 driving hours cannot be used until another 10 consecutive hours off duty, so the earliest restart is 05:30 Wednesday. If the consignee was 110 miles away at 19:30, the 06:00 Wednesday appointment is now at risk even though the ELD showed driving time left.

• Dock time was the cause: the 4 hours at the shipper consumed 29% of the window, and only the gate log can show how much of that was the facility's delay.
• The meal break bought nothing: the 30 minutes off duty at 13:30 did not move the window end, which stayed at 19:30.
• The 30-minute break rule was not the limit: 395.3(a)(3)(ii) accepts on-duty not-driving time as the interruption, so the 4-hour dock wait already satisfied it and the driver never approached 8 hours of uninterrupted driving.

Why fuel stops, meals and the 30-minute break never pause the clock

Only one thing removes time from the 14-hour calculation for a property carrier: a qualifying sleeper berth period paired under 49 CFR 395.1(g)(1). Off-duty time in a truck stop, a meal, a 30-minute break and a breakdown all count as elapsed window time. The rule text says "14 consecutive hours", and nothing else in 395.3 interrupts it.

Drivers sometimes log a long lunch as off duty expecting it to extend the day. It does not. It only reduces the share of the window spent on duty, which matters for the 60 and 70-hour weekly limits in 395.3(b), not for the daily window. Planners should treat every hour after the window opens as spent, whatever the status line says.

Worked log two: using a 7/3 sleeper split to pull the window forward

A sleeper berth split is the only lawful way to exclude rest from the window. Under 49 CFR 395.1(g)(1)(ii), two rest periods can together equal a 10-hour reset if neither is shorter than 2 hours, one is at least 7 consecutive hours in the sleeper berth, and the two total at least 10 hours. Under 395.1(g)(1)(iii)(B), those qualifying periods do not count toward the 14 hours.

The log below uses a 3-hour sleeper period while the driver waits for a night receiving slot, then a 7-hour period to complete the pair. Count the window only from on-duty and driving lines, and recalculate both limits from the end of the first rest period, as 395.1(g)(1)(iii)(A) requires.

Without the split, this driver's window would have closed at 20:00. Because the 3-hour sleeper period is excluded, the driver lawfully drives until 21:00 and reaches the full 11 hours. After the 7-hour period, counting restarts at 15:30: 5 hours of driving and 5.5 window hours are already used, so the driver may drive 6 more hours, and the window ends at 12:30.

Sleeper berth pairing under 49 CFR 395.1(g)(1)(ii) excludes a qualifying rest period of at least 2 hours from the 14-hour window when it pairs with at least 7 consecutive sleeper hours totalling 10 or more; the ELD log must show both periods, and limits are recalculated from the end of the first period.

The split is a planning tool, not a loophole. Driving before and after each rest period must still fit inside 11 hours and must not breach the 14-hour limit, under 395.1(g)(1)(ii)(D). A pair that fails either test leaves the driver on the ordinary window, so dispatch should never schedule a split until the safety team has checked how the ELD will pair the periods.

Exceptions that stretch the window: 16-hour, adverse conditions, short-haul

Three exceptions can lengthen or remove the window, and each has conditions narrow enough that a planner should treat them as rare. None of them is a substitute for a load plan that fits within 14 hours.

• The 16-hour exception: 49 CFR 395.1(o) exempts a driver from 395.3(a)(2) when the driver was released at the normal work reporting location for the previous five duty tours, is released there within 16 hours of coming on duty, and has not used the exemption in the previous 6 consecutive days unless a 34-hour restart began a new period.
• Adverse driving conditions: 395.1(b)(1) allows up to 2 additional hours beyond the maximum hours in 395.3(a) to finish a run or reach safety, but only for snow, fog, unusual road or traffic conditions not known before the duty day or dispatch, as 395.2 defines them.
• 150 air-mile short-haul: 395.1(e)(1) removes the logbook requirement, not the time limit. The driver must stay within 150 air miles (172.6 statute miles) and be released within 14 consecutive hours, with time records kept for 6 months.
• Non-CDL short-haul: 395.1(e)(2) exempts drivers of vehicles not needing a CDL from 395.3(a)(2), but limits driving to the 14th hour on 5 days and the 16th hour on 2 days of any 7.
• Passenger carriers: bus drivers follow 49 CFR 395.5 instead, which bars driving after 15 hours on duty following 8 hours off and caps driving at 10 hours.

Dispatch and yard decisions that burn the window before the wheels turn

Most window violations are planned in the office, hours before the driver breaks the rule. A load accepted at 15:00 for a driver who came on duty at 05:30 has, at most, 4.5 hours of window left, whatever the driving balance says. The test belongs at load assignment, and it needs the window end time, not just remaining drive time.

Window end time for a property-carrying driver (illustrative check)

W_end   = T_on + 14 h + S_q + A_x
D_left  = 11 h - D_used
W_left  = W_end - T_now
Feasible if: (ETA_leg_hours <= D_left) AND (T_now + ETA_leg_hours + Dock_hours <= W_end)

T_on    = first on-duty event after 10 consecutive hours off (395.3(a)(2))
S_q     = qualifying sleeper periods excluded under 395.1(g)(1)(iii)(B); 0 if no valid pair
A_x     = adverse-condition extension, 0 to 2 h, only when 395.1(b)(1) and 395.2 are met
D_used  = driving since the last reset (or since the end of the first split period)
Dock_hours = planned on-duty time at the receiver before the last driving leg
Example: T_on 05:30, S_q 0, A_x 0, T_now 15:00 -> W_end 19:30, W_left 4.5 h

Yard practice matters as much as dispatch. A live load that runs two hours over appointment, a trailer that is not ready at the drop yard, or a gate queue at a distribution centre all spend window time on the carrier's driver. That is the commercial case for drop-and-hook, discussed in our guide to drop and hook versus live loading, and for writing detention terms that start the clock at the appointment.

The dispatch rules below are fixed checks that software should enforce, alongside the tasks where software can only help a person judge. Keeping them apart prevents a planning tool from approving a load because a model guessed the dock would be quick.

For the ELD side of this, including how unidentified driving minutes can silently consume a driver's window, see our explainer on unassigned driving time on ELDs. The architecture view of locking dispatch against all hours-of-service clocks is covered in the older HOS dispatch lock architecture page; this article stays with the 14-hour window itself and how to read it on a log.

Timestamped trace: a late reload that ended in an out-of-service order

The trace below shows how a window violation is assembled from ordinary decisions. Each step was reasonable in isolation; the failure came from planning against the driving balance instead of the window end.

• 05:30, load 41187 pre-trip: driver logs on duty at the terminal; ELD window end is 19:30. Driving balance at start is 11:00.
• 09:40 to 13:55, shipper dock 7: live load runs 2 hours 15 minutes past appointment; gate log GL-2207 records arrival 09:40 and release 13:55, all on duty.
• 15:10, reload offer accepted: dispatcher sees 4:20 driving left in the TMS and books reload 41203, a 3.5-hour leg, with pickup at 16:00. No window check runs.
• 19:30, window closes on the highway: driver is 30 minutes from the consignee with 1:20 driving left and continues, intending to park at the receiver.
• 19:50, weigh-station inspection: officer finds driving after the 14th hour; driver is placed out of service under 395.13(b)(1) and must take 10 hours off before driving again.

A controlled version of the same day changes one step. At 15:10 the TMS adds the 16:00 pickup, 30 minutes of loading and the 3.5-hour leg, gets a 20:00 finish against a 19:30 window end, blocks the assignment, and offers the reload to a relief driver who came on duty at 11:00.

What a blown window costs: out-of-service orders, penalties, lost revenue

The direct penalty is only part of the cost. A driver found driving beyond the maximum periods is placed out of service under 49 CFR 395.13(b)(1), the carrier must complete the certification of action taken on the examination report within 15 days under 395.13(c)(2), and the violation feeds the carrier's safety record.

Civil penalties are set by Appendix B to 49 CFR Part 386 and adjusted for inflation. The amounts published in the eCFR in October 2026 were up to $19,246 per violation for a carrier's non-recordkeeping violation and up to $4,812 for a driver. The worked example below sets those exposures beside the operating cost of a wasted window, using illustrative rates.

The India overtime line assumes a monthly wage of ₹24,000 over 26 working days, giving ₹923 per day and ₹115.38 per hour for an 8-hour day, doubled to ₹230.77 for overtime. The hours after which overtime applies are those prescribed by the appropriate government under section 27, so confirm the state rules before using this arithmetic. Revenue per truck hour comes from your own fleet; our article on revenue per truck per week shows how to derive it.

India after the OSH Code: spread-over replaces a fixed 14-hour window

India has no direct counterpart to a 14-hour driving window. The Motor Transport Workers Act, 1961 was repealed by section 143(1)(f) of the Occupational Safety, Health and Working Conditions Code, 2020, which the government brought into force on 21 November 2025. Working hours for motor transport workers now sit in sections 25 to 27 of the Code and in the rules made under it.

Section 25(1) limits work to eight hours in a day, with intervals and spread-overs notified by the appropriate government rather than fixed in the Code. For a motor transport worker, the hours include running time of the vehicle, subsidiary work such as loading, unloading, garaging, paperwork and travel between the sign-on point and the vehicle, and periods of mere attendance at terminals of less than fifteen minutes.

Motor transport working hours in India fall under section 25 of the Occupational Safety, Health and Working Conditions Code, 2020, effective 21 November 2025: an eight-hour daily limit, spread-over notified by the appropriate government, and loading time counted as subsidiary work, with section 27 paying overtime at twice the wage rate.

• Weekly holiday: section 26(1) bars work on more than six days a week, but its proviso lets a motor transport undertaking require holiday work so long as no worker goes more than ten consecutive days without a full day off.
• Overtime consent: section 27 requires twice the rate of wages for overtime and makes overtime subject to the worker's consent.
• Spread-over figure: the Code leaves the cap to notification, so the number that applies to a fleet depends on the state rules for that undertaking. Do not carry over the old Act's figure without checking.

The practical difference for a planner is the measuring stick. A US window is elapsed time from the first on-duty minute; an Indian limit counts working hours, including loading, inside a spread-over set by notification. A fuller comparison of the two regimes is planned as a separate guide; until then, treat this section as orientation, not a compliance opinion.

Rolling a window-aware dispatch check into daily planning

A fleet does not need new software to stop window violations; it needs the window end time on every screen where a load is promised. Start with the checklist below, then measure how many loads per week were re-planned because the window, not the driving balance, was the binding limit.

For more on hours-of-service operations across the network, browse the Logistics and Supply Chain hub. If you are scoping a dispatch or TMS change that puts window end times in front of planners and billing teams, you can describe the requirement through our request for proposal page.