HOS / ELD Simulator

HOS / ELD SIMULATOR Training + Planning Use: learn rules visually + reduce violations

HOS & ELD Simulator: see how your log changes before you learn the hard way.

This simulator helps drivers, dispatchers, and safety teams understand Hours-of-Service by showing how duty status, breaks, and sleeper decisions play out on an ELD-style timeline. Test scenarios, spot violations early, and build confidence with a workflow that feels like real log management.

Simulator Scenarios Rules basics How to use FAQ
Launch Simulator Tools Hub Compliance Hub
  • Practice real-world HOS decisions (status changes, breaks, and planning).
  • See violations before they happen (time limits, recap timing, and improper breaks).
  • Understand how edits/annotations affect a log review mindset.
  • Train teams faster with consistent scenarios and repeatable outcomes.
Best use
Run scenarios
Common mistake
Break timing
Big win
Fewer violations
Next best click
Compliance hub
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 AM • Boise, 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.