Project scope
We handle business, technical, legal, marketing and personal documents. For interpreting, provide the date, location, format and subject. Language direction, staffing and timing are confirmed after reviewing the brief.
Language and regional requirements
Business communication, product interfaces and consumer-facing content call for different levels of formality. Include the relationship between speakers, screen context or reader background.
Delivery and review
Share the source, reference translations, terminology and target format. Agreed checks cover names, figures, units, formatting and completeness. Recurring projects can retain terminology and version records.
Agree the language variety and naming rules
- Provide speaker relationships and UI functions to align levels of politeness; confirm company names, katakana loanwords, model codes and established character names separately.
- For ambiguous short phrases, provide surrounding sentences, screen context or a subject definition rather than asking for a choice from an isolated word.
A ready-to-use enquiry checklist
- Source → target language, target country or locale, readers and specific use.
- Representative source files, volume and formats; identify typesetting, stamps or system import requirements.
- Organization/product names, terminology references, open questions, review window and intended use date; for interpreting add time, place and format.
Confirm the document type and language direction
The same language has different specialist requirements. Contract obligations, manual specifications and personal-record names need the relevant review criteria. Agree shared terminology and language-specific delivery lists for multilingual work.