The DOT Short Haul Exemption can save paperwork, but it doesn’t erase Hours of Service rules. If you run local freight, the real question is whether each trip actually qualifies under FMCSA rules, what records still matter, and what changes the moment a day runs long.
DOT Short-Haul Exemption FAQs: What It Does and Does Not Do#
The DOT short-haul exemption is really an exception from using an Electronic Logging Device and preparing Records of Duty Status on qualifying days, not a free pass from Hours of Service limits. Drivers still have to follow the underlying HOS rules that apply to their operation.
An Electronic Logging Device (ELD) is the device that records a driver’s duty status and driving time. Records of Duty Status (RODS) are the daily logs showing when a driver is driving, on duty, off duty, or in the sleeper berth. Hours of Service (HOS) are the federal limits on driving time, on-duty time, and required rest under FMCSA rules.
The short-haul exception is not an exemption from all HOS limits#
If a driver qualifies for the short-haul exception, that mainly affects logging. It does not wipe out the 11-hour driving limit, the duty window rules, or the required off-duty time before the shift.
That point gets missed all the time. A local route can still break HOS rules even if the driver never leaves town.
Who should check whether the rule applies#
This rule matters most to property-carrying commercial motor vehicle operations that are subject to federal HOS rules. If you have a USDOT number, operate a truck in interstate commerce, or run a combination of local and non-local trips, you need to check each day’s facts instead of assuming “local” means exempt.
A USDOT number is the identifier FMCSA uses to track motor carriers and certain commercial operations. If your setup changes based on state rules, intrastate operation, cargo type, or vehicle size, those facts can change the answer.
The difference between local work and qualifying short-haul work#
“Local” is not the legal test. A day qualifies only when every condition is met, including reporting location, radius, duty window, and required rest.
That’s why two drivers can both run short routes and get different compliance answers. One qualifies for the exception; the other needs standard logging.
How to Qualify for the Standard Short-Haul Exception#
To qualify for the standard short-haul exception, treat it like a trip-by-trip checklist, not a permanent label for a driver or company. Under FMCSA Hours of Service guidance and 49 CFR 395.1(e), the day has to meet every condition, including radius, reporting location, duty window, and off-duty time.
A good rule of thumb is simple: qualify the day before dispatch, then re-check it when the day starts changing.
Start and return to the same work-reporting location#
The driver has to start the day at the normal work-reporting location and return to that same location at the end of the duty day. This is one of the easiest conditions to overlook when dispatch changes a final stop or sends the truck somewhere else to park.
If the driver doesn’t return to that reporting location, the short-haul exception usually falls apart for that day.
Stay within the 150 air-mile radius#
The route has to stay within a 150 air-mile radius of the normal work-reporting location. An air mile is a straight-line measurement from point to point, not the road miles shown on your GPS.
That’s where drivers get tripped up. A route that looks short on paper can drift outside the radius once you add actual stop locations, detours, or a last-minute delivery change. Plan with a buffer instead of running right up against the limit. FMCSA’s Hours of Service materials are the right starting point for this standard short-haul framework at fmcsa.dot.gov.
Meet the 14-consecutive-hour duty window#
The driver must be released from duty within 14 consecutive hours after coming on duty. That means the day can’t just “mostly” fit. Once the duty day stretches past that window, the short-haul exception is no longer available for that trip.
This also doesn’t create extra driving time. A driver still can’t drive beyond the applicable 11-hour limit just because the trip otherwise looks local.
Confirm the driver has required off-duty time before the shift#
Before the shift starts, the driver must have at least 10 consecutive hours off duty. That rest requirement is part of qualifying for the day, not an optional cleanup item after the fact.
A clean dispatch board doesn’t fix a bad reset. If the off-duty time wasn’t there, the day doesn’t qualify the way many small carriers assume it does.
What Happens When a Trip Exceeds the Short-Haul Limits#
If a trip exceeds any short-haul condition, the driver cannot use the short-haul ELD and RODS exception for that day. The operation still has to comply with the underlying HOS rules, and the driver and carrier need a compliant way to create and keep the required duty-status record.
Leaving the 150 air-mile radius#
Once the trip goes beyond the radius, that day is no longer a qualifying short-haul day. It doesn’t matter that the dispatch started as a local run.
This is where late changes cause problems. A “quick extra stop” can turn into a logging issue fast.
Not returning to the reporting location#
If the driver ends the day somewhere other than the normal reporting location, that can break eligibility too. Parking at a different yard, customer site, or safe haven may make sense operationally, but it can still change the compliance answer.
Remaining on duty past 14 hours#
If the driver stays on duty beyond the standard 14-hour window and no separate exception applies, the short-haul exception is gone for that day. Don’t assume a delayed receiver, breakdown, traffic event, or dispatch change preserves short-haul status.
Switching to compliant ELD or paper-log procedures#
Small fleets need a fallback process before the day goes sideways. That means knowing whether the driver will use a compliant ELD workflow or a permitted paper-log process when the short-haul exception no longer applies.
This is where owner-operators get burned: the trip changes, nobody escalates it, and the paperwork gets reconstructed later. If your operation has outgrown true local work,
about whether your trucking coverage still matches your authority, radius, and hauling activity.
How the 16-Hour Short-Haul Exception Works#
The 16-hour short-haul exception is a limited extension of the on-duty window for certain property-carrying drivers, not a blanket right to work or drive 16 hours whenever the day gets long. Under 49 CFR Part 395, including 49 CFR 395.1(o), the 11-hour driving limit still remains in place.
A lot of drivers call this the “big day” rule. That’s fine as shop talk, but the legal conditions still matter.
What the 16-hour exception changes#
The main change is the duty window. Instead of being released from duty within 14 consecutive hours, a qualifying driver may be released within 16 consecutive hours on that day.
That does not mean 16 hours of driving. The applicable 11-hour driving limit still applies.
The same-location and return-to-location requirements#
The driver still has to return to the same reporting location. This isn’t a general long-day exception for any trip that runs late.
If the day starts from one reporting point and ends somewhere else, don’t assume the 16-hour exception fixes it.
Five previous qualifying workdays#
The driver must have used the standard short-haul provisions for the previous five duty tours. In plain language, the recent work pattern has to show true short-haul operation before this longer-duty-window exception can be used.
That detail matters because some carriers try to use the 16-hour rule after a mixed week of local and non-local runs. That’s where a single missed condition can wreck the analysis.
How often the exception may be used#
In general, a driver may use the 16-hour exception once in any 7 consecutive days, unless the driver has had a qualifying 34-hour restart. Because these details turn on the actual facts of the operation, it’s smart to verify edge cases with FMCSA guidance or a qualified compliance resource instead of guessing.
Short-Haul Recordkeeping: What Drivers and Carriers Still Need to Keep#
Qualifying short-haul drivers generally do not have to prepare RODS, but the motor carrier still has to maintain time records. Those records need to show when the driver came on duty, when the driver was released, total hours on duty, and the time for the preceding seven days when applicable.
That recordkeeping requirement is part of the rule, not extra admin. Under 49 CFR 395.1(e), the carrier has to be able to show what actually happened.
Required time records for qualifying short-haul drivers#
At minimum, keep the driver’s report time, release time, and total on-duty hours for the day. If the driver is used for the first time or intermittently, the carrier also needs the total time on duty during the preceding seven days when required.
That means a vague note like “worked local” isn’t enough.
Six-month retention period#
Carriers must keep qualifying time records for six months. That’s a long enough window that sloppy record habits tend to catch up with small fleets later, usually when an audit or claim forces someone to prove what the truck was really doing.
Supporting documents that make time records easier to defend#
Time sheets help, but they shouldn’t stand alone. Dispatch records, GPS or location data, bills of lading, fuel receipts, maintenance entries, and gate or yard timestamps can all support the day’s actual route and work pattern.
A clean time sheet cannot cure a day that really exceeded the radius or duty window. If the operation changed, the records need to match the real trip.
A simple owner-operator and small-fleet process#
Use one routine every day: confirm the reporting location, record on-duty start time, monitor route changes, document release time, and save supporting records in one place. That gives you something defensible if FMCSA asks questions later.
If your operation is growing from “mostly local” into a wider radius or mixed freight profile,
about keeping insurance aligned with your current radius, authority, equipment, and cargo.
Use This Trip-by-Trip Short-Haul Compliance Check#
Use a trip-by-trip compliance check before dispatch and again whenever the day changes. The safest approach is to document the actual workday, not the planned workday.
Before dispatch#
Confirm the normal reporting location, calculate the 150 air-mile radius, verify the driver had the required off-duty time, and check whether the day is realistically set up to return within the standard duty window.
Also decide your fallback logging plan before the truck rolls.
During the route#
Reassess the day if the route changes, a receiver delays unloading, a breakdown happens, or dispatch adds stops. A trip that qualified at 7 a.m. can stop qualifying by lunch.
At the end of the duty day#
Confirm whether the driver returned to the same reporting location and was released within the required window. Then save the time record and supporting documents while the day is still fresh.
When to stop and use standard logging procedures#
If the truck is about to cross the radius, miss the return location, or blow past the allowed duty window, stop assuming it’s a short-haul day. Evaluate the 16-hour exception separately, and if it doesn’t fit, use standard compliant logging procedures.
FAQ#
How to qualify for short haul exemption?
To qualify for the short-haul exception, start with the actual trip, not the driver’s job title. The driver must be operating under the applicable FMCSA HOS framework, start and return to the same normal work-reporting location, stay within a 150 air-mile radius, and be released from duty within the standard 14-consecutive-hour window. The driver also needs the required off-duty time before the shift starts. Even when the exception applies, the underlying HOS limits still apply, and the carrier still has to keep the required time records for qualifying days.
How to use 16-hour short haul exemption?
Use the 16-hour exception only after checking its separate conditions. It is not an automatic add-on to every long local day. A qualifying property-carrying driver must return to the same reporting location, meet the prior five-duty-tour requirement tied to standard short-haul operation, and stay within the rule’s frequency limit. The exception extends the duty window to 16 consecutive hours, but it does not create 16 hours of legal driving. The 11-hour driving limit still applies, so treat it as a narrow exception, not a general rescue rule.
What is Trump’s new CDL law?
There isn’t one simple federal rule that should be treated as “Trump’s new CDL law” for short-haul compliance. Drivers often mix up CDL licensing rules, enforcement policy changes, proposed legislation, training standards, and HOS exceptions. If you’re hearing a claim like that, verify it through current FMCSA guidance and your state’s CDL agency before acting on it. Don’t rely on political shorthand from social media or truck-stop talk, because licensing rules and HOS rules are different topics and can change on different timelines.
What criteria must be met to use the 16-hour short haul big day exception?
The practical criteria are pretty specific. The driver must be in a qualifying property-carrying operation, return to the normal work-reporting location, and be released from duty within 16 consecutive hours instead of 14. The driver also must have used the standard short-haul provisions for the previous five duty tours, and the exception generally can be used only once in seven consecutive days unless a qualifying 34-hour restart resets eligibility. It helps to check the facts in 49 CFR Part 395 before relying on the rule for a long day.
Does the short-haul exemption mean I don’t need an ELD at all?
Not exactly. It means you may be excepted from using an ELD and preparing RODS on days when every short-haul condition is met. It does not mean your operation is permanently outside logging rules, and it does not erase HOS requirements. If a day runs outside the 150 air-mile radius, misses the return location requirement, or goes beyond the allowed duty window, you need a compliant way to create and retain the required duty-status record for that day. That’s why small fleets should have a backup logging procedure before dispatch changes happen.
