The 30-Minute Break Rule: What Counts and Common Violations

The driver left the yard at 05:10, fuelled for 18 minutes near the state line, stopped for coffee for another 14, and was 25 miles from the consignee when the ELD flagged a rest-break violation at 13:42. Two stops added up to 32 minutes off the wheel, yet neither one counted. The load arrived on time, the inspector at the next weigh station still wrote the violation, and the safety manager now has another entry in the fleet's Hours-of-Service record.

Most break violations are planning failures rather than driver defiance. The rule is short: no more than 8 hours of driving without one consecutive 30-minute interruption. Fleets that place that interruption into the dispatch plan, often at a shipper dock where the driver is waiting anyway, remove nearly all of these citations without adding a single minute to the trip.

• What this guide explains: the exact text of 49 CFR 395.3(a)(3)(ii), how the 8 hours are counted, which duty statuses satisfy the break, and who is exempt.
• What it adds: five violation patterns from log reviews, a timestamped incident, a planning formula, a worked cost comparison in dollars and rupees, and India's separate rest-interval rule for transport crews.

What 49 CFR 395.3(a)(3)(ii) requires after the 2020 rewrite

A property-carrying driver may not drive once more than 8 hours of driving time have passed without at least a consecutive 30-minute interruption in driving status. Off duty, sleeper berth and on-duty not driving time all qualify, alone or combined, as long as the block is unbroken for 30 minutes.

The current wording dates from FMCSA's Hours of Service final rule published on 1 June 2020 at 85 FR 33396 and effective 29 September 2020. The earlier version tied the trigger to time on duty and did not accept on-duty not driving time as the break. The 2020 rule moved the trigger to driving time and let a non-driving on-duty period, such as waiting at a dock, satisfy the requirement.

Under 49 CFR 395.3(a)(3)(ii), a property-carrying driver recorded on an ELD may not drive after 8 cumulative hours of driving unless one consecutive interruption of at least 30 minutes has been logged, and off-duty, sleeper berth or on-duty not driving status all count toward that single 30-minute block.

The break sits beside, not inside, the other property-carrying limits in section 395.3. Those are the 10 consecutive hours off duty before a shift, the 14-hour window after coming on duty, the 11-hour driving ceiling within that window, and the 60-hour or 70-hour limit over 7 or 8 days. A driver can be legal on all four and still violate the break, which is why ELD vendors show it as its own clock.

• Who it covers: drivers of property-carrying commercial motor vehicles; passenger carriers follow section 395.5 and are outside this article.
• Who is excused: drivers who qualify for either short-haul exception in section 395.1(e)(1) or (e)(2) on that day.
• What resets it: any qualifying 30-minute interruption, including the 10-hour off-duty period that starts the next shift.

Eight hours of driving time, counted since the last full interruption

The clock counts driving minutes only, and it keeps counting across short stops. Section 395.2 defines driving time as all time spent at the driving controls of a commercial motor vehicle in operation, so a 20-minute stop pauses the count without resetting it. Only a single block of 30 minutes or more puts the counter back to zero.

That is the point drivers and dispatchers most often get wrong. A driver who stops every two hours for 15 minutes feels rested and has been off the wheel for an hour by mid-afternoon, but the ELD still shows 8 hours of accumulated driving since the last qualifying block. Dispatch tools that display "time since last stop" rather than cumulative driving since a 30-minute block encourage exactly this mistake.

# Break planning check for one driver and one planned route
# D_since   = driving minutes logged since the end of the last
#             non-driving block lasting 30 consecutive minutes or more
# R         = 480 - D_since            (driving minutes left before a break is required)
# B         = planning buffer, 20 minutes for traffic and dock-door moves
# drive(s)  = planned driving minutes from now to stop s
# hold(s)   = planned single non-driving block at stop s, in minutes

break_plan_ok = EXISTS stop s ON route WHERE
                    drive(s) <= R - B
                AND hold(s) >= 30
                AND no driving is planned inside hold(s)

# If break_plan_ok is false, dispatch inserts a 30-minute stop at the
# last safe parking location before drive reaches R - B.

The buffer matters more than it looks. A driver who plans to reach a rest area at 7 hours 55 minutes of driving has five minutes of margin against a lane closure. A 20-minute buffer means the break is taken somewhere around 7 hours 40 minutes, which costs nothing in available driving because the 11-hour limit, not the break, usually ends the day.

Which duty statuses satisfy the break and which pieces fail

Any status other than driving counts, provided the block is consecutive and at least 30 minutes long. The ELD records the break correctly only when the driver changes status before the vehicle moves and does not touch the wheel until the block is complete.

• Off duty: a meal, a rest stop or a personal errand away from the truck, logged as off duty for 30 minutes or more, satisfies the rule.
• Sleeper berth: any sleeper period of 30 minutes or more counts, including the shorter part of a split-sleeper pairing under section 395.1(g)(1), which our guide to the sleeper berth split explains.
• On duty not driving: waiting to be loaded, attending the trailer during unloading, inspecting the vehicle, fuelling or completing paperwork counts when logged in that status for 30 straight minutes.
• Co-driver time: on a team run, time riding as the non-driving partner is on duty not driving under the section 395.2 definition, so a co-driver who rides for 30 minutes has had a break.
• Combinations: 10 minutes on duty fuelling followed by 20 minutes off duty at a counter meal is one 30-minute interruption, because the rule allows a combination of the three non-driving statuses.
• Pieces that fail: two blocks of 18 and 14 minutes, or a 29-minute block ended by a short repositioning move, do not satisfy the rule however long the total.

Dock waits, yard moves and fuel stops used as planned breaks

The cheapest break is the one the driver is already taking. Loading appointments, live unloads and fuel stops are non-driving time on almost every run, and since 2020 each of them can carry the 30-minute interruption if it is logged as one unbroken block.

Dock time creates one specific trap. Shippers often ask a driver to pull from the waiting line to a door, then from the door to a scale. If those moves are logged as driving, a 50-minute dock wait becomes three short pieces. The ELD technical specification handles this with the yard move special category in 49 CFR Part 395, Subpart B, Appendix A, section 4.4.1.1: the driver sets on duty not driving, indicates a yard move, and the status stays on duty not driving until the driver ends it.

Yard moves still need limits. A driver who selects the category for travel on a public road between two sites is recording driving as something else, which risks a false-report finding under section 395.8(e)(1). Write the permitted locations into the driver manual, keep them to private property such as a shipper's lot, terminal or rail ramp, and audit a sample of yard-move segments against GPS each month.

Dock waits satisfy the FMCSA 30-minute break when the ELD logs 30 unbroken minutes of on-duty not driving status; door-to-scale moves recorded with the yard move category under 49 CFR Part 395 Appendix A section 4.4.1.1 keep that block intact, while the same move logged as driving splits it.

Five violation patterns that log reviews keep finding

Break violations cluster into a handful of repeatable patterns, and each one has a different fix. Sorting a month of flagged logs into these buckets tells a safety manager whether the problem is training, ELD configuration, dispatch planning or the short-haul paperwork.

• Split short stops: two or three stops under 30 minutes each, none of them qualifying; fixed by teaching cumulative counting and showing the break clock on the driver display.
• The 29-minute block: the driver changes status to driving a minute early to reach the exit; fixed by a 32-minute minimum in company policy so rounding never decides compliance.
• Door moves as driving: repositioning at a shipper logged as driving because the yard move category is disabled; fixed in the ELD carrier portal.
• Lost short-haul status: a local driver runs past 150 air miles or beyond 14 hours, loses the exception, and has taken no break; fixed by a dispatch alert when a route change breaks either condition.
• Reassigned segments: an unidentified driving segment is later accepted by the driver and lands inside a break; fixed by reviewing unassigned driving time on the ELD before logs are certified.

The trace below shows the reassignment pattern, which is the hardest to see because the original log looked clean on the day it was certified.

1. 06:00, Tuesday: Driver D-114 comes on duty at the Joliet terminal, completes a 15-minute pre-trip inspection and departs at 06:15 with load 88213.
2. 10:40: After 4 hours 25 minutes of driving, D-114 waits at a supplier dock in Fort Wayne, logged on duty not driving until 11:15; at 10:58 a yard jockey moves tractor 5521 for 6 minutes while the driver is inside, creating an unidentified driving event on that tractor.
3. 14:55: D-114 reaches 8 hours 0 minutes of driving counted from 11:15; the ELD shows the break satisfied by the 35-minute dock block, and the log is certified that evening.
4. Thursday, 09:20: The fleet's log auditor, clearing the unidentified queue, proposes the 6-minute segment to D-114 because the driver was logged in on tractor 5521; the driver accepts without checking the time.
5. Thursday, 09:21: The recertified Tuesday log now shows two non-driving blocks of 18 and 11 minutes, no qualifying break since 06:15, and a section 395.3(a)(3)(ii) violation at 14:40; the auditor rejects the reassignment, assigns the segment to the yard jockey's account and annotates both records.

Short-haul drivers under 395.1(e) and when they lose the exemption

Drivers who meet a short-haul exception for the day do not need a 30-minute break at all. The exemption is day-specific, so a local driver who qualifies Monday to Thursday and runs a longer route on Friday must plan a break on Friday. The conditions themselves are covered in our 150 air-mile short-haul exemption guide.

Section 395.1(e)(1) covers drivers operating within a 150 air-mile radius, or 172.6 statute miles, of the normal work reporting location who return there and are released within 14 consecutive hours, with at least 10 consecutive hours off duty between shifts. Section 395.1(e)(2) covers drivers of property-carrying vehicles that do not require a CDL, within 150 air miles, returning to the reporting location, with a 14-hour limit on five days and 16 hours on two days in any seven.

The practical control is a route-level flag. When a planner adds a stop that pushes the furthest point beyond 150 air miles or the planned release past 14 hours after the start, the dispatch screen should mark the driver as a non-exempt driver for the day, require an ELD log if the fleet's short-haul time record no longer applies, and insert a break stop. For other ELD-exempt cases, our ELD malfunction rules guide covers the paper-log fallback.

Building the break into dispatch plans and appointment times

Dispatch, not the driver, controls most of the levers that decide whether a break lands in a useful place. Appointment times, fuel network choices and the order of stops all determine whether 30 non-driving minutes already exist inside the first 7 hours 40 minutes of driving.

Existing guides on HOS dispatch locks, such as our architecture for HOS dispatch interlocks, focus on blocking loads that would breach the 11-hour or 14-hour clocks. This article narrows to one clock that those locks often ignore. A planner who books a delivery at 13:30 for a driver starting at 05:00 with no planned stop has created a probable break violation, even though both larger clocks look healthy.

• Appointment spacing: book the delivery so that the planned dock wait at pickup, not a roadside stop, carries the interruption.
• Fuel network choice: route fuel stops to sites with a counter meal so a fuel stop can stretch to a full 30 minutes.
• Stop sequence: on multi-stop runs, put the stop with the longest expected unload inside the first 7 hours of driving.

The table sets out which record each party owns and who approves changes to it. Clear ownership is what lets a fleet answer an investigator's question about a break in minutes rather than days, because every supporting document has a named keeper for the six months that section 395.8(k)(1) requires.

Appointment negotiation is part of the plan. When a shipper offers a 06:00 pickup and a 14:00 delivery 430 miles away, the planner should ask whether a 30-minute wait at the pickup is likely. If the answer is yes, the driver logs it as on duty not driving and the break is done before the truck reaches the highway.

What a missed break plan costs a fleet in dollars and rupees

A break taken in the wrong place costs more than 30 minutes. The truck often misses a delivery slot, incurs a reschedule fee and pushes the next load, while a planned break at a dock costs nothing extra because the wait was already in the schedule.

The worked example compares one US lane and one Indian lane, with illustrative figures. The US case uses an hourly running cost for a tractor-trailer and a typical retailer reschedule fee. The Indian case treats the rest interval under the state's labour rules rather than an ELD rule, because India has no electronic driving log requirement for trucks, and prices the delay with a per-hour truck cost and a missed warehouse slot.

The table excludes enforcement costs on purpose. A break violation found at roadside adds to the carrier's Hours-of-Service compliance record used in FMCSA's safety measurement, and penalties depend on the case, so treat them as an additional downside rather than a line to budget. The operating cost alone usually justifies a planner rule that every trip over 7 hours 30 minutes of driving shows a named break stop.

Rest intervals for Indian truck crews under the OSH Code

India has no equivalent of the US driving-time break or of electronic logging for trucks. The comparable obligation is a labour-law rest interval measured on hours of work, set under the Occupational Safety, Health and Working Conditions Code, 2020, which came into force on 21 November 2025 and absorbed the Motor Transport Workers Act, 1961.

Section 25(1) of the Code limits work to eight hours a day and leaves intervals and spread-over to be notified by the appropriate government. For motor transport workers, its proviso counts running time, subsidiary work such as loading and upkeep, and periods of mere attendance at terminals under fifteen minutes as working hours. That means a driver waiting to load is working, as on duty not driving is in the US rule.

Ministry of Labour and Employment notification S.O. 2517(E), dated 13 May 2026 and made under section 25(1)(b) of the Occupational Safety, Health and Working Conditions Code, 2020, notifies not more than five hours of continuous work followed by an interval of at least half an hour, effective from its Gazette publication on 14 May 2026.

That is a work-time rule, not a driving-time rule, so the arithmetic differs. Five hours of combined driving, loading and terminal attendance triggers it, against eight hours of driving alone in the US. Whether the Central notification or a state's own notification governs a particular fleet depends on which government is the appropriate government for that establishment under the Code, so transport operators should read the rules of the state where they are registered.

Rule-based ELD checks, reviewer judgement and an audit checklist

Counting minutes is a job for software; deciding whether a log is honest is a job for a person. A fleet should automate every check that is pure arithmetic over duty status events and keep human review for status choices, yard-move use and reassigned segments.

Use the checklist below when setting up the process or auditing it once a quarter. It works the same way for a 20-truck carrier and a 2,000-truck private fleet; only the sample sizes change.

Break compliance rarely needs new hardware. It needs the yard move setting switched on, a planner rule that names a stop, and a reviewer who checks reassigned driving before it lands in a certified log. For the dock side of the plan, see our comparison of drop-and-hook and live loading, which sets how much dock time a driver has to work with, and browse the wider logistics and supply chain library.

If you are specifying dispatch or ELD software that must plan breaks rather than report them after the fact, our team can help you write the requirements and test scripts. Share your lanes and current violation report through the request for proposal form and we will reply with a scoped plan.