Every new agency relationship starts the same way: a project manager reaches out, often under some time pressure, to see if you’re a fit for their vendor pool. What happens in the first 48 hours after that initial contact often determines whether the relationship becomes a recurring source of work or a one-off assignment that never gets repeated.
Agencies don’t have the bandwidth to slowly ramp a new vendor up over weeks. They need someone who can absorb their process almost immediately — style guide, formatting rules, delivery expectations, communication preferences — and start producing work that fits seamlessly into their pipeline. Here’s how I approach that window, and how any subcontracted linguist can make the most of it.
Read Everything Before Asking Anything
The fastest way to look unprepared to a new agency contact is to ask questions that are already answered in the materials they sent. Before replying to a project brief, I read through every attached document: the style guide, any reference translations, glossaries, and formatting notes. Agencies often reuse the same onboarding packet for every new vendor, which means the answers to most “how do you want this done” questions are already sitting in your inbox.
Only after reviewing everything do I follow up with genuinely open questions — things like clarifying an ambiguous instruction, confirming file-naming conventions, or asking how to handle content that falls outside the style guide’s scope. This signals to the project manager that I’ve done my homework and that any question I do ask is one that actually needs an answer.
Mirror Their Terminology From Day One
Every agency has its own terminology preferences, often shaped by the end client’s own internal glossary. Legal clients might have strict preferences on how contract clauses are rendered; entertainment clients might have franchise-specific terms that must never be translated literally. On the very first assignment, I build a personal reference file capturing every terminology choice specific to that account, so by the second or third project, I’m not re-learning decisions I’ve already made.
This matters because agencies notice consistency — or the lack of it — faster than almost anything else. A translator who uses three different renderings of the same term across three projects looks unreliable, even if each individual translation is technically correct. A translator who locks in terminology after the first project and applies it consistently looks like someone who can be trusted with larger, more complex accounts.
Confirm Delivery Format Before, Not After
Nothing frustrates a project manager more than receiving a file in the wrong format after a deadline has already passed. Before starting any new assignment, I confirm exactly how the finished work should be delivered — file type, naming convention, whether tracked changes are expected, whether the file needs to be uploaded to a portal or sent by email. This is a five-minute conversation upfront that avoids a much longer, more stressful conversation after the fact.
Set Realistic Expectations Immediately
New agency relationships often come with a slight mismatch between what the project manager assumes about turnaround and what’s actually feasible. Rather than agreeing to a timeline that sounds convenient but isn’t realistic, I confirm turnaround explicitly on the first assignment, including any buffer needed for self-QA before delivery. Agencies would rather hear “I can deliver this by Thursday at noon” upfront than “yes, that works” followed by a late delivery.
The Second Assignment Is Where Trust Is Built
The first assignment from a new agency is essentially an audition. The second and third assignments are where the relationship either solidifies or quietly fades. If the first project goes well, agencies tend to test a subcontractor again fairly quickly — often with a slightly larger or more complex piece of work. Being ready for that test means having already absorbed their style guide and terminology preferences well enough that the second project takes less back-and-forth than the first.
Building a Repeatable Onboarding Checklist
Over time, subcontracting for multiple agencies means managing multiple sets of preferences simultaneously. I keep a simple checklist for every new agency relationship: style guide location, glossary file, delivery format, preferred communication channel, and any account-specific quirks. This isn’t complicated, but it’s the difference between onboarding smoothly onto a fifth agency relationship versus starting from scratch each time.
Agencies remember which vendors made their first project painless and which ones required constant clarification. The first 48 hours are a small window, but they set the tone for everything that follows.
Avoiding the Common First-Impression Mistakes
There are a handful of onboarding mistakes that come up again and again among linguists new to subcontracting, and avoiding them is often just as important as doing the positive steps well. One common mistake is over-promising on turnaround to seem eager, then struggling to deliver on time. Another is glossing over a style guide’s more tedious sections — formatting rules for numbers, dates, or units of measurement — because they seem minor, only to have a reviewer flag repeated errors in exactly those areas. A third is failing to ask about file security or confidentiality expectations upfront, which can matter a great deal to agencies handling sensitive legal or corporate content.
Building Your Own Onboarding Template
Because so much of onboarding onto a new agency follows a similar pattern, it’s worth building a personal onboarding template that can be reused and adapted for each new relationship. Mine includes fields for the agency’s preferred communication channel, standard turnaround expectations, style guide location and version, terminology reference files, delivery format and naming conventions, and any account-specific notes gathered from the first few projects. Having this structured from the start means every new agency relationship benefits from lessons learned in previous ones, rather than starting completely from scratch each time.
Why Speed of Onboarding Matters More Than It Seems
Agencies frequently reach out to multiple potential subcontractors at once when evaluating new vendors, especially for urgent projects. The linguist who responds quickly, asks smart and specific questions, and demonstrates readiness to start immediately has a real advantage over one who takes days to review materials or asks questions that suggest they haven’t engaged with the onboarding packet at all. In a competitive vendor pool, the speed and quality of that initial onboarding conversation can be the deciding factor in who gets the first assignment — and, by extension, the chance to prove themselves for everything that follows.