10 Grammar Mistakes That Ruin Business Emails

Recipients do not evaluate your grammar consciously. Nobody reads a proposal and thinks, this person used a comma splice, therefore reject. The judgement happens earlier and faster than that. A reader builds an impression of competence in the first two sentences, and that impression colours everything afterwards — including whether they trust your numbers, your timeline, and your promise to deliver.

This is why the same request gets two different responses. “Me and my team we will send you the files tomorrow” and “My team and I will send you the files tomorrow” carry identical information. Only the second one signals that the sender checks their work. In procurement, recruiting and client services, that signal is part of the product.

None of this means your emails must read like a legal document. Clarity beats formality, and a short plain sentence outperforms an ornate one every time. The goal is not perfection; it is removing the handful of errors that make a reader stop and re-read.

This is the single most common structural error in business email, and it is almost invisible to the writer. A comma splice joins two complete sentences with only a comma. Both halves could stand alone, so the comma does not have the strength to hold them together.

The reliable test: cover the comma and read each half on its own. If both halves are complete sentences with their own subject and verb, a comma is not enough. Use a period, add and / but / so, or use a semicolon when the two ideas are genuinely equal in weight.

Run-ons are the same mistake with the comma deleted: I received your invoice I will process it today. The fix is identical. In short business emails, the period is nearly always the cleanest choice — it also improves readability on mobile screens, where most business email is now read.

Business emails are full of deadlines, timestamps and status updates, which makes them a minefield for tense errors. The rule is simple: a finished time word forces the simple past. Present perfect cannot coexist with yesterday, last week, ago or a specific date.

The second business-specific trap is the scheduled future. For fixed timetables and agreed plans, English prefers the present simple or present continuous over will: The meeting starts at 10:00, Our supplier delivers on Monday, I’m travelling to Berlin next week. Using will in these cases sounds like a prediction rather than a plan, which subtly weakens your commitment.

The third is the perfect pairing for status updates. I have reviewed the document and have two questions is correct because the review is recent and the questions are live now. Switch to simple past only when you add a finished time: I reviewed it on Tuesday.

Preposition errors are the fastest way for a reader to identify a non-native writer, and business English has a fixed set of them. These combinations do not follow logic — they follow convention — so they have to be memorised as single units.

Two of these deserve special attention because they appear in almost every business email. Discuss never takes about — the verb already contains the meaning, so discuss about is redundant. And explain always needs to before the person: explain the timeline to the client, never explain the client the timeline. This second one trips up speakers of Spanish, French, Portuguese and Italian, whose languages allow the double-object construction.

Time prepositions follow a size rule worth memorising: at for clock times (at 9:00), on for days and dates (on Monday, on 4 July), in for months, years, seasons and longer periods (in June, in 2026, in the third quarter).

Business writing produces long subjects full of prepositional phrases, and long subjects cause agreement errors even among native writers. The mechanism is called proximity attraction: your eye grabs the noun closest to the verb instead of the real subject.

The three phrases to watch for in business email are each of, one of, and the number of — all singular. Contrast the number of tickets has doubled (the count is singular) with a number of tickets are unresolved (a number of means several, plural).

Two more patterns appear constantly in corporate writing. Either/or and neither/nor agree with the nearest noun: Neither the manager nor the engineers were available, but Neither the engineers nor the manager was available. And along with / as well as / together with do not create a compound subject: The CEO, along with the board, is reviewing the offer.

An opening phrase like After reviewing the contract… must be followed by the person who did the reviewing. When it is not, the sentence attaches the action to whatever noun comes next — usually something that cannot perform it. These errors read as unintentionally comic, which is the worst possible tone for a business email.

Misplaced modifiers are the subtler sibling, and they change meaning rather than merely sounding odd. She only reviewed the first draft (she did nothing else) versus She reviewed only the first draft (she did not review the second). In an email about scope of work, that difference matters.

The rule for both: put the modifier immediately next to the word it describes, and make sure the noun right after an introductory -ing or after/before + -ing phrase is the actual doer of the action.

The passive is not a grammar error — it is a legitimate construction. The problem is that business writers default to it exactly when they should not: at moments of commitment, apology and accountability. Readers notice. Passive voice in those positions reads as evasion.

Keep the passive where it genuinely helps. It is the right choice when the actor is unknown, irrelevant, or deliberately unnamed: The payment was processed on Tuesday, The office will be closed on Friday, Your feedback is appreciated. It is also useful in bad-news emails where naming a person would be needlessly harsh.

A practical rule for commitments: every promise in a business email should have a subject. If you cannot point at the noun doing the action, rewrite the sentence. Deadlines without owners are the most common cause of dropped work, and they start as grammar.

Grammar carries tone in English, and modals are the main vehicle. A bare imperative in a business email is not rude by intent but is read as rude by the recipient — especially across cultures, where a direct translation from your own language can land far harder than you meant.

Three modal patterns are worth internalising. Could/Would you…? for requests. I would appreciate it if you could… for formal or upward requests. Would it be possible to…? when you are asking for something that may be inconvenient. Note the grammar of the last one: appreciate it if, not appreciate if — the dummy it is required.

The opposite error also costs credibility: over-hedging until the message disappears. I was just wondering if you might possibly perhaps be able to send… signals a lack of confidence and wastes the reader’s time. One polite modal is enough. Could you send the revised quote by Thursday? is both courteous and clear.

Finally, watch the conditional in apologies. I apologise for the delay is direct and professional; I would like to apologise softens it unnecessarily. And avoid Sorry for the inconvenience as a reflex closer — repeated across an email thread, it reads as a template rather than an acknowledgment.

Spell-checkers rarely flag apostrophe errors, because both forms are real words. That makes them the highest-visibility mistakes in a business email — visible to a reader, invisible to a tool.

The replacement test settles it every time: if you can swap in it is and the sentence still works, use it’s. Otherwise use its. The same logic covers your/you’re, their/they’re/there, and whose/who’s.

Company and family names create the second apostrophe trap. Pluralise without an apostrophe, then add one for possession: two Smiths, the Smiths’ account; three VPs, the VPs’ reports. Never write the Smith’s to mean more than one person, and never write two Smith’s. Singular company possession follows the regular rule: the client’s requirements, Microsoft’s policy.

A small set of word pairs accounts for most meaning-level errors in professional writing. Unlike the structural mistakes above, these change what the sentence says — and in a contract, invoice or scope-of-work email, that is a financial risk, not just a stylistic one.

Two more are common in formal correspondence. Per takes no article — per your request, not per the your request — and regarding needs no preposition after it: regarding the invoice, never regarding about. Both errors come from over-formalising a phrase the writer is unsure of.

Finally, irregardless, alot, and could of (from mishearing could have) have no place in business writing at all. The third is the one that damages credibility most, because it signals that the writer has never seen the phrase in print.