HOS Trip Planning
Dispatcher Load Acceptance Checklist
A dispatcher checklist for accepting truck loads with realistic HOS, parking, fuel, receiver, weather, and escalation assumptions.
By Dale Connors, Founding Editor · Content reviewed quarterly against FMCSA guidance and official state resources. A load can be legal on paper and still be a poor dispatch decision. The difference usually appears before acceptance: the parking plan is vague, the receiver has no staging, the driver has fewer weekly hours than the route assumes, or weather turns a tight schedule into a fragile one.
This checklist is for the moment before the load is committed. It helps a dispatcher decide whether the plan is actually plannable, not merely possible if every stop is instant and every mile runs at posted speed.
Use it with the dispatcher HOS planning guide when the main risk is driver hours, and with the dispatcher backup parking workflow when the load ends near a high-demand parking market.
Load acceptance screen
| Question | Acceptable answer | Warning sign |
|---|---|---|
| Does the driver have the right hours for the load? | Current available hours, projected recap, and post-delivery parking move are all accounted for. | Plan uses theoretical maximum driving time and ignores loading, fuel, break, staging, or parking search time. |
| Is overnight parking named? | Plan A, Plan B, and trigger time are named before dispatch. | Parking is listed as TBD or assumed near the receiver. |
| Can the receiver handle the arrival plan? | Gate hours, staging rules, appointment window, and after-hours process are known. | Receiver parking is assumed because the map shows space nearby. |
| Is fuel planned separately from parking? | Fuel reserve and stop timing do not consume the final parking window. | Fuel and parking are both left to the last stop of the day. |
| Does weather or grade exposure change the plan? | Weather, wind, pass, and grade checks have a stop-short decision point. | The plan relies on a weather segment staying normal all day. |
When to reject or rebuild the plan
A dispatcher does not need to reject every tight load. But the plan should be rebuilt before acceptance when the only way it works is if every uncertain piece goes right. That is not a plan; that is a stack of assumptions.
Rebuild the load when the driver has no practical parking after delivery, the 14-hour window leaves no room for detention, the receiver will not confirm staging, or the weather segment has no stop-short answer.
Planning moves that help
- Ask for the driver's current HOS before negotiating the final appointment expectation.
- Name the post-delivery parking move when the receiver does not allow overnight parking.
- Separate fuel timing from the last parking decision so a long pump delay does not erase the stop window.
- Use a conservative average speed through metro, mountain, winter, or inspection-heavy corridors.
- Document the escalation point if detention exceeds the planned buffer.
- For unfamiliar lanes, check the relevant state guide or corridor guide before treating the route as routine.
Common planning mistake
The common mistake is accepting the load first and solving the planning conflict later. Once the load is accepted, the dispatcher often has fewer appointment options, less rate flexibility, and a driver who is already moving toward a fragile schedule.
A second mistake is asking only whether the driver can make pickup and delivery. The better question is whether the driver can make pickup, delivery, fuel, break, parking, and the post-delivery reset without the last hour becoming the most dangerous hour of the plan.
What to check before relying on this
- Current HOS and weekly hours, including recap or restart assumptions.
- Pickup and delivery appointment windows, gate hours, staging rules, and detention history.
- Named parking before and after delivery, including trigger time and backup.
- Fuel reserve, card or network constraints, reefer needs, and service gaps.
- Weather, wind, winter, grade, or inspection exposure on the lane.
- Carrier policy for paid parking, reserved parking, personal conveyance, rest areas, and after-hours escalation.
What makes a load acceptance checklist different from a trip checklist?
A load acceptance checklist is used before the carrier or dispatcher commits to the load. It asks whether the plan is realistic enough to accept. A trip checklist is used after the load is already in motion or assigned, when the main task is execution.
Should dispatchers reject loads with tight HOS?
Not automatically. A tight load may still be workable if parking, fuel, appointment timing, and backup decisions are clearly named. The problem is a load that only works if loading is instant, traffic is light, parking is open, and weather is normal.