Every subcontracting relationship eventually hits a moment of pressure: a file arrives late, a source document turns out to be incomplete, a deadline gets moved up, or an unexpected complication surfaces midway through a project. How a subcontractor communicates in that moment says more about their reliability than almost anything else — and it’s often the single biggest factor in whether an agency keeps using them.
Silence Is the Worst Response
The single most damaging thing a subcontractor can do under pressure is go quiet. A project manager who hasn’t heard from a vendor as a deadline approaches has no way to plan around a potential delay, no way to reassign work if needed, and no way to manage the end client’s expectations. Even bad news delivered early is infinitely more valuable to an agency than silence followed by a missed deadline.
I make it a rule to flag any potential issue — a delay, an ambiguity in the source material, a technical problem — as soon as I identify it, rather than waiting to see if it resolves itself. A short message that says “I’ve hit an issue with section three of the contract — the source text seems to be missing a clause reference, can you confirm before I proceed?” takes two minutes to write and can save hours of wasted work or a missed deadline.
Give Options, Not Just Problems
When something does go wrong, the most useful communication doesn’t just describe the problem — it offers a path forward. Rather than simply saying “I’m going to be an hour late,” I try to frame updates around what I can control: “I can deliver the full file by 3pm instead of 2pm, or send the first half now and the remainder by 3pm if that’s more useful for your review process.” Giving a project manager options, rather than just a problem, makes it far easier for them to make a quick decision and move on.
Match the Agency’s Preferred Channel
Different agencies have different communication preferences — some run everything through a project management platform, others prefer email, and some expect quick responses over instant messaging for urgent issues. Part of onboarding well onto a new agency relationship is figuring out, early, which channel they actually check regularly and using that channel for anything time-sensitive, rather than defaulting to whatever is most convenient for me.
Confirm Receipt and Set Expectations Proactively
When a new brief or file arrives, especially one with an unusually tight turnaround, I make a habit of confirming receipt immediately along with a realistic estimate of when the completed work will be ready — even if that confirmation is just a two-line message. This closes the loop for the project manager and removes any uncertainty about whether the request went through and is being handled.
Handling Disagreements Professionally
Occasionally a reviewer’s feedback or a style guide instruction seems genuinely wrong — a mistranslation being introduced by a “correction,” or a formatting rule that conflicts with the source material. In those situations, pushing back is sometimes appropriate, but it has to be done carefully. I raise concerns as questions rather than accusations: “I want to flag that this correction changes the meaning of the original clause — can we double check this with the reviewer before it goes final?” This keeps the conversation collaborative rather than adversarial, and it respects that the agency, not the subcontractor, owns the final relationship with the end client.
Consistency Builds a Reputation
Over enough projects, a pattern emerges in how a subcontractor communicates under pressure. Agencies remember which vendors flag problems early and offer solutions, and which vendors either go silent or become difficult to work with when something goes wrong. That reputation, built project by project, often matters more in the long run than any single piece of translated work — because it determines whether an agency feels safe handing over the next high-stakes, time-sensitive assignment.
Being genuinely dependable under pressure isn’t about never having problems. It’s about how quickly and clearly those problems get communicated, and how much easier that communication makes the agency’s job of managing the bigger picture.
Managing Expectations When Multiple Agencies Compete for Time
As a subcontracting practice grows to include several agency relationships, deadline pressure sometimes comes from more than one direction simultaneously. Handling this well means being honest with each agency about current capacity rather than overcommitting to please everyone and then quietly falling behind on all of them. If a new request would conflict meaningfully with an existing commitment, I say so directly and offer a realistic alternative timeline, rather than accepting the work and hoping the timing somehow works itself out. Agencies generally respond better to a clear “I can take this, but not until Thursday” than to a vague yes that later turns into a missed deadline.
The Value of Over-Communicating Early in a New Relationship
With newer agency relationships especially, I lean toward communicating more than might strictly be necessary, at least until a clearer sense of their expectations and preferences develops. A quick note confirming a file was received, a brief update halfway through a longer project, or a short message flagging a minor ambiguity all help build a track record of responsiveness before any real problem ever arises. Once a relationship is well established and trust has been built, the frequency of check-ins can naturally decrease, but starting cautious and communicative rather than assuming radio silence is acceptable tends to pay off in how quickly trust develops.
Recovering Well When Something Actually Goes Wrong
Even with the best communication habits, occasional real mistakes happen — a missed detail, a technical file issue, or a genuine misunderstanding about scope. How a subcontractor handles the recovery from a mistake often matters more to an agency than the mistake itself. I focus on acknowledging the issue clearly and quickly, proposing a concrete fix, and following through without making the project manager chase me for updates. Agencies are generally far more forgiving of an honest, promptly corrected mistake than of a vendor who becomes defensive, slow to respond, or evasive once something has gone wrong.