A partner sends a job. Seven languages, customer-service calls, each one mixed with English. The batches are small and the deadlines are short. The email asks one thing: can you take it?

The usual vendor reply is a list of questions. Which tagging convention? What audio quality? How many hours per language? Each question is fair. Together they read as “maybe”, and on a short deadline a maybe is how the job goes to someone else.

We answer yes or no first, then ask. This piece is about what has to exist before the email arrives so that a yes is safe to give. The example is a recent program we delivered for a global language services company: about 50 batches and roughly 3,000 conversations in seven languages.

Answer first, ask second

Partners managing a short-deadline job are juggling several vendors at once. What they need first is a commitment they can plan around. Questions about conventions and edge cases still need answers, but they belong after the yes, inside the job, where they can be settled with the partner’s own specification.

That order only works if a yes is not a gamble. Three things make it safe.

1. A named owner, and the same people on each language

One named owner answered for the account from the first batch to the last. On the seven-language program (Mandarin, Cantonese, Taiwan Mandarin, Japanese, Korean, Turkish and Tagalog, each mixed with English), more than 30 transcribers worked across the languages, and the same people stayed on a language from batch to batch.

The benefit is not speed on day one. It is that nobody is learning the client’s rules for the first time on a tight batch. Context carries over: the last batch’s corrections are already in people’s heads when the next one arrives.

2. One rule sheet per language, exceptions first

The general tags were learned in a day: how to mark a foreign stretch, a spelled-out acronym, overlapping speech, an inaudible passage, a cut-off word, with each segment kept under 15 seconds.

The errors sat somewhere else: in the rules that override the general guideline, one language at a time. In Tagalog, a single English word inside a sentence is how people talk, so it gets no language tag, and numbers stay in digits. Mandarin and Korean work the other way round. Japanese and Korean also need English written in their own script. A transcriber who learned the general rule first applies it by reflex, and the output looks clean until someone checks it against that language’s page of the specification.

So each language got its own rule sheet with its exceptions at the top, merged side by side with the client’s specification, and each exception became a line on the delivery checklist.

3. Our own deadline, ahead of the client’s

Every batch had an internal deadline six hours before the client’s. That window belonged to internal review and nothing else. When a batch ran late, the review window did not shrink, because it was never part of the production time in the first place.

Each task was self-checked item by item against the checklist, then reviewed internally, then delivered.

What changed

Over about 50 client batches we delivered roughly 3,000 conversations (around 670 task links), about 850 transcriber hours in total. In most languages, by the second month the average time per task had fallen below half of the first month’s.

People did not listen faster. The exceptions were written down, they stopped moving, and the same people kept applying them.

A question for your next vendor

If you manage vendors, ask one question before the next short-deadline job: what do you answer first? Then ask where each language’s exceptions sit on their checklist. The answers tell you more than a rate card.

Read the partner case · How we work with partners

Questions teams ask

How should a language subcontractor respond to a short-deadline job?

Answer yes or no first and ask clarifying questions after accepting. A list of questions before any commitment reads as a maybe, and on a short deadline a maybe usually means the job goes elsewhere.

What makes a fast yes safe for a subcontractor?

Three things in place before the job arrives: a named owner for the account and people who already know the client's rules, one rule sheet per language with that language's exceptions at the top, and an internal deadline ahead of the client's that is reserved for review.

Where do errors come from in multilingual code-switching transcription?

Usually not from the general tagging rules, which transcribers learn quickly, but from each language's own exceptions. For example, Tagalog leaves a single English word inside a sentence untagged, while Mandarin and Korean tag it.