Working time

GardyProp records how long a visit took: the technician starts the stop, works, and finishes it. That span is the working time.

Good to know

It is measured per visit, not per day. Every stop carries its own start and finish, and the timer keeps running across a break in the connection — it comes from the recorded start, not from when the screen was last open.

This is what an hourly rate is applied to. Duration × rate × on-cost is the labour cost of that visit, and that is what appears in profitability.

A daily rate does not need the duration. It is divided by the number of stops that person did that day. Somebody who did eight pools carries an eighth of their day on each.

Times that a device reports implausibly are discarded. A phone with a wrong clock would otherwise produce a visit that lasted eleven hours or minus three minutes, and both would run into the labour cost.

What it does not include

Driving, loading and waiting at a gate are not in it. What is recorded here is time at the pools, not time at work. The working day is measured separately, from the working day — and the difference between the two is the unproductive time.

A monthly salary is attributed through the clock, not through this figure. Monthly cost divided by the tour hours of the month gives an hourly rate, and that rate is applied to the duration of the visit. Without a single finished tour in the month the labour cost stays empty rather than being guessed.