Skip to main content
Jobs and journeys

Optimize travel time management with Organilog.

Tony Archambeau avatar
Written by Tony Archambeau
Updated over a week ago

There are several ways to manage travel times.

Via Jobs 🚧

To implement this method, you need to create a fictional client to which the journey-type jobs will be attached. This will also make it easy to consult and export them if necessary.

This fictional client can be named "Journeys," "Trips," or something else.

It is also possible to create an associated job category, allowing for applying a specific colour to the relevant jobs in the schedule.

This way, you can create jobs that match your travel schedule.

  • Defined in advance: in "planned" status.

    In this instance, these tasks can be verified and enhanced with real journey times if needed.

  • Or you entered as you go along, in the "Done" status.

    In this case, these can be created at time T as the day progresses, indicating the start and end time of the journey.

Through Common actions ⌚

It is possible to consider that the total duration of a job includes travel time and to specify the time spent on the road during a current task.

For more details, please check this article:

Through Custom fields 🎨

This approach involves creating custom fields to input travel times for each job.

In particular, it allows for all the declared values to be retrieved, if necessary, through a job export in CSV format (spreadsheet), and to be reworked.

It is advisable to use "hour" or "numeric" type fields for declarations in minutes.

Through Non-working time

Time spent travelling can also be calculated using the "time not worked" field of a job.

With this method, the actual working time must be declared using the "working time" field. Once the job has been recorded, the non-working time (travel time) will be automatically calculated by subtraction.

⚠️ Please note, however, that this approach does not allow data to be retrieved through an export of jobs.

Through Time clocks

⚠️ This method operates completely independently: there is no connection, calculation, automation, or reconciliation between the clockings and the jobs/ job schedule.

With Organilog, you can create customized "clock-in buttons" to track working time comprehensively, including travel time.

These buttons can be activated with a simple click from a web browser or mobile phone. They can be used to record the precise time at the beginning or end of a journey, among other functions.

The times are aggregated on a weekly and monthly basis, and the resulting tables can be exported in CSV (spreadsheet) format.

Did this answer your question?