Email writing is invisible labor. It doesn't appear on a project plan, it doesn't get estimated in a sprint, and it doesn't show up in a time audit unless someone is being unusually deliberate. It just happens — in the gaps between meetings, during morning ramp-up, in the evening when everything else is done. The cost is real and it's large, but because it's diffuse and habitual, it rarely gets treated as a productivity problem worth solving.
This piece is about putting a number to that cost and thinking through what follows from it.
The arithmetic of email composition
Estimates on email volume and composition time vary, but reasonable figures for knowledge workers at director level and above cluster in a consistent range. Studies of email behavior in professional settings typically find that senior knowledge workers compose somewhere between 25 and 40 emails per working day, with composition time per email averaging between 3 and 6 minutes depending on complexity and role.
Using conservative middle-range figures — 28 emails per day, 4 minutes each — that's 112 minutes, or nearly two full hours, spent on email composition on a typical working day. Over a standard five-day work week, that's roughly 9.5 hours. In a year with 48 working weeks, it's approximately 450 hours of writing time. At senior compensation levels, that figure represents a significant cost — one that most organizations haven't examined explicitly.
Those numbers need context. Not all email composition is avoidable or undesirable. Some of it is core to the work — client correspondence, deal negotiation, team leadership communication. You wouldn't want to eliminate that writing. But a meaningful fraction of those 28 daily emails are replies that follow predictable, repeatable patterns: status updates, meeting acknowledgments, follow-ups that say essentially the same thing to different people, short answers to recurring questions. These are the emails where the cost is genuinely high relative to the informational value being exchanged.
The hidden cost: task-switching, not just typing
The direct time spent typing is only part of the real cost. Email composition also carries a task-switching overhead that's harder to measure but arguably larger than the writing time itself.
Consider what happens when an email requires composing. You shift from the work you were doing. You open the compose window. You orient yourself to the context of the email — what's the situation, what's the relationship, what tone is appropriate, what's actually being asked. You write. You reread. You send. You return to what you were doing, and you spend a moment re-orienting to where you were before the interruption.
Research on attention recovery after task interruption consistently places the re-orientation cost somewhere between 10 and 25 minutes for deep work, though the range varies significantly by task type and interruption length. Email composition fits the profile of a short interruption — under five minutes typically — but the re-orientation cost applies regardless of the interruption length. For someone who composes 28 emails across a working day and does so in scattered individual sessions rather than batched email blocks, the cumulative task-switching overhead may substantially exceed the composition time itself.
Where the repeatable patterns are
Looking at a real email output over a two-week period reveals a consistent pattern for most knowledge workers: a large fraction of outgoing email falls into a small number of structural categories.
There are acknowledgment and scheduling replies: "Confirmed for Thursday," "Let me know when you're free," "Works on my end." There are status update replies: "We're on track," "This is complete — see attached," "We've pushed this to next week." There are context-routing replies: "Adding [name] who owns this," "Forwarding to the right person," "Here's the background doc you need." There are soft-declination replies: "I'm not the right person for this, but you might try," "This isn't something we can take on right now." And there are follow-through replies to existing threads that primarily serve to confirm or advance a decision already in motion.
By rough estimate across these categories — and this will vary significantly by role and organization — somewhere between 40 and 60 percent of email composition time is spent on replies that follow one of these patterns. The content varies. The structure and intent don't.
The opportunity in structured repetition
When the patterns are visible, the path to reducing composition cost becomes clearer. The emails that follow predictable structures — where the required content is largely determined by the incoming email's type and the sender relationship — are candidates for assistance. Not automation: the relationship context, the specific details, the appropriate tone still matter. But those details can be provided as a starting draft that captures the structure and matches the relational register, rather than being built from a blank text field every time.
The meaningful comparison is: what does a draft that's 70% right actually save versus starting from zero? Even for a 3-minute email, having a draft that's substantially correct means the composition task shifts from "write a reply" to "review and adjust a reply." Those aren't the same cognitive task. The second is lighter and faster, and — critically — it can happen with less re-orientation overhead because you're evaluating rather than constructing.
A senior account director at a growing professional services practice, managing relationships with 30 active clients, might compose the same essential "project update" reply structure 40 or 50 times per month. If each one starts from zero in a 4-minute average composition window, that's 3+ hours per month on structurally repetitive writing. If a starting draft is generated based on the thread context and her established writing patterns with that client, and review takes 90 seconds instead of 4 minutes, that's roughly 2 hours recovered per month without any reduction in reply quality.
What draft assistance doesn't fix
We're not saying that drafting tools eliminate the email cost. The emails that carry real informational weight — where the response requires actual thought, judgment, or relationship sensitivity — still require the time they require. A difficult client conversation, a sensitive internal negotiation, a reply that carries strategic implications: these emails need the full attention of the person writing them, and no draft assistance meaningfully shortens that process.
Draft assistance also doesn't reduce incoming email volume. If you receive 120 emails per day, you receive 120 emails per day regardless of how quickly you can compose replies. Reducing composition time without reducing incoming volume may simply create capacity for more email — a version of induced demand. The composition problem and the volume problem are related but distinct, and solving one doesn't automatically solve the other.
Seeing the cost clearly
The starting point is treating email composition as a real cost, not an invisible overhead. If you spent two hours a day doing any other knowledge work task, you'd probably want to know what it was producing and whether the time allocation was reasonable. Email composition rarely gets that scrutiny.
Running a simple count — how many emails did you compose today, and how long did each take — usually produces numbers that surprise people. Not because the problem is worse than they expected, but because they've never looked at it as a number before. The cost was there all along; making it visible is the first step toward deciding whether it's worth addressing.
Whether you pursue tooling, batching, delegation, or simply better habits around when you write rather than how, the prerequisite is the same: treating email composition as a quantifiable use of your time, not as background work that doesn't count.