A qualifying split-sleeper pairing for a property-carrying driver uses two rest periods that meet the rule's duration and location conditions and total at least ten hours. The ELD can calculate availability, but the driver and carrier still need to verify the pairing and applicable rules.
What this means for your fleet
Train with complete 24-hour examples and have drivers check the earlier and later qualifying periods together. Do not rely on a single “available hours” number when a rejected or unpaired segment changes the calculation.
Worked 7+3 recap
A property-carrying driver takes 3 consecutive hours off duty, later takes 7 consecutive hours in the sleeper berth, and uses those two periods as a qualifying pair. The periods total 10 hours, neither is shorter than 2 hours, and one includes at least 7 consecutive sleeper-berth hours. For the recalculation, the qualifying periods are excluded from the 14-hour window and driving immediately before and after each period is tested together against the 11-hour and 14-hour limits.
If a later edit shortens the 7-hour sleeper period or places work inside either period, the pair must be recalculated. The ELD recap is an aid; the retained record should identify both event ranges and the rule set reviewed.
What to check
Use these checks before changing a log, policy, device, integration, or buying decision.
| Check | How to verify |
|---|---|
| 1. Verify the driver and rule set | Cite the current property- or passenger-carrier provision and keep driver, operation, rule set, reviewer, and dated applicability decision. |
| 2. Identify both qualifying periods | Retain both rest periods with start/end, duration, status, sleeper-berth location where required, original events, edits, and pairing ID. |
| 3. Check total and sleeper-berth conditions | Show the duration total and each condition, excluded time, rule calculation, pass/fail result, reviewer, and effect of any later edit. |
| 4. Review recalculated driving window | Save the original and recalculated 11/14-hour or applicable window, both paired periods, driving segments, calculation version, exception, and reviewer. |
| 5. Annotate unusual context | Keep the unusual fact, specific annotation, supporting event/location context, current provision, qualified decision, and retained audit history. |
Common failure modes
- Pairing two non-qualifying breaks.
- Assuming any 7/3 clock split works.
- Ignoring a later edit that breaks the pair.
Limits and exceptions
This guide does not decide a fact-specific legal exception, certify a record, or guarantee a compliance, safety, cost, or audit outcome. Keep the original ELD record and any edit history. Use the current official rule for applicability and the exact installed-device manual for screen-by-screen actions.
Sources, review date, and limits
Reviewed August 10, 2026. Each source supports only the point described beside it. Rules and product details can change; recheck dynamic facts before changing a fleet workflow or signing a contract.
- Current 49 CFR Part 395 text covering HOS limits, exceptions, RODS, supporting documents, ELD duties, and technical requirements — Office of the Federal Register and U.S. Government Publishing Office.
- Editing, annotation, certification, and original-record preservation — Federal Motor Carrier Safety Administration.
- Current first-party product, plan, feature, and support representations; dynamic facts require release-date recheck — Factor ELD.
Review the exact operation
Bring the driver, vehicle, trip, jurisdiction, current official rule, and original ELD record for a qualified determination. Factor ELD can demonstrate its current product; rule applicability remains a fleet compliance decision.