Driver onboarding in 90 minutes: what your TMS should make easy

The last time I helped a fleet onboard a driver "properly", we lost two days to paperwork. He arrived at 07:00 on a Monday eager to start. He left at 16:00 on Tuesday still not on a truck. Between those two timestamps sat a paper licence form filled in twice because the first copy went in the bin by accident, a DBS portal that wouldn't accept his middle name, a vehicle inspection booklet nobody had reordered, and a forty-minute hunt for the dispatcher who held the only laptop with the driver-account-creation screen on it. By the time he did his first run on the Wednesday, he'd been paid for fourteen hours of standing around and we'd missed two slots at a regional DC.

That's the version every transport manager I know has lived through at least once. And it's the reason I'm going to argue something that sounds aggressive: driver onboarding should take 90 minutes, not two days. Not 90 minutes of corner-cutting — 90 minutes of doing the same job, with software that doesn't make you do it three times.

Why fleets still take days

The thing that kills onboarding isn't the legal work. The DVLA licence check takes about two minutes once you've got the driver's check code. A DBS verification, where you actually need one, runs in the background — you don't sit and wait for it. Working time directive briefings are a fifteen-minute conversation with a printed handout. None of those are the blocker.

The blocker is how many people and systems the driver has to touch before they can do their first run. In most fleets I've seen, that list looks something like this: HR creates a payroll record. Compliance creates a CPC/tacho card record. The TMS admin creates the user account — but only after the compliance record exists, because the account needs a "type". The dispatcher assigns a route, but only after the account exists, because the route picker won't accept a driver who isn't active. The yard manager hands over keys, but only after the route exists, because the vehicle is locked to the route. The driver downloads the mobile app, but the app needs a temporary password that expires in 24 hours and got emailed to the HR inbox, not the driver. And so on.

Every one of those steps is fine on its own. Stacked, they take two days because the dependencies are serial and the systems are different. Each handover is a separate human waiting on the previous one to finish. Your driver is the courier between four software systems that don't talk.

Fix the dependencies, and you fix the timeline.

The 90-minute timeline

Minutes 0-15: Pre-arrival prep

This block happens before the driver walks through the door. If it doesn't, you're not doing 90-minute onboarding, you're doing 90-minute theatre on top of two days of slack.

The transport manager creates the driver record the day before. Not a payroll record, not a DBS record — the operational record in the TMS. Name, mobile number, licence categories, CPC expiry, tacho card number. Pick a four-digit PIN. Assign the driver to a depot. Pre-assign them to a run for tomorrow — the run can be a supervised one, doesn't have to be a real revenue run. Print the induction pack: a one-page summary of the depot's start/end times, fuel-card PIN policy, and the emergency dispatcher number.

That's it. Fifteen minutes the day before, done while the kettle boils. The point is the driver arrives to a system that already knows who they are.

Minutes 15-30: Compliance

The driver arrives, signs in, and sits down with you (the manager) at a screen. Not at a desk with three forms — at a screen with a TMS open to their record.

Licence check: the driver gives you their DVLA check code, you paste it into the gov.uk portal, you screenshot the result and attach it to the driver record. Two minutes. DBS verification, if your contracts demand it: the basic DBS check happens through an online provider in five minutes; the result lands in your inbox over the next hour and you attach it then. You don't wait for it. Working time directive briefing: the printed handout from the induction pack covers it. You walk through the daily and weekly driving limits, the 45-minute break rule, and what "other work" means on the tacho. The driver signs the bottom of the handout. You scan it into the driver record on your phone.

Fifteen minutes for compliance. The trick here is that nothing is blocked on a different department. HR and payroll happen in parallel — they're not on the critical path to getting the driver on a truck.

Minutes 30-50: Vehicle handover

The yard manager joins you for this block. Keys for the vehicle the driver is assigned to. Fuel card with the PIN written on a separate card (never on the fuel card itself). A quick walk to the vehicle for the inspection demo.

The vehicle inspection is the bit most fleets still do on paper. Don't. The driver opens the mobile app — which you're about to install — and walks through the inspection on their phone. Lights, tyres, mirrors, wipers, AdBlue, oil, body damage. Each item is a tap. Defects get a photo. The signed-off inspection lands in the TMS attached to the vehicle, time-stamped, with the driver's name. If there's a defect, the dispatcher sees it before the driver gets back in the cab.

The first time a driver does this they'll fumble. That's the point of doing it during onboarding, not on day one of solo runs.

Minutes 50-70: System walkthrough

Driver app install. The driver hands you their phone, you scan a QR code from the TMS, the app installs and pre-fills their employee number. They tap their PIN. They're logged in.

That's the whole login flow. Not a username, not a password, not a "forgot password" link to a personal email account that the driver hasn't checked since 2019. A PIN, on a registered device, against a known employee number. If the device changes, the manager re-pairs it from the TMS in ten seconds.

Then you run a "start job" demo. Pull up a sample shipment — a test one in the dev environment, or a real one that's scheduled for tomorrow — and walk the driver through the flow. Tap "start job". The app asks them to confirm the vehicle. They tap go. The map shows the collection address. Tap "arrived at collection". Tap "loaded". The map updates to the delivery address. Tap "arrived at delivery". The POD screen comes up. Sign with a finger, take a photo of the pallets in the bay, tap "complete".

That's the entire driver-side flow. Drive, arrive, collect, drive, arrive, deliver. Five taps per stop. The driver does it twice with you watching, asks two or three questions, and they've got it.

The other thing you cover in this block: POC (proof of collection) capture when something goes wrong. Damaged pallet at collection — photo, note, supervisor flag. Customer not on site at delivery — refused-delivery flag with a reason code. You spend ten minutes on the exception paths because that's where new drivers panic, and a driver who panics calls dispatch, and a dispatch call costs you ten minutes you don't have.

Minutes 70-90: First real shift starts

The driver climbs into the cab. They start their first job. They're supervised — either you ride along for the first collection, or you put them on a "co-driver" run where the second driver is a senior who can talk them through the first POD.

The supervision matters less than the fact that the driver is on a truck doing work within ninety minutes of arriving. Everything they were going to learn on day two of paperwork onboarding, they're going to learn faster by doing it once for real with a fallback.

What your TMS needs to make easy

The 90-minute timeline only works if your TMS does five things well. If any one of these is missing, you fall back to two days.

Per-driver PIN provisioning, not username/password. A driver should log in with a four-digit PIN on a device the manager has paired. Usernames and passwords belong on the back-office side. The driver's phone is a single-purpose work tool — treat it like a card reader, not a laptop.

Mobile-first job flow. Drive, arrive, collect, drive, arrive, deliver. Five states per stop. Each transition is one tap. The driver should never have to choose between sixteen menu items to find "I've arrived". If your TMS makes drivers think, your TMS is wrong.

GPS-on-by-default with a clear opt-out path. Tracking shouldn't be a checkbox the driver might forget. It should be on the moment the job starts, off the moment the shift ends, and the driver should know exactly when it's on. No surprise tracking, no "wait, was it recording?" arguments. The default is on during a job; the default is off during a break.

Offline-capable POD/POC capture. Drivers go into rural delivery points with no signal. The app has to capture the signature, the photo, the timestamp, and queue them locally. When the signal comes back, the data syncs. If your driver has to drive to higher ground to upload a POD, you've already lost the customer.

Self-service shift management. The driver clocks on from their phone when they arrive at the depot. They clock off the same way. They don't ring dispatch. They don't sign a paper sheet. Their timesheet is built from their shift state and their job states automatically. The dispatcher sees a live board of who's on shift; the manager sees a payroll-ready timesheet at the end of the week.

Get those five right and 90 minutes is achievable. Get them wrong and you're back to two days.

Where most TMS implementations fail

Three failure modes show up over and over.

Multi-step logins. The driver app asks for a company code, then a username, then a password, then a 2FA code from an email the driver hasn't set up. By the time they're in, they've forgotten what they were doing. I've watched senior drivers — twenty years on the road — give up and hand the phone to the manager. That's a TMS failure, not a driver failure.

Dispatcher-dependent shift starts. "Ring in when you arrive so I can mark you as on shift." The dispatcher is on the phone to a customer when the driver calls. The driver waits. The driver's first hour is already 20 minutes of waiting. Multiply by twelve drivers per depot and you've burned three hours of paid time before any wheels turn. Self-service clock-on solves it permanently.

Paper-based vehicle checks. A paper book in the cab. The driver ticks the boxes. The book gets handed in at the end of the week. The defect from Monday is read on Friday. The vehicle has been on the road for four days with a known fault. This is a compliance disaster waiting to happen and it's purely a software gap. A digital vehicle inspection lands the defect in dispatch in real time.

If any of these sound familiar, your onboarding timeline is being set by your tooling, not by the work.

The "first 30 days" follow-up

Ninety minutes gets the driver in a cab. The next thirty days is where you confirm the onboarding actually stuck. Three metrics, watched per-driver, sorted weakest-first:

GPS hygiene. What percentage of the driver's shift has live GPS pings? A new driver should be hitting 95%+ within their first week. If they're at 60%, they're either forgetting to start jobs in the app or they've discovered the airplane-mode workaround. Either way it's a conversation, not a punishment — but the data has to be in front of you.

POD completion rate. What percentage of delivered shipments have a signature and a photo attached within ten minutes of the "delivered" tap? A trained driver hits 98%+. A new driver should be at 90% in week one and climb. If they're stuck at 75%, the demo block in the onboarding didn't land and they need a second walkthrough.

Exception flag rate. How often does this driver flag a stop as an exception — refused, damaged, customer-not-on-site? New drivers over-flag because they're nervous. Experienced drivers under-flag because they want to keep moving. The interesting drivers are the ones who flag consistently with photos and notes — that's the behaviour you want to compound across the fleet.

You can review all three in five minutes per week per driver if your TMS gives you the dashboard. If it doesn't, you'll review none of them and onboarding ends at minute 90 with no follow-up loop. Which is exactly how drivers drift back into paper-on-the-dashboard habits within a quarter.

The point

Two-day onboarding isn't a sign that you're being thorough. It's a sign that your tooling is making you do the same job in five places. The legal work is fast. The paperwork is fast. The driver wants to be on a truck and you want them on a truck. The only thing standing between you is a stack of systems that don't share a record.

Pick a TMS where the driver record, the route, the vehicle, the inspection, the app login, the GPS, and the timesheet are all the same record from the same screen, and ninety minutes stops being aspirational. It becomes the default. Loaditude's logistics management is built around that single-record principle — and the delivery tracking is the same screen the driver, the dispatcher, and the customer all see.

Onboarding is the first impression a driver has of how the fleet runs. Make it the impression that says: we know what we're doing, and we're not going to waste your time.