Skip to content

Guide

The English Mistakes That Make Good Work Look Careless

A field guide to the English mistakes that make careful, competent non-native professionals look careless at work — not big grammatical errors, but small recurring ones: articles, prepositions, tense drift in status updates, false cognates, translated idioms, and directness or hedging calibrated to the wrong workplace culture. Each category comes with real before/after examples grouped by the language backgrounds where they show up most, plus a short process for catching them before you hit send.

The mistakes that undercut careful non-native English writers at work are rarely big grammar errors — they're small, recurring ones: dropped or mismatched articles (a/an/the), preposition slips inherited from your own language, tense that drifts mid-status-update, false cognates that look right but mean something else, translated idioms, and directness calibrated to the wrong workplace culture.

THE PROCESS

Step by step

Do one error pass at a time

Don't try to catch articles, prepositions, and tense in a single read. Read once for articles (specific vs. general vs. countable), once for verb+preposition pairs, once for tense. Each pass is faster and more accurate than one pass trying to catch everything.

Split status updates into three time blocks

Write what's done (past simple: "finished," "sent"), what's in progress (present continuous: "I'm working on"), and what's next (will/going to: "I'll present") as three distinct blocks, and keep each block's tense fixed. This removes the ambiguity a mixed-tense update creates for the reader, not just the accent.

Treat lookalike words as suspects

If an English word looks identical to a word in your own language and it came to you instantly, pause on it. Actually, eventually, assist, pretend, and sensible are the most common false cognates in work writing, and they all read as fully correct English while quietly meaning the wrong thing.

Picture the idiom literally before you send it

If you can't picture the phrase happening in English, the reader can't either. Translated idioms (calques) are grammatically fine and still stop the reader cold — swap them for a plain description of what you mean.

Reread as the recipient, not the writer

Check whether the message would land as blunt or as vague to someone raised on English business register, independent of whether your grammar is correct. Adjust the softening, not the ask — the deadline or the correction should survive the edit.

Articles: the mistake even fluent speakers never fully stabilize

Languages without articles — Russian, Ukrainian, Polish, and most Slavic languages, plus Japanese, Korean, and Chinese — never ask a writer to decide whether a noun is specific, one of several, or general. English asks that question on nearly every noun, which means writers from these backgrounds are making a grammatical decision their first language never required, on every sentence, for as long as they write in English. It doesn't reliably improve with vocabulary or fluency the way other skills do, which is why it shows up even in writing that's otherwise advanced.

It clusters hardest at the first mention of something — a report, a client, a meeting — because that's where English decides whether the noun is being introduced (a/an) or already known to the reader (the), and everything after it depends on that first choice.

Overcorrection runs the other way too: writers who've been told to 'always use articles' start adding 'the' in front of general or uncountable nouns where English uses none at all.

  • Before: "I sent report to client yesterday, and I am waiting for feedback." After: "I sent the report to the client yesterday and I'm waiting for their feedback."
  • Before: "We need budget approval before we start project." After: "We need budget approval before we start the project" (a specific, already-discussed project) — or "before we start a project" if it's still hypothetical. The article is the only thing signaling which one you mean.
  • Overcorrected before: "The good communication is important for the team." After: "Good communication is important for the team."

Prepositions: verb patterns that don't cross languages

Most preposition errors aren't random — they're a direct translation of the verb pattern in the writer's own language. Spanish and French both attach a preposition to "discuss" (discutir sobre, discuter de) that English doesn't use, because English "discuss" already takes a direct object. The same happens with "depend" (depende de / dépend de becomes "depends of" instead of "depends on") and with "agree," where Spanish and French both build the sentence around a form of "to be" (estar de acuerdo, être d'accord), which pulls an unnecessary "am" into the English sentence.

Time-marker prepositions cause a second, quieter version of the same problem: "since two weeks" (calqued from depuis deux semaines) instead of "for two weeks" — since marks a starting point, for marks a duration, and the two aren't interchangeable in English the way they are in the source phrase.

  • Before: "We discussed about the timeline with the client." After: "We discussed the timeline with the client."
  • Before: "The results depend of how fast the vendor responds." After: "The results depend on how fast the vendor responds."
  • Before: "I am agree with your approach." After: "I agree with your approach."
  • Before: "I've been on this account since two weeks." After: "I've been on this account for two weeks."

Tense consistency in status updates

Chinese, Vietnamese, Thai, Indonesian, and several other languages mark time through context and time words rather than verb conjugation, so writers from these backgrounds often default to one tense throughout an update, or shift tense without the shift meaning anything. In English, tense is doing real work in a status update — "finished" versus "is finishing" versus "will finish" tells the reader exactly where a task stands, which is the entire job of a status update.

A manager skimming a mixed-tense line like "I work on revisions" genuinely can't tell whether that's done, in progress, or planned — they have to stop and ask, which is the friction the update was supposed to remove.

  • Before: "Last week I finish the client deck and I am sending to design team. Today I work on the revisions and tomorrow I will present to leadership."
  • After: "Last week I finished the client deck and sent it to the design team. Today I'm working on revisions, and tomorrow I'll present to leadership."

False cognates: the word your brain reaches for first is often wrong

A false cognate is a word that looks identical to a word in your own language but means something different in English. These are more damaging than typos because they read as fully correct, fluent English — the mistake is invisible to the writer and often to a casual reader, so it just quietly changes the meaning of the sentence instead of flagging itself as an error.

  • "Actually" (in fact, contradicting an assumption) vs. Spanish/Portuguese/Italian actualmente/atualmente (currently). Before: "Actually we are a team of six." After, if you mean right now: "Currently we're a team of six."
  • "Eventually" (in the end, after some delay) vs. French éventuellement (possibly). Before: "Eventually we could push the deadline." After: "We could possibly push the deadline."
  • "Assist" (help) vs. Spanish asistir (attend). Before: "I will assist to the kickoff call." After: "I'll attend the kickoff call."
  • "Pretend" (fake) vs. Spanish/Portuguese pretender (intend). Before: "I pretend to finish the migration by Friday." After: "I intend to finish the migration by Friday." This one is worse than most in a status update — "pretend" can read as if you're admitting to faking progress.
  • "Become" (to turn into) vs. German bekommen (to receive). Before: "I become the report tomorrow." After: "I'll get the report tomorrow."

Idioms translated word for word

A calque is an idiom carried over from your first language piece by piece — each word translates correctly, but the phrase doesn't exist in English, so the reader has to stop and decode it instead of just getting the point. It costs a beat of confusion in exactly the channels (Slack, status updates) that exist to save the reader time.

  • Russian/Ukrainian/Polish "to make an elephant out of a fly" → English uses the opposite image: "to make a mountain out of a molehill," or just "you're overreacting to something small."
  • Portuguese "estou com dúvidas" translated as "I am with doubts about the proposal" → "I have doubts about the proposal" or "I'm not sure about the proposal."
  • German "das hat weder Hand noch Fuß" translated as "that has neither hand nor foot" → "that doesn't add up" or "that doesn't make sense."

Directness and hedging: calibrated to the wrong workplace culture

English business writing has its own shape for politeness, and it doesn't match the default register of every workplace culture — the mismatch runs in both directions depending on where you learned to write at work.

Writers from flatter, more direct workplace registers (German, Dutch, Russian, Hebrew, among others) often write requests that are grammatically perfect and still land as blunt or curt in English, because English business writing typically wraps the same request in a question or a softener. Writers from higher-context, indirection-first registers (Japanese, Korean, Thai, Indonesian, among others) often hedge so heavily that the actual request disappears, and an English reader can skim right past it without registering that anything was asked.

The fix isn't 'always hedge' or 'always be direct' — it's matching the amount of softening to what English business readers expect for that specific ask, while keeping the ask itself (the ask, the deadline, the correction) fully intact. That's a register decision, not a grammar rule, which is why it's the hardest of these to self-correct.

  • Too blunt — Before: "Send me the numbers by Friday." After: "Could you send me the numbers by Friday?"
  • Too blunt — Before: "This is wrong. Fix it." After: "This doesn't look right to me — could you take another look?"
  • Over-hedged — Before: "I was wondering if it might perhaps be possible to maybe take a look at this sometime, if it's not too much trouble." After: "Could you review this by Thursday? Let me know if that timeline doesn't work."

FAILURE MODES

What goes wrong, and what to do instead

Skipping articles because your language doesn't have them, then overcorrecting by adding "the" in front of general or uncountable nouns to compensate.

Run a dedicated article pass, separate from any other editing: for each noun, ask if it's specific to both writer and reader (the), one of several (a/an), or general (no article).

Translating a verb's preposition straight from your own language — discuss about, depend of, agree with becoming "am agree with."

Keep a short running list of your own verb-plus-preposition mismatches as you catch them. They repeat across your writing, so five minutes now saves rereads for months.

Letting a status update drift between tenses because your language doesn't conjugate for time the way English does.

Write the update in three fixed blocks — done (past simple), in progress (present continuous), next (will/going to) — and don't let tense shift within a block.

Trusting a word that looks identical to one in your own language — actually, eventually, assist, pretend, sensible, become.

Treat lookalike words as suspects, not answers. If a word arrived instantly and feels too easy, check what it actually means in English before you send.

Matching your own workplace culture's directness norm instead of English business register — landing either too blunt or hedged into invisibility.

Edit the softening language separately from the ask itself. A deadline or a correction should survive the edit intact, whichever direction you're adjusting.

Questions writers ask about this

Why do I still make article mistakes (a/an/the) after years of speaking English?

For most speakers of article-less languages, article use isn't a vocabulary or fluency problem — it's a mental category (specific vs. general vs. countable) your first language never asked you to track. That's why it's one of the last things to stabilize even in advanced, otherwise error-free writing.

Is mixing tenses in a status update actually a problem, or just a style preference?

It's a status problem before it's a style problem. A manager reading "I work on revisions" can't tell if that's finished, ongoing, or planned, and has to ask. Keeping each time block's tense consistent removes the ambiguity, not just the accent.

What's a false cognate and why is it worse than a typo?

A false cognate is a word that looks like a word in your own language but means something different in English — actually, eventually, assist, and pretend are common examples. It's worse than a typo because it reads as fully correct English, so the error is invisible — it just quietly changes what you meant to say.

How do I know if I'm being too direct or too indirect in English?

It tracks to your workplace culture's baseline register more than your personality. Flatter, more direct cultures (German, Dutch, Russian, Hebrew, among others) tend to need a question form or softener added in English. Higher-context, indirection-first cultures (Japanese, Korean, Thai, Indonesian, among others) tend to need the actual ask stated plainly, with excess hedging trimmed back so it doesn't disappear.

Can a generic grammar checker catch these mistakes?

It catches article and preposition errors reasonably well, since those break standard grammar rules. It generally can't catch false cognates or translated idioms, because both are spelled correctly and grammatically valid — the problem is meaning, not syntax. That's closer to what Copynote's draft-to-English rewriting is built for: when you draft in your own language, it works from your intended meaning instead of translating word-for-word, so a false cognate or a literal idiom is less likely to slip through in the first place. It's still in beta and won't catch everything.

Do these mistakes show up the same way across every language background?

No — they cluster by first language. Article errors concentrate in article-less languages (Slavic, East Asian). False cognates concentrate in Romance and Germanic languages that share Latin or Germanic roots with English. Directness mismatches run in both directions depending on the writer's workplace culture. The categories are universal; the specific words and phrases inside each one aren't.

Read next

Writing a Professional Email in English When It Isn't Your First Language

A practical breakdown of the four decisions that actually make or break a professional email in English: which greeting fits the relationship, whether the ask is stated early enough to be read, how much context is too much, and whether the formality level matches how well you know the recipient. Written for people whose English is grammatically fine but who keep getting told their emails feel "off."

Confident, Not Rude: Getting Your Register Right in English

A guide to the specific grammar (modal verbs, hedge phrases) that English business register uses to signal "request" instead of "order" or "nothing at all" — and why writers whose first language is either more direct or more indirect than English trip on it in opposite ways.

Knowing the moves
is half of it

The other half is an editor that keeps meaning, tone and grammar in one pass. Copynote is in beta — apply and we’ll reach out as spots open.

Apply for beta

*Beta opens this season — starting with people who write at work in a second language.

The Copynote writing workspace