Is it Time for Four? An Analysis of the Four-Day Workweek
Bibliographic record
Abstract
Have you ever sat down on a Sunday night wishing that your weekend did not fly by and was a bit longer? Do you sometimes wish you had more time to do the things you love outside of work? This is where the four-day workweek comes in. Over time, we have seen the standard United States workweek evolve from what was once a sixty-hour week, to a forty-hour week, and now we see that four-day, compressed workweeks are being implemented across not only the United States, but around the world. Increasing amounts of attention have been going towards work-life balance, job satisfaction, and employee productivity and in this paper, we will be looking at how the four-day workweek affects these variables and explore the reasons behind different findings. There have been many case studies and amounts of research conducted on these topics, but the result varies. Typically, the four-day workweek consists of four 10-hour days, but in some cases, it consists of four eight-hour days. Generally, pay will remain the same for employees who take on this schedule, which is an important factor. There are many reasons behind why a company would implement such a schedule, which include the desire to reduce costs of operating daily, reducing employee burnout, and increasing employee retention, in addition to the variables just discussed, work-life balance, productivity, and job satisfaction (Agovino, 2021). The four-day workweek is a very popular topic today and we will seek to understand the ways in which it affects employees.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.012 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.004 | 0.007 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.006 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".