When employees regularly exceed the statutory maximum working hours, many project-based companies treat it as an unavoidable side effect. Deadlines, client escalations, project peaks. Everyone knows these situations. But what feels like an operational state of emergency is often a structural signal: project planning does not reflect actual capacity. That is why Working Hours Act violations in Germany are as much a planning issue as a compliance issue.
Violations of the German Working Hours Act (Arbeitszeitgesetz, ArbZG), often also called the Working Time Act, are not a marginal problem in project-based companies. They arise where resources are scarcer than the plan assumes, where time data is recorded incompletely and where nobody has a real-time overview of actual utilization. The risk of fines is real. But the real economic consequence goes deeper: permanent overtime distorts project margins, conceals planning errors and creates follow-up costs that only become visible months later.
Key points at a glance:
- Overtime in projects is often a symptom of poor resource and capacity planning
- Violations of the Working Hours Act can be fined up to €30,000 per individual violation, with a two-year limitation period
- Unrecorded extra work leads to systematically underestimated project budgets and distorted margins
- Project time tracking creates the data basis for spotting utilization bottlenecks before they escalate
- Compliance and project control are not separate topics but two sides of the same data basis
Which Working Hours Act violations are most common in Germany
The Working Hours Act sets clear limits: a maximum of ten hours per day, an average of eight hours over six months, at least eleven hours of rest between two working days, and mandatory breaks after six hours. These rules are well known. Yet in project-oriented companies they are exceeded regularly.
The most common violations according to the current catalogue of fines of the German Federal States' Committee for Occupational Safety and Safety Engineering (Länderausschuss für Arbeitsschutz und Sicherheitstechnik, LASI):
The limitation period is two years. Supervisory authorities can therefore inspect all working time records from the past 24 months. With 20 employees and repeatedly faulty documentation, fines quickly add up to five- or six-figure sums. In the case of intentional endangerment of health, there is also the threat of criminal consequences, including imprisonment of up to one year.
Why overtime in projects is rarely down to the individual
According to Destatis, the Federal Statistical Office, around 4.4 million employees in Germany regularly worked more than contractually agreed in 2024. Almost one in five of them worked unpaid overtime. In knowledge-intensive industries with a high share of project work, this figure is structurally higher.
The problem is well known. Yet its cause is often misdiagnosed.
When a consultant is still reachable after 8 pm three evenings a week, when an IT project lead regularly works twelve hours, when an engineer goes weeks without a full rest period during the delivery phase: this is rarely due to a lack of self-discipline. It is because the project calculation underestimated the effort, because too many projects are running in parallel, because capacity was not checked against actual availability.
The BAuA working time survey 2023 of the Federal Institute for Occupational Safety and Health shows a direct link: employees without systematic working time recording report blurred boundaries of working time and poorer recovery significantly more often. The lack of recording is often both cause and consequence: if you do not record, you do not see the scale of the problem. If you do not know the scale, you plan the next project phase on unrealistic assumptions.
How the project business systematically leads to working time violations
The project business has structural characteristics that make working time violations more likely than in other industries. Four of them are particularly relevant.
Unrealistic project planning
Projects are often calculated with effort estimates rather than historical time data from comparable projects. The result: the plan is too tight, resources are not enough, and the gap is closed with extra work. This pattern repeats project after project because the cause is never addressed.
Without project time tracking that documents effort per phase, per trade and per service area, you have no reliable basis for realistic planning. Today's planning error is tomorrow's working time violation.
Missing resource planning
In many project-based companies, employees are scheduled on projects without anyone checking their actual overall utilization. Someone is booked at 100 percent on three projects at once but in fact has only 60 percent available capacity, because internal tasks, vacations and absences were not taken into account.
The result: overtime becomes the only solution. The cause regularly lies in resource planning that provides no transparency about real capacity.
Incomplete project time tracking
Without complete project time data, nobody knows how much time individual project phases actually take. Buffers are set by gut feeling. Extra and reduced effort is not recorded systematically. Deviations only become visible once the budget is already overspent.
At the same time, the basis for detecting Working Hours Act violations in the first place is missing. If you do not document working hours, you can neither check rest periods nor prove to the supervisory authority that the statutory limits were observed.
Lack of transparency about utilization
Many project-based companies manage their utilization reactively. Overload becomes visible when employees fall ill, resign or projects escalate. An early-warning system that shows utilization peaks before they occur is missing.
If you see capacity and time data in real time, you can take countermeasures: redistribute tasks, adjust timelines, bring in external resources before the statutory limits are exceeded. This requires a resource utilization analysis based on current data.
What working time violations mean for project-based companies
Fines and liability risks
The immediate financial consequences are considerable. Individual violations are fined up to €30,000. In practice, if there is a suspicion, supervisory authorities examine the time records of all employees for the past two years. Companies that cannot present complete documentation risk fines per employee and per violation that quickly add up to six-figure sums.
On top of this comes the personal liability of management. The company and its authorised representatives can be fined directly. Delegating internally to HR or team leads does not release management from its organisational responsibility.
Falling employee satisfaction and turnover
Permanent overload creates costs that are not found in any catalogue of fines. Skilled employees who regularly fall short of their rest periods resign sooner. In a market with an ongoing shortage of skilled workers, especially in IT consulting, management consulting and engineering, replacement costs are considerable. And project-specific know-how leaves with the person.
No predictability for follow-up projects
Permanent overtime in one project distorts the data basis for all further calculations. If a 40-hour project in fact becomes a 55-hour project but the difference is not documented, the next comparable project is calculated on the same wrong assumptions. The error reproduces itself.
Distorted project margins
Unrecorded extra work makes projects look more profitable than they really are. A fixed-price project calculated at 400 hours that needs 530 hours appears profitable in the books if the 130 hours of extra work are not recorded. The margin is fiction.
This is not a theoretical scenario. According to Destatis, around 19 percent of employees who worked extra hours in 2024 did so unpaid. In project-based industries with a high share of trust-based working time, this figure tends to be higher. The company bears the cost of this extra work invisibly.
{{blog-cta}}
How project time tracking helps detect violations early
The legal requirement for recording working time is clear: since the 2019 ruling of the Court of Justice of the European Union (ECJ) and the 2022 decision of the Federal Labour Court (Bundesarbeitsgericht, BAG), employers in Germany are obliged to provide an objective, reliable and accessible system for recording daily working time. Trust-based working time does not release them from this obligation.
For project-based companies, this is an opportunity that goes beyond pure compliance.
Complete time data does not only show whether someone worked 11 hours today. It shows in which project phase the strain arises, for which tasks effort is systematically underestimated and where capacity is regularly overloaded. Project time tracking that brings working time and project time together on one data basis delivers exactly this information in real time.
In concrete terms, this means:
- Rest periods are checked by the system, and shortfalls become visible immediately
- Daily working time limits are monitored automatically, without manual checks by team leads
- Breaks are documented, completely and audit-ready for two years
- Utilization overviews show which employees are under how much strain in which projects
This is not a control system. It is an early-warning system. And it relieves managers who today still try to manage overload by gut feeling and escalation meetings.
From compliance to project control: working time data as a management tool
Working time violations are the last visible symptom of a problem that starts much earlier. Its origin lies in planning: too little buffer, too tight capacity, too little historical data for realistic calculations.
If you use working time data only for compliance documentation, you are giving away considerable steering potential.
Time data analysed at project level answers questions that are central to the profitability of project-based companies:
- In which project phases does extra effort systematically arise?
- Which client projects consistently have higher utilization than planned?
- Which teams are chronically overloaded, and which have free capacity?
- Do the calculated hourly rates match the actual effort?
That is project controlling based on real data. It requires working hours to be recorded completely, per project and in real time.
Companies that take this step manage their utilization proactively instead of reactively. They spot capacity bottlenecks before they lead to violations. They calculate follow-up projects on reliable effort data. And they protect their employees without needing a separate HR monitoring system.
Example from IT consulting
An IT service provider with 60 employees runs five larger projects in parallel. Resource planning is based on reported availability, absences are maintained manually, and time data comes from three different tools.
During an audit phase, it turns out that two project leads regularly fall short of the statutory rest period because evening coordination meetings with a client in a US time zone were not planned as working time. This creates a risk of fines and at the same time explains why the project needs 23 percent more effort than calculated.
The cause is not a lack of discipline. The cause is a lack of data transparency.
Example from management consulting
A management consultancy with 45 consultants manages workload and utilization via an Excel dashboard that is updated manually every week. Overtime is recorded but not analysed per project.
The result: in hindsight, projects with high client satisfaction show the lowest margins, because the actual consulting effort exceeded the calculation by 30 to 40 percent. The information was in the system but not aggregated at project level.
With ZEP: compliance and project control on one data basis
ZEP combines working time tracking, Project Time Tracking and Resource Planning (available as an add-on) on one platform. This means compliance requirements are met automatically, while the same data is used for operational project control.
- Automatic limit checks: ZEP detects breaches of the daily maximum working time, missing breaks and shortfalls in the minimum rest period in real time and flags anomalies directly.
- Audit-ready documentation: all working and project hours are stored in an audit-proof way, with two-year retention in line with the legal requirements.
- Resource Planning with real-time data: the Resource Planning add-on in ZEP automatically takes approved absences, public holidays and current project bookings into account. The utilization overview shows realistic availability, not planning assumptions.
- Project time tracking by client and project: employees book their hours directly to projects and tasks. Team leads and project leads see plan-vs-actual comparisons in real time, spot deviations early and can take countermeasures before budgets or capacity are exceeded.
- One data basis: working time, project time, absences and utilization flow into the same system. No parallel spreadsheets, no manual consolidation, no data gaps before the next audit.
Conclusion
Use working time recording as an operational steering tool, not as a downstream documentation duty. Check whether your resource planning reflects actual capacity or only reported capacity. Analyse time data per project to spot systematic planning deviations. And make sure rest periods, break requirements and maximum working hours are checked by the system instead of relying on manual control.
If you only discover Working Hours Act violations during an audit, you have a steering problem. If your system detects them before they happen, you have a competitive advantage.
FAQs
Does the German Working Hours Act also apply to project staff with trust-based working time?
Yes. Trust-based working time governs when and where someone works, not how much. The statutory maximum working hours, break requirements and minimum rest periods of the Working Hours Act (ArbZG) apply regardless of how working time is organised. Since the 2019 ECJ ruling and the 2022 Federal Labour Court decision, even companies without a time clock are obliged to provide a reliable system for recording daily working time. Project-based companies with trust-based working time therefore carry the full compliance risk without automatically having the data to monitor it.
How can project leads tell early whether employees are breaching working time limits?
Without complete time data, they cannot. Systematic detection requires working hours to be recorded to the day and per project, and the system to actively flag anomalies, such as missing breaks, days with more than ten hours or rest periods that were too short. Manual monitoring by team leads is too error-prone and too late: when a violation comes up in an escalation meeting, it has already happened. A digital system that checks limits in real time is the only reliable solution.
Why do unrealistic project schedules structurally lead to working time violations?
Because the gap between calculated and actually required effort has to be closed somewhere. In practice, this happens through extra work: employees work longer to meet deadlines. If this extra work is not documented, it stays invisible and is not included in the next calculation, so the planning error repeats itself. Reliable project calculations require historical time data showing how long comparable tasks and phases actually took in the past.
What happens if rest periods are regularly cut short during intensive project phases?
In the short term, there is a risk of fines: LASI puts the fine for falling short of the minimum rest period at up to €80 per started hour, with a two-year inspection period. In the medium term, the risk of sickness and turnover rises, especially in project-oriented industries with high demand for qualified specialists. The BAuA working time survey 2023 shows that employees without systematic working time recording report exhaustion and poor recovery significantly more often. The economic follow-up costs usually far exceed the risk of fines.
How can working time data be used in project controlling?
Working time data at project level shows whether planned effort matches the effort actually delivered. This makes it possible to identify systematic planning deviations, calculate project hour costs precisely and trace utilization peaks back to individual phases or employees. For project controlling, this creates a data basis that considerably improves plan-vs-actual comparisons, margin transparency and forecast quality. It requires working hours and project hours to be recorded and analysed on the same platform.
What are the current documentation requirements for working hours in projects in Germany?
Under § 16(2) ArbZG, working hours that exceed the regular working time on working days must be documented and kept for at least two years. Following the ECJ ruling and the Federal Labour Court decision, the complete daily working time must be recorded. For project-based companies, this means documenting both total working hours and their allocation to projects, to meet both the statutory obligation to provide evidence and the needs of internal control. Incomplete or retrospective documentation is regularly insufficient in an inspection.
