Oregon travel time pay: 4 checks beyond 30 miles

Key takeaways

• Record the official base and destination distance.
• Identify the assignment type before choosing an example.
• Log departure and arrival times for each leg.
• Ask payroll about unclear cases before approval.

Why the 30-mile line matters

In Oregon, the Bureau of Labor and Industries (BOLI) addresses that question on its worker guidance page, which asks: "Does my employer have to pay me for the time when I travel more than 30 miles to a worksite?" The travel time and mileage page gives a one-day assignment example beyond that radius.

Distance and assignment type both matter. Do not apply the one-day example to every trip. This post walks through four checks you can run on each trip before you approve the time. Each check ties back to an example from BOLI's guidance.

This is general information for managers, not legal advice. If a case is disputed or unusual, ask BOLI or an employment attorney before you decide.

Before the checks: pin down the official base

The 30-mile test is measured from the employee's official base. That is the reference point for every check that follows, so settle it first. Use the travel time and mileage page when reviewing that reference point.

For someone who works across several sites, ask HR or payroll to confirm the official base. Your organization should write down its own rule for that and apply it the same way to every trip. Put the official base on each trip request so the reviewer does not have to guess which station the trip started from.

Check 1: is the worksite more than 30 miles from that station?

Start with a plain question: how far is the distant worksite from the official base? A destination that sounds far can be close, and a short-sounding name can be far away, so check the distance itself rather than relying on a sense of how far the trip feels.

Write the distance on the trip request. Use the same measuring method for every trip, so two managers reviewing the same route reach the same answer. If you change methods partway through the year, note the change, because a record that mixes methods is hard to defend.

If the worksite sits within 30 miles, the one-day example above does not cover the trip, and you should not assume the travel is paid the same way. Send that case to HR or payroll for a decision rather than deciding from memory. The point of Check 1 is not to approve or deny the time. It is to decide which of the remaining checks apply.

Check 2: which hours does the travel cover?

BOLI's guidance uses an employee named Chet as an example. Chet travels by bus on Wednesday, from 10:00 a.m. to 4:00 p.m. Chet returns home by bus on Saturday, traveling from 2:00 p.m. to 8:00 p.m. For that Saturday return, the guidance says the employer must pay for the three hours between 2:00 and 5:00 p.m., "the travel time which cuts across Chet's normal work hours."

Keep the Saturday example separate from the Wednesday trip when reviewing the hours involved.

For Chet's Saturday return, identify the overlap without assuming the remaining hours are unpaid.

To apply this, ask staff to log departure and arrival times for each leg of the trip, not a single total for the day. Compare each leg against the employee's normal schedule and note where the travel overlaps those hours. A single line reading "travel, 8 hours" gives you nothing to compare.

Check 3: what shape is the assignment?

BOLI's examples cover two shapes. One is a one-day assignment to a city beyond the 30-mile radius. The other is a trip that runs from one day into another, like the Wednesday-to-Saturday example involving Chet. Before you approve, confirm which shape applies to the trip in front of you.

The shape matters because it changes how many legs and dates you have to check. A one-day trip out and back has a small set of times to review. A trip that spans several days has more departures, arrivals, and days on which the travel may overlap normal work hours. The record should show every date and every leg so you can check each one against the guidance.

If the trip does not fit either shape, do not force it into one. Note the details, and ask HR or payroll how the trip should be handled before you approve it. An unusual trip is the most likely place for an error to slip through a routine review.

Check 4: does the example fit the employee's role?

BOLI's paid-time page includes an example about a truck driver who is sent from Portland to Medford, leaving at 6 a.m. and arriving at noon. The page says that driver will be paid for all this time as hours worked.

In that example, the clock runs from departure to arrival. For managers, the practical point is that your staff's records should show departure and arrival times, not a flat entry labeled "travel." Without those two times, you cannot check how much of the trip counts as paid time, and you cannot tell whether the paid hours match the trip as it actually happened.

Be careful about how far you take this example. Read the full paid-time page before you apply its logic to a different role, and do not assume the truck driver example covers every kind of worker you approve.

Build a record that holds up

Each of the four checks needs specific information. If the record lacks it, the approver is guessing. A solid travel record for a trip beyond 30 miles should include:

• The date of each leg of the trip.
• The official base the trip started from.
• The distant worksite and its distance from that station.
• The departure time and arrival time for each leg.
• The mode of travel, such as bus, truck, or personal vehicle.
• The purpose of the trip and who approved it.

Ask staff to submit this record with the trip request, not after the fact. A record written days later from memory is less reliable, and it is harder to correct once the pay period has closed.

Keep the format the same across your team. When every manager uses the same fields, payroll can compare trips quickly, and a question about one trip does not turn into a question about the whole system. For the wider review process, see timesheet approval and edit rules.

Illustrative example: review the record before deciding pay

An illustrative trip request lists a destination 60 miles from the official base and a travel leg lasting 30 minutes. The reviewer still needs the assignment type, travel mode, actual departure and arrival times, and normal schedule. Distance and duration alone do not establish which example applies or settle the paid hours.

What to tell staff before they leave

Most of the problems managers face with distant travel start before the trip, not after it. An employee who knows what to record can make your review quick. An employee who does not may submit a total that you cannot check.

Give staff a short written note before a trip is approved. It should say which information to write down, when to submit it, and whom to ask if something is unclear. Keep the note brief enough that people will read it. A one-page list is usually better than a long policy document.

Ask staff to record times as they happen, not to estimate them at the end of the day. A departure time written on a phone at the station is more reliable than one reconstructed from memory on Friday afternoon. If a bus is late or a route changes, ask them to note the actual times and the reason, so the record reflects what happened rather than what was planned.

Also tell staff what they should not do. They should not round every leg to the nearest hour, and they should not submit one lump of travel time for the whole assignment. Those habits make the overlap check in Check 2 impossible to complete.

Finally, make clear that questions are welcome. An employee who asks before submitting a timesheet saves everyone time. An employee who is afraid to ask may guess, and a guess is harder to correct later.

Today, review one trip request for missing dates, times and assignment details, then send any open pay question to payroll. Use the payroll handoff checks to organize that review.

Questions managers often ask

Does every mile over 30 count the same way? Do not calculate paid hours by adding pay for each mile beyond 30. Review the assignment and travel hours instead.

What if the employee works at several sites? Ask HR or payroll to confirm the official base before reviewing the trip. Choose a rule, write it down, and apply it consistently. Then send any unusual pattern to HR or payroll before you approve it.

Can I approve the trip in advance? Yes, you can approve a trip using its expected itinerary. That helps you plan the review. Advance approval of the trip does not replace the record of actual departure and arrival times, which you still need when the timesheet arrives.

What if the times on the record look wrong? Ask the employee to check them before you decide. A mistake in a single time is often easy to explain. A pattern of times that do not match the dates, or a record that is missing for one leg, is worth a closer look and a conversation with payroll.

Does the example in BOLI's guidance settle my case? Compare your case closely with the example before relying on it. The Chet example involves a bus trip that runs over several days, and the truck driver example involves a truck making a single trip from Portland to Medford. If your case differs in distance, mode, or dates, the example is a starting point for the question, not a final answer. Ask BOLI when the difference matters.

How long should I keep the records? Ask HR or payroll which retention requirements apply. Keep the trip records under those requirements so you can answer later questions about the hours approved.

Common mistakes to avoid

Several errors come up often when managers review distant travel. Watch for these:

1. Treating every assignment alike. Match the trip's details to the relevant example before deciding how to review its hours.

2. Measuring distance by feel. A rough sense of how far a city is will not hold up if the timesheet is questioned.

3. Applying one example to every job. Check the employee's role before relying on an example.

4. Approving a flat travel block. A fixed number of hours for every trip skips the checks that matter most, especially the overlap with normal work hours.

5. Waiting until the end of the pay period. A missing departure time is easy to fix the day the trip is submitted and hard to reconstruct weeks later. Check each trip as it comes in.

6. Deciding unclear cases alone. If you are unsure about a trip, the cost of asking is small compared with the cost of an error in a timesheet that was already paid.

A routine for each trip

Here is a simple sequence you can use for each trip submitted beyond the 30-mile line. It brings the four checks into one review.

1. Confirm the official base for the employee. Write it on the trip request.
2. Measure the distance from that station to the distant worksite. If the worksite is 30 miles or less, send the trip to HR or payroll with a note and stop there.
3. If the worksite is beyond 30 miles, pull the departure and arrival time for each leg of the trip.
4. Confirm the assignment shape before choosing which example applies.
5. Compare each leg with the employee's normal schedule and record any overlap without assuming other hours are unpaid.
6. Check whether the employee's role matches the example, and confirm that the record supports the hours you are approving.
7. Write down any open question and send it to HR or payroll before the timesheet is approved.

The routine is not a substitute for the guidance itself. It is a way to make sure you have asked each question before you sign off.

When to escalate

Send any unclear case to HR or payroll. Escalate it sooner if the distance is close to 30 miles, if the trip runs across several days, if the employee disputes the time, or if you cannot get departure and arrival times for each leg. Those are the situations where a judgment made from memory is most likely to go wrong.

BOLI's travel time and paid time pages are the public reference for the examples in this post. Read them directly, and when a case does not match an example, ask BOLI rather than stretching the example to fit.