Workforce analytics

What is workforce analytics?

Workforce analytics uses data about how people spend their working time to plan capacity, budgets and staffing. This guide explains the four types, the metrics a time tracker can support, and how to keep analytics fair and privacy-first.

Four types, explained clearly
Metrics that come from time data
Privacy-first, team-level reporting

Start free Pricing

From descriptive to predictive

Start with hours by team and project, then add budget checks, trends and capacity forecasts as your data history grows.

Project budget tracking

Compare booked hours with planned hours per project, so overruns show up while there is still time to act.

Utilisation and overtime by team

Follow utilisation and overtime trends by team, to spot overloaded groups before deadlines slip.

No individual scores

zeitfair does not rank or score people. Reports are built for teams and projects, not performance reviews.

Workforce analytics turns work data into planning decisions

Workforce analytics is the practice of using data about how people spend their working time to plan capacity, budgets and staffing. The data can come from HR systems, project tools and time records. Time records are often the most dependable source, because they show what was worked on, for how long and under which project.

Most analytics projects stall for the same reason: the underlying data is incomplete. If hours are logged late or only at month end, every chart built on them is a guess. The foundation is consistent, daily time recording.

What is workforce analytics?

Workforce analytics uses data about people's work to answer questions about capacity, cost and planning. Typical questions include whether a project will finish within budget, which team will run out of capacity before a launch, and whether overtime is rising in one department.

The answers should guide decisions at group level. Good workforce analytics explains why a team is overloaded or why a project is drifting, and what could change. It does not try to explain why one individual is slower than another. That kind of question leads to surveillance, and it rarely produces better planning.

The four types of workforce analytics

Analysts often describe workforce analytics in four types. Each one builds on the one before it:

Descriptive: what happened? For example, how many hours did the design team log last quarter?
Diagnostic: why did it happen? For example, why did one project run over budget?
Predictive: what is likely to happen next? For example, will the team run out of capacity before the launch?
Prescriptive: what should we do? For example, move a role to another project or rebalance deadlines.

Most teams get the most value from the first two. Predictive models need a long history of clean data, and prescriptive recommendations need clear decision rules. A time tracker is a strong source for descriptive and diagnostic work.

Descriptive analytics

Descriptive analytics summarises past work: hours by team, project and month. It usually appears as a standard report or dashboard, and it is the starting point for every other type.

Diagnostic analytics

Diagnostic analytics looks for causes. Comparing planned and actual hours, finding tasks that consistently take longer than expected, or linking a rise in overtime to a deadline are all diagnostic questions.

Predictive analytics

Predictive analytics estimates future load, such as the free capacity over the next six weeks, based on current bookings and past patterns. The forecast is only as good as the time that has been recorded.

Prescriptive analytics

Prescriptive analytics suggests or prepares actions, such as reassigning work or changing a project plan. People should make these decisions, with the team involved, rather than leaving them to an automated rule.

Workforce analytics metrics

Time data supports a focused set of metrics. The table below lists the ones a time tracker can answer, and the level at which each should be reported.

Metric	Question it answers	Report at
Utilisation rate	How much available time goes into planned or billable work?	Team, project
Budget against actual	Are booked hours on track against planned hours?	Project
Overtime trend	Is extra time rising over weeks or months?	Team
Absence rate	How much planned capacity is lost to approved absences?	Team
Capacity forecast	How many hours are free in the coming weeks?	Team, project

Metrics such as turnover, time to hire or engagement come from HR or survey tools, not from time records. They can matter for a people strategy, but a time tool should not claim to produce them.

Workforce analytics examples

Project budget forecasting

After two weeks, a project manager sees booked hours running ahead of plan. A diagnostic view shows that the extra hours come from an unplanned review round. The team can agree a scope change early, instead of discovering the overrun on the final invoice.

Overtime as an early warning

A team-level overtime trend rises across three sprints. The manager reviews priorities and deadlines with the team. The conversation is about workload and planning, not about how many hours any one person worked.

Capacity planning before a launch

A forecast of available hours for the next six weeks shows that the design team is close to full. The team moves one non-urgent task to the next quarter, and the launch keeps its date.

These examples are illustrative scenarios, not customer results.

A privacy-first approach to workforce analytics

Workforce analytics has a poor reputation in many organisations, and often for good reason. Tools that score individuals, track activity or rank people damage trust and create legal risk. A privacy-first approach keeps the planning value and leaves out the surveillance.

Team and project level, not individual scores

zeitfair reports on teams and projects. It does not produce productivity scores for individuals, and it does not rank employees. Reports are designed for planning meetings, not for performance reviews.

Keep groups large enough to be anonymous

A report that breaks hours down to one or two people is effectively a personal report. Show results only for groups large enough that no single person can be identified. This is good practice rather than a fixed legal number, so agree the threshold with your data protection officer. Where AI work summaries are offered, a manager sees an individual's summary only if the workspace enables it and the employee consents.

Involve the works council in Germany

The Federal Labour Court confirmed co-determination rights for time recording systems on 13 September 2022 (BAG, 1 ABR 22/21). Analytics built on the same data usually raises the same questions. Agree early which reports will exist, who can see them, and how long data is kept.

Under the GDPR, workforce analytics should follow four principles:

Purpose limitation (Art. 5(1)(b)): use time data for planning, budgets and working-time compliance only.
Data minimisation (Art. 5(1)(c)): collect what the purpose needs, and nothing more.
Transparency (Art. 13): tell employees which data is recorded and which reports are produced.
Storage limitation (Art. 5(1)(e)): delete data once the retention period ends.

Larger analytics programmes may need a data protection impact assessment (Art. 35). zeitfair stores data in the EU (Frankfurt), offers a data processing agreement online, and supports data export and deletion.

What to avoid

Some features do not belong in workforce analytics at all. Avoid tools that record keystrokes, take screenshots, measure mouse movement or assign activity scores to individuals. These approaches measure presence rather than results, they are hard to justify under the GDPR, and they tend to lower data quality, because people learn to game them.

zeitfair deliberately does not offer these features. Its analytics answer planning questions with time data that employees can see and understand.

How to start with workforce analytics

Pick one question. For example: are our projects within budget, or is overtime rising in one team?
Check the data. Make sure time is logged daily, projects are tagged consistently and absences are recorded.
Agree the reports. Decide with managers and, where required, the works council, which reports exist and who sees them.
Review every two weeks. Look at trends rather than single entries, and agree a concrete action when a trend is clear.
Expand carefully. Add metrics only when a real decision needs them.

Get started

zeitfair is free for up to 3 users. Set up your projects, invite your team and start tracking. To see how these reports are built, read the workforce analytics overview. For the basics behind the data, see time tracking and project time tracking.

This page is general information, not legal advice. Check your obligations with a lawyer or your data protection officer before you introduce new reports.