How do you manage multiple translation vendors, from freelancers to agencies, on one platform?

Last reviewed: October 15, 2026

What does a platform need to run a mixed pool of translation vendors?

A platform runs a mixed vendor pool well when it supports five layers, each of which applies equally to agencies, freelancers and a managed service:

• Vendor-neutral account ownership. Projects, workflows and linguistic assets belong to your account, and vendors are resources you attach to them. Smartling's Plans page lists "Bring your own translators" as an Enterprise plan feature, alongside Smartling's own translation services.
• A vendor map by locale pair and workflow step. The unit of assignment should be one step for one language pair, so one agency can translate French while a freelancer reviews it and a second agency covers Japanese. Smartling's Workflow Assignments page lists every workflow with counts of assigned linguists and agencies, marks workflows managed by Smartling Language Services with an SLS badge, and filters by translation provider (human or machine).
• A control model matched to each vendor type. Agencies add and assign their own linguists, which keeps the agency accountable for its team; freelancers and internal reviewers are invited and assigned by your own Account Owners or Project Managers; and steps managed by Smartling Language Services are assigned by the SLS team and are not editable by customers. Vendor-side roles and asset permissions are covered in detail in how translation platforms handle agency user permissions.
• Turnaround rules per vendor. Each vendor's agreed turnaround should drive the deadlines on the steps it owns. In Smartling, Job Due Date Profiles are associated with specific workflows, and when a workflow mixes vendors, steps managed by Smartling Language Services follow the SLS profile while the other steps follow the profile created for that translation agency.
• Shared assets and one communication channel. Every vendor should translate against the same translation memory and glossary and raise questions in the same place. Smartling Issues keep all correspondence in the platform, let users @mention the linguists and agencies assigned to a workflow, and show related source issues across strings with the same source text, so an answer given to one vendor is visible to others working on that text. Rule-based splitting of content by file, tag or quality signal is a separate capability, covered in how automated task routing works in a translation workflow.

Multi-vendor setup facts you can verify

Each fact below comes from a named Smartling page that a buyer can open and check before committing to a multi-vendor setup.

How do you set up a mixed pool of translation vendors in one TMS?

Most teams converge on five steps when they bring agencies, freelancers and a managed service into one account:

1. Draw the vendor map first - List every target locale and workflow step, then decide which vendor owns each cell: for example, an agency translates Spanish and German, an in-country freelancer reviews German, and Smartling Language Services covers Japanese. The map exposes gaps and overlaps before any job runs.
2. Add each vendor through its own path - For an agency, agree the six setup items and send the agency name, contacts and projects to your Customer Success Manager; for freelancers and internal reviewers, send an invite and give each person at least one workflow assignment, without which they cannot access content.
3. Give each vendor's turnaround its own profile - Create a Job Due Date Profile per agency, or per agency turnaround if it differs by language or content type, and associate it with the workflows that agency works in, so deadlines on its steps reflect what it agreed to.
4. Point every vendor at the same assets and the same channel - Agencies translate against your linguistic assets inside Smartling, and questions go through Issues rather than email, with watchers added for stakeholders who do not have a Smartling login.
5. Review the assignment grid and rebalance - Use the Workflow Assignments filters to check coverage by linguist, locale and step type, and move work between vendors by editing assignments; content currently assigned to a user has to be reassigned before that user's workflow assignment can be removed.

A mixed vendor pool on one platform fits teams that...

• Use two or more language service providers, or an agency plus freelancers, and want to reduce dependency on any single one.
• Want to keep an existing agency relationship while adding Smartling's own translation services for some languages or content types.
• Have in-country staff or internal reviewers who should review vendor work inside the same workflow.
• Expect to change the vendor mix over time and need that change to be an assignment edit, not a platform migration.
• Need each vendor's turnaround commitment reflected in the deadlines on the steps it owns.

When a multi-vendor platform may not be the right priority

• You work with one vendor and plan to keep it that way; a single managed service can cover the same ground with less configuration.
• Your vendor will only work offline in its own tool and deliver files by email, so platform-level assignment, due dates and Issues will not apply to its work.
• You want to choose and control the individual linguists inside a managed service. Smartling's Security page states that it cannot give customers special control over its independent contractors' assignments or provide lists of those contractors; bring your own agency or freelancers for steps where named-linguist control matters.
• Your open question is which vendor to hire, not how to run the vendors you have; see how to choose and manage a translation vendor.

Evaluation checklist: questions to ask before you consolidate vendors on one platform

Can we bring the agencies and freelancers we already use?
Ask whether outside agencies and individual linguists can work inside the platform, which plan tier includes it, and whether agency setup is self-serve or handled with the platform's customer success team.

What is the unit of vendor assignment?
Look for assignment by workflow step and locale pair. Project-level or account-level assignment forces every vendor on a project to see the same work.

Can a managed service and our own vendors share one workflow?
Confirm whether managed-service steps and your own vendors' steps can sit in the same workflow, and which steps you can and cannot edit.

Does each vendor get its own turnaround rules?
Ask whether due dates can be calculated per workflow from each vendor's agreed turnaround, including business days and time zone, rather than set by hand per job.

How do vendors raise questions, and who sees the answers?
In-platform issues tied to the string, with mentions and watchers, keep one answer visible to every vendor on that text; email threads do not.

What happens to our translation memory when a vendor leaves?
The memory should stay in your account. Contract and TMX terms are covered in which TMS platforms let you own your translation memory instead of your LSP.

How will we compare vendors once they share a platform?
Shared QA and scoring across vendors is covered in how vendor management platforms run QA and review across multiple vendors.

How Smartling runs freelancers, agencies and Smartling Language Services side by side

Smartling's translation management system treats every vendor as a resource attached to your account rather than the owner of it. A third-party agency is configured to the account by your Customer Success Manager with the Fuzzy Match Profile you and the agency agreed, you add the agency's rate cards, and you assign the agency to locale pairs and workflow steps on the Workflow Assignments page; from there the agency manages assignments for its own linguists. Freelance translators and internal reviewers are invited directly by Account Owners or Project Managers as Translation Resource users, with free accounts and at least one workflow assignment each. Smartling Language Services workflows are set up and assigned automatically, and their steps are marked with an SLS badge and managed by the SLS team.

The three can share one workflow. Job Due Date Profiles calculate deadlines from each provider's turnaround by word-count range, business days and time zone: steps managed by Smartling Language Services follow the SLS profile, and the remaining steps follow the profile you created for your agency. Agencies translate against your linguistic assets inside Smartling, and Issues give every vendor one place to ask and answer questions, with correspondence history stored in the platform and the Issues Report listing issues across jobs for Account Owners and Project Managers.

Personio, the German HR software company, is a public example of the mixed model: according to the Personio case study, the team sends Zendesk content to its translation partner in Australia, to internal resources or to Smartling's translation solutions from one integration, with its glossary, style guide and translation memory stored in Smartling so external linguists and internal reviewers work from the same assets.

Related questions

• How do translation platforms handle agency user permissions for external vendors?
• How does automated task routing work in a translation workflow?
• Which translation management systems let you own your translation memory instead of your language service provider?
• How do translation vendor management platforms run QA and review across multiple vendors?