Free Calculator
What Your Team's Inbox Actually Costs
Email is work, until it is a substitute for a doc, a decision, or a norm nobody set. Widely cited research puts email at roughly a quarter of the average knowledge worker's week. Here is your team's bill, and the slice of it you could stop paying.
Loaded cost uses salary × 1.3
Count all the scattered touches, honestly
Status updates, cc chains, threads that should be docs
Avoidable email cost per year
$0
Team hours / week
0
in email and chat
Total annual cost
$0
all email time, loaded
Share of workday
spent in the inbox
Days / person / year
0
full workdays on email
What Better Norms Would Recover
The avoidable slice does not require new tools or a ban. It requires a handful of norms: status lives in a doc, decisions get owners instead of threads, cc lists shrink by default, and long threads become short conversations.
Current annual bill
$0
After fixing the avoidable
$0
the necessary remainder
What This Number Means for You
The hours are only half the bill.
Every inbox touch is also an interruption, and interrupted work pays a refocus tax on top of the minutes. If your team checks email dozens of times a day, the context switching cost calculator prices the half of the bill this one leaves out.
Email volume is a symptom. The causes have names.
Missing documentation creates the same answers typed weekly. Unclear ownership creates decision threads with no decider. Meeting-shy cultures negotiate by reply-all. Fix the upstream cause and the inbox shrinks on its own; the manager's time management guide covers the system-level fixes.
You set the norms, starting with your own sends.
Teams mirror their manager's inbox behavior. Every message you send at 9 PM, every unnecessary cc, every thread you let run to reply twelve teaches the team what is normal. Meetings have the same dynamic and a bigger price tag; the meeting cost calculator covers that half.
The Inbox Is Where Missing Systems Send Their Bills
Nobody's job description says "email," and yet it routinely consumes a quarter of the week. The reason is that email is the default fallback for every system a team has not built. No shared documentation? The same questions get answered by reply, forever. No decision process? Decisions become threads, and threads become archaeology. No norms about cc? Everyone gets everything, and reading it all becomes a part-time job nobody applied for.
That is why the avoidable share is the number that matters. The goal is not inbox zero, and it is certainly not banning email. It is noticing which slice of the volume exists only because something upstream is missing, then building the small missing thing: a status doc, a decision owner, a three-reply rule. Each norm you add converts a recurring cost into a one-time fix.
Five Norms That Shrink the Bill
Status lives in a doc. The recurring status email dies first. It is the highest-volume, lowest-value category, and a living document replaces it completely. Decisions get owners. A thread past three replies becomes a five-minute conversation between the two people who own the answer, and the outcome gets written down once. Cc shrinks by default. The question is not "who might want to know" but "who has to act." Everyone else reads the doc. Async has hours. No expectation of replies after hours, ever, and the manager's own send times prove it. Questions become documentation. Any question answered twice gets its answer moved somewhere findable, so the third asking never happens.
Frequently Asked Questions
Is email time actually waste? Communication is part of the job.
How do I estimate hours per day honestly?
What is a realistic "avoidable" percentage?
We use Slack or Teams more than email. Does this still apply?
Should we just ban internal email?
What is the fastest single win?
Fix the Systems. The Inbox Follows.
Pick one norm this week (the status doc is the fastest win), tell the team why, and model it yourself. The volume drops within a month.