Flex
Flex
Flex is automatically calculated by Treks on a periodic basis (a period is usually one week). Each user has a setting for the number of working hours per day, set by the contract. This is usually 8 hours.
This becomes the basis for the expected number of hours worked per week, usually 40 hours / week (8 hours * 5 days). The number of expected hours for the period is always visible at the top right of the page where the user registers their time.
If you want finer control over which reported time is included in the flex, you can set this per customer project, internal project and absence type. On the settings page for each project, there are modes that you can select to specify whether the project is included in the flex.
If Flex restriction is set to STRICT, flex is not counted for this project (see modes below). This means, for example, that if a user reports 45 hours on this project for a week where the week's expected working hours amount to 40 hours, the user thus gets 0 hours in flex even though he has worked more hours than required.
Conversely, if set to NONE, the flex balance would increase by 5 hours in the example above.
By default, flex is calculated for all projects, internal projects and absences. But it is possible to change by selecting the mode for Flex restriction.
The flex time is calculated in connection with the user locking the period. For unlocked periods, no flex is calculated. This means that for the current period it will not show how the flex balance is affected day by day. Only when the period is locked, the flex balance will be updated.
Flex restriction modes
None
This mode should be pretty self explanatory. No restriction to flex calculation is made. This is the default.
Optimistic
This mode will restrict the hours from exceeding the scheduled work hours. That is, it will count the hours up to 8 hours/day but any excess hours will be ignored. This is useful for projects like travel time or internal projects like conference or learning.
Strict
Using strict mode the hours won't be used in flex calculations at all. From a flex calculation perspective it's like these hours weren't entered at all.
Calculating flex can be complicated when combining flex and flex-restrictive projects. Here is an example on how it works under the hood. You can completely disable flex for a user by unchecking the flex box in the user contract.
If the total hours is less than the user scheduled work hours, the flex will reflect that. Flex-restriction only applies when the total hours are more than the user scheduled work hours. First all non flex-restricted hours are calculated. If the total exceeds the user scheduled work hours then we're done. The excess is added to the flex.
Defaults
Reported time on a project normally contributes to flex time if more time than full working time is reported in one day. You can set how flex time is handled on each project. If you do not want flexitime to be used for a project, select a mode for flex.
The default settings for each project type are:
Customer project: NONE
Internal project: NONE
Absence: NONE
Last updated