How do you measure a team's workload?

A team's workload is measured by reading, at team level rather than individual level, the gap between what is requested, the resources available and the deadlines set. A structured collective measure, repeated at a regular cadence, tracks clarity of priorities, quality of interfaces and the share of unplanned work absorbed. Counting hours is not enough: it measures a duration, not intensity or trade-offs.

What is the difference between prescribed, actual and perceived workload?

Prescribed workload is what the organisation asks for: objectives, volumes, deadlines. Actual workload is what the team really does to meet them, including adjustments and rework. Perceived workload is how that effort is experienced, which depends on resources and on the meaning of the work. Making workload objective means making the gaps between these three levels readable.

Does assessing workload objectively amount to controlling employees?

No, provided the system is collective by design. Collection is pseudonymous, reporting is aggregate-only and anti-re-identification thresholds prevent any reading of groups that are too small. Neither the employer nor the provider can consult an individual response. This structural constraint protects people and, at the same time, secures the sincerity of answers.

Is mental load at work the employer's responsibility?

On its organisational side, yes. The employer must assess psychosocial risks, including work intensity, unclear objectives and contradictory instructions, and organise their prevention in the DUERP. Whatever concerns an individual's health belongs to occupational medicine. Collective steering addresses organisational causes, never individual situations.

What should you do when a team is overloaded?

First qualify the situation with the team: temporary peak or structural imbalance, internal cause or failing interface. Then take a proportionate regulation decision, most often an arbitration rule, a renegotiated scope or a paused initiative. Finally assign it to an owner, date it and verify its effect in the next cycle.

Workload: measuring it at team level

Workload is the most discussed and least objectively assessed subject in any organisation. Everyone talks about it, in team meetings and with employee representatives alike, yet nobody holds a shared reading that would support a decision. So leadership arbitrates on intuition, or waits for a sick leave or a resignation to settle the matter.

Why workload resists measurement

The difficulty starts with vocabulary. One word covers three distinct realities that ergonomics has long told apart.

Prescribed workload is what the organisation asks for: objectives, volumes, deadlines, procedures, job scope. Actual workload is what the team really does to meet those demands, including the adjustments, rework and workarounds nobody planned. Perceived workload is how people experience that effort, which depends on the resources available to them and on the meaning they find in the work.

These three levels never fully coincide. The gap between prescribed and actual workload measures the share of work invisible to management. The gap between actual and perceived workload signals that resources, room for manoeuvre or recognition are not keeping pace. Assessing workload objectively means making those gaps readable at the level of a collective, without pretending to reduce them to a single figure.

Mental load at work: what belongs to the organisation

Mental load at work is the effort of coordination, anticipation and arbitration that work demands on top of its execution. It rises when priorities change often, when instructions contradict each other or when interruptions fragment activity. The French occupational health institute INRS lists "contradictory instructions" and "unrealistic or unclear objectives" among the components of work intensity.

In this article, mental load is treated as a property of the organisation, not a state of individuals. What can be read collectively is the frequency of unresolved trade-offs and competing priorities. Whatever concerns an individual's health belongs to occupational medicine and to the procedures designed for it.

Three classic mistakes when measuring workload

Counting hours

The most common reflex is to count time. Time is easy to collect, but it says nothing about intensity, interruptions or the quality of the outcome. Two teams with identical hours can live opposite situations: one absorbs a stable load with clear priorities, the other spends its days reshuffling priorities.

Time tracking measures a duration, not a load. It says nothing about actual workload, let alone perceived workload. It also tends to shift the debate towards attendance control, which erodes trust without improving the reading.

Individualising

The second mistake is to handle workload person by person: one-to-one interviews, case-by-case relief plans, ad hoc reassignments. These responses have their place when an individual situation requires them, but they do not address what produces the overload of an entire team.

Team overload almost always has an organisational cause: a poorly regulated inflow, an interface that sends work back upstream, an objective set without matching means. Read individually, it becomes a question of competence or personal resilience. Read collectively, it becomes a steering question.

Waiting for the alert

The third mistake is to wait for a strong signal: sick leave, the resignation of a key person, a formal alert from employee representatives. By then the situation has been in place for months and options have narrowed. INRS reminds employers that prevention should "give priority to collective measures likely to avoid risks as far upstream as possible". Reading workload early is precisely what a steering-oriented approach to psychosocial risk prevention makes possible.

Reading the gap between workload, resources and deadlines at team level

A collective approach shifts the question. It is no longer whether a given person is overwhelmed, but whether a given team has resources and deadlines compatible with what it is asked to deliver. The unit of reading is the operational scope: a team, a site, a department.

Several dimensions can be tracked in a structured way, cycle after cycle:

The fit between requested volume, available headcount and set deadlines.
Clarity of priorities and the frequency of conflicting trade-offs.
The quality of interfaces with upstream and downstream teams, including rework and requests outside the agreed process.
The share of unplanned work absorbed without renegotiating scope.
The team's ability to raise a difficulty and get an answer.

These dimensions share one feature: they describe how the collective functions, not the state of individuals. They can be set alongside data already available, such as delivery delays, declared overtime or postponed leave. None of these data points explains a situation on its own; their convergence shows where to look.

Workload regulation begins when this reading is shared with the team concerned. A signal is not a diagnosis. The discussion with the collective is what separates a temporary peak from a structural imbalance, and what allows a proportionate action to be chosen.

What the prevention framework says, in plain terms

French labour law does not impose a method for measuring workload. It imposes an outcome: the employer must assess the risks employees are exposed to, including psychosocial risks, and organise their prevention. That assessment is formalised in the single occupational risk assessment document, the DUERP. INRS states that psychosocial risks "must be taken into account in the same way as other occupational risks".

Among the six families of psychosocial risk factors identified by INRS, the first is work intensity and working time. It covers pace constraints, unrealistic or unclear objectives, uncontrolled demands for versatility, contradictory instructions and long working days. Lack of autonomy forms another family, autonomy being understood as "the possibility of being an actor in one's own work". The imbalance between high demands and a lack of autonomy is described there as a strained work situation.

The framework also sets a direction for method. INRS indicates that "a collective prevention approach, centred on work and its organisation, is to be preferred", and that actions centred on employees' individual resources, while sometimes necessary, are not sufficient. Its five-step approach, from preparation to follow-up of actions, runs through the analysis of real work situations. In other words, assessing workload objectively at team level is not one methodological option among others: it follows the path recommended by the reference institution. Related duties are covered in our article on QVCT duties and their steering.

What this changes for a leadership team or an HR director

For leadership, an objective, team-level reading of workload changes three things.

First, the nature of the information that comes up. Instead of a sum of individual complaints or an annual satisfaction score, the leadership team holds a reading by scope: where the gap between demand and resources is widening, for how many cycles, and in connection with which recent decision. Trade-offs can then be debated on collective facts rather than impressions.

Second, the nature of decisions. Workload regulation rarely translates into a hire. It usually takes the form of an explicit arbitration rule between projects, a renegotiated scope with an upstream team, a paused initiative or a clarified role. These are leadership decisions, not HR adjustments.

Third, the nature of follow-up. A regulation decision has an effect only if it is assigned to an owner, dated and paired with a verifiable completion criterion. The next cycle shows whether the gap has narrowed on the scope concerned. Without that loop, workload goes back to being a topic of conversation.

One framing point is essential. This reading covers collective aggregates. Collection is pseudonymous, reporting is aggregate-only, and anti-re-identification thresholds prevent the display of groups that are too small. Neither the employer nor the provider can read an individual response. This constraint is not only a safeguard for people: it conditions the sincerity of answers, and therefore the reliability of the measure. The terms used here are defined in the collective dynamics glossary.

Where to start

Pick one or two scopes where the workload issue is acknowledged: a team under sustained strain, a department at the junction of several flows, a site that absorbs the overflow of others. Install a short, regular reading shared with the team, and take a first regulation decision before extending.

Brainmood structures that cycle: structured collective measurement, steering-oriented reading, operational stabilisation and decision-ready reporting, following a four-pillar method. The first prioritised trade-offs are delivered within four to six weeks. To discuss your context and identify a first scope, a 30-minute discussion is enough.

Workload: assessing it objectively at team level, without individual control.