A driver leaves the terminal at 6:10 a.m. The route looks local, every customer is nearby and the truck is expected back before dinner. At 7:55 p.m., dispatch still describes the day as “short haul.”
That label does not settle the question. The federal short-haul exception depends on whether the driver satisfied every condition of the exception for that particular duty period, not whether the route felt local.
A truck can stay well inside the 150-air-mile boundary and fail because the driver is released too late. Another driver can finish early and fail because one operating point falls outside the radius. A third can satisfy the operational test while the carrier keeps inadequate time records.
The paperwork can be simpler under the short-haul exception. The rule itself is not.
Treat the exception as four gates
For a property-carrying driver using the federal short-haul provision in 49 CFR § 395.1(e)(1), a useful review starts with four questions.
| Gate | Question to answer | What should the carrier be able to verify? |
|---|---|---|
| Distance | Did the driver remain within the permitted radius? | Every operating point remained within 150 air-miles of the normal work reporting location |
| Return | Did the driver come back to the required location? | The driver returned to the normal work reporting location |
| Time | Was the driver released in time? | Return and release occurred within 14 consecutive hours |
| Records | Can the carrier prove the day? | Required time records are accurate, true and retained |
For a property-carrying driver, there is another condition sitting behind that table: at least 10 consecutive hours off duty must separate each 14-hour on-duty period.
Passing three gates does not compensate for failing the fourth.
That sounds obvious when written in a table. In daily dispatch, it is where shortcuts begin.
A dispatcher sees “local.”
A driver sees “no overnight.”
An owner-operator sees “home every night.”
None of those phrases appears in the regulatory test.
The 150-air-mile boundary is not the whole exception
The distance figure gets most of the attention because it is the easiest part to remember.
FMCSA currently permits a driver using § 395.1(e)(1) to operate within a 150-air-mile radius of the normal work reporting location.
The regulation gives the equivalent as 172.6 statute miles.
That does not mean:
“Any route shorter than 172.6 road miles qualifies.”
The rule describes a radius around the normal work reporting location. Actual highway mileage can be longer because roads do not travel in straight lines.
For a carrier that regularly runs close to the boundary, relying on a driver’s impression that a customer is “about 150 miles away” is a weak control.
The better question is operational:
Where is the normal work reporting location, and can the carrier demonstrate that every point of the qualifying operation remained inside the permitted radius?
For a one-truck business running the same local lanes every week, that may be straightforward.
For a carrier taking spot freight, construction work, service calls or changing delivery points, it deserves more attention.
The boundary does not move because today’s load pays well.
The 14-hour requirement has two verbs: return and release
Distance is only half of the common mistake.
Section 395.1(e)(1) requires the driver, except a driver-salesperson, to return to the work reporting location and be released from work within 14 consecutive hours.
Consider this day:
| Event | Time |
|---|---|
| Driver reports | 5:45 a.m. |
| Final delivery completed | 5:10 p.m. |
| Truck returns to terminal | 6:35 p.m. |
| Fueling and post-trip work completed | 6:55 p.m. |
| Driver released | 7:00 p.m. |
The duty period is 13 hours 15 minutes.
Assuming the other conditions are met, the timing can fit the short-haul exception.
Now change only one fact.
A customer delay pushes the return back by 55 minutes.
The driver is released at 7:55 p.m.
The operation may still look local on a map. The driver may still have returned to the same terminal. But the 14-hour short-haul condition has been exceeded.
This is one of those rules that looks simple until the truck is already moving.
A 14-hour duty period does not create 14 driving hours
Another mistake comes from treating the maximum short-haul duty period as a driving allowance.
It is not.
FMCSA’s property-carrier guidance states that a driver using the short-haul exception remains limited to 11 hours of driving time after the required off-duty period. The separate 11-hour and 14-hour rules still matter even when the driver does not complete a daily RODS.
So this does not work:
“He is short haul, so he can drive until the end of the 14th hour.”
The daily clocks still matter.
A driver might spend part of the shift:
- loading;
- unloading;
- fueling;
- inspecting equipment;
- waiting while on duty;
- completing paperwork;
- performing other work.
Those activities can consume the duty window without adding driving time.
The short-haul exception changes the method used to document the day. It does not turn the HOS rules off.
The real benefit is a time record instead of a daily RODS
When § 395.1(e)(1) applies, the driver is exempt from the normal requirements of §§ 395.8 and 395.11.
Practically, that means a qualifying driver can use the short-haul time-record system instead of completing the normal daily record of duty status.
That distinction matters.
The exception is sometimes described casually as:
“Short-haul drivers do not have to log.”
A carrier operating on that assumption can create a compliance problem very quickly.
There still has to be a record.
Under the current regulation, the motor carrier must maintain accurate and true time records showing:
- the time the driver reports for duty each day;
- the total number of hours the driver is on duty each day;
- the time the driver is released from duty each day;
- the total time for the preceding seven days for a driver used for the first time or intermittently, when § 395.8(j)(2) applies.
The carrier must retain these records for six months.
A clean form does not fix a bad process.
If dispatch, payroll and the time record each show different start or release times, the fact that a short-haul sheet exists is not particularly reassuring.
What a useful short-haul record looks like
The regulation identifies the required information. It does not require a carrier to build an elaborate daily compliance packet.
For a small carrier, simplicity is an advantage if the information is reliable.
A practical record might look like this:
| Date | Report time | Release time | Total on-duty hours | Short-haul status |
|---|---|---|---|---|
| Sept. 14 | 06:10 | 18:05 | 11.92 | Qualified |
| Sept. 15 | 05:55 | 19:42 | 13.78 | Qualified |
| Sept. 16 | 06:05 | 20:18 | 14.22 | RODS required |
The final column is not one of the specific data fields listed in § 395.1(e)(1).
It can still be useful as an internal control.
It forces somebody to ask whether the exception actually applied instead of assuming that every driver assigned to “local” operations qualified automatically.
For carriers using payroll software, dispatch systems or time-clock applications, the same principle applies: the system should produce the information the carrier needs and the records should remain retrievable for the required period.
Four days that look similar but produce different answers
A rule becomes easier to apply when the borderline cases are separated.
Day A — comfortably inside the limits
The driver:
- reports at 6:00 a.m.;
- remains inside the 150-air-mile radius;
- drives 9.5 hours;
- returns to the normal reporting location;
- is released at 6:40 p.m.;
- had more than 10 consecutive hours off before reporting.
Result: the day can qualify under § 395.1(e)(1), assuming the remaining requirements are satisfied and the carrier maintains the required time record.
Nothing unusual here.
That is what the exception is designed for.
Day B — local route, late release
The driver:
- reports at 5:30 a.m.;
- remains inside the radius all day;
- returns to the terminal at 7:10 p.m.;
- completes a post-trip inspection;
- is released at 7:42 p.m.
Elapsed time: 14 hours 12 minutes.
Result: the driver cannot rely on the short-haul exception for that day.
The problem is not mileage.
It is time.
Day C — early finish, one stop outside the radius
The driver:
- reports at 7:00 a.m.;
- performs several nearby deliveries;
- accepts one additional stop beyond the permitted radius;
- returns to the terminal at 5:15 p.m.
The shift lasts only 10 hours 15 minutes.
Result: the short duration does not rescue the exception. Once the operation goes outside the qualifying radius, the driver no longer meets the short-haul conditions for that day.
This is why adding a late spot load deserves a compliance check before dispatch clicks “accept.”
Day D — the exception breaks unexpectedly
The driver begins a normal short-haul day.
A road closure and customer delay make it clear late in the shift that the operation will no longer satisfy the short-haul conditions.
FMCSA’s driver guidance says that when the driver cannot meet the terms of the exception, the driver must complete a RODS for that day as soon as the exception no longer applies.
That transition is where the carrier needs a procedure.
Waiting until next week to reconstruct the day from memory is not a procedure.
Paper RODS or ELD? Count the non-qualifying days
A driver who normally qualifies for short haul does not automatically need an ELD because of one unusual day.
FMCSA explains the distinction through the 8-days-in-30 threshold.
If the driver is required to complete a RODS on 8 or fewer days within the previous 30 days, the driver can generally use a paper RODS for those days.
If the driver is required to complete a RODS on more than 8 days in any 30-day period, the driver generally needs to use an ELD when subject to the ELD rule, unless another exception applies.
The broader device rule and its other exceptions are covered in the ELD requirements and exemptions guide.
This creates a simple but important carrier control:
count exception days before the ninth one happens.
A carrier running local freight most of the month can drift into ELD territory gradually:
- one long regional load;
- two weeks later, another;
- several days covering another lane;
- an unexpected customer assignment;
- a driver helping a different operation.
Each individual day may look harmless.
The 30-day history is what changes the answer.
The 30-minute break works differently for qualifying short-haul operations
For property-carrying CMV drivers operating under § 395.1(e)(1), FMCSA states that the driver is also excepted from the required 30-minute break provision while operating within the short-haul exception.
That does not mean a carrier should stop tracking the issue entirely.
The important moment is the point at which the driver discovers that the short-haul exception will not work for that day.
FMCSA has specific guidance for a driver who unexpectedly exceeds the short-haul limitations after enough driving time has passed that the break issue becomes relevant.
The agency’s guidance says the driver is not automatically in violation merely because the driver could not have predicted earlier that the short-haul exception would fail. The driver should annotate the RODS explaining why the break was not taken earlier and take the break at the earliest safe opportunity.
That is a narrow compliance answer to an unforeseen situation.
It should not become a dispatch strategy.
Do not confuse § 395.1(e)(1) with the non-CDL short-haul exception
There is another short-haul provision in § 395.1(e)(2) for certain property-carrying CMVs that do not require a CDL.
It is not simply the same rule with a different vehicle.
The non-CDL provision has its own conditions, including rules that can permit driving beyond the 14th hour on a limited number of days.
Mixing the two exceptions is an easy way to create a policy that is wrong for both groups.
For a carrier operating a mix of equipment, the compliance file should identify which exception is actually being used.
“Short haul” is not specific enough.
This guide focuses primarily on the § 395.1(e)(1) 150-air-mile short-haul exception commonly relevant to CDL property-carrying operations.
The reporting location can change between shifts—but not within the shift
The 150-air-mile radius is measured from the driver’s normal work reporting location. FMCSA’s current short-haul training materials clarify an important point: the start and end location may differ from one shift to another, provided the driver starts and ends each individual shift at the same reporting location.
That means a carrier is not necessarily locked to one terminal forever. A driver can legitimately begin one qualifying shift from one reporting location and another shift from a different reporting location if the facts support that arrangement.
What the carrier should not do is use one location to start a shift and another to finish it while treating the same shift as qualifying short haul. The radius for that shift also needs to be measured from the reporting location actually being used.
For carriers moving drivers among terminals, yards or project sites, a clean control is to record the reporting location with the daily time record. That makes the radius analysis reproducible later instead of dependent on memory.
The map should follow the operation, not be reconstructed after the fact to make the route fit.
A dispatch check can prevent most short-haul failures
For a small operation, the control does not need to be complicated.
Before assigning a route as short haul, dispatch should know:
Before departure
- What is this driver’s normal work reporting location?
- Are all planned operating points inside the permitted radius?
- Has the driver received the required off-duty time?
- Is the driver’s recent RODS history approaching the ELD threshold?
During the shift
- Is the estimated release time still within 14 consecutive hours?
- Has a new stop changed the radius analysis?
- Has a delay made short-haul qualification doubtful?
At release
- What time was the driver actually released?
- Did the day satisfy every short-haul condition?
- Was a RODS required?
- Has the carrier’s six-month time record been captured accurately?
Notice what is missing from that list:
“Did the driver go home tonight?”
Going home is not the legal test.
A seven-minute overrun should not be treated as rounding
Suppose a driver reports at 5:00 a.m. and is released at 7:07 p.m.
The carrier’s timesheet system rounds the shift to:
5:00 a.m. — 7:00 p.m.
That may be convenient for payroll.
It is not a good reason to rewrite what happened for HOS purposes.
The regulation requires accurate and true time records.
A carrier should be wary of payroll rounding, automated time-clock rules or administrative habits that make a non-qualifying day appear compliant.
Seven minutes can look trivial.
For a rule containing a specific 14-consecutive-hour condition, it is not a number I would want a compliance process to silently erase.
The carrier should be able to reconstruct a day without interviewing the driver
Six months after a September route, an investigator may not care that everybody remembers it as an ordinary local day.
The records should answer the basic questions themselves:
- when did the driver report?
- when was the driver released?
- how much on-duty time was accumulated?
- what was the normal reporting location?
- did the operation stay within the radius?
- was a RODS required instead?
- if it was, was paper permitted or should an ELD have been used?
Not every one of those facts has to appear on one federal form.
The carrier’s records, taken together, should make the answer understandable.
That is a better standard than simply asking whether a time sheet exists.
A monthly short-haul audit can be very small
For a one-to-five-truck carrier, I would not build a complicated compliance dashboard just to administer this exception.
A monthly sample can be enough to reveal whether the process is drifting.
Pick several short-haul days and compare:
- dispatch assignment;
- start and release times;
- actual route;
- driver time record;
- any RODS generated during the month;
- the driver’s rolling 30-day count of RODS-required days.
Then ask one uncomfortable question:
If one of these days did not qualify, would our current process actually catch it?
If the answer depends on the driver remembering to mention it, the control is weaker than it looks.
The exception simplifies records, not responsibility
The short-haul rule is valuable precisely because genuinely local operations do not always need the full logging process used for over-the-road work.
That is a meaningful simplification.
It is not a different universe of hours-of-service compliance.
The carrier still needs to know where the driver operated, when the duty period started, when it ended, how long the driver drove, whether sufficient off-duty time preceded the shift and whether the exception continued to apply throughout the day.
The best short-haul process is therefore not the one with the most paperwork.
It is the one that makes a non-qualifying day difficult to miss.