Writing at work in a language that isn't your first

Working in a second language does not mostly cost you accuracy. Past a certain level of fluency your grammar is fine and the errors that remain are small. What it costs you is time and control over tone. The time goes on re-reading four sentences to convince yourself they are fine. The tone is the part that fails silently: a message can be flawless and still arrive twice as blunt or twice as apologetic as you intended, and nobody replies to tell you so.

The cost nobody puts on the timesheet #

The re-reading tax. You write a four-sentence reply in three minutes and spend eleven more auditing it: change please to could you, read it again, put please back. That audit does not shrink as your grammar improves, because it is driven by not being able to feel whether something is right. Fluency removes the mistakes long before it removes the doubt.

Hedging drift. Unsure how hard a sentence lands, you add a softener. Then, still unsure, a second. “I just wanted to quickly ask if maybe you could possibly take a look at this when you have a moment, if that is okay.” Five hedges around one request. It reads as anxious or evasive, both worse than the plain version you were afraid to send.

Range collapse. In your first language you have twenty ways to say no, graded by how much you mean it. In your second you reliably have two, and both are the polite one. So you agree to the call at 7am. Nobody sees the eighteen options you did not have.

Avoidance. The quiet one: you write the sentence you can definitely build rather than the sentence you meant, fast enough that you barely notice choosing. From the outside that looks like having fewer opinions.

Why you sound blunter, or more deferential, than you mean #

Because politeness is stored in a different part of the language depending on which language it is, and translation moves the words, not the storage.

English keeps courtesy almost entirely in grammar: a modal verb (could, would), the question form, and a past tense used as distance (I was wondering whether). “Send me the file” and “Could you send me the file?” contain the same content words; the modal and the question mark are the entire difference between an instruction and a request.

German stores it in the pronoun and a particle instead: “Schicken Sie mir bitte die Datei.” is courteous German. Word for word it becomes “Send me please the file”, which in English is an instruction with a please attached, roughly what a manager says to an intern. Nothing was mistranslated. The courtesy was carried by Sie, and English has nowhere to put it except a modal the translation never added.

The same mechanism runs the other way. Japanese and Korean encode respect in obligatory verb morphology (keigo, jondaemal). English has no such system, so the deference gets re-expressed in vocabulary and stacks up: “I am very sorry to trouble you, and I apologise for the inconvenience, but if it would not be too much of an imposition…” To an English-speaking reader that signals either that something has gone badly wrong or that the writer does not mean it. One marker of deference is the English maximum.

There is a second axis, and it is not grammar at all. Some writing cultures put the ask at the end, after the context that justifies it; English business writing puts it first. If your reader is in an English-speaking office, front the ask: it will feel rude to you and read as considerate to them.

What goes wrong, by language #

These are transfer patterns, not statements about people: the predictable result of a structure your first language has and English does not, or the reverse. A pattern you can name is one you can drill in an afternoon.

Slavic and East Asian first languages: articles

Russian, Polish, Czech, Ukrainian, Mandarin, Japanese and Korean have no articles. Definiteness is carried by word order, context or a demonstrative, so there is no habit to transfer, and the errors land in three reliable places:

• Dropping the before something already introduced: “I attached report you asked about” should be “I attached the report you asked about.”
• Dropping a before a singular countable noun: “I am developer on the payments team” should be “I am a developer on the payments team.”
• Adding the to a general plural or an abstract noun: “The customers want the transparency” should be “Customers want transparency.”

A rule of thumb that gets most of it: if you could point at the thing and you both know which one, use the; if it is one of several and you are introducing it, use a; if you mean the category rather than an instance, use nothing.

Word order is the second transfer. Russian and Polish order words for emphasis, because case endings already say who did what; English word order carries the grammar itself, so fronting an object reads as a mistake. Put the stress in a word: only, even.

Romance first languages: false friends and register inflation

Spanish, French, Italian and Portuguese share an enormous Latin vocabulary with English, which is mostly a gift. The exceptions are consistent enough to memorise:

• Actual means current: “the actual version” should be “the current version.”
• Eventually is not eventual. “Eventually we will need a second server” promises something; “we may need a second server” was what you meant.
• Assist to is not attend: asistir and assister mean to be present at.
• Sensible means sensitive, and demander means to ask. English demand does not.

Register inflation does more damage than any single false friend. In Romance languages the Latinate word is the everyday one; in English it is the formal one. So utilise for use, commence for start, solicit for ask for. Each is correct English, and together they make an ordinary Tuesday email read like a legal notice. When two words are available, the shorter Germanic one is almost always the right register for work.

German first language: sentence length and the cost of directness

German tolerates a much longer sentence, with the main verb parked at the end, and readers hold the structure open until it arrives. Transfer that into English and the verb turns up after three subordinate clauses; English readers do not hold structures open that long. The fix is mechanical: split at the comma.

Politeness transfers well: “Könnten Sie mir bitte…” maps almost exactly onto “Could you please…”. The norm for disagreement does not. A German-normal “Das ist falsch” rendered as “That is wrong” is a much harder line in an English-speaking office than the writer intends, because English prefaces disagreement: “I might be missing something, but I think that is wrong.” The preface is not dishonesty; it signals that you are disagreeing with the claim, not the person. Two false friends: bekommen is receive, and eventuell is possibly.

Japanese and Korean first languages: the missing subject

Beyond the deference stacking above, both languages drop the subject whenever context recovers it, and English does not. “Will send by Friday” is complete in Japanese and ambiguous in English: the reader cannot tell whether you are sending it or they are. Two words fix a real coordination failure, not just an oddity.

Tactics that are not “use a tool” #

1. Write the ask first. One sentence at the top containing the verb you want the reader to perform and the date you want it by. Context goes underneath. This fixes more perceived-tone problems than any amount of vocabulary: most emails that read badly in a second language are not ungrammatical, they are long, hedged and back-loaded.
2. One softener, not three. Choose could you or when you get a chance. Not both, and not both plus sorry to bother you. Stacked hedges read as anxiety, and anxiety reads as something being wrong.
3. Cap sentences at about twenty words. Nearly every sentence that reads strangely in a second language is a translated long sentence. Split it at the comma.
4. Steal sentences instead of composing them. Keep a file of lines you have received from first-language writers that did the job: openings, chasers, polite declines, bad news. Reuse them with the nouns swapped. It is how first-language writers learn register too. They just call it reading a lot of email.
5. Read it aloud once. Your ear for rhythm in a second language runs ahead of your grammatical intuition, so awkwardness surfaces audibly before you can explain it. It also catches the sentence that turned out to be forty words long.
6. Name the constraint instead of hedging around it. “I can review this by Thursday, not before” is shorter and less risky than three sentences of apology. Precision reads as confidence; vagueness reads as reluctance.
7. Find one register reader. Not a proofreader, but someone who will tell you “that came across as annoyed” once a month. One honest colleague beats a year of self-editing.
8. Never apologise for your English in the email. It moves the reader's attention from what you said to how you said it, and makes a competent message look uncertain.

Where a checker genuinely helps #

A checker cannot decide how direct you want to be: that is a judgement about a relationship, and the tool does not know the relationship. What it can do is take the mechanical layer off your hands so the revision goes to the decision instead of the audit:

• The mechanical layer. Articles, agreement, prepositions and tense are predictable from your first language and tedious to hunt yourself. FixMeBot's mistakes correction works in 90+ languages and detects which one you are writing in, so a Polish message gets Polish rules rather than English ones applied through a translation.
• The re-reading tax. The real return: ten minutes spent proving to yourself that four sentences are fine become one pass, and the confidence comes from having checked rather than from having stared.
• The inbound direction. Half the difficulty is what you receive: a contract clause, an idiom, an acronym everyone else seems to know. Explanation answers in the language you are reading in; an explanation in your third-best language is another translation problem.
• Drafting in your strongest language. For something high-stakes, write it where you have all twenty ways to say no, then translate it with the register kept, and edit the English afterwards, because even a good translation carries first-language structure across with it.

And where it does not help: it will not settle how blunt to be, and it may replace a term your team uses with a more common word. It is also not evidence of anything about your English. First-language writers use spell-check, style guides and editors, and nobody reads that as a verdict on them. Writing is a second pass; the only question is what you spend it on.