A transit commitment is easy to write and hard to keep if it ignores geography. Across the Western states, the same number of miles can include mountain grades, desert heat, coastal congestion, winter passes, or a wildfire detour that did not exist when the routing guide was printed. Hours-of-service rules still cap the legal day. An appointment window is not the same thing as a must-arrive-by promise, and a tracking map is not the same thing as a guarantee.
Shippers who buy freight across Teocal’s published twelve-state territory need language that a dispatcher, a plant manager, and a customer service team can all defend. The aim is to describe a realistic window, name the variables that can move it, and agree how both sides will share information when the plan changes.
Start with the actual map, not with a single number of days
Teocal’s US Western State Freight Delivery page lists twelve contiguous states: Arizona, California, Colorado, Idaho, Montana, Nevada, New Mexico, Oregon, Texas, Utah, Washington, and Wyoming. That list is useful because it is specific. It is not a transit-time table. A Hayward-to-Phoenix run, a Kent-to-Salt Lake City run, and a Denver-to-Dallas run ask different things of a driver even when a mapping app reports similar hours.
Mountain passes, urban approaches, and long stretches with limited services all affect whether remaining drive time is actually usable. The FHWA Office of Freight Management and Operations publishes national freight-network context that shippers and public agencies use when they think about bottlenecks and the cost of delay. It will not give you a private SLA, but it will remind a procurement team that highway performance belongs in the transit conversation.
When you ask for a commitment, describe origin, destination, pickup and delivery constraints, and whether the freight is a live load, a drop, or a multi-stop run. A single “two-day transit” line that ignores those facts is how two honest teams later argue about a day that was never defined.
Leave room for a legal day
Federal hours-of-service rules for property-carrying drivers live in 49 CFR Part 395. The familiar limits include 10 consecutive hours off duty before a new driving window, a 14-hour on-duty window, 11 hours of driving time, a 30-minute interruption of driving after 8 hours of driving, and weekly 60-hour/7-day or 70-hour/8-day limits, with a 34-hour restart available under the rule. Exceptions exist in section 395.1; they are not a general waiver that lets a shipper write any arrival time it wants.
Those limits belong in transit language even if you never recite the section numbers to a customer. If a quoted window assumes continuous driving with no pickup dwell, no delivery dwell, no required break, and no place to stop, the window is not a transportation plan. It is a hope that someone else will absorb the conflict. Build pickup and delivery time into the commitment, and say whether the clock starts at pickup, at dispatch, or at another defined event.
Do not ask a carrier to promise a result that would require a driver to operate past a legal limit. If a must-arrive time cannot be met without that conflict, change the pickup time, the loading method, or the promise itself.

Say whether you are booking an appointment or a must-arrive time
An appointment is a planned window at a dock. A must-arrive-by time is a harder promise and should be priced and planned as one. Many Western receivers use appointment systems that can refuse an early or late truck even when the highway part of the trip went well. If your customer needs the freight on the floor by a production start, say so, and ask what happens if weather, a prior stop, or a missed dock causes a miss.
Write the difference into the routing guide. “Deliver on Tuesday by appointment” is not the same sentence as “must arrive Tuesday by 7 a.m. or production stops.” The second sentence requires a buffer, a named after-hours contact, and an agreed fallback such as a later door, a controlled-yard drop, a layover, or a revised production plan. If no fallback exists, the commitment is more fragile than it looks.
Consider a Reno-to-Denver machinery delivery that has to meet a Wednesday maintenance window — an illustration, not a customer claim. The honest conversation includes mountain routing, pickup dwell, a legal rest plan, and what happens if the receiver cannot open the door at the promised hour. A neat two-day line that skips those questions will not become more accurate in bold type.
Write weather and disruption language you can actually use
Western lanes are exposed to winter storms, high winds, heat restrictions, and seasonal wildfire or smoke events that can close or slow a route. You do not need to predict a particular fire or storm to write a contingency sentence. You do need to say who watches conditions, who may reroute, and how a delay will be communicated.
National Weather Service forecasts and alerts are one public source shippers and carriers can use when they talk about weather risk. State transportation departments publish highway conditions and closures. Those tools should inform the conversation on the day of the run, not be used later as if a newer forecast had been available when the load was tendered.
Useful contract language describes process rather than blame: if a route becomes unsafe or closed, the carrier will notify the shipper using a published dispatch contact, propose an alternate route or a later appointment, and document the reason. The shipper will identify who can approve a change to the receiving window. That is clearer than a clause that simply says “subject to weather” and leaves both sides to argue about what it excused.
Teocal’s dispatch center page describes 24/7 Northern California dispatch coverage. If after-hours notice is part of your transit commitment, say how you want that coverage used. A must-arrive promise with no night contact path is incomplete.

Use location visibility as shared information, not as a warranty
GPS can give both sides a common picture of where a tractor is and whether it is still moving. Teocal’s GPS shipment tracking page describes dispatch using GPS devices to monitor location, status, and condition between distribution points and delivery sites, with activity alerts on a secure internet platform used by dispatch personnel. That published capability can support a transit conversation. It does not guarantee an arrival time, and it does not replace a phone call when an appointment needs to move.
Agree what visibility you expect: how often location is reviewed, who is notified if a tractor dwells unexpectedly, and how quickly the shipper will hear about a delay. Then match those expectations to the commitment. A routine appointment may need a check-call and an exception alert. A production-critical must-arrive may need named contacts on both sides and a pre-agreed fallback if the map and the clock disagree.
When you compare carriers, verify the legal name you are buying from with FMCSA’s SAFER Company Snapshot. A precise transit sentence is worth little if written about one company and performed by another.
Do not hide geography inside a scorecard
On-time measurements are only as honest as the promise underneath them. If every Western lane is scored against the same number of days, a mountain run and a short coastal drain will look like a quality difference when they may be a planning difference. Separate lanes that share similar distance, appointment rules, and dwell from lanes that do not. Then compare carriers against the sentence you actually wrote, not against an unofficial faster time mentioned on a call.
If you use a percent-on-time report, define the start and stop events. Does the clock begin when the truck is dispatched, when it arrives for pickup, or when it leaves the dock? Does it end at check-in, at unload complete, or at a customer milestone the driver cannot see? Those definitions matter more than the adjective in front of transit. A report that silently changes definitions from month to month will create arguments that no map can settle.
Be cautious with penalty language tied to arrivals. A fee that assumes the carrier controls every variable, including a prior customer’s overtime, a receiver that will not accept an early truck, or a closed mountain pass, will either be ignored or produce disputes instead of better planning. If you want a consequence for a missed must-arrive time, tie it to a clearly defined commitment that already includes dwell, legal rest, and a named fallback.
Match the hardness of the promise to the people who have to keep it
Procurement can write a tight sentence. Operations has to live with it, and dispatch has to staff it. Before you lock a must-arrive time across several Western states, ask the people who schedule docks whether they can receive at that hour, including after a weather delay. Ask dispatch whether the pickup appointment leaves enough legal time for the route. If either answer is no, change the sentence before it is printed in a routing guide.
Shared visibility helps only if someone is assigned to act on it. A map that nobody watches will not protect a production window. Pair location updates with a named contact at the shipper and the carrier, and decide in advance who may authorize a later door or an inland hold. That is especially important when the freight crosses state lines and the receiving plant is in a different time zone or on a different calendar from the shipping dock.
None of this requires you to accept vague service. It requires you to buy the kind of commitment the lane can support. A realistic appointment window, honestly scored, is more useful than an aggressive must-arrive sentence that everyone treats as optional.
A short way to draft the next commitment
Before you lock a Western transit sentence, try to complete this list:
- Origin, destination, and any intermediate stops, with pickup and delivery appointment rules.
- Whether the promise is an appointment window or a must-arrive time, and what happens if that time is missed.
- How pickup dwell, delivery dwell, required rest, and a realistic route were included in the window.
- Who communicates a weather, closure, or congestion change, and through what published number.
- What location visibility dispatch will use, and what it will not be asked to guarantee.
If you cannot complete the list, you are not ready to score the carrier against the sentence. Ask Teocal dispatch to walk through the origin, destination, and timing you have in mind, and to say which parts are appointments, which parts are estimates, and which parts would require a harder, separately agreed commitment. A clear transit conversation will not flatten the Western map, but it will keep the next scorecard from treating geography as an excuse after the fact.
Sources
- Federal Highway Administration, Office of Freight Management and Operations: https://ops.fhwa.dot.gov/freight/
- Electronic Code of Federal Regulations, 49 CFR Part 395: https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395
- Federal Motor Carrier Safety Administration, SAFER Company Snapshot: https://safer.fmcsa.dot.gov/CompanySnapshot.aspx
- Teocal Transport, US Western State Freight Delivery: https://teocaltransport.com/us-western-state-freight-delivery/
- Teocal Transport, GPS Shipment Tracking: https://teocaltransport.com/gps-shipment-tracking/
- Teocal Transport, Contact the Dispatch Center: https://teocaltransport.com/contact-the-dispatch-center/