Service
Translation & Localisation Data in India
Human translation and parallel-corpus creation across Indian languages, built for machine-translation training and multilingual LLM evaluation rather than for publication.
- Turnaround
- 2-4 weeks for typical corpus volumes per language pair.
- Languages
- 14 Indian languages + Indian English
- Delivery
- Sentence-aligned parallel data
What you get
- Sentence-aligned parallel data
- Updated glossary
- Reviewer notes on ambiguous source
Technical specification
Every parameter below is written into the statement of work before recording begins. If your pipeline needs different values, they replace ours rather than being converted after delivery.
| Parameter | Standard |
|---|---|
| Direction | English to Indian languages and between Indian languages |
| Output | Sentence-aligned parallel corpora |
| Register | Formal, colloquial, or matched to your product tone |
| Review | Independent bilingual review pass |
| Terminology | Client glossary enforced and returned updated |
How the work runs
- Glossary and register agreement
- Translation by native speakers of the target language
- Independent bilingual review
- Alignment verification
- Delivery with terminology report
Quality control
Back-translation checks are run on a sample so you can see where source ambiguity, not translator error, causes divergence.
QA failures are remedied by re-collection, not by editing the delivered files. Repaired audio introduces artefacts that survive into your model.
Speaker and contributor sourcing
Translators are native in the target language and screened on domain samples.
Consent is captured per participant and mapped to file IDs, so provenance survives an external audit of your training data.
Timeline
2-4 weeks for typical corpus volumes per language pair.
Staged delivery is available: first batches ship while later batches are still recording, so training can start early.
The numbers we hold ourselves to
- 100% of delivered files pass automated technical QA for SNR, clipping, duration and silence
- 5-25% of files pass a second native-speaker content review, stratified by city, dialect and transcriber, and escalating to 100% on any batch that fails the agreed threshold
- Accepted yield runs 85-90% for scripted speech, 60-70% for spontaneous, 55-65% for conversational and 50-60% for telephony
- Default cohort quotas: 50/50 gender, with age bands at 30% (18-25), 40% (26-40) and 30% (41-60)
- 48 kHz / 24-bit capture, delivered as 16-bit PCM WAV, with studio sessions held below a -50 dBFS noise floor
- First response within one working day; a scoped, fixed quote within two to three
These are the figures a delivery is measured against, not aspirations. A batch that misses them is re-recorded at our cost rather than repaired.
Commonly used for
- MT training
- Multilingual LLM eval
- Product localisation data
Frequently asked
What is the minimum volume for translation?
Programmes typically start around 50 hours or equivalent units per language. Smaller pilots are accepted when they lead into a larger build, because most of the setup cost is in specification and recruitment rather than recording time.
Can you work to our schema instead of yours?
Yes. Manifest fields, file naming, directory structure and label schema are set by you. Working to your schema from the start avoids a conversion pass that usually loses metadata.
Who owns the delivered data?
You do. Deliverables come with a perpetual, transferable licence and participant consent that covers model training and distribution of the resulting model.
How is pricing structured?
Per delivered hour or per unit, quoted against a written specification. Quotas, recording conditions and QA thresholds all move the price, which is why we quote from a spec rather than from a price list.
Get a quote for translation & localisation data
Send the specification you already have, or the rough shape of it, and you get a scoped quote with a timeline.