Part of the series “Working With a Translator: A Guide for Clients”
You send your files to the agency.
You get translations back.
Some are fine. Some are… strangely flat. Some cause problems three months later when a parent complains, or a donor queries a sentence in your report.
On paper, there’s a “project manager” looking after all this. In practice, that person can either be your best ally… or the invisible reason your translations always feel a bit off.
This article is about the second kind: the checked-out, lazy, or overwhelmed PM — and how you, as the client, can protect your projects from the fallout.
What a Good Translation PM Should Be Doing (So You Notice When They’re Not)
Let’s start with the ideal. A good translation project manager is not just a file forwarder. They should:
- Turn your needs into a clear brief
Who is this for? Parents? Staff? A ministry? What country? What reading level? What tone? What’s at stake if something is misunderstood? - Match the right translator to the right text
An IEP is not a party flyer. A humanitarian report is not a marketing brochure. Subject-matter expertise matters. - Manage queries and clarifications
Collect the translator’s questions, group them, send them to you in a digestible format, and share your answers with the whole team. - Keep continuity over time
Maintain glossaries, translation memories, and style guides so key terms and tones don’t change from one project to the next. - Handle the admin and tech layer
File prep, platforms, SDLTM/TM management, QA tools — so the translator can actually… translate.
When a PM does this, you barely notice. Things “just work.” When they don’t, you feel it everywhere — but often can’t quite name why.
The “Lazy PM” Patterns: Red Flags You Can See From the Outside
You don’t see their inbox or their CAT tools. But you do see patterns. Here are a few you can spot even if you never touch a termbase yourself.
1. The Email Forwarder
You send files. They forward them on with “Please translate, same as usual” — no questions, no briefing, no mention of audience or stakes.
If your documents cover everything from legal policies to party invitations and the brief is always “same as before,” that’s a red flag.
2. The Gatekeeper Who Blocks Queries
Translators ask questions. The PM doesn’t pass them on:
“The client is too busy.”
“Just decide something.”
“We’ve always done it like that.”
Result: translators guess. Ambiguous policies, unclear acronyms, program names that matter politically — all handled on assumptions instead of facts. Your translation hangs in mid-air because key decisions are never actually made.
3. The One-Style-Fits-All Zealot
One real example: a public school district where the PM announced that all documents must be written for a six-year-old reading level.
On that account were:
- legal notices,
- Individualized Education Plans (IEPs),
- superintendent letters,
- internal memos,
- party flyers and event announcements.
Some of those should be accessible to very young readers or to parents with low literacy. Others carry legal obligations or delicate, technical detail. Flattening everything to one reading level is not “inclusive,” it’s careless: you lose nuance where you can’t afford to lose it, and you talk down to people in contexts that require respect.
4. The Admin Offloader
This PM pushes their own job down the chain. Typical moves:
- asking translators to create and export separate translation memory (SDLTM/TM) files for every single document,
- requesting the same information in three different formats “for the system,”
- having linguists re-upload, relabel and reorganize files in a platform — all unpaid.
Meanwhile, nobody is actually talking to you about audience, tone or risk. The energy is going into moving boxes around, not into getting the content right.
5. The Non-Native Terminology Tinkerer
This one is more subtle — and dangerous. It’s the PM whose working language isn’t the target language, but who still decides to “clean up” the termbase and style decisions that specialists have carefully calibrated for your field.
- They open a TB that has taken years to refine — with legal, humanitarian or education-sensitive entries — and start “harmonizing” entries based on their own second-language instincts.
- Domain-specific choices get replaced with generic adverbs and half-calques:
- consistently in a QA or compliance context becomes constamment, everywhere, even where the nuance should be “systematically,” “reliably” or “de manière cohérente.”
- They “improve” terminology based on what sounds good to them, not on how the field actually writes.
From your side you see a glossary that suddenly feels fluffy, repetitive or oddly literal. From the translator’s side, years of careful work are quietly overwritten in a Friday-afternoon “cleanup.”
How Lazy Project Management Shows Up in Your Translations
From your side, you don’t see the internal chaos. You see its shadow.
- Tone mismatch
Legal and policy texts come back weirdly childish or vague. Party flyers sound like government circulars. - Inconsistent terminology
Program names, job titles or key concepts are translated differently in each document because queries never reached you and no glossary is kept up to date. - “Improved” but actually worse terminology
Phrases that used to be sharp and field-appropriate are suddenly full of generic additions:- adverbs like constamment sprinkled everywhere because someone equated “consistency” with “constantness”;
- previously clear terms replaced by literal, non-native-sounding equivalents.
- Vague, “floating” sentences
Places where a translator clearly needed a decision and nobody would ask you — so they wrote something generic that “can’t be wrong,” but also doesn’t really say anything. - Hidden costs
Your staff spend hours rewriting, clarifying, or apologizing. You hold extra review meetings. Parents, communities or partners feel confused or patronized. - No clear accountability
When something goes wrong, everyone blames “the translation” — but nobody can tell you who was actually responsible for managing the project as a whole.
What “Engaged” Looks Like: Questions You Should Be Hearing
Whether you work with an agency or directly with a freelancer, someone serious about your content will ask things like:
- About your organization and audiences
- Who are these texts really for — parents, staff, donors, ministries, local partners?
- Are there different literacy levels, languages, or cultural references we need to respect?
- About each document
- Is this legal, technical, informational, persuasive, or celebratory?
- How formal should it be? What reading level is appropriate for this text?
- About style and constraints
- Do you have existing translations, glossaries, or style guides we should follow?
- Are there terms or acronyms that must stay in the original language?
- About queries
- Who is the best person to answer questions?
- How and when do you want to receive them (spreadsheet, comment bubbles, weekly batch)?
- About the termbase and TMs
- Do you already have a TB for this field? Who created it?
- Are there entries that must not be changed without your approval?
- About feedback and continuity
- How will we record your preferences so we don’t repeat the same questions on the next project?
If nobody ever asks you these things, chances are your translation is being handled on autopilot — and your carefully crafted terminology is at risk of being “improved” into mush.
How to Protect Your Projects (Even If the PM Is Sleepwalking)
You can’t micromanage an agency, and you shouldn’t have to. But you can set some basic protections.
- Use a simple briefing template
For every project, make sure you tell them:- who the audience is,
- what type of document it is (policy, IEP, flyer, internal memo, report…),
- what’s at stake if it’s misunderstood,
- the desired tone and reading level.
- Protect your termbase
- Ask who owns and maintains your TB.
- Make it explicit that changes to key terms (legal, clinical, humanitarian, education-specific) must be discussed, not made unilaterally by a non-native PM.
- If you start seeing odd, repetitive adverbs or off-key terms in your glossary, ask who changed them and why.
- Ask agencies a few direct questions before you sign
- Who is my day-to-day PM and what exactly do they do?
- How do you choose translators for my field?
- How do translators send you questions, and how do those questions reach me?
- Who maintains our glossaries, style guides and translation memories, and what’s their level in the target language?
- Insist on differentiated style, not one-size-fits-all
Make it explicit that legal/policy texts, IEPs, public flyers, superintendent letters and internal memos cannot all be treated the same. Ask them how they will handle this. - Watch for admin offloading
If you discover that translators are doing a lot of unpaid project management and engineering, ask why. If the PM isn’t managing, someone else is — and that someone may be cutting corners to stay afloat. - For high-stakes content, ask to speak to the translator
Sometimes a 20-minute call with the person actually making the linguistic decisions will save you weeks of back-and-forth through a passive PM.
When It Makes Sense to Work Directly With a Specialist Translator
Agencies and good PMs absolutely have their place, especially for huge multilingual volumes. But for high-stakes, nuanced texts — humanitarian reports, public-sector communications, legal or education content, IEPs — a checked-out or termbase-tinkering PM is a liability.
Working directly with a specialist translator means:
- the same person who worries about nuance is the one asking you questions;
- admin and tech (glossaries, TMs, query logs) are part of a transparent, agreed-upon workflow, not hidden in the word rate;
- you can develop a relationship where they learn your context, your constraints, your stakeholders — and carry that knowledge from project to project;
- nobody “improves” your carefully tuned terminology by turning consistent into constamment everywhere.
That’s what I do as an EN–FR translator in the humanitarian and public-sector space: act as both linguist and mini-project-manager for your content, so nothing crucial falls through the cracks because “we didn’t want to bother the client” or “it sounded fine to me.”
Quick Checklist: Is Your Translation Being Properly Managed?
Keep this near your inbox:
If you can answer “yes” to most of these, you’re in good hands:
✅ Someone asked who each document is for and what kind of document it is.
✅ Legal/technical documents are treated differently from flyers and party invitations.
✅ Translator queries reach you in time, in a format you can handle.
✅ Your answers and preferences are remembered from one project to the next.
✅ Admin and tech work (TMs, platforms, file prep) are clearly planned and owned.
✅ Changes to your termbase are intentional, documented, and made by people who actually write in the target language.
If these feel familiar, you may have a lazy PM problem:
❌ You never see questions; translations just “appear.”
❌ The PM insists on one style or reading level for everything.
❌ Legal, IEP or policy content comes back oversimplified or oddly vague.
❌ Translators seem to be doing PM or engineering tasks off the side of their desk.
❌ Your TB suddenly fills up with generic adverbs and literal calques that nobody discussed with you.
❌ Every project feels like the first time you’ve ever worked together.
Good project managers exist, and they’re worth their weight in gold. But if you recognize the lazy — or overconfident non-native — patterns in your current setup, you don’t have to put up with them. In fact, the people who feel those patterns most sharply are your best translators, and they quietly vote with their feet. They’re the ones who care about nuance, push back on bad termbase changes, and send the “annoying” queries that protect you from risk; when those signals are ignored or punished, they simply stop accepting work from that agency. From the outside, all you see is a slow slide in quality and a revolving door of new names. From the inside, it’s simple: the professionals who could have built long-term value for you fled first.
You’re allowed to ask better questions.
You’re allowed to expect real management, not just file forwarding and termbase tinkering.
And you’re allowed to choose translators and partners who actually act like partners—so the people you most want on your side have a good reason to stay.