Hours are a lagging indicator — the real measure is control
In 14 years of managing people, I've watched plenty of folks burn out on 45-hour weeks and plenty of others thrive on 55. The difference was almost never the count of hours. It was whether they controlled when, where, and how those hours were spent. A 55-hour week of your own choosing at work you care about is a different animal than a 48-hour week where your manager pings you at 9pm expecting an answer.
This tool produces a single balance score out of 100, weighted on four inputs: hours per week, schedule flexibility, off-hour boundaries, and job satisfaction. The score uses hours above 40 as a penalty (each extra hour subtracts 2 points) and the three 1-10 subjective inputs as positive drivers. It's deliberately rough. What it's good for: benchmarking the same job at two points in time, or comparing two jobs before you take an offer.
A 75 or above means you've got a sustainable setup. 55-74 is the murky middle — some weeks are fine, some weeks you're resentful. Below 55 is structurally broken; the job is asking more than it gives. If you score there for more than a quarter, something has to change, either the job or your relationship to it.
How to rate the four inputs honestly
Hours per week. Your real average over the last 90 days, not your good weeks. Most people underestimate by 3-5 hours. Check your calendar, time tracker, or laptop usage if you're unsure. Include evening email, weekend Slack checks, and pre-work prep time. If you commute and your commute is mandatory (not a choice), add half the commute time.
Flexibility (1-10). Can you move a 2pm meeting to 4pm without a two-day negotiation? Can you start at 10 instead of 9 on a tired day? Can you work from a different city for a week? 10 = "I mostly set my own schedule, subject to client calls." 1 = "I'm on a rigid clock, need permission for anything, get flagged for being 5 minutes late."
Boundaries (1-10). How protected are your evenings, weekends, and vacations? 10 = "My team respects my off-hours; nobody texts me about work after 6pm." 1 = "Slack pings all evening, email on weekends, vacation routinely interrupted." Many jobs look fine on paper but fail here.
Job satisfaction (1-10). Day-to-day enjoyment, not prestige or pay. 10 = "I'd do this work even for 20% less pay." 1 = "I dread Mondays and mentally check out by Wednesday." Most mid-career workers land 6-8; above 8 is rare and worth protecting.
What a real 85+ looks like
An 85+ score tends to share a specific structure. I coached a software engineer who landed there after two years of deliberate moves: 42 hours/week, 9/10 flexibility (fully remote, flexible schedule), 8/10 boundaries (his team honored off-hours, had a public on-call calendar), 8/10 satisfaction (he worked on infrastructure he'd helped design). Score: 92.
He didn't start there. Three years earlier he'd been at a growth-stage startup: 58 hours/week, 4/10 flexibility (core hours 10-6 Eastern enforced), 3/10 boundaries (CEO would DM at 11pm expecting responses), 7/10 satisfaction (the work was interesting). Score: 52. He took a pay cut of $18k to leave that role. Three years later his comp had caught back up and his score had nearly doubled.
If you're evaluating an offer from a company known for burn-out culture, ask in the interview loop: "Walk me through a recent on-call week — when did you start, when did you stop, how many evening pages did you get?" If the interviewer gives a vague answer, your boundaries score at that company is likely 3-5. If the interviewer gives specific numbers, they've likely measured it and the number is actually okay.
The 50-hour trap
A large chunk of professional work lives at 50 hours/week. It's the default at investment banks, consulting, growth-stage startups, law firms, and senior IC tech roles. At 50 hours you feel productive enough to defend the schedule but not so overloaded that you quit. It's a local optimum the system wants you to stay in.
The math: 50 hours × 50 weeks = 2,500 hours of work per year. A 40-hour version of the same job would be 2,000 hours — 500 fewer hours, or 12-13 full weekends. Over a decade, 50-hour weeks cost you 5,000 hours compared to a 40-hour schedule. Those hours would have bought a master's degree, a side business, a triathlon habit, or a second child worth of real presence.
If you're at 50+ hours and your score drops below 65, the job is asking for more than it's paying. Options: push back on scope (specifically, name three things you'll stop doing), renegotiate to a 40-hour expectation in writing, or start looking. Over half the time, none of those three happens and workers just stay at 50 hours until they burn out. Don't be that pattern.
Why the boundary score matters more than hours
If I had to pick one of the four inputs as the best predictor of burnout, it would be boundaries. A 42-hour week with 2/10 boundaries (constant interruption during off-hours) predicts burnout within 18 months better than a 55-hour week with 8/10 boundaries. The interruption isn't just the minutes it costs — it's the cognitive load of staying half-on during your time off.
Fixing boundaries often has outsized payoff. Concrete moves that work: delete Slack from your phone (not just set it to silent — actually uninstall); set a hard stop-time and leave your laptop downstairs after it; negotiate a response SLA in writing with your manager ("I'll respond to non-emergency pings within 8 business hours, not evenings or weekends"); turn off email notifications on personal devices. Each of these moves a 3/10 boundary score to a 6-7 within a month if you stick with it.
The expected pushback: "but my job requires me to be responsive." For 90% of roles that's not actually true. It's a norm you've accepted. Test it: next time you don't respond to a weekend ping, track what actually happens. Almost always: nothing. A specific teammate takes care of it, or the question answers itself by Monday, or the asker apologizes for pinging.
Flexibility as a hidden raise
Flexibility is routinely undervalued in offers. If you can work from home two days a week, you save ~$2,500-5,000/yr in commute, lunch, and wardrobe costs. If you can shift start time, you avoid peak traffic and save another 40-80 hours a year of commute. If you can do a deep-work block in the morning and meetings in the afternoon, your output rises materially — often 20-30% more completed work per week vs. calendar-fragmented schedules.
Negotiation move: if you can't get $10k more in base, ask for flexibility. "I'd like to work from home Tuesday and Thursday, core hours 10-4 Eastern, with async work before and after." Most employers treat flexibility as low-cost because it is — for them. For you, it's worth real money. The calculator's flexibility score goes up 2-3 points with that kind of arrangement.
When satisfaction is the load-bearing variable
You can grind 55 hours a week on work you love without burning out. You can't grind 42 hours on work you hate. If your satisfaction score is below 5, the calculator's total score will be misleading — you'll feel worse than the number suggests. Satisfaction is multiplicative, not additive.
Warning signs the satisfaction is a 3 or 4 even if you tell yourself it's a 7: Sunday night dread; the part of your week you look forward to most is the commute home; you've stopped mentioning your job to friends; you can't remember the last thing you did that you felt proud of. If two or more of these are true, the score undercounts the problem. Start looking or start rebuilding what you do in the role.
Using the score before an offer decision
If you have a current job and an offer, score both. In the offer version, estimate the four inputs based on everything you learned in the interview loop — and call two current employees in similar roles to calibrate. The score gap between current and offer is the real comparison, not the salary gap.
A common pattern: current job scores 62, offer scores 78, but pays $10k less. Is the offer worth taking? In my experience: yes, if you believe the 78 score. A 16-point balance improvement is worth $10k in most mid-career lives. The inverse — leaving an 82 for a 65 at $20k more — is usually a mistake; the extra money doesn't compensate for the lifestyle downgrade, and people rarely acknowledge this until about month 14 of the new role.