SOPs for Translation Agencies: How to Document Your Processes and Stop Keeping Everything in Your Head¶
Your project manager quit on Friday. Monday morning you’ve got 12 active projects, three freelancers waiting for instructions, and a client escalation sitting in your inbox. The problem? All the knowledge about how things work - which translator gets medical projects, what the QA checklist looks like, how you handle rush orders - was in your PM’s head. And now it’s gone.
If this scenario makes you break into a cold sweat, you don’t have a people problem. You have a documentation problem.
A Standard Operating Procedure (SOP) is a written, step-by-step description of how a specific process works at your company. It’s not a policy (“we believe in quality”). It’s not a guideline (“try to respond quickly”). It’s a concrete set of instructions: when X happens, do Y, then Z, then check W.
For a translation agency, SOPs cover everything from how you receive a new project to how you pay freelancers. They’re the difference between a business that depends on specific people and a business that runs on systems.
Let’s figure out which SOPs you need, how to write them, and - most importantly - how to make sure your team actually uses them.
Why Your Translation Agency Needs SOPs: 5 Reasons That Solve Real Problems¶
SOPs aren’t bureaucratic paperwork you create to impress auditors. They solve five very specific problems that every growing translation agency faces.
1. Faster onboarding¶
When a new PM or coordinator joins your team, how long does it take before they can handle projects independently? Without SOPs, the answer is usually “weeks” - because they’re learning by asking questions, making mistakes, and absorbing tribal knowledge one conversation at a time.
With documented processes, that timeline shrinks dramatically. According to Brandon Hall Group research, organizations with structured onboarding improve new hire productivity by over 70%. In a translation agency context, that means your new PM can start managing simple projects within days instead of sitting next to a senior colleague for a month.
2. Consistent quality regardless of who works¶
Your best PM handles client communication perfectly - confirms deadlines, sends progress updates, flags issues early. Your newest PM? Forgets to send the style guide to the translator and delivers the project without a final QA check.
SOPs eliminate this variance. When the process is written down - with checklists, decision trees, and quality gates - the output quality depends less on individual skill and more on the system.
3. Scaling without chaos¶
You’re growing from 5 to 15 freelancers, from 20 to 60 projects a month. Without documented processes, every new person multiplies the chaos. With SOPs, every new person plugs into an existing system. This is exactly what separates a freelancer-with-helpers from an actual agency. More on this transition in our guide on scaling a translation agency from solo freelancer to full LSP.
4. ISO 17100 preparation¶
If you’re planning to get ISO 17100 certified, documented processes aren’t optional - they’re a requirement. The standard explicitly demands that translation service providers have formalized procedures for project management, translation, revision, and quality control.
As ISO’s official description states:
ISO 17100 specifies requirements for all aspects of the translation process directly affecting the quality and delivery of translation services. It includes provisions for translation service providers regarding the management of core processes, minimum qualification requirements, and the availability and management of resources.
You can’t pass an ISO audit by saying “we know how to do this.” You need it written down, versioned, and followed consistently.
5. Bus factor protection¶
The “bus factor” is a morbid but useful concept: how many people need to get hit by a bus before your business can’t function? If the answer is “one” - your PM, your vendor manager, you - that’s a single point of failure.
SOPs don’t eliminate the pain of losing a key team member. But they make sure the knowledge that person carried doesn’t leave with them. When your QA process is documented, it survives personnel changes. When your escalation procedure exists only in someone’s memory, it doesn’t.
The 8 SOPs Your Translation Agency Needs First¶
You don’t need to document everything on day one. Start with the eight processes that touch revenue, quality, and client satisfaction directly.
1. Intake and Quoting¶
This is where projects begin. The SOP covers: how you receive requests (email, form, portal), what information you collect (language pair, word count, deadline, subject matter, file format), how you calculate the quote (rate card, volume discounts, rush fees), and who approves it.
Why it matters: inconsistent quoting is one of the fastest ways to lose money or lose clients. If PM #1 quotes 0.12/word for a medical translation and PM #2 quotes 0.18/word for the same thing, you’ve got a problem.
2. Translator and Vendor Assignment¶
How do you decide which translator gets a project? The SOP should cover: matching criteria (language pair, specialization, availability, quality tier), how to check availability, what to do when your first choice isn’t available, and turnaround time expectations.
This ties directly to your vendor management system. Without a documented assignment process, you default to “whoever the PM knows” - which works until that PM leaves.
3. TEP Process (Translation, Editing, Proofreading)¶
This is the core of what you sell. The TEP workflow is also the backbone of ISO 17100 compliance. The standard mandates that every translation goes through at least two stages: translation and revision by a different person.
As iso17100.com explains the standard’s requirement:
Another person other than the translator revises the translation. Revision is defined as a bilingual examination of target language content against source language content for its suitability for the agreed purpose.
Your SOP should define: what the translator checks before submitting, what the editor/reviser checks (terminology, accuracy, completeness), what the proofreader checks (grammar, formatting, consistency), and how handoffs work between each stage.
4. Quality Assurance¶
QA goes beyond TEP. It includes: running automated checks (spell check, QA tools in your CAT tool), verifying formatting and tag integrity, checking terminology against glossaries and TMs, and sampling for spot-checks on larger projects.
Your QA SOP should also define what you measure and what thresholds trigger action. For concrete metrics to track, see our guide on KPIs for translation agencies.
5. Delivery and Client Feedback¶
How do you deliver the finished product? The SOP should cover: final file preparation (format conversion, cleanup), delivery method and channel, what to include in the delivery message (word count confirmation, notes on decisions made), and how to collect and process client feedback.
The feedback loop is critical. If you’re not systematically collecting client feedback and routing it back to translators, you’re missing the single most valuable source of quality improvement data.
6. Vendor Onboarding¶
When you bring on a new freelance translator, what’s the process? The SOP covers: where to source candidates, what qualifications to verify (degrees, certifications, experience), test translation procedure (what text, who evaluates, scoring criteria), NDA and contract signing, adding to your TMS/vendor database, and initial briefing on your style guides and processes.
A documented onboarding process means every translator goes through the same vetting - no shortcuts because “a colleague recommended them.”
7. Escalation and Issue Resolution¶
Things go wrong. A translator misses a deadline. A client rejects a translation. A file gets corrupted. Your escalation SOP defines: what counts as an escalation (severity levels), who gets notified at each level, response time expectations, how to communicate with the client during the issue, root cause analysis after resolution, and how to prevent recurrence.
Without this SOP, escalations get handled differently every time - some get over-communicated, some get swept under the rug, and nobody learns from either.
8. Billing and Freelancer Payments¶
Money is where mistakes hurt the most. The SOP covers: when and how you invoice clients, payment terms and follow-up for overdue invoices, how freelancers submit their invoices, payment schedules and methods, and how to handle disputes.
For a deeper dive into the financial side, check out our guide on cash flow management for translation agencies.
Prioritization: Where to Start¶
You can’t write eight SOPs in a week - not good ones, anyway. Here’s a priority order based on impact and urgency:
| Priority | SOP | Why First |
|---|---|---|
| 1 | Intake and Quoting | Directly affects revenue; inconsistency = lost money |
| 2 | TEP Process | Core service delivery; highest quality impact |
| 3 | Quality Assurance | Prevents costly rework and client complaints |
| 4 | Translator Assignment | Reduces bottlenecks and PM dependency |
| 5 | Escalation and Issue Resolution | Protects client relationships during failures |
| 6 | Delivery and Feedback | Closes the quality loop |
| 7 | Vendor Onboarding | Important for growth, less urgent day-to-day |
| 8 | Billing and Payments | Critical but often already semi-formalized |
Start with #1 and #2. Get those working, refined, and adopted by your team. Then move down the list. Trying to document everything at once leads to eight mediocre SOPs instead of two good ones.
How to Write SOPs Your Team Will Actually Use¶
The biggest risk with SOPs isn’t writing bad ones. It’s writing ones that nobody reads. Here’s how to avoid that.
The 7 Elements Every SOP Needs¶
Every SOP in your agency should include these seven elements:
- Name and ID - A clear, searchable title. “SOP-003: Project Intake and Quoting” not “How we handle new projects.”
- Scope - What this SOP covers and what it doesn’t. “This SOP applies to all new project requests received via email, web form, or direct client portal. It does not cover internal projects or test translations.”
- Owner - One person responsible for keeping this SOP current. Not a team - a name.
- Trigger - What event starts this process. “A new project request is received from a client or prospect.”
- Steps - The numbered sequence of actions. Each step should be concrete enough that someone new could follow it without asking questions.
- Checklists - Verification points within the process. What must be true before moving to the next step?
- Edge cases - What to do when things don’t fit the standard flow. “If the client requests a language pair we don’t cover…” or “If the deadline is under 4 hours…”
Example: Abbreviated Intake SOP¶
Here’s what a simplified intake SOP might look like:
SOP-001: Project Intake and Quoting Owner: Senior PM Trigger: New project request received
| Step | Action | Checklist |
|---|---|---|
| 1 | Log request in TMS within 2 hours of receipt | Source file attached? Language pair identified? |
| 2 | Analyze source files (word count, format, subject matter) | CAT tool analysis complete? Repetitions calculated? |
| 3 | Check for existing TM/glossary for this client | Client profile reviewed? Previous project notes checked? |
| 4 | Calculate quote using rate card + volume/complexity factors | Rush fee applied if deadline < 48h? Minimum fee met? |
| 5 | Send quote to client using template QT-01 | Quote includes: price, deadline, scope, T&C link? |
| 6 | If no response in 48h, send follow-up using template QT-02 | - |
| 7 | On approval, create project and trigger Assignment SOP | Project ID generated? Client confirmation saved? |
Edge cases: - Client requests a specialization we don’t cover - refer to partner agencies list, inform client of referral - Source files are scanned/image-based - add OCR step, adjust quote by +20-30% - Client requests certification/notarization - check country-specific requirements, add certification fee
This is about half a page. That’s all it takes. If your SOP is longer than 2-3 pages, you’re probably over-documenting.
Three SOP Formats: Which One to Use¶
Different processes work better in different formats. Here’s a comparison:
| Format | Best For | Pros | Cons |
|---|---|---|---|
| Step-by-step (numbered list) | Linear processes with clear sequence (intake, delivery) | Easy to write and follow; works in any tool | Doesn’t handle branching well |
| Flowchart | Decision-heavy processes (escalation, assignment) | Visual; great for complex branching | Harder to maintain; needs diagramming tools |
| Checklist | Verification processes (QA, pre-delivery check) | Quick to scan; hard to skip steps | Doesn’t explain how, only what |
Most agencies use a mix. Your TEP process might be a step-by-step with embedded checklists. Your escalation procedure might be a flowchart. Your pre-delivery check is definitely a checklist.
Where to Store SOPs¶
The single biggest killer of SOP adoption is accessibility. If your team has to dig through Google Drive folders or ask “where’s that document again?” - they won’t use it.
As Samantha Kasbrick writes about SOP management:
You start with good intentions - you’ve got your Google Docs, maybe a few PDFs, and a ‘SOPs’ folder buried somewhere in Drive - and before long, it’s a tangled mess no one can find or update.
The fix: store SOPs where your team already works. If you live in Notion, put them in Notion. If you use Confluence, put them there. The worst choice is the one nobody opens.
Tools for Creating and Maintaining SOPs¶
You don’t need a dedicated SOP tool to start. But as your agency grows, the right tool makes the difference between SOPs that live and SOPs that rot. Here’s a comparison of the most common options:
| Tool | Cost | Best For | Key Strength | Key Limitation |
|---|---|---|---|---|
| Google Docs | $0-6/user/mo | Solo founders, micro-agencies | Free, everyone knows it | No structure, version chaos at scale |
| Notion | $0-10/user/mo | Small-to-medium agencies | Flexible, good for wikis + SOPs | Not purpose-built for SOPs; can get messy |
| Confluence | $5.42+/user/mo | Agencies already using Atlassian | Strong search, permissions, templates | Steep learning curve; overkill for small teams |
| Process Street | $25+/user/mo | Agencies that need workflow automation | Checklists + automation built-in | Expensive for small teams; rigid structure |
| Waybook | ~$83/mo (flat) | Growing agencies focused on training | AI-assisted writing, training verification | Newer product; smaller ecosystem |
If you’re just starting out: Google Docs or Notion. Zero friction, zero cost. Write your first three SOPs there. You can migrate later when you’ve outgrown them.
If you’ve got 5+ people: Notion or Confluence. You need search, permissions, and some structure.
If SOPs are your competitive advantage (you’re ISO-certified, you’re scaling fast): Process Street or Waybook. The automation and tracking features justify the cost.
The tool matters far less than the habit. A team that updates Google Docs weekly beats a team that has Process Street and hasn’t logged in since January.
Common Mistakes When Creating SOPs¶
After helping translation agencies set up documentation, the same five mistakes come up again and again.
1. Writing SOPs “for yourself”¶
You know what “run QA” means. But does your new PM? Does the freelancer you’ll hire in six months? SOPs should be written for the person who doesn’t know anything about your company. Use concrete actions, not jargon. “Open MemoQ, run Verify > QA Checker with profile ‘Standard-EN’” not “do QA.”
2. Write once and forget¶
An SOP that was accurate 18 months ago might be actively harmful today - it describes a tool you no longer use, a step you’ve since removed, or a policy that’s changed.
As VisualSP recommends in their SOP guide:
Regularly review and update SOPs, ideally every 6-12 months, or whenever processes change.
If your SOPs don’t have a review date and an owner responsible for updates, they’re already decaying.
3. Over-documenting¶
Not every process needs an SOP. If only one person does it, if it changes weekly, or if it’s genuinely simple enough to explain in a Slack message - don’t create an SOP for it. Over-documentation creates noise that drowns out the important procedures.
A good rule of thumb: if a process involves more than one person, happens more than once a month, and would cause problems if done incorrectly - it deserves an SOP. Otherwise, it probably doesn’t.
4. Ignoring edge cases¶
The standard flow is easy to document. It’s the exceptions that kill you. What happens when the client changes the deadline after the translator already started? What happens when a freelancer delivers late? What if the source file is corrupted?
Your SOP doesn’t need to cover every possible edge case. But it should cover the ones that happen at least once a quarter. Check your email for the last six months - what situations caused confusion or required you to intervene personally? Those are your edge cases.
5. No metrics¶
How do you know if your SOP is working? If you don’t track anything, you don’t. At minimum, track: how often the process completes without escalation, average completion time, and error rate (client complaints, rework requests).
If your intake SOP takes an average of 4 hours from request to quote sent, and your industry benchmark is 2 hours - you know where to focus improvement efforts.
SOP Review and Maintenance: The Process for Your Processes¶
SOPs aren’t finished when you publish them. They need their own maintenance cycle. Here’s a practical framework:
Monthly: Collect Feedback¶
At the end of each month, ask your team two questions: - “Which SOP did you find confusing or incomplete this month?” - “Did you have to deviate from any SOP? Why?”
Keep a simple log. This is your raw material for updates.
Every 6 Months: Full Review¶
Twice a year, the SOP owner reviews each document against reality. Questions to ask: - Are all the tools/systems mentioned still in use? - Have any steps been added or removed in practice? - Are the checklists still relevant? - Has the team grown or changed in a way that affects the process?
Update the SOP, bump the version number, and notify the team.
Immediately: When Tools or Policies Change¶
If you switch from MemoQ to Trados, your TEP SOP needs updating that day - not at the next scheduled review. If you add a new language pair with different QA requirements, update the QA SOP now.
The rule: any change to tools, team structure, or client requirements triggers an SOP review for affected procedures.
Versioning¶
Keep it simple. Use “v1.0, v1.1, v2.0” or date-based versioning (“2026-04-27”). What matters is that everyone knows which version is current and can see what changed. Most wiki tools (Notion, Confluence) handle this automatically with page history.
SOPs and Your Bigger Business Strategy¶
SOPs don’t exist in a vacuum. They’re the operational backbone that supports everything else in your business.
Business plan: Your translation agency business plan describes what you want to build. SOPs describe how you’ll actually run it day to day. Investors and partners take you more seriously when you can show documented processes, not just projections.
Scaling: When you’re growing from solo freelancer to LSP, SOPs are what allow you to delegate without losing quality. You can’t hire a PM into chaos and expect them to figure it out. You hand them your SOPs and say “this is how we work.”
ISO certification: If ISO 17100 certification is on your roadmap, SOPs are literally a prerequisite. The certification audit will ask to see your documented procedures for translation, revision, project management, and vendor qualification. Starting your SOP documentation now means you’re already halfway to certification.
KPIs and improvement: You can’t improve what you don’t measure, and you can’t measure what isn’t defined. SOPs give you baseline processes to measure against. Your agency KPIs become meaningful when they’re connected to documented workflows - you can see exactly where bottlenecks happen and which step needs optimization.
The connection works both ways: your business strategy tells you which SOPs to prioritize, and your SOPs generate the operational data that informs your strategy.
FAQ¶
How long does it take to create one SOP for a translation agency?¶
For a core process like intake or TEP, expect to spend 4-8 hours on the first version. That includes mapping the current process (often by interviewing the people who do it), writing it up, having someone else test-follow it, and revising based on their feedback. Simpler processes (pre-delivery checklist, invoice submission) can be done in 1-2 hours. The first SOP always takes the longest because you’re also establishing your format and template.
Should I write SOPs in English if my team speaks another language?¶
Write them in the language your team actually works in. If you’ve got a mixed team - some German-speaking, some Ukrainian-speaking - write the primary version in your company’s working language and translate the key sections. The goal is comprehension, not elegance. An SOP that half your team can’t comfortably read is worse than no SOP at all. If you’re preparing for ISO 17100 certification, check with your auditor whether they need English versions.
Which SOPs are required for ISO 17100 certification?¶
ISO 17100 doesn’t prescribe a specific list of SOP titles, but it requires documented procedures for: translation project management (including client communication and requirements analysis), translator and reviser qualification and selection, the translation and revision process itself, handling client feedback and complaints, and competence verification for linguists. In practice, this maps to at least five of the eight SOPs described in this article: Intake, Assignment, TEP, QA, and Delivery/Feedback.
Can you use AI to write SOPs for a translation agency?¶
AI (ChatGPT, Claude, etc.) can give you a solid first draft and help you structure your thoughts. But it can’t tell you how your agency actually works. The value of an SOP is in the specifics: your tools, your rates, your escalation contacts, your edge cases. Use AI to generate a template or outline, then fill in the real details yourself. Also, have the person who actually does the work review the AI draft - they’ll catch the steps that the AI invented that don’t match reality.
How many SOPs does a small translation agency need?¶
A micro-agency (1-3 people, under $15K/month revenue) can function well with 3-5 core SOPs: intake/quoting, TEP process, QA checklist, delivery, and maybe vendor onboarding if you’re working with freelancers. As you grow past 5 people or $30K/month, you’ll need the full set of 8-10 SOPs covering escalation, billing, and more specialized workflows. Don’t create SOPs for processes that don’t exist yet - document what you actually do today, then add new ones as new processes emerge.
How do you get your team to actually follow SOPs?¶
Three things make the difference. First, involve your team in writing the SOPs - people follow processes they helped create, not ones handed down from above. Second, make SOPs easy to find - if they’re buried in a folder nobody opens, they’re dead. Put them where your team already works (your project management tool, your internal wiki, your TMS). Third, use SOPs during onboarding and training, not just as reference documents. When every new team member learns by following SOPs from day one, it becomes the culture, not an afterthought.