On-Call, Travel and Training: Which Hours Count

The three categories that swallow hours quietly

Nobody argues about whether you should be paid for the shift itself. The arguments happen at the edges — the weekend you spent tethered to a phone, the two hours driving between sites, the certification course on a Saturday. Each of these has a rule, none of the rules is intuitive, and the default assumption in most workplaces is that none of it counts.

What makes these worth understanding together is that they share a shape. In all three, the question is not whether you were productive but whether the employer had the benefit of your time. Once you hold that question in your head, the answers stop feeling arbitrary and start following a pattern you can apply to a situation nobody has written a rule about.

On-call: whose time is it really

The distinction that decides on-call pay is whether you are waiting to be engaged or engaged to wait. If you can genuinely use the time for your own purposes — go out, see people, sleep normally, and simply respond if something comes in — the waiting is generally not compensable even though you are technically available. That is the situation most on-call arrangements are designed to look like on paper. Whether it describes yours is a factual question about the constraints rather than a question about what the policy says.

What flips it into paid time is the tightness of the constraints. A response window short enough that you cannot leave the area, a requirement to remain on or near the premises, a restriction on drinking or on being unreachable for even short stretches, or a call frequency high enough that the shift is functionally continuous. Any one of these can make the whole period compensable rather than just the calls themselves. They are also cumulative, so an arrangement with three mild constraints can land in the same place as one with a single severe one.

The practical test is a question you can answer honestly about last weekend. Could you have driven forty minutes to see family, had a glass of wine with dinner, and gone to bed without a phone on the pillow? If the honest answer is no, the employer was getting the benefit of that time whether or not the phone rang, and that is exactly what the rule is about.

Travel: the commute is the exception, not the rule

Ordinary travel from home to work and back is not compensable, and that single case is what almost everybody generalizes from. It is genuinely the exception rather than the rule. Travel that forms part of the day’s work — between job sites, from the office to a client, from one location to another mid-shift — is working time and is paid. The distinction is whether the journey is getting you to work or is itself work.

Special one-day assignments in another city are treated more generously than most people expect, with the travel time typically counting as work time. The employer may deduct what your normal commute would have been, which is a small adjustment rather than a reason to exclude the journey. Overnight travel is the fiddly one: time spent traveling during your normal working hours counts, even on a day you would not normally work. So a Sunday flight taken during what would ordinarily be your Tuesday working hours is compensable, which surprises people every time.

For anyone doing site work, travel is the largest of the three categories by volume and it is not close. Two hours of inter-site driving a day is ten hours a week. If those hours are not on the timesheet then they are not merely unpaid — they are invisible when the weekly total is checked against forty, which means the overtime they should have triggered never surfaces either. That second effect is usually worth more than the first.

Training: the four conditions, and why they rarely all hold

Training time is working time unless all four of these are true at once: it happens outside your normal working hours, attendance is genuinely voluntary, the course is not directly related to your job, and you perform no productive work during it. All four have to hold simultaneously, which is a much higher bar than it sounds. Failing any single one of them makes the time compensable. The conditions are worth memorizing as a set, because remembering three of them produces the wrong answer.

In practice most workplace training fails at least two. Compliance modules are related to the job and not voluntary. Product training is directly related to the job by definition. Even a course framed as an optional development opportunity may not be voluntary in the relevant sense if declining would carry consequences, and “voluntary” gets read against what a reasonable employee would understand rather than against what the invitation said.

The one that genuinely qualifies is the independent evening course you chose to take, in a subject that is not your job, with no work performed during it. That is a considerably narrower category than the phrase “optional training” suggests. Most of what gets called optional in a workplace is optional in the sense that nobody will physically stop you from declining, which is not the sense the rule uses.

A worked week

Take a field technician on $28 an hour. Monday to Friday they work eight-hour shifts, drive roughly ninety minutes a day between sites, and spend two hours on Thursday evening in a mandatory safety refresher. The timesheet at the end of that week says forty hours, because the shifts were eight hours each and the shifts are what the system records. Nothing about that is a deception; the timesheet is accurately recording the thing it was built to record.

The inter-site driving is 7.5 hours across the week and the safety training is another 2, because it is job-related and mandatory. The actual total is 49.5 hours, which means 9.5 hours of overtime at $42 an hour — $399 — on top of the straight time for those hours. Across a year of similar weeks the gap is well into five figures, and none of it appeared on a timesheet anybody looked at.

The pieces that vanish for a different reason

Short breaks are worth mentioning here because they interact with all three categories. Rest breaks of roughly twenty minutes or less are compensable working time under federal rules, so a paid ten-minute break is not a concession anybody made. It is the default position, and an unpaid short break is the thing that would need explaining.

And where a system rounds or auto-deducts, these edge hours are the ones most likely to disappear, because they sit outside the scheduled shift where nobody is looking for them. If your employer’s timekeeping has no category for inter-site travel, the hours do not merely go unpaid. There is nowhere to record them even if somebody wanted to, which means the problem is structural rather than anybody’s decision, and structural problems are usually easier to raise.

What to do

Record these three categories separately in your own notes, with dates, for a month. Not as a grievance file — simply as a factual record of where the hours went. The first thing anybody will ask is how much time is actually involved, and a month of real data answers that immediately while an impression does not. It also tells you whether this is worth pursuing at all, which is a legitimate thing to find out before starting.

Then ask the process question rather than the entitlement question. “How should I be recording the driving between sites?” is a question about a timesheet category, and it is much more likely to get a workable answer than asking whether you are owed money for the last six months. If the answer is that there is no category, that is itself the finding, and it is a reasonable thing to ask to have fixed going forward.

This is general information about how the rules are structured rather than legal advice about your situation. On-call in particular turns heavily on the specific constraints in your arrangement, so if there is real money in it, your state labor agency or an employment lawyer can tell you where you stand — and state agencies will discuss a question without any obligation to file.