Translation agency client onboarding: practical workflow

A translation agency client onboarding workflow starts by agreeing how work will be handled:

Set the handling boundary

Before files arrive, ask the client to identify any sector, contract, or publication obligations it believes apply, and name someone able to confirm them. Record that answer beside the agency's handling commitment and any subcontractor requirements. A file label alone does not establish which duties govern the assignment.

Under the HIPAA Privacy Rule, a service provider may be a business associate when it creates, receives, maintains, or transmits protected health information on behalf of a covered entity to perform services. HHS business associate guidance can help the client assess that question, including whether a business associate agreement and safeguards are needed. Applicability depends on the parties’ roles and the assignment, so have the client’s qualified adviser confirm it. Record the client’s response so the people arranging the work can find the agreed boundary.

Build a written-work record

A written assignment needs more than a welcome message: collect each input with an owner and due date, and name a reviewer for every locale. Record the review window and a fallback for missed deadlines, so files have a clear path through the client side. Set due dates backward from handoff: reviewer comments should arrive early enough for the agreed correction pass, and query replies should be due by the point at which a decision would otherwise block production. If a reviewer misses the window, notify the client, pause work that depends on the review, and confirm any revised delivery date rather than silently letting the schedule slip.

If the glossary is incomplete, mark gaps and capture candidate terms from the initial batch. Keep the reviewer, review period, and missed-deadline fallback visible to delivery staff. This gives the work a named contact and agreed expectation rather than allowing an ownerless file to circulate.

Give interpreting a separate route

Interpreting requires a separate booking route because assignment coordination depends on a scheduled start, not only file volume. Distinct intake keeps spoken work from being mistakenly placed in a written-translation workflow and gives clients a contact channel suited to a booked assignment.

Use the booking route to gather scheduling, setting, cancellation, subject briefing, participants, recording, travel, waiting time, and invoicing details. Keep those questions with spoken work rather than relying on a file-and-volume request to supply information for a scheduled assignment.

Make the distinction clear to agency staff and client contacts: written translation follows the file and volume route, while interpreting uses its own intake and contact channel. Separate handling helps prevent spoken requests from being processed under assumptions designed for written materials.

Agree on query handling

Set the question routine before source files arrive: it limits repeated interruptions, protects context around each uncertainty, and makes clear how a delayed reply affects the deadline. Agree which channel carries grouped questions, when answers are due, and the fallback if no response comes.

Keep the routine consistent across assignments and store decisions where the team can retrieve them. Set a reply deadline that leaves time to resolve the question before delivery. If it passes, flag the blocked item and schedule impact, pause that work or proceed only under a client-approved default, and tell the client about any delivery change; do not silently infer an answer.

Test, hand over, and close

A manageable first assignment tests whether the intake record works in practice and lets both sides spot unclear arrangements. Ask for focused feedback about confusing instructions, unexpected wording for a locale, and reasons for edits; the answers distinguish lasting preferences from points that still need a client decision.

Save lasting answers in the glossary and style notes. A single feedback round is not a verdict; recurring edits or questions may still show where the arrangement needs attention. If clients disengage after intake, revisit the way responsibilities and expectations were communicated.

Record project feedback against the intake record: note whether confusing instructions or edits came from missing source material, unclear ownership, or unanswered questions. Route any new preference for confirmation before adding it to standing guidance for later work.

Send files in the format already agreed, with change notes, open questions, and any action for the client. Mention relevant length changes and locale conventions so the recipient can assess what arrived. The delivery checks cover a broader operational sequence than this assignment's handoff.

For public-facing material, ask which accessibility requirements and output format apply. For state and local government entities, the U.S. Department of Justice’s 2024 ADA Title II web and mobile accessibility rule, codified in 28 C.F.R. Part 35, is a reference point. Whether a particular client or project is covered depends on its circumstances, so refer legal interpretation to the client’s adviser. See the federal accessibility rule.

Define in advance what acceptance means, the length of the client’s review period, and the consequence of no specific objection. Put those terms in the agreement and repeat them in the handoff note, so both sides use the same closeout rule. If no consequence for silence has been agreed, do not treat silence as acceptance; ask the client to confirm the status and keep the closeout unresolved until it is clear.

Silence has only the meaning agreed by the parties in advance. State the rule plainly, apply the agreed business-day window, and repeat the consequence in the delivery note. Consistent wording helps prevent a missed reply from being understood differently by the client and agency.

Make the agreed details available to staff scheduling and delivering later work. Check that promised services match the agency's commitment, and set clear limits through service package boundaries. This keeps intake decisions with the records used to arrange subsequent assignments.

Repeated questions, late reviews, or unplanned changes may signal that intake needs attention. The intake repair process addresses that issue. Keep this workflow focused on client intake: marketing and growth context and agency startup context are separate topics, not onboarding steps.