Support – HR Hydra

Time Tracker Policy Overview

A. How Custom Hours Are Configured

Each month, a manager chooses the time policy (Daily, Weekly, Monthly). This can be changed at any time, but the user’s entries for that month follow the policy set by the manager.

        Credited hours for Urlaub, Krankheit and Kind Krank tell Hydra how many hours to count when a day is marked with those reasons. You can keep them consistent (e.g., 08:00) across modes or tailor them.
      

B. Break Policy Fields

Break duration (minutes) and Break starts at: Break starts at means after how much work time the break begins (e.g., 06:20 means the break triggers after 6 hours and 20 minutes of work).” data-de=”Pausendauer (Minuten) und Pause beginnt nach: Pause beginnt nach bedeutet, nach wie viel geleisteter Arbeitszeit die Pause startet (z. B. 06:20 = nach 6 Stunden 20 Minuten).”> Break duration (minutes) and Break starts at: Break starts at means after how much work time the break begins (e.g., 06:20 means the break triggers after 6 hours and 20 minutes of work).

        Even if no break is entered, Hydra enforces the break at the configured point and subtracts the configured duration.
      

C. Expected Hours & Overtime Logic

Daily time policy describes how many hours are expected by the user. It defines how many hours are to be spent before overtime starts, and if overtime are to be given daily or to be counted toward the week’s threshold first. Daily break options are also available and enforceable. Companies that use compulsory breaks can use the settings to define after how many hours of work is break enforced.

Aron is expected to work 7 hours daily. He noticed that after tracking from 8:00 am to 3:00 pm, his total hours show 6hrs 30minutes instead of 7hrs. What is a possible explanation?

A. A 30 minutes break policy is enforced. B. His hours are wrongly calculated.

Weekly setting lays out the week’s threshold. Leaving this setting empty means that the daily work hours settings are used for the week’s total. If daily settings for overtime are to count toward the week’s total hours, they will be represented only after exceeding the week’s amount of anticipated hours

Managers can define the month’s expected threshold for their workers. The setting caps the highest expected total work hours in any month, pushed in from the daily and weekly settings.

          Calendar lock defines after how many weeks into the following month the previous month becomes read-only for users (admins can still unlock).
        

Peter works 8 hours per day. A 20-minute break is enforced once he has worked 6 hours. He worked from 07:30 to 15:30 but forgot to enter a break. Later he remembers he paused 10:30–11:00. Will entering the break now make a difference?

Yes No

Peter’s break lasted 38 minutes while the enforced minimum is 30 minutes. What happens?

A. The extra 8 minutes are also subtracted and affect his weekly balance. B. Nothing happens; only 30 minutes are ever deducted. C. The entire break is ignored.

Peter notices that his monthly policy was set wrongly and his manager corrected it after the month ended. Does Peter need to re-enter his time?

A. Yes, he must re-enter the entire month. B. No, Hydra recalculates automatically based on the updated policy.

Mirjam submitted an Urlaub Wunschtag for 21 August 2025. Which are true? (Select all)

A. The admin may leave it pending, approve, or deny. B. Manager approval appears in Mirjam’s calendar and locks other selections; only an admin can cancel it. C. The approved Urlaub appears in Urlaub Historie under the correct year filter.

How many hours will be credited to Mirjam’s Urlaub tag?

A. The manager defines the credited hours. B. 8 hours. C. 0 hours.

On the approved Urlaub day, Mirjam decides to return to work. Which statement applies?

A. Her work hours are added on top of Urlaub hours; she can earn overtime easily. B. Urlaub days are locked; further entries are not possible unless the manager cancels the approval.

Daily work policy examples: Peter’s Expected Hours (Daily) are 08:00 and overtime threshold is 00:30. If the toggle is set to Yes, only time beyond 08:30 becomes overtime. He works 08:20 → no overtime. If set to No, any time beyond the 00:30 threshold counts even if the daily target hasn’t been reached exactly.

Weekly work policy examples: With Expected Hours (Weekly) = 40:00 and threshold 01:00, the toggle set to Yes means overtime appears only after the weekly sum exceeds 41:00. Peter does +1:00 Monday and −1:00 Tuesday → no overtime because totals balance out.

Monthly work policy examples: Expected Hours (Monthly) = 168:00 with threshold 02:00. With the toggle at Yes, overtime is shown only after 170:00 is exceeded across the month.

Wolfgang’s daily expected total is 8 hours. He has worked 9 hours yet the overtime management section does not show it. What is happening?

A. Only 8 hours of work are accepted and his extra hour is considered free for the company. B. His company uses overtime to meet the weekly threshold first, before reporting overtime.

Sofia (manager) sets up August 2025 for Peter. She selects Peter as the User, Year = 2025, Month = August, and chooses ‘Monthly’. From that point, Hydra uses the Monthly settings for Peter’s entries in August until Sofia changes them.

Mirjam needs different weekly hours during school holidays. Sofia switches the Default Settings Type to ‘Weekly’ for July only. Peter keeps ‘Monthly’ for August. Each user’s entries follow the policy configured for that specific month.

Sofia sets ‘Calendar should lock in how many weeks into a new month?’ to 3. On 22 September, Peter can no longer edit August entries because August is now locked. He spots a mistake on 10 August; Sofia unlocks that day, fixes the Urlaub tag, and Hydra recalculates automatically.

          When a day is marked as Urlaub, Krankheit or Kind Krank, Hydra locks the second-agenda project button and manual time inputs for that day because these are constant credited values.
        