A work-time model says what is expected of a person on each day of the week. The model is versioned: when you change it, a new version comes into being from the effective date onwards, and the calculation of old weeks does not change.
The models live under Settings → Working time → Working time models.
Create a new model
Press New working time model. Fill in the mandatory details:
- Name.
- Effective from.
- Seven per-day targets.
- Model default shift type.
- The lower and upper flex limits.
A person has exactly one model version in force at a time. The version may change mid-week: the first days of the week are calculated on the old version and the rest on the new one. A change can therefore be timed mid-week, and you do not have to wait for a week boundary.
Which model a person is on is a dated fact too. On the person page, choose Record a change → Working time model in the Working time section. Kelomo asks the day the new model takes effect: earlier days are calculated on the previous model, and confirmed days keep the target they were confirmed with. The history shows which model changed to which, who recorded it and when; a change that has not taken effect yet can be undone.
Flexible working time (Working Hours Act, section 13)
The model form also sets the Working-time regime. The default is standard working time. Flexwork (Working Hours Act § 13) is a regime of its own, separate from both standard working time and flexitime, and the Act sets its own conditions for it:
- The employer and the employee agree on flexwork in writing.
- The employee places at least half of the working time and decides where the work is done.
- Regular working time may be at most 40 hours a week on average over a four-month averaging period.
When a model uses flexwork, the person’s daily targets become indicative: days are recorded and confirmed as usual, and the day’s target is a guideline. Current legislation: Working Hours Act (Finlex).
Changing a model = creating a new version
An existing version is never edited in place. Choose Change settings in the model’s actions, set the date in Effective from and press Create version.
A new version closes the previous one automatically. The validity range cannot be edited afterwards – a change is always made as a new version going forward. If you made a version with the wrong date, the fix is once again a new version.
When a day is confirmed, the model version used is locked to that day. Editing the model later therefore does not touch confirmed days.
What does not belong to the model version
Per-day defaults are not details of the model version; they are set on the shift type chosen in Model default shift type:
- the frame anchor
- breaks
- the flex window
- daily overtime
So if you want to change breaks or the per-day flex window, the change is made on the shift type, not on the model. See Shift types. The per-day flex ceiling and floor cut the balance, whereas the model’s flex limits do not – see Flexitime balance.
Where the day’s target comes from
When Kelomo calculates a day’s target, it goes through the sources in this order and uses the first one that hits:
- The person’s published shift.
- The group’s published shift.
- The model’s shift-type binding.
- The model’s default type or weekday target.
The source used is always shown in the day breakdown.
The Where the day’s target comes from field narrows the sources: Working time model uses the model’s daily targets, Published shifts uses published shifts (without a shift the day is off), and Shift, otherwise working time model uses the published shift and otherwise the model.
A binding of a shift type to weekdays wins over the default type on a matching day; ties break on priority (higher wins). A clock-time window lets a punch without a plan resolve to the type by the time of day.
The break deduction happens at confirmation: if a long day’s recorded break is shorter than the minimum, the difference is deducted automatically. The deduction is shown in the day breakdown.
Period-based working time (Working Hours Act, section 7)
In period-based working time the regular hours are arranged per period, not per day: no daily overtime forms, and overtime is measured against the period’s working time. When period-based working time is chosen as the regime, the figures are pre-filled from the law. Replace them with the agreed ones if a shorter working time has been agreed.
If something goes wrong
I changed the model and I am afraid old weeks changed. Old weeks do not change. The new version is in force only from its effective date onwards, and a confirmed day has the version it was calculated with locked to it.
I gave the new version the wrong effective date. The range cannot be edited afterwards. Make a new version with the right date – it closes the previous one automatically.
A day’s target is not the one I set in the model. Look at the source in the day breakdown. A published shift overrides the model, so the person’s or the group’s shift is the likely explanation.
A user is told they have no work-time model. The person has no model version in force for that day. Check that the model’s validity starts early enough.