My team and I would like the ability to change workload schemes by setting a start date to be included as a feature. For example, when the new scheme starts on 16 February, the app will still recognise the previous scheme, so there will be no modifications to past entries.
For context:
My team uses Timesheets to track all of our working hours. Each person uses a workload scheme based on their weekly working hours. If we change that scheme because of a modification to the weekly working hours contract, the weekly hours change retroactively as well. This is problematic for us because we cannot report correctly due to the modifications.
Possible scenario: We need to increase a colleague's weekly working hours from 15 to 40 hours in the middle of the month. However, because of changing the workload scheme, the Timesheets app is showing the colleague as having 50 negative hours. This is not the case in reality, but this is what the app says.
Antonia Bothur
| Tempo Products | Tempo Timesheets |
| Tempo Platform | Cloud |
We are facing the same issues; this HAS to change or we will find other solutions. Our team changes teams and workloads a few times a year. This change is critical for our reporting. At the moment this shows incorrect data
We are facing the exact same critical issue. In our company, we have seasonal schedule changes (8.5 hours/day in Winter vs. 7 hours/day in Summer).
Even though we created two completely separate Workload Schemes to handle this, moving a user to the Summer Scheme retroactively modifies their required hours for past months like April or May. This completely breaks our historical capacity reports, utilization metrics, and resource planning for the first half of the year.
Tempo urgently needs to support date-effective or scheduled Workload Schemes that preserve historical data.