The mileage log is a byproduct, not a chore
A routed day already contains everything the IRS asks for. Making a rep type it again on Friday is where the money and the goodwill leak out.
Adam DeLeon · Founder, Adelo CRM
6 min read
Ask a field rep what they do on Friday afternoon and a lot of them will say the same thing: the mileage log. Open the spreadsheet, scroll back through the calendar, guess at the order of Tuesday, look up the address of the office on the far side of the bayou, type it all in, add it up, send it to the manager. Nobody likes doing it, and almost nobody does it well.
Here is the thing. By Friday the company already has every fact that log is supposed to contain. It just has them in the wrong place.
What the IRS actually wants
The rules for a mileage reimbursement that holds up are shorter than people think. For each trip the record needs the date, where you went, why you went, and how far it was. Four things. Keep them for every business trip, at or near the time of the trip, and a cents per mile reimbursement at the federal rate is not taxable income to the rep. Miss them and it is.
Now look at a routed day. The plan has the date. It has every stop, by address, in the order the rep drove them. It has the reason for each one, because the stop is on the plan for a reason: an appointment, a cadence that was due, a coverage call on the way past. And it has the distance, because the planner computed the legs on real roads to build the order in the first place. All four elements, written down before the rep left the house.
The Friday log is a rep reconstructing, from memory, a document the system wrote on Monday.
What that costs, in numbers you can redo
Take a ten rep team. Say a typical planned day is around ten and a half miles, which is what a tight metro territory with six stops comes to, and say there are twenty one field days in a month. Redo this with your own figures; the shape holds.
- At the federal rate of 76 cents a mile, ten and a half miles is $7.98 a day. Over a month that is about $168 a rep, and about $1,680 across the ten.
- If each rep spends fifteen minutes on Friday rebuilding the week, that is two and a half hours of selling time a week across the team, or about ten hours a month. At any reasonable cost of a rep hour, the time spent writing the log is worth more than the smallest reimbursement on it.
- Logs built from memory drift. Round a few legs up, forget a coverage stop, double count a return trip, and a ten percent error either way is normal. On $1,680 a month that is $168 the company paid for nothing, or $168 a rep was owed and never got.
None of those numbers is large on its own. Together they are a few thousand dollars a year and a standing argument between the field and finance, over a document that could have written itself.
The log should fall out of the day
The fix is not a better spreadsheet, and it is not a tracker that follows the rep around and asks them to swipe left or right on every drive at the end of the day. Both of those still treat the log as a separate job. The fix is to let the plan be the record.
When the route and the log live in the same place, a finished day is already a finished entry: the stops that were worked, in order, with the miles between them priced at the rate in force that day. The rep confirms what changed, which is usually nothing or one stop, and goes home. The manager sees planned against worked without asking. Finance gets a log where every line points at a stop on a plan, which is a much better answer to an audit than a spreadsheet and a shrug.
That is the whole idea behind running mileage inside the CRM rather than next to it. The day plan is the expensive part to get right. Once you have it, the mileage log is free.
A finished route is already a mileage log. Nobody should have to type the same day twice.
If you only change one thing
Stop asking reps to produce the log on Friday. Ask them to confirm it on the day, from the plan they drove, while the day is still in their head. Whatever tool you use, that single change fixes most of the drift and gives back most of the Friday. If the tool can build the entry from the route by itself, better still. That is what Adelo Drive does, and the plan it reads is the one Adelo CRM wrote.
Written by Adam DeLeon, Founder, Adelo CRM. Every figure in this piece is either arithmetic you can redo (the inputs are stated in the text) or it is labeled as an assumption. None of it is a customer outcome. No Adelo CRM customer has agreed to be named yet, and we would rather say so in the footer of every post than imply one.