How is the 0-100 score calibrated?

Each input contributes load against a published threshold: projects (Miller's 7-item working-memory limit, capped at 30 pts), decisions (Bargh & Vohs 60-decision ceiling, capped at 25 pts), open loops (7-item working-memory limit, capped at 25 pts), meetings (Cal Newport 6/wk healthy threshold, capped at 15 pts), notifications (30/day baseline, capped at 15 pts), sleep (each hour below 7.5 adds 8 pts). Total caps at 100. Zones: 0-30 low (sustainable indefinitely), 31-50 moderate (typical knowledge-worker baseline), 51-75 high (productivity degrading, watch for burnout), 76-100 overload (course-correct now).

Why is sleep weighted so heavily?

Because sleep research (Walker, Huberman, decades of empirical work) shows it's the single highest-leverage cognitive-load lever — not because it's special, but because it's a multiplier on every other capacity. Sleep-deprived decision-making, working memory, mood regulation, and attention are all measurably impaired; conversely, +1 hr sleep recovers more cognitive capacity than any other 1-hr intervention. The 8-pts-per-hour-below-7.5 weighting reflects this multiplier — it's the load that magnifies all other loads.

What if I have 50 projects but they're all low-effort?

The calculator counts 'distinct active projects with open deliverables' — a low-effort project still occupies a working-memory slot. Even if it's just 'reply to person X this month', that intent costs cognitive bandwidth until closed. The math is conservative — a true 'no thinking required' project (auto-pay bill) doesn't count. Use honest judgment: if it's on a list you check, it counts. If it's truly zero-thought (recurring autopay), it doesn't.

Why the 23-min recovery cost on notifications?

Atlassian's research surveyed knowledge workers and measured that each interruption costs an average 23 min to fully recover focus / re-orient to the deep-work task. The number is widely cited in productivity literature (Cal Newport, Maker's Schedule literature). At 80 notifs/day, the math says 30 hrs of recovery time — obviously you don't actually get 30 hrs of recovery, which is why the load score climbs. The recovery time you 'don't get' is the productivity tax that's invisible but real.

How do I drop a high score quickly?

Top drag tells you which lever delivers the most reclaim. Most knowledge workers' top drag is one of: (1) close 25+ todos in one focused session — drops loops load 10 pts immediately; (2) batch meetings to 2 days/wk — drops meetings load 6-8 pts; (3) disable 80% of push notifications + batch email to 2-3 windows daily — drops notifs load 5-10 pts; (4) add 1 hr sleep — drops sleep deficit 8 pts directly. The calculator's 'top drag recommendation' identifies your specific highest-leverage move — apply it first.

Is this a clinical diagnostic?

No. Decision-support, not medical. The 0-100 score is calibrated against published research thresholds (Miller, Bargh & Vohs, Walker, Atlassian) but it's a self-report tool, not a diagnostic. If you're scoring 75+ and feel actively burned out, a real conversation with a clinician matters more than the calculator. Use this to surface the load and identify the highest-leverage reclaim — not to label yourself.

Why are meetings + notifications in 'recovery' instead of 'workload'?

Because they fragment recovery time during the workday, even though they look like workload. A 30-min meeting in your 2-hr focus block destroys the entire block — the cost isn't the 30 min, it's the 60+ min of fragmented context-switching surrounding it. Same for notifications: each one isn't 30 sec, it's 23 min of recovery you don't get. Both interrupt the fragile recovery process that lets focus build between deep-work blocks.

How is this different from sleep-debt-calculator?

Sleep-debt is one-dimensional — it computes the running deficit from your target sleep across the week, useful for catching up. Cognitive-load is multi-dimensional — sleep is one of six inputs, integrated into a holistic score. Use sleep-debt for the specific question 'how much sleep do I owe?'; use cognitive-load for the holistic 'what's eating my mental bandwidth across all sources?'. They pair well — sleep-debt's output feeds cognitive-load's sleep input.

What about ADHD / neurodivergence?

The published thresholds (Miller, Bargh & Vohs) reflect neurotypical averages — neurodivergent users may have meaningfully different working-memory limits, decision-fatigue ceilings, and notification-recovery times. Use the calculator as a relative tool (compare your week-over-week scores, identify your specific top drag) rather than an absolute benchmark. The 'top drag identification' logic still works because it's based on your specific load distribution, not the absolute thresholds.

How often should I re-run this?

Weekly is the sweet spot. Daily is too volatile (single bad night sleep skews); monthly is too slow (you've already burned out by the time the score moves). Check in once a week, look at the top drag, apply the recommended reclaim, re-run the next week. The compounding effect across 4-6 weeks is what actually moves the score sustainably down.

ProductivityFree · No signup · 25K+/month

Cognitive Load Calculator — Score Your Working-Memory Tax

Drop your active projects, daily decisions, open todos, weekly meetings, daily notifications, and 7-day average sleep. Calculator computes a 0-100 cognitive-load score against published thresholds (Miller 7-item working memory, Bargh & Vohs 60-decision ceiling, Atlassian 23-min interruption-recovery, Walker sleep literature), identifies your top drag, and recommends the single highest-leverage reclaim.

Instant result
Private — nothing saved
Works on any device
AI insight included

Reviewed by CalcBold EditorialLast verified May 4, 2026Methodology

Active projects

Distinct active projects with open deliverables. Working-memory research (Miller, 'The Magical Number Seven') suggests 4-7 items max for sustained focus. First 4 are free; each beyond 4 adds 8 pts cognitive load up to a 30-pt cap.

Daily decisions (conscious)

Conscious decisions per day. Bargh & Vohs research: total daily decisions ≈ 35,000 inc. autopilot; conscious choices for office workers typically 60-100. Recommended ceiling: 60. Decision-quality measurably degrades after the 70th decision.

Open loops (todos)

Open todos pending closure across all systems. 7-item working-memory limit means anything beyond 7 leaks into background processing — costs cognitive bandwidth even when you're not actively working on them (David Allen / Getting Things Done framing).

Meetings per week

Meetings per week including 1-on-1s. Each meeting fragments deep-work blocks; even a 30-min meeting in the middle of a 4-hr focus window destroys the entire window (Cal Newport, Deep Work). 6/wk is the healthy threshold.

Notifications per day

Slack / email / push notifications per workday. Atlassian research: each interruption costs ~23 min recovery time. At 80 notifs/day, that's 30 hrs of theoretical recovery overhead — your brain isn't actually getting that, which is why the load score climbs.

7-day average sleep

7-day rolling average sleep. Walker / Why We Sleep: <6 hrs measurably degrades cognitive performance on next day, with cumulative deficit compounding over weeks. Each hour below 7.5 adds 8 pts to load. Single highest-leverage hidden contributor.

Embed builderDrop the Cognitive Load on your site →Free widget · 3 sizes · custom theme · auto-resizes · no signupGet embed code

What This Calculator Does

The Cognitive Load Calculator computes a 0-100 score for the working-memory tax your current life is paying. Drop your active projects, daily decisions, open todos, weekly meetings, daily notification volume, and 7-day average sleep. The calculator weights each input against a published research threshold, sums to a capped score, identifies your top drag (the single highest-load source), and surfaces the specific reclaim move that delivers the most relief per minute spent.

Most productivity advice is opinion. The cognitive-load framing here is research-anchored. Working-memory limits come from Miller’s “Magical Number Seven” foundational paper. The 60-decisions/day ceiling traces to Bargh & Vohs glucose / willpower work. Sleep weighting reflects Walker’s “Why We Sleep” literature. Notification recovery uses Atlassian’s 23-min-per-interruption research. Meeting-fragmentation framing follows Cal Newport’s “Deep Work” cadence math. The score is decision-support, not a clinical diagnostic — but the inputs and weights aren’t arbitrary.

The Math — Six Sources, Capped at 100

Each source has a research-anchored threshold (4 projects, 60 decisions, 7 loops, 6 meetings/wk, 30 notifs/day, 7.5 hrs sleep) and a per-unit weight beyond the threshold. Sources cap individually so no single input dominates the score; total caps at 100. Zones: 0-30 low (sustainable indefinitely), 31-50 moderate (typical knowledge-worker baseline), 51-75 high (productivity degrading, watch for burnout), 76-100 overload (course-correct now). The “moderate” zone is where most knowledge workers live — not comfortable, not catastrophic, but with measurable productivity drag.

The top-drag identification picks the single source contributing the most points. For most knowledge workers, this is open loops (more todos than working memory can hold) or sleep deficit (chronic under-sleeping multiplies every other load). Closing 25+ todos in one focused session immediately drops loops load by ~10 pts. Adding 1 hr sleep drops sleep deficit by 8 pts directly. Both are within reach in 1-2 weeks of deliberate effort. The calculator’s job is to identify which one matters most for you specifically.

Worked Example — A Typical Knowledge Worker

Plug in defaults: 6 active projects, 80 conscious decisions/day, 35 open todos, 12 meetings/wk, 80 notifications/day, 6.5 hrs sleep. Per-source loads: projects (6-4)×8 = 16; decisions (80-60)×0.5 = 10; loops (35-7)×0.4 = 11.2; meetings (12-6)×1.2 = 7.2; notifications (80-30)×0.1 = 5; sleep (7.5-6.5)×8 = 8. Total = 57.4 → 57/100, “high zone”. Top drag = projects (16 pts). Recommendation: pause/close 2-3 projects, drop ~16 pts to ~41 (moderate zone).

Note the asymmetry: notifications feel constant and annoying, but contribute only 5 pts to the total score. Projects contribute 16 pts. The intuition (“notifications are killing me”) often diverges from the math (“you’re running too many parallel projects”). The calculator surfaces this divergence so you focus reclaim effort where the score actually moves. Notifications are real — but a 5-pt source isn’t the lever.

Why Sleep Is The Multiplier

Sleep is weighted heavily not because it’s special as a category, but because it multiplies every other capacity. Sleep-deprived working memory is measurably smaller (you can hold fewer items in active consideration). Sleep-deprived decision quality is measurably worse (Levav & Avnaim-Pesso parole-board study, multiple replications). Sleep-deprived attention recovers more slowly from interruptions. Sleep-deprived mood regulation is impaired. The per-hour weighting reflects this multiplier — adding 1 hr sleep recovers more cognitive capacity than any other 1-hr intervention available to you.

This is also why the calculator weights chronic deficit (running 6.5 hrs/night for weeks) more heavily than single-night dips (one all-nighter). The math assumes 7-day rolling average — single bad nights recover within 1-2 days; chronic deficits compound and require multi-week recovery to fully reset. If your sleep input is honest and the calculator flags sleep-deficit as your top drag, the recovery is a genuine multi-week project, not a one-night fix.

Common Mistakes

Counting only “real” projects. Active projects = anything with open deliverables you check on. Including the side project you check weekly but haven’t advanced in 6 months. Including the recurring meeting series you can’t cancel. The cognitive load is real even if the project feels background. Honest counting is the hard part — most knowledge workers underestimate by 20-40%.

Treating notifications as the main villain. Notifications matter (they cost 23 min recovery each), but the calculator caps notification load at 15 pts because the recovery time is partial — you don’t actually lose 30 hrs/day to recovery. The score reflects the productivity tax that’s real but bounded. Don’t over-index on disabling notifications if your top drag is something else.

Skipping sleep input because “it’s fine”.Most chronic under-sleepers report “feeling fine” — the cognitive impairment is invisible to the impaired person (Walker, replicated multiple times). Honest 7-day average. If you’re consistently below 7 hrs and don’t feel impaired, the calculator’s output is the signal that the impairment is there but masked.

Re-running daily.Daily cadence is too volatile (single bad night sleep, single Monday meeting day). Weekly is the sweet spot — track week-over-week scores, look at top-drag changes, apply the recommended reclaim, recheck. Most knowledge workers can move 75 → 45 over 6 weeks of deliberate reclaim. Less than that pace probably means the inputs weren’t honest or the reclaim wasn’t applied.

Confusing cognitive load with workload. Workload is measured in hours and tasks. Cognitive load is measured in mental bandwidth — the sustained ability to think clearly. A 40-hr week with 4 batched meetings and one focused project is low cognitive load. A 30-hr week fragmented across 6 projects + 18 meetings + constant Slack pings is high cognitive load. Same hours, very different drag.

Related Calculators

Pair this with the Decision Fatigue Calculator — decision fatigue is the next-layer-down diagnostic for the “decisions load” input here. If decisions is your top drag, decision-fatigue surfaces your specific decision-quality crash hour and the routine-ization moves that compress conscious decisions back below the 60-ceiling. The Sleep Debt Calculator is the next-layer-down for the sleep input — shows your running deficit and the recovery schedule. The Meeting Cost Calculator adds the dollar layer to the meetings input — most recurring meetings cost $500-2K each in attendee-hours, making the “cut to 2 batched days/wk” move financially obvious. And the Deep Work ROI Calculator surfaces the dollar impact of reclaiming the deep-work hours your current cognitive load is bleeding.

How to Read the Verdict

The 0-100 score is a check; the top-drag input and recommended reclaim move are the action. Sleep is the single highest-leverage variable — even a 30-min improvement reweighs the whole score because the model treats sleep as a multiplicative cap on capacity, not just additive.

Score > 75 (overload).One-week reset: drop 30% of active commitments, set 10pm bedtime, kill notifications. The math says you’re past Miller’s 7-item limit and decisions degrade fast.
Score 50-75 (heavy load). Apply the recommended move — usually consolidating decisions (Sunday-night meal-plan, capsule wardrobe) or batching notification windows.
Sleep is top drag. Stop optimizing everything else. Two weeks of 7+ hrs sleep moves the score more than every other tweak combined.
Score < 35.You have headroom to take on more — that’s usually growth, a side project, a stretch role. Cognitive load too low is its own pathology.

Frequently Asked Questions

The most common questions we get about this calculator — each answer is kept under 60 words so you can scan.

How is the 0-100 score calibrated?
Each input contributes load against a published threshold: projects (Miller's 7-item working-memory limit, capped at 30 pts), decisions (Bargh & Vohs 60-decision ceiling, capped at 25 pts), open loops (7-item working-memory limit, capped at 25 pts), meetings (Cal Newport 6/wk healthy threshold, capped at 15 pts), notifications (30/day baseline, capped at 15 pts), sleep (each hour below 7.5 adds 8 pts). Total caps at 100. Zones: 0-30 low (sustainable indefinitely), 31-50 moderate (typical knowledge-worker baseline), 51-75 high (productivity degrading, watch for burnout), 76-100 overload (course-correct now).
Why is sleep weighted so heavily?
Because sleep research (Walker, Huberman, decades of empirical work) shows it's the single highest-leverage cognitive-load lever — not because it's special, but because it's a multiplier on every other capacity. Sleep-deprived decision-making, working memory, mood regulation, and attention are all measurably impaired; conversely, +1 hr sleep recovers more cognitive capacity than any other 1-hr intervention. The 8-pts-per-hour-below-7.5 weighting reflects this multiplier — it's the load that magnifies all other loads.
What if I have 50 projects but they're all low-effort?
The calculator counts 'distinct active projects with open deliverables' — a low-effort project still occupies a working-memory slot. Even if it's just 'reply to person X this month', that intent costs cognitive bandwidth until closed. The math is conservative — a true 'no thinking required' project (auto-pay bill) doesn't count. Use honest judgment: if it's on a list you check, it counts. If it's truly zero-thought (recurring autopay), it doesn't.
Why the 23-min recovery cost on notifications?
Atlassian's research surveyed knowledge workers and measured that each interruption costs an average 23 min to fully recover focus / re-orient to the deep-work task. The number is widely cited in productivity literature (Cal Newport, Maker's Schedule literature). At 80 notifs/day, the math says 30 hrs of recovery time — obviously you don't actually get 30 hrs of recovery, which is why the load score climbs. The recovery time you 'don't get' is the productivity tax that's invisible but real.
How do I drop a high score quickly?
Top drag tells you which lever delivers the most reclaim. Most knowledge workers' top drag is one of: (1) close 25+ todos in one focused session — drops loops load 10 pts immediately; (2) batch meetings to 2 days/wk — drops meetings load 6-8 pts; (3) disable 80% of push notifications + batch email to 2-3 windows daily — drops notifs load 5-10 pts; (4) add 1 hr sleep — drops sleep deficit 8 pts directly. The calculator's 'top drag recommendation' identifies your specific highest-leverage move — apply it first.
Is this a clinical diagnostic?
No. Decision-support, not medical. The 0-100 score is calibrated against published research thresholds (Miller, Bargh & Vohs, Walker, Atlassian) but it's a self-report tool, not a diagnostic. If you're scoring 75+ and feel actively burned out, a real conversation with a clinician matters more than the calculator. Use this to surface the load and identify the highest-leverage reclaim — not to label yourself.
Why are meetings + notifications in 'recovery' instead of 'workload'?
Because they fragment recovery time during the workday, even though they look like workload. A 30-min meeting in your 2-hr focus block destroys the entire block — the cost isn't the 30 min, it's the 60+ min of fragmented context-switching surrounding it. Same for notifications: each one isn't 30 sec, it's 23 min of recovery you don't get. Both interrupt the fragile recovery process that lets focus build between deep-work blocks.
How is this different from sleep-debt-calculator?
Sleep-debt is one-dimensional — it computes the running deficit from your target sleep across the week, useful for catching up. Cognitive-load is multi-dimensional — sleep is one of six inputs, integrated into a holistic score. Use sleep-debt for the specific question 'how much sleep do I owe?'; use cognitive-load for the holistic 'what's eating my mental bandwidth across all sources?'. They pair well — sleep-debt's output feeds cognitive-load's sleep input.
What about ADHD / neurodivergence?
The published thresholds (Miller, Bargh & Vohs) reflect neurotypical averages — neurodivergent users may have meaningfully different working-memory limits, decision-fatigue ceilings, and notification-recovery times. Use the calculator as a relative tool (compare your week-over-week scores, identify your specific top drag) rather than an absolute benchmark. The 'top drag identification' logic still works because it's based on your specific load distribution, not the absolute thresholds.
How often should I re-run this?
Weekly is the sweet spot. Daily is too volatile (single bad night sleep skews); monthly is too slow (you've already burned out by the time the score moves). Check in once a week, look at the top drag, apply the recommended reclaim, re-run the next week. The compounding effect across 4-6 weeks is what actually moves the score sustainably down.