Where Did the 5-Day, 260-Day Work Year Come From?

The number nobody questions

Every salary-to-day-rate calculator, including the one on this site, quietly assumes something: that a working year looks like roughly 260 days, built from 5 days a week for 52 weeks, minus whatever holidays you're entitled to. It's such a universal starting point that it barely registers as an assumption at all — it just feels like how work works.

It isn't a law of nature. It's a specific historical outcome, decided within living memory of people who are still alive today, and it's worth knowing where it actually came from — partly because it's genuinely interesting, and partly because it makes clear that "260 working days" is a policy choice, not a physical constant, which matters more than it sounds like the next time someone proposes changing it.

Before the 40-hour week was normal

At the turn of the 20th century, a 60-hour work week was unremarkable for American workers. Government tracking from 1890 found manufacturing workers commonly logging 100-hour weeks; by the late 1890s, domestic workers in Massachusetts were documented working 78 to 83 hours a week. Six-day weeks were standard. Sunday off was often the only reliable break, sometimes with a half-day on Saturday if you were fortunate.

The push toward shorter hours had been building for decades before anything changed nationally. Labor organizations were calling for an 8-hour day as early as the 1880s — the Federation of Organized Trades and Labor Unions called for it by name in 1886 — but early attempts at legislation were limited, patchily enforced, or struck down by courts. This wasn't a quick fix; it was a fight that ran across generations of organizing before it produced durable national change.

Ford's role, and its limits

Henry Ford's contribution is real but frequently overstated. In 1926, Ford moved his automobile plants to a 5-day, 40-hour week with no reduction in pay — a genuinely notable move from one of the largest employers in the country. His stated reasoning was partly self-interested: workers with leisure time and disposable income were also potential customers, including for cars.

But Ford was accelerating a trend, not originating it. Organized labor had been pushing for shorter hours for decades before Ford's plants changed policy, and Ford's move affected his own workforce — it didn't become a legal standard for the country. That took federal legislation more than a decade later.

The law that actually made it standard

The Fair Labor Standards Act (FLSA), signed by President Franklin D. Roosevelt in 1938 as part of the New Deal, is the specific legal event that made a shorter work week a nationwide baseline rather than one company's policy. It came after earlier attempts — including the National Industrial Recovery Act — had been struck down by the Supreme Court, and after years of continued labor action, including a wave of strikes in 1919 alone involving roughly 4 million American workers.

The FLSA's original version capped the work week at 44 hours and created the first federal overtime rules, requiring time-and-a-half pay beyond that threshold. An amendment in 1940 brought the cap down further, to the 40 hours that has remained the enduring US standard ever since. It's this 40-hour, 5-day figure — not Ford's factory policy on its own — that eventually became the implicit default baked into how salaries, day rates, and "working days per year" get calculated almost everywhere, including in calculators like this one.

Why an employee costs more than their salary

Separately from the history of hours, there's a related concept worth understanding if you're converting between salaries and day rates: total cost of employment, sometimes called employer on-costs.

The salary figure on an offer letter is not what an employee actually costs their employer. Once you add employer-side payroll taxes, pension or retirement contributions, and the administrative cost of benefits, the real cost to the employer typically runs 15–25% above the stated salary. This is largely invisible to the employee — it's paid by the employer on top of, not out of, the salary figure — which is exactly why it's easy to underestimate.

This gap matters directly for day-rate conversions. A contractor doesn't receive any of that additional employer-side spending — no employer pension contribution, no employer tax contribution, no subsidized benefits. So when a contractor's day rate looks meaningfully higher than an equivalent employee's implied daily salary, a real portion of that gap isn't profit — it's simply making visible, and paying for directly, costs an employer would otherwise have absorbed quietly on the employee's behalf.

Day rate and per diem aren't the same thing

These two terms get used loosely and interchangeably in casual conversation, but they mean genuinely different things, particularly for tax purposes.

A day rate is compensation for a day of labor. It's income, plain and simple, and taxed as such.

A per diem (Latin for "per day") is a reimbursement for expenses incurred while working — typically travel, meals, and accommodation. Because it's compensating a cost rather than paying for labor, many jurisdictions treat per diem payments up to a specified limit as non-taxable, provided they genuinely correspond to expenses incurred rather than functioning as disguised extra pay. The distinction isn't just semantic — it has real tax consequences, and contracts that blur the two informally can create real problems if a tax authority later disagrees with how a payment was categorized.

A quick word on IR35

If you're contracting in the UK, you'll run into IR35 sooner or later, and it's worth understanding in plain terms rather than just knowing it exists.

IR35 is tax legislation aimed at identifying contractors who are, in practical terms, working like employees — same hours, same day-to-day supervision, same integration into a company's structure — despite being engaged through a limited company rather than direct employment. A contract found to sit "inside IR35" gets taxed broadly the way employee income would be, which removes much of the tax efficiency that's historically been part of the appeal of contracting. This is part of why day rates for inside-IR35 roles tend to run higher than comparable outside-IR35 ones: some of the financial case for the uplift comes specifically from tax treatment that inside-IR35 status removes.

What this means for the number you actually use

None of this history changes the arithmetic — a working year is still, by convention, built from days per week times weeks per year minus days off. But it reframes what that convention actually is: a specific, comparatively recent legal and cultural settlement, not an unquestionable fact about how humans must work. Various compressed-week experiments and proposed legislation exist today precisely because that settlement has never been permanent — it was negotiated once, and there's no rule saying it can't be renegotiated again.

For your own numbers, rather than the history, the Salary to Daily Rate Calculator handles the conversion in either direction — including going from a day rate back to an equivalent salary, correctly removing any contractor uplift first if the rate you're starting from already includes one.

Sources

1. U.S. Department of Labor. Fair Labor Standards Act of 1938, as amended (1940 amendment establishing the 40-hour standard week).
2. History.com. The 5-Day Work Week: How We Got Here.
3. National Geographic. A 4-day workweek? Here's how history shaped our working lives.

---

This article is for general informational purposes and is not tax or legal advice. Per diem rules, IR35 status, and employment classification vary by jurisdiction and individual circumstance — consult a qualified accountant or tax advisor for guidance specific to your situation.