Route complex language briefs through one accountable desk.
Send the language list, files, deadline, and controls. The DD desk routes coverage, names sourcing risk, assigns one program manager, and returns a scoped delivery path.
- Coverage desk
- 250+-language index checked before scope lock
- Desk owner
- 1 PM coordinates sourcing, QA, cadence, and handoff
- Evidence
- QA log, edit history, glossary delta, and compliance summary on request
Four ways teams enter this desk.
Briefs land for one of four reasons. Pick the lane that matches yours and see the relevant coverage, format, and lead time before sending a brief.
Rare or under-served language pair
Cover a pair your current vendor cannot deliver — which means fewer stalled RFQs and a sourcing window named in the written scope.
Multi-language programFive or more pairs, one coordination point
Replace five vendor relationships with one accountable PM, which means one batched delivery, one invoice, and one QA log format.
LSP overflowDelivery capacity for established LSP partners
Your brand, our delivery — which means white-label overflow and rare-pair sourcing without exposing your end client.
Compliance-sensitiveDocumented controls, audit-ready QA log
ISO-scoped delivery, NDA on engagement, per-batch QA log — which means fewer audit gaps and faster procurement sign-off.
Five regions. 250+ languages. Every major writing system.
Coverage indicators reflect active sourcing across regional desks. Rare-pair availability is sourced on demand and confirmed in scope return.
Navajo, Haitian Creole, Nahuatl
Quechua, Guarani, Aymara
Romani, Sami, Kashubian
Tigrinya, Wolof, Hausa, Oromo
Meitei, Dari, Karen, Sylheti
Thirty rare languages, by status and script.
A sample of pairs teams have brought to this desk in the last 18 months. Active = on the DD roster after intake review. On-request = sourced from vetted bench, with lead time confirmed before scope lock.
| Language | Region | Script | Status |
|---|---|---|---|
| Tigrinya | Eritrea / N. Ethiopia | Geʽez | Active |
| Amharic | Ethiopia | Geʽez | Active |
| Oromo | Ethiopia / Kenya | Latin / Geʽez | Active |
| Somali | Horn of Africa | Latin | Active |
| Wolof | Senegal / Gambia | Latin | Active |
| Hausa | W. Africa | Latin | Active |
| Fula (Pulaar) | Sahel belt | Latin / Adlam | Active |
| Yoruba | Nigeria / Benin | Latin | Active |
| Igbo | S.E. Nigeria | Latin | Active |
| Bambara | Mali | Latin / N'Ko | On-request |
| Mandinka | W. Africa | Latin / N'Ko | On-request |
| Tamazight | Morocco / Algeria | Tifinagh / Latin | On-request |
| Pashto | Afghanistan / Pakistan | Perso-Arabic | Active |
| Dari | Afghanistan | Perso-Arabic | Active |
| Uzbek | Central Asia | Latin / Cyrillic | Active |
| Kazakh | Central Asia | Cyrillic / Latin | Active |
| Kyrgyz | Central Asia | Cyrillic | On-request |
| Turkmen | Central Asia | Latin | On-request |
| Karen | Myanmar / Thailand | Burmese-derived | Active |
| Karenni / Kayah | Myanmar | Burmese-derived | On-request |
| Burmese | Myanmar | Burmese | Active |
| Rohingya | Myanmar diaspora | Hanifi Rohingya | On-request |
| Meitei (Manipuri) | Manipur | Meitei Mayek | Active |
| Sylheti | Bangladesh / Assam | Bengali / Sylheti N. | Active |
| Chin (Hakha) | Myanmar / India | Latin | On-request |
| Hmong (White/Green) | SE Asia diaspora | RPA Latin | Active |
| Quechua | Andes | Latin | Active |
| K'iche' | Guatemala | Latin | On-request |
| Haitian Creole | Haiti / diaspora | Latin | Active |
| Navajo (Diné) | U.S. Southwest | Latin | On-request |
Ask about a language not on this list
Sourcing status · How the desk names a pair's readiness
- Active bench
- Languages with verified DD linguists or interpreters available within standard turnaround. Status shows as Active on the matrix above. Scope return names the lead time before any session or document moves.
- Vetted network
- Pairs not on active bench but available via DD's screened freelance partners. Lead time is named in the scope return, along with credential evidence on file for the assigned linguist or interpreter.
- On-request
- Rare pairs that require fresh sourcing before scope lock. The brief reply names the sourcing window, any credential or compliance constraint, and a written risk note on availability. No assumption of bench depth until a candidate is on file.
Deliverable · Format handoff
Format handoff is named in the scope return. DD lists the source-file types accepted, the output formats produced, file-naming conventions, and any QA log or compliance evidence shipped alongside the deliverable, which means procurement and audit teams see a documented engagement contract rather than guessing at scope after delivery. Format handoff is not a separate billable line — it is the engagement's documentation contract, so that downstream review never blocks payment.
What we deliver, organized by desk.
Each desk has a named lead and a standing roster. One DD program manager coordinates across desks when a program spans more than one.
AI Data Services
Multilingual annotation, GenAI evaluation, speech transcription, data collection. Domain-tested annotators matched to data type; structured QA on every batch.
Translation
Human translation across rare and high-volume pairs. Terminology built from scratch where no glossary exists. White-label delivery for LSP overflow.
Localization
Software, web, and marketing localization with multilingual rollout coordination. RTL, CJK, and complex-script handling. TMS integration with Phrase, XTM, MemoQ, Smartcat.
Interpretation
OPI, VRI, and on-site interpretation for legal, medical, and government settings. Contingency planning is scoped where the session needs it.
Multimedia
Subtitling, dubbing, voice-over, transcription for media platforms and enterprise content. SDH captioning, audio description, multi-format coordination.
How a program moves through this office.
Six checkpoints from intake to close. Timing markers below reflect a typical 4-week program; rare-language sourcing or compliance-heavy work extends the early phases and is scoped explicitly on intake.
Your current vendor vs this desk, by line item.
Most teams reach Dynamic Dialects after hitting a specific gap with an existing LSP. Below is the line-item read on where the gaps usually sit.
| Your current vendor | Dynamic Dialects | Why it matters | |
|---|---|---|---|
| Uncommon pair availability | Many rosters concentrate on ~40 high-volume pairs; uncommon pairs often require extended sourcing | 250+ languages on active or vetted-bench rosters; uncommon pairs scoped with sourcing lead time named explicitly | Refugee, indigenous, and small-diaspora communities are not served through standard rosters. |
| Scope-and-quote turnaround | Typical scope follows an intake form and a discovery call | Scope returned after one-page brief review; no discovery call before scope | Compressed timelines (regulatory deadlines, public-safety releases) rarely survive a multi-step sales cycle. |
| White-label / overflow | Co-branding or named-subcontractor disclosure is the more common arrangement | Deliverables, communications, and outputs carry your brand; subcontractor disclosure coordinated per your client agreements and applicable ISO traceability | When you're already in a client relationship, overflow capacity needs to align with your existing disclosure terms. |
| Multi-language coordination | One PM per language pair is common; cross-pair coordination falls to the client | One accountable PM coordinates linguists, QA, deadlines, and deliverables across all pairs in a program | A 12-language rollout shouldn't require 12 separate vendor relationships. |
| Documentation deliverables | Translated files; QA log and edit history typically scoped as an add-on or omitted | QA log, edit history, glossary delta, and a compliance summary mapping to applicable ISO clauses on request | Procurement, legal, and audit teams need provenance, not just deliverables. |
| ISO scoping | ISO 17100 is common; 27001 and 9001 coverage varies by provider | ISO 9001:2015, 27001:2022, and 17100:2015 are all active; scope return names which standard applies to which deliverable | Compliance-sensitive work (healthcare, public sector, finance) typically requires all three standards together. |
What usually triggers a brief.
Five patterns account for most engagements that land here. They tend to surface during a quarterly program review, after a vendor RFQ comes back wrong, or in the week before a regulatory deadline.
- A current vendor cannot cover the language pair: particularly rare, indigenous, or refugee-resettlement languages.
- Timeline is compressed beyond standard vendor sourcing: multilingual launches, regulatory deadlines, public-safety releases.
- Multi-language rollout needs one coordination point: instead of routing through five separate LSPs.
- Compliance-sensitive work needs documented controls: ISO certifications, NDA coverage, audit-ready QA logs.
- Overflow support for LSP partners: white-label delivery without client-facing exposure.
What a one-page program brief looks like.
No sales-cycle form, no scoping call before a scope. Seven fields, sent by email or pasted into the form. We return a scope, timeline, sourcing plan, and risk notes after review.
- Program
- Customer-support knowledge base for a multilingual rollout at a refugee-resettlement nonprofit
- Languages
- Tigrinya · Pashto · Dari · Karen · Karenni · Rohingya · Burmese
- Source format
- 200 articles · ~85,000 source words · Notion export
- Volume
- ~640,000 target words (estimate, expansion factors applied per language)
- Deadline
- Rolling delivery over 8 weeks; active-roster languages (Pashto, Dari, Burmese, Tigrinya) within 21 days; on-request languages (Karenni, Rohingya) confirmed at scope lock
- Compliance
- NDA before scope; ISO 27001 controls applied; final QA pack required
- Notes
- Source written in plain English (Grade 8 reading level). Tone calibrated for newly-arrived caseworkers; preserve that register. Glossary not available; build from scratch.
What's documented, what's audited.
Quality management
ISO 9001:2015 across all service desks. Per-program QA gates documented in delivery logs.
Information security
ISO 27001:2022. NDA coverage applied before any linguist receives source material.
Translation services
ISO 17100:2015 for translation production. Reviewer step on every TEP engagement.
Documentation
QA log, change history, and compliance summary available on request after delivery.
What teams ask before sending a brief.
Questions we hear most often during scope conversations. If yours isn't here, send it in the brief and we'll answer in the scope return.
Can you cover a rare language pair on a short-deadline brief?
Active-roster languages may be viable after intake. Rare and on-demand languages (Tamazight, Bambara, Hanifi Rohingya, K'iche', etc.) require a sourcing window, with bench-depth verification before scope lock. We will tell you in the written scope return whether your pair is active or sourcing.
Do you sign an NDA before scope discussion?
Yes. Mutual NDA on engagement is standard; we'll countersign yours or send ours during intake. Linguists working on your program receive program-specific NDAs that bind to your source material before they see any content.
How does pricing work — per-word, per-hour, or project?
Translation, localization, and AI data work are typically per-word or per-unit with volume tiers. Interpretation is per-hour with minimums. Multimedia (subtitling, dubbing, voice-over) is per-minute of source duration. Project-based pricing available for sprints with defined scope. Scope and pricing are returned together in the written scope reply.
What does white-label delivery mean for LSP overflow?
Your client signs with you. We staff, produce, QA, and deliver under your brand. Deliverables, communications, and final outputs carry your identity. Subcontractor disclosure follows your client agreements and applicable ISO 17100 traceability requirements; we coordinate disclosure language in scope so your existing terms are honored. Used by LSP partners who hit a coverage gap, a capacity ceiling, or a request they can't fulfill internally.
Is ISO 17100 in scope for all services?
ISO 17100:2015 specifically governs translation production. It applies to our human translation and review work (TEP). It does not extend by definition to interpretation, AI data annotation, transcription, or evaluation; those operate under ISO 9001:2015 and ISO 27001:2022. We name which standard applies to which deliverable in scope.
Can you coordinate across five or more language pairs in one program?
Yes. This is the most common reason teams bring us in. A single DD program manager coordinates linguists, QA, deadlines, and deliverables across all pairs. You receive one batched delivery per cadence (rolling weekly, milestone-based, or final), one consolidated QA report, and one invoice, not five separate vendor relationships.
What does your QA documentation deliverable look like?
On request, every program ships with: per-batch QA log (reviewer, gate results, change counts), full edit-history file, glossary delta (terms added, terms changed), and a compliance summary mapping deliverables to applicable ISO clauses. Useful for audit prep, procurement sign-off, and downstream regulatory submissions.
How do you handle compliance escalations during a program?
Compliance-sensitive issues (data residency, source provenance, reviewer credentialing, regulated content) escalate to the DD program manager during intake or production review. We don't reassign without your sign-off. If we identify a compliance risk in your source material before delivery, we flag it in writing and pause production until you confirm direction.
Send a brief. Get a scoped reply from the desk.
Tell us the program, the languages, the volume, and the deadline. We return a scope, timeline, sourcing plan, and risk notes within intake review. No sales cycle to clear before we engage.
The desk
Dynamic Dialects
200 E Robinson Street, Suite 1120-H16
Orlando, FL 32801
Tel (407) 537-2522
Email info@dynamicdialects.com
Hours Mon–Fri · 8a–7p EST