Travel time between properties: the hours nobody counts
· portfolio, scheduling, labor cost
At a small portfolio the most expensive hour in a maintenance tech’s week is usually the one spent getting between properties, and it is the only hour on nobody’s schedule, nobody’s timesheet and nobody’s labor report. Whether you owe wages for a particular drive is a legal question this post will not answer — it turns on how the day is structured and on rules that differ by state and change, and the people to ask are counsel licensed where you operate and your own state labor department. What you can settle this week without any of that is smaller and has a number attached: how many times a week does your schedule move one person between two properties, and what does each move consume? Below, four times and three hours — and nobody had ever added either up.
Count the hops before you cost them
A schedule shows assignments. It does not show transitions, and the transition is what you are paying for.
An invented three-property operator in one state: a 58-room off an interstate exit, a 46-room eighteen miles away, and a 34-room on the far side of a triangle — fourteen miles from the 46-room, twenty-two from the 58-room. One maintenance tech covers all three, and on paper the week looks sensible, because every property gets seen:
| Day | Where | Hops | Miles |
|---|---|---|---|
| Monday | 58-room | 0 | — |
| Tuesday | 46-room, then 34-room | 1 | 14 |
| Wednesday | 58-room, then 34-room | 1 | 22 |
| Thursday | 34-room, then 46-room | 1 | 14 |
| Friday | 58-room, then 46-room | 1 | 18 |
Four hops and sixty-eight miles a week. Neither number is written anywhere, because the schedule was built a property at a time: each row is a reasonable answer to “who covers this hotel on Tuesday,” and the hops are what four reasonable answers add up to. Same blind spot as a portfolio report that totals hours without telling you which property drifted — the information is already in your records, in a shape that answers a different question.
What one hop actually consumes
Not the drive. The drive plus both of its ends.
| Piece | Minutes |
|---|---|
| Shutting down at the first property — tools in the van, keys back, work orders closed out | 10 |
| Driving (seventeen miles, average, mixed two-lane and interstate) | 25 |
| Starting up at the second — finding whoever knows what is broken, getting the list | 10 |
| Per hop | 45 |
Four hops at forty-five minutes is three hours a week — 150 hours a year at fifty working weeks, which against a forty-hour week is the better part of a month of that tech’s year spent arriving and leaving.
The ten minutes at each end is the part operators undercount, and it does not shrink when the properties are close together: two hotels four miles apart still cost twenty minutes of stopping and starting per hop. Distance is the cheap half.
Travel time between properties, priced three ways
Capacity. Three hours of a forty-hour week is 7.5% of your maintenance capacity, spent in transit. Take that number seriously even if every other figure here turns out not to apply to you, because it holds regardless of who pays for the drive.
Coverage. For the whole forty-five minutes of a hop neither property has the tech available, so a guest-facing problem landing in that window waits a bit over twenty minutes on average before anyone can touch it — three hours a week of that exposure. It is the coverage arithmetic for a front desk with one person and three buildings instead of one building and several people.
Wages, conditionally — and this is where it gets expensive. Say the drive is on the clock in your arrangement. At a placeholder $24 an hour, three hours is $72 a week, about $3,600 a year. But this operator already schedules the tech’s on-property work to fill the week, so the three travel hours are not the first three hours of the week. They are the last three — the ones past the threshold the schedule was built against. At time and a half, $36 an hour, they cost $108 a week and about $5,400 a year, roughly $1,800 more than the same hours inside the shift. The dollars come from this invented property’s rate and its own scheduling practice and yours will differ, but the shape holds at whatever threshold you operate under. Travel is the cheapest-looking hour on the schedule and it prices at the margin, which is the most expensive place an hour can land.
Mileage is the smallest line and the easiest to find: sixty-eight miles a week is about 3,400 a year, roughly $2,100 at a placeholder 62 cents. Use your own figure, not that one — the federal standard rate is republished annually and many operators set their own policy anyway, so look it up rather than taking a number off a blog.
If you would rather see each property’s day land on its own clock while the schedule can still change, that is what the per-property daily labor flash is for.
The same week with one hop instead of four
Change nothing about the work. Change only which day it happens on.
| Day | Where | Hops | Miles |
|---|---|---|---|
| Monday | 58-room | 0 | — |
| Tuesday | 46-room | 0 | — |
| Wednesday | 58-room | 0 | — |
| Thursday | 34-room | 0 | — |
| Friday | 46-room, then 34-room | 1 | 14 |
One hop, fourteen miles. Forty-five minutes of transition instead of three hours, fifty-four fewer miles, and — the part worth more than the minutes — one interrupted day a week instead of four. Be clear about what did not change: Friday still breaks in the middle, because the tech works at the 46-room, drives, and works at the 34-room, exactly as Tuesday did in the first schedule. The hop is no cheaper. There is just one of it.
That recovers about two and a quarter hours a week, call it 112 hours a year, for nothing but the decision. One property a day wherever the work allows is not a clever idea; it is the schedule somebody would have written if the hops had been visible while they were building it.
What you are trading, and what you are not
This is not free, and a post that pretended otherwise would be selling you something.
You are trading visit frequency for working time. In the first schedule the 34-room got three partial visits; in the second it gets one full day and one part-day. Three arrivals become two, so thirty minutes of starting up becomes twenty, and the full day reaches jobs a two-hour visit never starts. Sometimes that is strictly better. Sometimes it is worse, and you find out by asking what actually waited. If the small property genuinely needs eyes on it daily, you cannot schedule the hop away, and your real choice is a second pair of hands or an honest hop budget.
You are not reducing emergencies. A failed boiler at three in the afternoon means a hop, and the right number of unplanned hops is not zero. The count tells you which hops were decisions and which were events — and the planned ones usually outnumber the emergencies, which is the part people do not expect. Your own count will tell you by how much.
If the hop is on the clock, record it as time, not as a gap
One failure mode destroys the number you just worked out, and it is the first thing to check for: the tech clocks out at the first property, drives, and clocks in at the second. Both records are now tidy and the drive exists in neither. You cannot cost it, cannot count it, and six months later cannot tell a 25-minute hop from a 90-minute one.
The alternative is one punch that spans the drive. Where clock-in is geofenced, a punch made away from the fence is flagged as out-of-fence rather than silently accepted — which is the right behaviour, because an off-site punch should be a manager’s decision and not a surprise. In ProfitClock that flag goes to an approval queue, and a correction a manager makes afterwards is kept as append-only history rather than overwriting what was first recorded. The point is not the flag; it is that an approved, dated punch is a number you can total at the end of a quarter and a gap between two clean punches is not.
Dating matters too: each punch belongs to its own property’s calendar day, which keeps a late hop from landing in the wrong day — or the wrong week — at one property and not the other. That is hours that split across two properties and clear a threshold at neither, arriving through a different door.
Where this doesn’t apply
One property. No hops. Nothing here is about you.
Properties on one site. Two buildings across a shared lot are a ninety-second walk, and formally costing that is theatre.
A salaried manager. The capacity and coverage arithmetic still holds — three hours a week in transit is three fewer hours of attention — but the wage and premium lines do not, and treating them as though they do overstates the case.
And the question this post declined. Whether a specific drive is compensable, and whether an ordinary commute becomes something else once the day has started, is a legal question whose answers are jurisdiction-specific and change. Nothing above is legal advice or a compliance opinion, and following it will not make you compliant with anything. Ask your state labor department and your own counsel — and give them the hop count rather than a hypothetical, because it is a better question with a number in it.
Start seeing what labor actually costs
Set up your property, put staff on the clock, and read tomorrow morning’s labor number.
14-day free trial · No credit card · Cancel anytime