Last week's Business Update established a foundational truth about Network 2.0: 
paying your drivers by the hour is the margin-protective move. Paying by the day — the model most Ground-only contractors grew up with — guarantees your driver a fixed income regardless of how long the route actually takes or how efficiently the work gets done. In a world where you are now running both Express time-definite stops and Ground volume on the same routes, that guaranteed-pay structure bleeds money every time a driver takes longer than planned.
But knowing that hourly pay is the right structure is only half the problem solved. The harder half is this: actually running an hourly operation is fundamentally different from running a daily one. The habits, the oversight cadence, the role of your Business Contact, the way you think about equipment, the way you handle afternoons — nearly all of it changes. Contractors who switch to hourly pay without changing how they manage will not capture the margin benefit. They will simply have a new pay structure layered on top of an old operational approach, and the numbers will not improve the way they should.
This post walks through what managing by the hour actually requires — the shifts in thinking, the systems you need, and the specific areas where most contractors leave money on the table during the transition. If you made the move to hourly or are about to, this is the operational framework you need to back it up.
Why the Management Model Has to Change Along with the Pay Structure
Before getting into the specifics, it is worth being clear about why this is not just a payroll adjustment. When you pay by the day, the financial incentive structure for your driver is simple: show up, get paid. Whether the route takes ten hours or six hours, the check is the same. Your oversight role as a contractor was largely reactive — you dispatched in the morning and handled problems as they arose. If a driver was slow, it cost you some service quality. It rarely cost you direct dollars, because the driver's pay was fixed anyway.
Hourly pay flips that dynamic. Now every hour on the clock is a cost you are incurring in real time. A driver who takes eleven hours to run a route you engineered for eight hours just cost you three extra hours of labor at whatever your hourly rate is. If that rate is $20, that is $60 of unplanned cost on one route, on one day. Multiply that across a fleet of ten drivers over a month and the math gets painful quickly. The margin you intended to capture by moving to hourly pay evaporates if you do not manage hours actively.
This is not a criticism of drivers — it is a description of incentive structures. When people are paid by the hour and supervision is loose, routes expand to fill available time. That is human nature, not a moral failing. The contractor's job is to build a management system that keeps hours disciplined and communicates expectations clearly throughout the day.
Shift Thinking: It Is Not a Route Anymore — It Is a Shift
The most important conceptual shift in moving to hourly management is this: your drivers are no longer assigned to routes. They are assigned to shifts. That distinction matters more than it sounds.
A route is a collection of stops to be delivered. A shift is a defined block of time with a start, an expected end, and performance benchmarks that apply throughout. When you manage by route, the implicit understanding is "deliver these stops and you're done." When you manage by shift, the understanding is "you are working from 8:00 AM to 4:30 PM, and here is what should be accomplished within that window."
This shift-based framing requires two things you probably do not have in your operation today: defined and enforced shift start times, and planned dispatch times that are used for engineering purposes.
Defined shift start times mean that your drivers are expected at a specific time, staging is complete at a specific time, and dispatch happens at a specific time. This is not optional in a Network 2.0 operation. Express time-definite commitments are exactly that — time-definite. A 10:30 AM commitment does not become an 11:15 AM commitment because the station's preload ran late. You need to know your planned dispatch time and engineer your operation around it.
Which brings up a critical issue that most contractors are not yet handling properly: FedEx preload end times that do not support your planned dispatch time. This happens more than it should. When it does, you have two jobs. First, contingency plan in real time so your Express commitments are not missed. Second, document every occurrence carefully, because these are compensable events in your settlement negotiations. A station that routinely delivers late-preloaded vehicles to your contractors is creating a unique operational cost that belongs in the settlement discussion. If you are not recording it, you cannot recover it.
Real-Time Monitoring: The BC Role Has to Change
Here is the thing that separates contractors who capture the margin benefit of hourly pay from those who do not: active, real-time monitoring of driver progress.
In the old daily model, a Business Contact could make the morning dispatch and then pivot to other tasks — vendor calls, vehicle issues, administrative work — with a vague awareness of where the drivers were. Drivers would check in when they had a problem. That is a trouble-shooter model. It worked tolerably well when driver cost was fixed.
It does not work in an hourly model. When driver cost is accumulating by the minute, your BC needs to be a dispatcher — actively tracking progress, comparing actual position and stop counts against the planned route timeline, and communicating with drivers throughout the day. Good performance needs to be acknowledged. Pace problems need to be addressed in real time, not at the end of the day when the damage is already done.
This is a significant cultural shift for most operations. Many experienced BCs have built their identity around being the person who handles emergencies. Asking them to shift into a proactive monitoring role — to call a driver at 1:00 PM because their stop count suggests they are running 45 minutes behind — requires both a clear directive from the contractor and a change in daily habit. It also requires your BC to have the right tools: real-time visibility into driver location and stop progress.
The practical upside is real. A BC who catches a driver running behind at 1:00 PM can often make a simple intervention — a reroute suggestion, an instruction to skip a problem stop and return later, a call to the customer on the tricky business stop — that saves 30 to 45 minutes. At $20 per hour, that is $10 to $15 per intervention, per driver, per day. Across a fleet of eight drivers, a proactive BC is worth thousands of dollars a month in recovered efficiency.
Afternoon Pickups: A New Priority You Probably Are Not Ready For
Ground-only contractors largely ignored the afternoon. Pickups were a modest tail on the day — handle what's there, get the drivers in. That era is over.
Network 2.0 means your routes now include Express services, and Express means same-day on-call pickups are a real operational requirement. A customer calls FedEx for a pickup, that call gets routed to your station, and your BC needs to coordinate a driver response — often within a tight window. If your closest available driver is already running behind on their delivery route, you have a conflict. If you have not built a process for afternoon pickup coordination, you will resolve that conflict badly, usually by making a costly AVP dispatch or missing the pickup commitment entirely.
This is one of the areas where part-time hourly drivers become a legitimate business tool rather than just a fallback for callouts. A part-time driver who comes on at 1:00 PM to handle afternoon pickups and tail-end deliveries can protect your full-time drivers' route efficiency while ensuring pickup commitments are met. The math only works if you have engineered the deployment carefully — a part-time driver dispatched without clear purpose is just an added cost — but done right, this structure protects both your service performance and your dispatch yield.
Equipment: The Time-Definite Environment Has No Patience for Breakdowns
In a Ground-only operation, a vehicle breakdown was disruptive and expensive, but the service implications were manageable. Ground packages have multi-day transit tolerances. A service failure on a Ground package was bad, but it was recoverable.
Express time-definite packages do not have that tolerance. A 10:30 AM commitment is a contractual obligation. A vehicle breakdown at 9:45 AM on a route with Express volume is not just an operational problem — it is a service failure that affects FedEx's relationship with that customer, and it creates pressure on your BC to respond immediately with whatever resources are available, often at significant cost.
The financial discipline here is preventive maintenance. Your vehicles must be in reliable condition, full stop. Deferred maintenance in an hourly, time-definite environment is not a cost savings strategy — it is a deferred expense that will surface at the worst possible moment, with cost multipliers attached. A vehicle that breaks down at 9:45 AM with Express freight costs you the emergency dispatch response, the service failure risk, and the lost productivity of a driver sitting on the side of the road. Track your maintenance intervals, do not skip PMs, and have contingency vehicle plans documented before you need them.
Dispatch Yield: Your Daily Financial Scorecard
Every day you operate, you should know two numbers for each dispatch: what it generated in revenue and what it cost to run. The difference is your dispatch yield, and in an hourly operation, this number requires active management both before and after the day.
Before the day: your BC and route engineers should have a planned yield expectation based on the forecasted volume, the planned dispatch time, and the expected hours in the field. That planned yield is your benchmark.
After the day: actual yield is calculated using real hours worked, real fuel, and real stop count. The gap between planned and actual yield tells you exactly where your operation is leaking — and in an hourly model, the primary driver of that gap is almost always hours. Too many hours in the field is the most common margin problem in the transition to hourly pay.
Here is a concrete illustration. A route with 120 stops, engineered at 8 hours, generating $480 in revenue from FedEx at $4.00 per stop average. Your planned labor cost at $20 per hour for 8 hours is $160. Add $60 in fuel and vehicle costs. Planned dispatch yield: $480 - $220 = $260. Now that driver runs 10.5 hours due to slow pace in the afternoon. Labor cost jumps to $210. Yield falls to $210 — an $50 swing on a single dispatch, in a single day. That driver running 10.5 hours three times per week costs you $150 per week, $600 per month, $7,200 per year on that one route alone. Multiply across your fleet and it is not a small number.
The BCs who cost contractors the most money are not the ones who make big, visible mistakes. They are the ones who make small, low-visibility decisions throughout the day — authorizing an extra service stop that was not efficient, allowing a driver to extend rather than pushing for pace — that chip away at yield in amounts that never trigger alarm but compound relentlessly.
Five Additional Considerations When Transitioning to Hourly Management
Beyond the core operational shifts above, there are several factors that contractors frequently underestimate when making this transition. Getting them wrong does not just cost money — it can expose you to legal liability or undermine the cultural changes you are trying to make.
1. Overtime compliance is not optional, and the rules are more complex than you think. Moving to hourly pay means your drivers are clearly W-2 employees whose hours you are tracking. Under the Fair Labor Standards Act, non-exempt employees must receive 1.5 times their regular rate for hours worked beyond 40 in a workweek. The Motor Carrier Act exemption — which removes overtime obligations for certain drivers — only applies when the vehicle has a GVWR over 10,001 pounds. Many Sprinters, cargo vans, and smaller step vans used in Network 2.0 operations fall under that threshold, meaning the MCA exemption does not apply. Additionally, some states layer daily overtime requirements on top of federal rules. Contractors operating in California, for example, owe overtime for hours beyond 8 in a single day. Before you deploy an hourly pay structure, know your vehicle GVWR classifications and your state's specific requirements. Getting this wrong invites back pay claims and penalties that can quickly dwarf any margin gains from the pay structure change.
2. Time-tracking infrastructure is now a business requirement. In a daily pay model, precise time records were largely irrelevant. In an hourly model, they are foundational — for payroll accuracy, for overtime calculations, and for your own management visibility into where hours are going. A manual timesheet process is a liability. Drivers estimating their hours after the fact is a compliance exposure and a data quality problem. You need a system — whether that is a mobile time-clock app, an integration with your existing route management software, or a dedicated tool — that captures actual clock-in and clock-out times daily. Those records also become your primary data source for analyzing dispatch yield and identifying pace problems. The investment in a reliable time-tracking system pays for itself quickly.
3. Driver communication and performance feedback must become daily habits. In the daily pay model, most performance communication happened reactively — a contractor or BC addressed problems when they escalated. Hourly management requires a different cadence. Drivers need to understand their pace expectations at the start of every shift, receive check-in communications mid-day when they are running ahead or behind, and hear brief performance feedback at the end of each day. This is not micromanagement — it is the basic accountability structure that keeps an hourly workforce operating at the pace you need. Drivers who consistently run long without feedback will not self-correct; they simply will not know there is a problem. Establish the feedback cadence now, while the hourly model is new, so it becomes routine before habits calcify.
4. Your settlement documentation strategy needs to reflect the new operational reality. Network 2.0 brings Express services, and Express services bring new sources of operational variability that affect your costs. Late preloads that delay planned dispatch times. Spike volume days that push hours beyond your planned model. On-call pickups that redirect drivers mid-route and extend the day. Each of these is a cost event — and each is a potential negotiating point in your settlement discussions with FedEx. But you can only negotiate what you have documented. Start building a systematic log of preload completion times, dispatch times, on-call pickup volume by day, and any other operational variables that create cost you did not plan for. That documentation is your financial defense in settlement negotiations and your evidence base when requesting adjustments to your contract terms.
5. Driver retention takes on a new dimension in an hourly model. In a daily model, most experienced drivers understood what their day would pay and planned accordingly. Hourly pay introduces variability — particularly for drivers who are accustomed to setting their own pace and may now feel more monitored. The contractors who manage this transition well communicate clearly with their drivers about why the model is changing, what the expectations are, and how performance will be assessed. Drivers who understand the system and feel they are being treated fairly adapt. Drivers who feel they are being watched without context or explanation become disengaged and eventually leave. Given the recruiting costs and Qual Cert investment involved in bringing on a new driver in Network 2.0, losing experienced drivers to a poorly communicated pay structure change is an expensive mistake. The conversation about hourly pay should happen before the paycheck changes, not after.
Putting It Together: A Framework for Hourly Workforce Management
This is a lot of change happening at once. Here is a practical sequence for getting it right.
- Reclassify dispatches as shifts. Every route becomes a shift with a defined start time, planned dispatch time, and expected end time. Engineer those times around your actual volume and Express commitments. Post them. Enforce them.
- Establish preload contingency protocols. Know what you will do when the station's preload end time does not support your planned dispatch. Document every late-preload occurrence with times and volume details — you will need that data.
- Retrain your BC as a dispatcher. Define what active monitoring looks like during the day, at what intervals your BC checks driver progress, and what communication happens when a driver is running ahead of or behind pace. Make this a written expectation, not a verbal understanding.
- Build afternoon pickup coordination into the daily plan. Identify which driver(s) are positioned for afternoon on-call response. If volume justifies it, evaluate a part-time afternoon shift to handle pickups without disrupting delivery route efficiency.
- Implement a time-tracking system before you move to hourly pay. Do not run an hourly pay structure on manual timesheets. Get the infrastructure right first.
- Know your overtime exposure. Pull the GVWR ratings on every vehicle in your fleet. Know your state's overtime rules. Calculate the overtime cost exposure in your payroll model before it shows up on a paycheck you were not expecting.
- Log everything that varies from plan. Late preloads, spike volume days, on-call pickups, extended hours, equipment issues. This is your settlement documentation and your margin analysis data. Build the habit now.
The Path Forward
Network 2.0 is not a temporary disruption — it is the operational environment FedEx Contracted Service Providers will compete in for the foreseeable future. The contractors who thrive in it will be the ones who build the management systems, the oversight discipline, and the financial visibility to run a genuinely efficient hourly operation. The hourly pay structure is the right foundation. Managing it correctly is what turns that foundation into margin.
If you are working through this transition and are not sure where your gaps are — in your BC's role, your dispatch yield tracking, your settlement documentation, or your overtime compliance — that is exactly the kind of challenge eTruckBiz Inc. works through with contractors every day. Our team has deep inside knowledge of how FedEx operations actually work, and we have helped CSPs across the country build the operational and financial infrastructure to compete effectively in Network 2.0. Reach out to us at etruckbiz.com to start the conversation.