To regulate workload, compare demands with resources, deadlines and the activity actually needed. Volume and time data are useful, but they need discussion with the team to understand interruptions, rework and trade-offs. This reading prepares a decision; it does not provide an individual diagnosis.
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 perspectives can reveal differences: unplanned work, rework, coordination constraints or limited room to act. They cannot be subtracted as equivalent measurements; examine the situations described and the resources actually available. 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 workload includes the cognitive demands of work. This article focuses on coordination, anticipation and trade-offs required by the organisation. 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 is insufficient to describe 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 records provide information about duration and can contribute to monitoring applicable duties. They do not describe intensity or difficulties on their own. Add volumes, unplanned work and discussion of the conditions for completing it.
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 can have several organisational causes: 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. These situations require an appropriate response without waiting for a collective survey. INRS also recommends acting upstream on risk factors. 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
Under French law, the employer must take necessary measures to protect health and safety, assess risks and organise prevention, including for psychosocial risks. The DUERP records assessment results. Workload and working-time monitoring requirements also depend on the situation and applicable agreements, particularly for annual day-based arrangements under Article L3121-60. A collective questionnaire alone does not fulfil these duties. The regulatory framework described by INRS explains the principles.
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 INRS prevention approach concerns work and its organisation. It includes preparation, analysis and action follow-up. This framework can inform collective workload discussions without validating a particular commercial method. 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. Depending on established causes, regulation may require extra capacity or recruitment, a priority rule, a renegotiated scope, a paused initiative or a clarified role. Specify what belongs to the team, leadership and the functions involved.
Third, the nature of follow-up. To track a regulation decision, assign it to an owner, date it and specify a verification 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 aggregated within the defined scope, and anti-re-identification thresholds limit the display of groups that are too small. Reporting for executives and managers is designed at the collective level. Pseudonymisation is not anonymisation: access, possible cross-referencing and retention rules must be specified. Protecting responses supports trust without guaranteeing representativeness. The terms used here are defined in the collective dynamics glossary.
Worked trade-off: three requests, limited capacity
Entirely fictional example, with no client outcome. A team and its managers estimate 20 days of capacity for planned tasks in the following week, accounting for absences and recurring activity. Requests total 26 days: delivery A, 10; rework B, 8; launch C, 8. These workload estimates remain open to discussion: skills and dependencies can make days non-interchangeable.
Leadership reviews deadlines with the team and requesting functions. In this example, A keeps 10 days, B keeps 8 and only 2 preparation days remain for C. Its other 6 days are postponed after agreement on a new deadline: 10 + 8 + 2 = 20 planned days. The choice must not simply transfer overload to another team.
The operations lead records the decision and informs requesters before work starts. A midweek check allows new requests to be reconsidered; the end-of-week review compares completed work, unplanned activity, postponements and team feedback. The aim is to check whether the capacity assumption held, without presuming a productivity gain or health improvement.
Use the thirty-day action plan to adapt this example: finding, action, owner, deadline and review criterion. The executive dashboard helps raise decisions beyond the team's authority.
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, explore the organisational diagnosis and Brainmood pilot conditions.