![\"Diagram](\"/article-assets/carico-di-lavoro/carico-di-lavoro-capacita-netta.jpg\")
You don't settle the difference by arguing: you settle it when workload stops being an impression and becomes a number next to a role.
\nWorkload is the amount of activity a role has to carry in a defined period, measured in the time those activities take up and not in the number of items on a list.
\nIt holds in a professional firm with two team members, in a fifteen-person family business and in an organization of a hundred: the scale changes, not the fact that the workload stays invisible.
\n\n\n\"I'm overloaded\" remains an opinion until the workload becomes a number tied to a role: from that point on, the discussion is no longer about who is more tired, but about what gets dropped, standardized or moved.
\n
This article walks through the inventory of recurring activities, the comparison with available capacity, the four moves of redistribution and the mistakes that make it useless.
\nTwo people with the same schedule can carry different workloads, and the difference lies in what goes into those hours.
\nFor \"carico\" (load), used figuratively, the Italian Treccani dictionary records a \"burden, weight of various kinds that falls on someone\" [1].
\nApplied to work in a company, the core stays the same — something that weighs on someone — and the object changes: not a weight on your shoulders, but the activities a role has to carry in a defined period.
\nThere is only one unit of measure that makes the definition operational: hours per month tied to a role, not to a person and not to the number of items on a list.
\nFrom here you can see the three boundaries that get confused most often in companies.
\nWorking hours say how long a person is present, not how much work has been assigned to that time.
\nThe number of open tasks counts items, not hours: ten ten-minute files and two half-day files take up the same space on a list.
\nDeadline pressure concerns the when, not the how much: a sustainable workload concentrated in three days gives the same signals as a workload that is too large, and the two conditions are corrected in different ways.
\nOnce the three boundaries are clear, the question becomes measurable: how many hours a month does the full set of that role's activities take up?
\nThe person who answers \"we're at our limit here\" and the one who answers \"it's doable\" are describing the same department, and neither is using a yardstick.
\n\n\nAs long as workload remains a perception, the meeting turns into a contest of impressions about who is more tired; once it becomes a number tied to a role, it becomes a decision about what gets dropped, standardized or moved.
\n
An institutional way out already exists, and it is an organizational one, not a medical one.
\nIn Italy, the November 18, 2010 circular of the Ministry of Labor and Social Policies sets out the methodology for assessing work-related stress risk for all employers, public and private; that process opens with a mandatory preliminary phase, which consists of \"collecting objective and verifiable indicators, numerically measurable where possible\" [2].
\nAmong the content indicators, the same source lists \"workloads and work pace,\" alongside working hours, shifts and the match between skills and requirements [2].
\nTwo choices in that method are worth applying even outside legal compliance.
\nThe first: the assessment covers homogeneous groups of workers, identified by job role or by organizational unit, and not individuals [2].
\nMeasuring a role keeps the discussion away from comparisons between people.
\nThe second: sentinel events.
\nSick leave, employee turnover, disciplinary actions and formal complaints are organizational signals, to be read against a baseline, that is, the average value over the last three years [2].
\nWithout a yardstick, the problem never makes it into any discussion: in the European ESENER 2024 survey (41,458 establishments with at least five employees in 30 countries, May–October 2024), a quarter of EU-27 establishments, 25%, report having none of the psychosocial risk factors considered [6].
\nNational averages also hide distributions: overtime accounts for 3.0% of hours worked in Italian companies with employees [3], and it doesn't tell you who carries those hours.
\nCounting everything is impractical; counting the activities that come back every month takes a couple of hours per role.
\nThe inventory is a list headed by a role, not a person, with four columns: recurring activity, frequency, average duration of one execution, who else knows how to do it.
\nFrequency times duration gives hours per month, and the sum of the column is that role's planned workload.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n| Recurring activity | Frequency | Average duration | Hours/month | Who else can do it |
|---|---|---|---|---|
| Customer invoicing | twice a month | 4 h | 8 | — |
| Payment reminders | weekly | 1 h 30 | 6 | — |
| Answering the phone | continuous | — | 22 (recorded) | reception |
scroll the table →
\nThree distinctions make the inventory useful.
\nThe first separates planned work from incoming work: unscheduled requests, rework, unexpected issues.
\nYou measure it with tally marks on a sheet for two weeks: how many times, how many minutes.
\nThe second concerns seasonal peaks: the inventory must be read over twelve months, because accounting closes, campaigns and tax deadlines shift the same role.
\nBy how much is something to measure inside the company.
\nThe third flags dependence on a single person: the rows where the last column stays empty are workload and risk in the same spot.
\nA hypothetical scenario, in a family-run manufacturing business with about twenty employees where administration is a single person: invoicing, reminders, banking, the de facto switchboard, and the business owner stopping by between two rounds on the shop floor with three things to get done \"when you have a moment.\"
\nThat role's inventory closes at 190 hours against 168 available, and the last column stays empty on eleven rows out of nineteen.
\nWith an average company size in Italy of 3.9 employees in 2022, measured on the harmonized European scope of industrial and service activities [5], that kind of concentration is the ordinary condition, not the exception.
\nTiming each individual activity is the job of a time audit: here the unit observed is the role, not the day.
\nIf incoming work turns out to be the largest item, the next step is managing interruptions.
\nContract hours are not available hours, and the gap is what makes every comparison done from memory optimistic.
\nIn defining hours worked, ISTAT, Italy's national statistics institute, excludes \"hours paid but not actually worked (annual leave, public holidays and sick leave, etc.), meal breaks and commuting between home and work\" [3].
\nA role's net monthly capacity is obtained through successive subtractions, in this order.
\nWhat remains is the capacity to compare with the planned workload from the inventory.
\n
The ratio between the two numbers is the saturation index, and it can be read in three ways.
\n100% is not a chosen threshold: it is the point where planned workload equals net capacity, in other words an identity of the ratio.
\nHow much margin to keep below that point depends on the company, and there is no reference percentage that holds outside the case that uses it.
\nThe second reading often leads to the wrong question, namely \"should we hire?\"
\nAdding capacity from outside is the slowest lever: in Italy's Excelsior bulletin for May 2026, 42.9% of the profiles companies were looking for were hard to find, rising to 55.5% among skilled workers [4].
\nIn the months between the decision and the new hire's start, the only lever that acts on workload is redistribution.
\nPeaks only show up when you look at twelve months together: it is weekly planning seen from above.
\nRedistributing without dropping anything just moves the bottleneck two desks over.
\nThere are four moves and the order matters: the first two reduce the total, the third moves it, the fourth increases capacity.
\n![\"Diagram](\"/article-assets/carico-di-lavoro/carico-di-lavoro-quattro-mosse.jpg\")
In the family business scenario, the first three moves have an outcome you can write down: payment reminders become a half-page procedure that a second team member carries out, the phone moves out of administration during the three hours of the accounting close, and the report nobody read is no longer produced.
\nThe workload doesn't disappear: it goes from 190 to 150 hours out of 168 available, and the dependence column empties on six of the original eleven rows.
\nThe procedures that make an activity transferable come from process mapping: here their job is to create a second person who can do the work.
\nMoving work is a matter of effective delegation, and the order in which you choose what goes first is that of priority management, applied to the scope of a role rather than to a single day.
\nWhen the third move stalls because approval always comes back to the same desk, the knot is not workload but micromanagement, which has its own remedies and its own ladder out.
\nFive recurring mistakes cancel out the measurement work before it has any effect.
\nA sixth mistake contains all the others: measuring once and never measuring again.
\nThe inventory is only as useful as its latest review.
\nThe ISTAT and Excelsior figures are Italian national sample averages, and the durations in the inventory are estimates: they describe a picture and make different rows comparable, they don't prove a causal link and they don't certify a time.
\nThe family business scenario is hypothetical, figures included — the 190 hours against 168 and the drop to 150: they show the procedure, not an achievable result.
\nNo saturation threshold here is taken from a source, because none of the admissible sources provides one.
\nIn roles with structural reactive exposure — customer service, switchboard, emergency response — incoming work is the work itself: there the reserved share loses its meaning and workload is measured on the volume of requests.
\nWork-related stress risk assessment is a legal requirement with its own roles and procedures [2]: this article deals with work organization and does not replace that assessment or professional advice on health matters.
\nWith a four-column sheet per role: recurring activity, frequency, average duration, who else knows how to do it.
\nFrequency times duration gives hours per month, and the sum is the planned workload.
\nUnplanned work is added with two weeks of tally marks.
\nWorking hours measure how long a person is present; workload measures how much work has been assigned to that time.
\nTwo roles with the same contract can have very different workloads: comparing people with the same hours tells you nothing useful.
\nReview the inventory at every change in headcount, product range or process, and in any case once a year.
\nSentinel events — absences, employee turnover, formal complaints — are read continuously, against the average value of the last three years [2].
\nThe second can only be tracked as a time series if it is always calculated the same way: the formulas and the denominator to declare are in how to calculate the turnover rate.
\nWork through the first three moves: eliminate activities with no recipient, standardize recurring ones to make them transferable, and move what's left together with the decision.
\nIf saturation stays above 100%, the problem is not organization but scope: the company has decided to do too many things with the people it has.
\nMeasuring workload starts from a list headed by a role, with the activities that come back every month, their frequency and their average duration.
\nMultiplying the two columns gives hours per month, and the sum is the planned workload.
\nAlongside it, measure incoming work with two weeks of tally marks: it is the part no plan can contain unless space is set aside for it.
\nCapacity is calculated by subtraction, starting from contract hours and taking away vacation, public holidays, fixed meetings and the share reserved for unplanned work.
\nThe ratio between the two numbers tells you which situation you're in: a seasonal peak, a structural excess or a fragmentation problem.
\nAbove 100%, the moves must be used in order, because the first two reduce the total and only the third moves it.
\nThe last row to look at is dependence: as long as an activity has only one possible performer, the redistribution holds until the first vacation.
\nWorkload is not a feeling to manage: it is a quantity to write down next to a role, and as long as it stays an impression, the meeting ends on who is more tired instead of on what gets dropped.
\nThe inventory, the comparison with capacity net of vacation, meetings and incoming work, and the four moves in order are the same path in a firm with two team members and in a company of a hundred employees.
\nWhen the measurement shows that the problem is not quantity but fragmentation, the path changes: that is the case of managing interruptions, where time is lost to inputs rather than volumes.
\nWhen instead the workload explodes with every unexpected event, the lever lies upstream: it is the path described in how to reduce unexpected problems.
\nWhen the workload to read is that of the person in charge, the signals that distinguish an intense period from an organizational problem are listed in too much work.
\nAfter two or three measurement cycles, the conversation changes subject: no longer how full everyone is, but which row of the inventory goes this month and who is the second performer of the one that stays.
\nIt is a difference you can see from the outside too: one person's vacation stops being a department problem, and the answer to a customer no longer depends on who happens to be in that day.
\n\n[1] Istituto della Enciclopedia Italiana, \"càrico²\", Vocabolario on line Treccani. Available at: https://www.treccani.it/vocabolario/carico2/
\n[2] Clerici, P. (Contarp), \"Il percorso di valutazione del rischio stress lavoro correlato\", Conoscere il rischio — Fattore umano series, INAIL, April 15, 2019. Available at: https://www.inail.it/content/dam/inail-hub-site/documenti/2015/10/Fattore_Umano_Percorso%20valutazione%20SLC_Apr%202019.pdf
\n[3] ISTAT, \"Il mercato del lavoro — IV trimestre 2025, una lettura integrata\", press release of March 12, 2026 (Q4 2025 data and 2025 annual average; companies with employees in industry and private services). Available at: https://www.istat.it/wp-content/uploads/2026/03/Mercato-del-lavoro-IV-trim_2025.pdf
\n[4] Unioncamere and Ministry of Labor and Social Policies, \"Lavoro: oltre 544mila entrate previste dalle imprese a maggio e 1,7 milioni entro luglio\", Excelsior Information System Bulletin, press release of May 8, 2026 (CAWI survey of more than 114,900 companies, March 17 – April 2, 2026). Available at: https://excelsior.unioncamere.net/sites/default/files/documenti/08052026_com_Excelsior_FIN_MLPS.pdf
\n[5] ISTAT, \"Industria e servizi — Strutture produttive\", Noi Italia 2025 (reference data 2022). Available at: https://noi-italia.istat.it/pagina.php?id=3&categoria=10&action=show&L=0
\n[6] EU-OSHA — European Agency for Safety and Health at Work, \"First findings of the Fourth European Survey of Enterprises on New and Emerging Risks (ESENER 2024)\", February 7, 2025 (41,458 establishments with at least five employees in 30 countries, survey May–October 2024; the 25% share is based on EU-27 establishments). Available at: https://osha.europa.eu/sites/default/files/documents/first-findings-esener-2024_EN.pdf
","headings":[{"level":2,"text":"Learning to tell workload apart from hours worked","id":"learning-to-tell-workload-apart-from-hours-worked"},{"level":2,"text":"From perception to numbers: making work overload visible","id":"from-perception-to-numbers-making-work-overload-visible"},{"level":2,"text":"The inventory of recurring activities: how to measure workload","id":"the-inventory-of-recurring-activities-how-to-measure-workload"},{"level":2,"text":"Comparing workload with available capacity, seasonal peaks included","id":"comparing-workload-with-available-capacity-seasonal-peaks-included"},{"level":2,"text":"Drop, standardize, move: managing workload across the team","id":"drop-standardize-move-managing-workload-across-the-team"},{"level":2,"text":"The mistakes that make workload redistribution useless","id":"the-mistakes-that-make-workload-redistribution-useless"},{"level":2,"text":"Limits and conditions of applicability","id":"limits-and-conditions-of-applicability"},{"level":2,"text":"FAQ","id":"faq"},{"level":3,"text":"How do you measure workload without dedicated software?","id":"how-do-you-measure-workload-without-dedicated-software"},{"level":3,"text":"What is the difference between workload and working hours?","id":"what-is-the-difference-between-workload-and-working-hours"},{"level":3,"text":"How often should the measurement be repeated?","id":"how-often-should-the-measurement-be-repeated"},{"level":3,"text":"What should you do if workload exceeds capacity and you can't hire?","id":"what-should-you-do-if-workload-exceeds-capacity-and-you-cant-hire"},{"level":2,"text":"Operational summary","id":"operational-summary"},{"level":2,"text":"Conclusion","id":"conclusion"},{"level":2,"text":"Sources and references","id":"sources-and-references"}],"tldr":"Do \"I'm overloaded\" and \"I'm disorganized\" describe the same condition or two different problems?","tldrItems":null}