DOT Hours of Service Calculator (2026) – Free, No Login

FG 2026 • Free Tool Driver-friendly Educational • Not legal advice

DOT Hours of Service Calculator (2026)

This DOT hours of service calculator helps truck drivers estimate the 11-hour drive limit, 14-hour duty window, split sleeper options, and weekly recap time — fast, clear, and mobile-friendly.

How the DOT hours of service calculator works

Use the DOT hours of service calculator to enter your on-duty start time and logged hours, then review your estimated drive time remaining and when your day ends. You can also explore split sleeper strategies and whether a 30-minute break is due based on driving time.

Built for real-world HOS planning

If you’re comparing HOS scenarios for dispatch planning, trip timing, or safe parking decisions, this DOT hours of service calculator gives a quick estimate you can verify against your ELD and company policy.

Home (Depot: 11:30 PM) Driver: Demo Driver • TZ: Local • Rule: Property (Interstate)
Connected
GPS OBD
!
i
Time to next break FMCSA 30-min rule • engine adjusts by rule set
07:55
Available Drive Time
Driving (11:00)
05:20
Remaining
Shift (14:00)
07:43
Remaining
Cycle
07:43
70/8 Remaining
DOT alignment note: This UI is designed to mirror real ELD workflows (status changes, logs, annotations, certification, DVIR, inspection mode). Your JS engine must implement the actual rule math and retain an audit trail for edits (who/when/why).
Important: This is a planning/training HOS calculator UI. It is not an FMCSA-certified ELD. Verify compliance decisions with official FMCSA guidance and your carrier’s safety policy.
Duty status Now: 8:30 AM
Current status
ON since 03:13 AMBoise, ID
ON
Personal Conveyance (PC) Off-duty movement rules
Yard Move (YM) On-duty not driving
Adverse Conditions Exception indicator
Split Sleeper 7/3 or 8/2 planning
Team mode Driver A / Driver B switcher active. Engine should ensure correct assignment of driving segments.
?
Unidentified driving 0 events pending review (placeholder).
System ready UI loaded. Your engine will populate timers, logs, and warnings.
!
Break reminder Next required break in 00:17 (placeholder).
!
Violation state (placeholder) Engine will show active violations here (drive/shift/cycle exceeded).
34-hour reset tracker: Not in progress
Safety: A real ELD should lock most interactions when duty = Driving and vehicle speed exceeds a threshold. Your engine should implement a lockout overlay except for critical roadside info.
Logs Select day • edit • annotate • certify
Log: Today
DOT-style grid placeholder. Engine can render as SVG/canvas and sync with event list.
Event Timeline 🔒 Not certified
OFF
12:00 AM → 03:13 AM
Boise, ID • Odo: 123,456 • Notes: —
ON
03:13 AM → 04:00 AM
Boise, ID • Yard checks • Annotation: —
D
04:00 AM → 08:30 AM
I-84 East • Shipping Doc: BOL-123 (placeholder)
Manual entry: Use “Add Event” or “Edit” to enter start/end times. Engine must require an edit reason when modifying certified logs.
DOT audit expectation: Logs should include driver, carrier, vehicle, trailer, shipping document, time zone, and daily certification. Your engine should preserve a clear edit history (original event, edited event, who approved, reason).
DOT Snapshot Carrier • vehicle • shipping docs
Carrier
Freight Girlz (placeholder)
USDOT: • MC:
Driver
Demo Driver
ID: • Co-Driver:
Vehicle / VIN
Tractor 001
VIN: • Odometer:
Trailer(s)
Trailer 100
Add/keep current per dispatch and safety policy.
Shipping Docs
BOL-123 (placeholder)
Bill of lading / manifest reference.
Certification
Not certified
Engine should lock certified days unless edited with note & policy.
!
Edits & annotations Make edit reasons mandatory, especially after certification. Consider “carrier approve required” policy in admin.
DVIR Vehicle inspection report
Brake lights Status: Needs repair (placeholder)
Tire (rear) Status: Monitor (placeholder)
Tip: Keep DVIR workflows consistent (pre-trip / post-trip). Engine can store history and export for audits.
DVIR History Recent reports
Last DVIR: Completed Yesterday • Tractor 001 • Trailer 100 (placeholder)
!
Follow-up required Defect marked “needs repair” should be tracked until resolved (engine).
DriverProfile & compliance
Driver name
Demo Driver
Time zone: Local • Rule: Property
Cycle rule
70/8
Engine should enforce cycle + recap rules.
Documents (placeholders)
Medical / License
Optional: reminders & expiring docs (engine).
Driver entry: Your engine should allow duty changes + manual add/edit events, but require: edit reasons, location context, and a signature token for daily certification.
Quick actionsCommon tasks
!
Reminder (placeholder) Engine can surface “recap needed”, “certify yesterday”, “missing trailer”, etc.
Safety note: Do not interact with devices while driving. Engine can enforce lockouts when duty = D.
VehicleTractor / trailer / OBD
OBD link (placeholder) Engine can display ECM hours, odometer, and sync state here.
!
GPS drift check Engine should flag improbable movements or missing location samples.
Trailers & DocsAudit completeness
DOT readiness: Many roadside checks focus on whether logs are complete (vehicle, trailer, shipping docs, time zone, certification). Engine should keep these fields visible and easy to update.
SettingsRules, display, exports
Rule set
Property / US (Interstate)
Supports Passenger • Oilfield/RMODS • Intrastate profiles.
Lockouts
Driving lock (engine)
Recommend lockout when moving; allow roadside essentials.
Export formats
CSV • PDF • Roadside Pack
Engine will implement export + print-ready format.
Dev warning: Keep time math in UTC internally, then render per driver time zone. Store rule profile + cycle in each day’s metadata to prevent “recalc drift.”
SupportHelp & diagnostics
UI version FG-ELD-UI-1.0.0 • Engine version will show here later.
!
Do not drive distracted Show a lockout overlay when duty = Driving, except for critical alerts (engine).
Dispatcher ConsoleTrip planning & compliance preview
What-If planning Engine can simulate schedule changes without altering certified logs.
!
Compliance guardrails Show “earliest legal depart”, “break due”, “cycle recap”, “split option” suggestions.
Dispatcher note: Your engine should keep dispatcher actions separate from driver-certified records unless carrier policy allows edits/requests.
Active WarningsFleet view slot
!
Break due soon Placeholder. Engine will populate based on selected driver and rule profile.
!
Potential violation Placeholder. Engine can flag if planned route exceeds legal limits.
Carrier AdminPolicy & audit controls
Admin warning: If you allow edits after certification, require reason + user identity + timestamp + optional approval chain. Keep original events preserved for audit.
DiagnosticsData integrity slots
Time sync Engine should show last sync time + drift check.
!
Missing required fields Engine should flag missing VIN, trailer, shipping docs, or certification.
Inspection Mode (Roadside)
DOT Snapshot ready Show driver, carrier, vehicle, trailer, shipping docs, time zone, and last certification.
!
Driving lockout Engine should prevent editing while moving; inspection view should be read-only.
Note: This overlay is UI-only. Your engine will toggle data-on="1" and fill the snapshot fields.
DOT Rules • HOS • ELD • “Social Media Confusion” Explained

Everything a Class A CDL driver (and fleet manager) needs to know about DOT (HOS) rules

This is the practical, real-world version of the rules: what inspectors look for, what trips drivers up, and how to write a fleet policy that keeps everyone compliant without killing productivity.

Built around FMCSA’s major HOS updates (30-minute break, adverse conditions, short-haul, split sleeper) and FMCSA’s official Personal Conveyance guidance and ELD FAQs. :contentReference[oaicite:0]{index=0}

Driver view Dispatcher view Admin view

HOS basics (the “non-negotiables”)

  • Driving window + break logic: Rules changed so the 30-minute break is triggered by 8 hours of driving time (not “on duty time”), and an on-duty/not-driving period can count as the break. :contentReference[oaicite:1]{index=1}
  • Split sleeper is real (and legal): Drivers can meet the 10-hour minimum by pairing a 7+ hour sleeper period with a 2+ hour off-duty (in or out of the berth), as long as the two periods total 10 hours; qualifying periods don’t count against the 14-hour window the same way a straight shift does. :contentReference[oaicite:2]{index=2}
  • Adverse conditions got expanded: The driving window can be extended by up to 2 additional hours under the adverse driving conditions exception (when truly unforeseen). :contentReference[oaicite:3]{index=3}
  • Short-haul got expanded: FMCSA expanded the short-haul exception to 150 air-miles and allowed a 14-hour work shift as part of the exception (when you meet all conditions). :contentReference[oaicite:4]{index=4}
Fleet manager takeaway: Most “violations” you see in audits come from bad status choices (PC/Yard), sloppy edits without notes, and inconsistent company policy—not because drivers don’t know what 11/14 means.
Audit readiness Safety Documentation

Supporting documents (what backs up the log)

FMCSA guidance says supporting documents are key for verifying RODS and identifies 5 categories in the regulations. :contentReference[oaicite:5]{index=5}

What counts as a “supporting document”?

Supporting documents are records created in the normal course of business that can verify a driver’s RODS. FMCSA identifies five categories (described in regulation) and treats them as evidence the log matches reality. :contentReference[oaicite:6]{index=6}

Practical rule: If it shows where, when, and what the driver did (fuel, tolls, BOLs, receipts, dispatch/telematics), it can help—or hurt—depending on whether your log matches.
ELD edits: can drivers/carriers delete mistakes?

FMCSA’s ELD FAQ makes it clear that deleting ELD records is not permitted. Corrections are handled by edits/annotations, and the original record is retained with an “inactive” status. :contentReference[oaicite:7]{index=7}

Carriers/support staff can propose changes, but edits by anyone other than the driver require the driver’s electronic confirmation or rejection (to prevent manipulation). :contentReference[oaicite:8]{index=8}

Fleet policy tip: Require a short, standardized annotation format for every edit: “WHAT changed + WHY + supporting reference (dispatch/ticket/BOL)”.
Most-misunderstood PC vs On-duty Enforcement risk

Personal Conveyance (PC): what it CAN and CAN’T be used for

The big idea (plain English)

Personal Conveyance is meant for personal use of the commercial vehicle when the driver is relieved from work and the movement is not for the benefit of the motor carrier. Inspectors focus on the “benefit to carrier” test and whether the driver was truly off duty.

Simple test: If you’re moving the truck to make the load happen (pickup/delivery/positioning/avoiding detention), it’s probably not PC.
Common “allowed” examples (done correctly)
  • Driving from a safe/legal parking spot to food/lodging after being relieved from duty.
  • Commuting in the CMV when the carrier allows it and you’re not advancing the load.
  • Moving for personal reasons that aren’t connected to picking up, delivering, or positioning freight.

These examples are consistent with FMCSA’s PC guidance framing: personal use, not benefiting the carrier, driver relieved from duty.

The “NOT allowed” stuff drivers argue about online

FMCSA’s PC guidance repeatedly warns against using PC to advance the load or otherwise benefit the motor carrier.

  • Using PC to get closer to the receiver/shipper for a better appointment or to beat traffic.
  • Leaving a shipper and PC’ing toward the delivery because “I’m tired” (that’s still freight movement).
  • PC to find parking after you already drove past safe parking to “make more miles.”
  • PC after being told to reposition by dispatch (that’s a work instruction → on-duty movement).
Fleet manager takeaway: PC needs a written policy (allowed situations, max distance/time, mandatory annotations). Without policy consistency, it becomes an audit magnet.
PC & ELD precision: what changes in the record?

FMCSA’s ELD FAQ notes that when PC is selected (when configured/allowed by the carrier), the CMV’s location is recorded with lower precision (approx. a 10-mile radius), and PC appears differently on the graph grid. :contentReference[oaicite:12]{index=12}

Operations Yard ELD behavior

Yard Moves (YM): what it is and how it’s recorded

Yard Moves in the ELD (what the system must do)

FMCSA’s ELD FAQ explains that the ELD can be preconfigured to allow yard moves; when enabled, the driver selects the start and end of the yard move period, and the graph grid shows it with a different style line/shading and an abbreviation. :contentReference[oaicite:13]{index=13}

Why this matters: YM is still work. It’s not “free time.” It’s typically treated as on-duty movement inside a yard/terminal.
YM vs PC: the fastest way to get in trouble

The risk pattern in audits is drivers using PC for movements that look like on-duty yard work (spotting trailers, moving between docks, repositioning for loading). If the movement supports carrier operations, keep it out of PC.

Split Sleeper (7/3 or 8/2) — what changed and what dispatch should know

FMCSA’s HOS final rule modified the sleeper berth exception so a driver can satisfy the 10-hour minimum off-duty requirement with at least 7 hours in the berth plus a second off-duty period of at least 2 hours (in or out of the berth), as long as the two periods total at least 10 hours. :contentReference[oaicite:14]{index=14}

Dispatch tip: If your plan relies on split, make sure the driver understands: (1) the 7+ must be in the berth, (2) the other break must be 2+ off-duty, (3) totals must be 10+, and (4) clean annotations help audits.
30-minute break — the part social media gets wrong

FMCSA’s HOS updates require a 30-minute break after 8 hours of driving time (not after 8 hours since you went on duty), and an on-duty/not-driving period can qualify as the break. :contentReference[oaicite:15]{index=15}

  • Can fueling count? If your status is on-duty/not-driving and it’s 30+ minutes, yes in principle.
  • Can waiting at a dock count? If you’re properly logged on-duty/not-driving and it’s 30+ minutes, yes in principle.
  • But: if you log it wrong (or “drive” sneaks in), the clock resets and you’re out of compliance.
Adverse driving conditions — what “unexpected” actually means

FMCSA expanded the adverse driving conditions exception by up to 2 additional hours of driving time. :contentReference[oaicite:16]{index=16}

Fleet policy should define “unexpected” clearly (e.g., sudden highway closure, crash, unforecasted severe weather), and require an annotation describing what happened and why it couldn’t reasonably be known at dispatch time.

Short-haul (150 air-mile) — who qualifies and what trips fleets up

FMCSA expanded the short-haul exception to 150 air-miles and allowed a 14-hour work shift as part of the exception. :contentReference[oaicite:17]{index=17}

Reality check: The exception is not “no rules.” It’s a different compliance path with conditions—especially around returning to the work-reporting location and maintaining proper time records.
Myth busting What inspectors cite What fleets should train

“Social media confusion” — quick myth checks

“PC is fine as long as I’m off duty.”

Being off duty is necessary but not sufficient. FMCSA emphasizes the movement must be personal use and not for the benefit of the carrier. If you’re advancing the load or repositioning for work, it’s not PC.

“Dispatch told me to PC to parking—so it’s okay.”

If the movement is directed by the carrier to support operations, it starts looking like on-duty movement that benefits the carrier. PC should be driven by the driver’s personal needs after being relieved from work, under a clear company policy.

“I can delete an ELD mistake and redo it.”

FMCSA’s ELD FAQ: deleting records is not permitted. Edits/annotations must retain the original record (made inactive) and preserve the history. :contentReference[oaicite:20]{index=20}

“The 30-minute break is after 8 hours on duty.”

FMCSA updated the break requirement to be after 8 hours of driving time, and an on-duty/not-driving period can satisfy the break. :contentReference[oaicite:21]{index=21}

“Yard moves are basically off duty because I’m not on the road.”

Yard moves are a special driving category that ELDs can record when enabled; drivers mark start/end and the graph grid displays it distinctly. It’s still operational time, not personal time. :contentReference[oaicite:22]{index=22}

Fleet manager playbook Training + enforcement Audit-proofing

Fleet policy checklist (what to put in writing)

Personal Conveyance policy (make it unambiguous)
  • Define allowed PC uses (food/lodging, personal errands after being relieved, commuting if permitted).
  • Define prohibited PC uses (advancing a load, repositioning for pickup/delivery, dispatch-directed moves).
  • Set a cap (distance/time) and require a standard annotation template for PC.
  • Train dispatch to never instruct “PC to make the appointment.” That’s the fastest way to create paper trails that fail audits.

FMCSA’s PC guidance centers on personal use + no benefit to carrier + driver relieved from work.

ELD edits & annotations (prevent “log manipulation” accusations)
  • Ban deletion attempts; require edits/notes instead (records must be retained). :contentReference[oaicite:24]{index=24}
  • Require the driver to confirm/reject carrier-proposed edits and document the “why.” :contentReference[oaicite:25]{index=25}
  • Standardize note format: “status change + reason + evidence”.
Supporting docs retention & review rhythm
  • Create a weekly “mismatch review” workflow: compare dispatch, fuel, tolls, BOL timestamps vs logs.
  • Teach drivers what documents can corroborate duty status and location/time patterns. :contentReference[oaicite:26]{index=26}
  • Coach “high-risk patterns”: repeated PC near customers, repeated late edits without notes, inconsistent YM use.
Training topics that reduce violations fastest
  • 30-minute break: triggered by driving time; on-duty/not-driving can count. :contentReference[oaicite:27]{index=27}
  • Split sleeper: how to plan it without creating accidental violations. :contentReference[oaicite:28]{index=28}
  • Adverse conditions: when it applies and how to annotate. :contentReference[oaicite:29]{index=29}
  • PC vs YM: the “benefit to carrier” test and what dispatch should never say in writing. :contentReference[oaicite:30]{index=30}
Compliance note: This section summarizes high-level FMCSA guidance and rule updates. Some operations (intrastate rules, oilfield, passenger carrier, agriculture, state-specific variations) can differ—always follow your written company policy and applicable jurisdictional requirements. :contentReference[oaicite:31]{index=31}