The 90-Day Number Your ATS Isn't Tracking

Open almost any driver recruiting system and follow a record forward. Lead, contacted, interviewed, documents collected, orientation, hired. The pipeline ends there. The record stops moving, the recruiter gets credit, the campaign gets attributed, and the last event ever written to that driver is the day they started.

Which means the system has no opinion about the most expensive thing that can happen next.

TL;DR

• Recruiting systems are built to end at the hire event. Turnover happens after it.
• Tracking retention at 30, 60 and 90 days changes which campaigns and which recruiters look good.
• The leave reason is the field that pays for the whole exercise.
• Early attrition is usually an expectation problem set during recruiting, not an operations problem.

Why the hire event is the wrong finish line

A driver who leaves at week six cost the full acquisition price and produced a fraction of the revenue that justified it. Under standard reporting, that hire counts identically to one still driving at eighteen months.

The consequences compound quietly:

• A recruiter who fills seats fast with drivers who leave fast outranks a slower recruiter with durable hires. Both are measured on hires.
• A campaign that attracts drivers shopping on pay alone looks like your best campaign, because it converts. Those are also the drivers most likely to leave for the next carrier offering four cents more.
• Cost per hire drifts steadily away from cost per productive seat, and nobody notices because only the first one is calculated.

What to record, and when

Retention tracking does not need a new system. It needs four fields on the hire record and a job that checks them.

• hired_at — the date, kept separately from the lead creation date so days-to-hire stays calculable.
• day_30_retained, day_60_retained, day_90_retained — three booleans, filled by a scheduled check.
• left_at and leave_reason — the date and the cause.
• recruiter_id and the source that produced the lead, carried forward from the pipeline.

Three checkpoints are enough. Thirty days captures orientation and first-dispatch failures. Sixty captures the settlement-shock window, when the first few real paychecks land and either match what was promised or do not. Ninety is the point where a driver who is still there is likely to stay.

The leave reason is the whole point

The booleans tell you how much turnover you have. The reason tells you what to do about it, and it is the field most likely to be left blank.

Keep the list short and specific enough to act on. Pay expectation not met. Home time not as described. Equipment. Dispatch or miles. Personal or medical. Terminated. Went to another carrier.

The first two are recruiting problems, not operations problems. If a meaningful share of your ninety-day attrition sits there, the fix is in what your ads and your recruiters are promising, and it is cheap to fix compared with everything else on the list.

What it changes

Once the data exists for a couple of quarters, three decisions get easier and one gets uncomfortable.

Campaign evaluation. Rank campaigns by ninety-day survivors rather than hires. The order usually changes. A campaign with a higher cost per hire and better retention is often the cheaper campaign on any honest accounting.

Recruiter evaluation. This is the uncomfortable one. Recruiters have never been measured this way and the first report will produce arguments. Introduce it as a shared diagnostic rather than a scorecard for the first cycle. The recruiters with good numbers will make the case for you.

Bonus structure. If a hire bonus pays out on day one, it pays the same for a driver who leaves in five weeks. Splitting it — part at hire, part at ninety days — aligns the incentive with the outcome the carrier actually wants. This is a change to make carefully and announce clearly, because it looks like a pay cut if it is presented badly.

Referrals. Referred drivers usually retain better. Without retention data that is folklore; with it, it is a budget argument for a referral program.

Start with what you already have

You do not need a year of history to begin. Take your last twenty hires, find out which ones are still driving, and write down why the others left. It is an afternoon of phone calls to dispatch and payroll.

That single table will tell you more about your recruiting spend than the last four campaign reports, because it is the first time the two ends of the process have been in the same place.

Then instrument it going forward so you never have to reconstruct it again.

Fleegital records the hire event with the lead's origin intact and tracks each hire at 30, 60 and 90 days with a leave reason — so campaign and recruiter performance can be read against seats that lasted, not seats that were filled.

Key takeaways

• The hire event is a milestone, not an outcome. Recruiting reporting should not end there.
• Thirty, sixty and ninety days cover the three distinct reasons early hires fail.
• Leave reason is the field that turns a turnover number into a decision.
• Ranking campaigns by ninety-day survivors usually reorders them.
• Reconstruct your last twenty hires by hand this week, then instrument it so you never do that again.