Skip to content
English
  • There are no suggestions because the search field is empty.

How OwlOps Calculates Travel Time and Labor Time

Overview

When you're clocked in, OwlOps can suggest two kinds of time for a ticket:

  • Travel: time spent getting to a site.
  • Labor: time spent working.

OwlOps works out a suggested Travel and Labor time when you open the Update or Close form for a ticket. You can change it before saving. What you save is what goes on your timesheet and invoice.

Close Task form showing suggested Travel Time and Labor Time

When you close a task, OwlOps suggests Travel Time and Labor Time from your clock-in and check-in. Adjust them if needed, then click Submit.

When does OwlOps suggest time?

OwlOps suggests time only when all three of these are true:

  • Your user has Timesheet turned on.
  • Your role can log hours.
  • You are clocked in.

Otherwise the Travel and Labor fields start blank. You can still type time in yourself.

Events OwlOps uses

  • Clock In: starts your day.
  • Clock Out: stops suggestions.
  • Check In at a site: the time before it counts as Travel, and the time after it counts as Labor.
  • Check Out from a site.
  • Saving time on a ticket: any update or close where you enter time resets the starting point.

Opening, reading or viewing a ticket is not an event.

How Travel time is calculated

Travel is the gap between your last activity and your most recent Check In.

OwlOps uses timestamps only. It doesn't use GPS or location data, and it doesn't know the distance between sites.

How Labor time is calculated

Labor runs from whichever is later: your most recent Check In or your last saved time entry.

  • Hours you've already logged since a Check In are subtracted, so time isn't counted twice.
  • If Labor works out to 0, the Travel value is moved into Labor.

After a Check Out

After a Check Out, all the time since then is suggested as Labor until your next Check In. At that next Check In, the gap since the Check Out becomes Travel.

Working from a desk (no site check in)

  • OwlOps doesn't time individual tickets. The suggestion is always the time since your last event, not the time spent on that particular ticket.
  • Your first update or close of the day gets everything since you clocked in. After that, each one gets the time since your previous saved entry.
  • If you close a ticket without entering time, that time moves onto the next ticket you close.
  • With no site check in, all the time is suggested as Labor.

Best practice: clock in at the start of the day, close tickets as you finish them, and check the suggested Labor before clicking Close. For example, if you spent 20 minutes but the suggestion shows 1:05, change it to 0:20.

Worked example

Time Event Suggested Travel Suggested Labor
Field tech visiting sites
8:00 Clock In    
8:40 Check In at Store 12 0:40  
10:10 Close ticket A at Store 12   1:30
10:30 Check Out    
11:00 Check In at Store 15 0:30  
11:45 Close ticket B   0:45
Working from a desk
8:00 Clock In    
8:50 Close ticket C   0:50
9:05 Close ticket D   0:15

Why didn't any time fill in?

  • You're not clocked in, Timesheet isn't on for your user, or your role can't log hours.
  • The dashboard checks whether you're clocked in when you sign in. If you clocked in on your phone after opening the dashboard, or left it open across a clock out, refresh the page (or sign out and back in) so it picks up your current status.
  • You just saved time on another ticket, so very little time has passed since your last event.

Billing rules

Minimum billing time and "disable travel time" are applied when the invoice is created, not on the timesheet or time entry.