Work & Careers

Why Your Emails Keep Getting Ignored (and What to Change)

Person at a desk looking at a laptop screen filled with unanswered work emails

Key Takeaways

  • Vague subject lines are the most common reason work emails go unread.
  • Emails that bury the request make it easy for recipients to defer and forget.
  • Sending a single, clear email beats following up multiple times on a confusing one.
  • Short, focused messages consistently get faster responses than long ones.

Why unreturned emails are usually a writing problem

When a work email goes unanswered, most people assume the recipient is busy, disorganized, or avoiding them. Often the real issue is the email itself. A message that lacks a clear subject, buries its request, or asks too many things at once gives the reader no obvious path forward. So they set it aside, intend to return to it, and forget.

This pattern affects everyone from new employees to senior managers. The good news is that most of the habits causing it are correctable, and the fixes are straightforward. Understanding what specifically goes wrong is the first step.

These problems also compound over time. Colleagues and managers form impressions based on your written communication. Consistently unclear emails can quietly affect how ready others perceive you to be for more responsibility. See the habits that stall promotability for a fuller picture of how small communication patterns add up.

Common mistakes that get emails ignored

The mistakes below cover the full range of structural and tonal problems that cause workplace emails to go unanswered. Each one is fixable with a small adjustment to how you write.

1

Writing a subject line that gives no hint of what the email contains or requires.

Why it happens: Senders focus on the body of the message and treat the subject line as an afterthought, typing something generic like "Question" or "Following up."

How to avoid: Write the subject line last, after you know exactly what you are asking. A useful format is: topic + action needed (e.g., "Budget report: approval needed by Friday"). The recipient should be able to decide whether to open the email based on the subject alone.
2

Burying the actual request several paragraphs into the message.

Why it happens: Writers feel they need to provide full context before making an ask, so they front-load background information and the request ends up near the bottom.

How to avoid: State the request in the first two sentences, then provide context below it. Readers scan quickly; if they do not see a clear ask near the top, many will defer the email until they have more time, which often means never.
3

Packing multiple unrelated requests into one email.

Why it happens: It feels efficient to consolidate, but recipients tend to answer the easiest question and mentally mark the thread as handled, leaving the harder asks unaddressed.

How to avoid: Limit each email to one primary ask. If several things genuinely belong together, use a numbered list so each item is visible and trackable. Make clear which item is most time-sensitive.
4

Writing emails that are too long for the request being made.

Why it happens: Wanting to be thorough or polite, writers add extensive background, caveats, and pleasantries that push the actual point well past the first screen of text.

How to avoid: Cut any sentence that does not add information the recipient needs to act. A three-sentence email asking for a meeting time will almost always get a faster reply than a twelve-sentence one asking the same thing.
5

Leaving the deadline or time sensitivity unstated.

Why it happens: Senders assume the urgency is obvious from context, or they feel awkward specifying a date because it seems demanding.

How to avoid: Name a specific date or time frame directly: "I need this by end of day Thursday" is clearer than "whenever you get a chance." Without a deadline, the email competes with tasks that do have one, and it loses.
6

Sending to too many recipients without specifying who needs to act.

Why it happens: Copying everyone who might be tangentially relevant seems like thorough communication, but it dilutes accountability. Each recipient assumes someone else will respond.

How to avoid: Address the email to the one person responsible for the action. Use CC sparingly and only to inform, not to spread responsibility. If multiple people must each do something different, say so explicitly: "Alex: please approve. Jordan: please update the spreadsheet."

Putting it into practice

~120

Business emails received per worker per day

Research from the Radicati Group has consistently placed the average number of business emails received daily per professional at roughly 120, meaning your message competes with a high volume of others.

Under 30 seconds

Typical time spent reading a work email

Communication researchers at the University of California, Irvine have found that most workers spend only a few seconds scanning an email before deciding to act, defer, or delete.

Before sending any email that requires a response, run through three quick checks. First, does the subject line tell the recipient exactly what the message is about and what action, if any, is needed? Second, is the specific request stated in the first two sentences? Third, is there only one primary ask?

These checks take about thirty seconds and will reduce the number of follow-ups you send. If you do need to follow up, a short, direct message referencing the original ask works better than a forwarded thread with a vague "just checking in." For guidance on follow-up timing and tone in a job search context, see how to follow up after a job application, which covers principles that transfer directly to workplace email as well.

Good email habits also help when you need something from a manager under pressure. If you are trying to raise a deadline concern or adjust a timeline, a clear, well-structured email gives the other person enough context to respond quickly. Negotiating deadlines professionally walks through how to frame those requests in writing.

Work & Careers Editorial Team is the collective byline for our editorial team and contributor network. Articles published under this byline or an editorial pen name are researched, written, and reviewed according to our editorial standards for clarity, consistency, and independence before publication.

View all articles by Work & Careers Editorial Team →
Disclaimer: The content on this site is for informational purposes only and is not a substitute for professional advice. Always consult a qualified professional for guidance specific to your situation.