A model employment framework being discussed by a group of large employers would offer the four-day week not as a contractual entitlement but as a conditional one, granted quarterly to teams whose measured output holds steady. The word used throughout the draft is earned, which appears alongside the word trust with a frequency that participants describe as load-bearing.
The commercial logic is real. Four-day week trials have generally reported maintained output, and employers who have read those results carefully noticed that maintained output was the condition, not the consequence. A framework that makes the condition explicit is, in one sense, simply honest. In another sense it converts a benefit into a target.
Measurement is where the framework becomes interesting. Under the draft, teams would agree their own output indicator with their manager, subject to a standard library of suggestions. The library reportedly contains forty-one indicators, of which thirty-eight are counts of things and three are attempts to measure whether the counted things were worth doing.
“The fifth day would not be taken away,” a spokesperson for the group would explain. “It would be held in reserve. We prefer to think of it as a day that is available to the team should the team turn out to need it, and we are confident most teams will discover they need it in November.”
The predictable effect would be a quiet inflation of the measured work. When a day off depends on a number, the number improves, and it improves first in the ways that are easiest to improve. Several participants in the discussion are said to have raised this. The minutes record the concern as noted.
There would also be a fairness problem across functions. Output is countable in a support queue and stubbornly uncountable in research, legal or safety work, where the good months look identical to the empty ones from the outside. Under the draft, those teams would be assessed by manager judgement, which is to say by the thing the framework was built to replace.
The four-day week remains, on the evidence, a good idea. What the framework illustrates is how a good idea survives contact with an organisation: intact in name, conditional in practice, and accompanied by a dashboard that nobody asked for and everybody will now check on a Thursday.
If you liked this…
Your resignation may need approval from your replacement
A proposed offboarding workflow would route the leaver's final knowledge transfer through the system inheriting the work. The system would be permitted to ask follow-up questions. It would have many.
Your voice may be scored for tone — never for feeling
Emotion recognition at work is prohibited in Europe. A compliance approach now circulating among vendors would keep the product intact and change the noun.
Being served by a person may become a paid upgrade
A pricing model circulating in the service industries would turn human assistance into a chargeable tier. The fee would be small. Its exact size would tell you, for the first time, what a company thinks your patience is worth.
Still laughing
We made it up. Then reality caught up.
What we wrote
We wrote it in 2021
One day the junior developer's main skill could be describing the problem clearly enough for the machine to solve it.
What actually happened
Reality caught up in 2025
AI coding assistants are built into mainstream development tools, and producing code from a plain-language description is now a routine part of professional software work.
Vendor product documentation and developer surveys on assistant adoption.
The joke was the job description. The job description was updated.
MISTAKE
TOMORROW, DELIVERED TODAY.
One email a week. The future, before it files a press release.
Worst case: you laugh. Best case: we predicted the future.
