The honest answer: Othello’s Bangkok bench operates engagement-tier in Thai ↔ English with trilingual desks for EN/TH/JP and EN/TH/DE only. Korean at engagement-tier — meaning under the full lockstep discipline (native pairing, structural rewrite, register matching, subject-matter routing, audit-trail) — is partner-routed through the credentialed regional partner network. The substantive scoping, sector-specialist routing, NDA discipline, termbase governance, QA cycle, and audit-trail consolidation run through the Bangkok bench. The engagement-tier production runs through partners under engagement-letter back-office scope.

Why this matters: vendor honesty is operationally important. Vendors that overclaim in-house capability and then sub-contract opaquely create downstream procurement-governance issues — undocumented sub-vendors, NDA chain breaks, terminology fragmentation, audit-trail gaps. Othello’s transparent positioning — scoping-direct, partner-routed, single engagement letter, single audit-trail at Bangkok — is validated by Big Law procurement, KEXIM-financed project boards, Korean EPC client-side matter teams, and SET-listed corporate procurement as a single-vendor engagement structure.

Korean EPC contractor matters are the flagship use case (Use Case 01 above). The substantive engagement footprint covers EPC contract bilingual production, FIDIC-aligned project documentation (Red Book, Yellow Book, Silver Book conventions where applicable), EPC variation orders, technical specifications, regulatory submissions to Thai ministries, completion documents (taking-over certificates, performance certificates), claims and disputes documentation. EN/TH/KR trilingual workflow under one engagement letter with the Bangkok bench managing source review and the credentialed Korean-engagement-tier partner handling substantive KR production.

Partner-side technical-vocabulary discipline is screening-tested at partner selection — Korean EPC industry-standard contractual vocabulary, power plant / refinery / petrochemical engineering terminology, KEPCO / KEPIC code references, FIDIC-Korean technical translation convention. Bangkok-side QA cycle verifies terminology consistency against the engagement-letter termbase. For Korean EPC client-side matter teams with Thai project deployment, the engagement model delivers single-vendor experience across the full project documentation cycle.

KEXIM project financing documentation is the second flagship use case (Use Case 02 above). The substantive cycle covers project finance loan agreements, security package documentation (mortgages, assignments, share pledges, account control agreements), conditions-precedent packages, drawdown documentation, KEXIM compliance certificates, ECA covered loan documentation, K-sure (Korea Trade Insurance Corporation) export credit insurance documentation, and cross-border legal opinion documentation.

Engagement-letter scope for KEXIM cycles typically bundles with Big Law cross-border Korea matters (Use Case 04) and Korean banking documentation (Use Case 06) under one engagement letter — the substantive matter team is usually the same Big Law cross-border practice. Privilege-protected matter-team-direct routing applies; NDA-from-first-email across the chain; engagement-letter audit-trail retains the substantive matter documentation. For KEXIM-financed Korean EPC projects in Thailand, the bundle is the substantive engagement structure.

The client signs one engagement letter with Othello International (Bangkok). The engagement letter records the substantive scope (use case, deliverable category, language combination EN/KR or TH/KR or EN/TH/KR trilingual), the partner-routing for engagement-tier production (named at engagement-letter execution where commercially appropriate), the NDA discipline (engagement-letter NDA from client to Othello + back-office sub-NDA from Othello to partner), the audit-trail retention (Bangkok-side), the deliverable cycle calendar, and the post-delivery support window.

The client does not sign a separate engagement letter with the engagement-tier partner — the partner relationship is back-office to Othello. The partner-side workflow is engagement-letter back-office: partner brief includes Bangkok-side termbase, register guidance, sector context, format conventions; partner produces engagement-tier KR content; partner-produced deliverable returns to Bangkok for QA; final sign-off issued through Othello to client. The single-vendor client experience is operationally preserved.

NDA from first email extends across the chain. Substantive content shared with Othello at first scoping triggers Othello’s NDA — the standard NDA-from-first-email discipline that applies to every channel. The engagement-letter NDA between client and Othello flows down to a back-office sub-NDA between Othello and the partner. The sub-NDA is engagement-letter-tier in confidentiality protection, with explicit alignment to client-side requirements (Big Law privilege framework, KEXIM project-board confidentiality framework, Korean EPC client-side confidentiality framework, SET-listed anti-corruption framework as applicable).

Privilege-disciplined matters (Big Law cross-border Korea M&A, attorney-client privileged content) operate under additional privilege-protection workflow with partner-side privilege training documented. The audit-trail records the NDA chain and the privilege framework alignment. The client’s confidentiality protection is engagement-letter-tier across the full engagement chain — not weaker because production is partner-routed.

The bilingual termbase governance extends to Korean for trilingual engagements. The Bangkok-side termbase includes EN/TH/KR-aligned terminology for substantive matter types — Thai capital markets terminology with KOSPI/KOSDAQ disclosure vocabulary equivalents, SET regulatory language with KRX listing rules terminology, Big Law legal terminology with Korean civil and commercial code, IFRS S2 framework vocabulary with K-ESG framework parallels, plus Korean EPC industry-standard contractual vocabulary (FIDIC-Korean translation conventions, KEXIM project financing terminology, KEPIC technical code references).

Operationally: the EN/TH side is produced in-house under bench discipline using the termbase directly. The KR side is partner-produced using the Bangkok-side termbase as the engagement brief reference. The QA cycle at stage 04 verifies KR-side consistency against the termbase. Termbase governance is Bangkok-side — partner-side production uses the termbase under engagement-letter scope, not the partner’s own termbase. This is operationally why trilingual deliverables ship with substantive terminology consistency across the three languages.

No. The Bangkok bench does not use consumer LLM endpoints (ChatGPT, Claude, Gemini, Naver HyperCLOVA consumer endpoints, etc.) for substantive client content processing. The partner network is screened on the same standard — partner selection includes documentation of partner-side data handling discipline, no consumer-AI endpoint retention, no third-party vendor handoff beyond Othello’s engagement chain, and Korean data sovereignty alignment under PIPA where applicable to the substantive matter type.

The discipline applies across the engagement chain. Engagement-letter NDA explicitly covers the in-house processing commitment for the Bangkok side and the engagement-letter sub-NDA covers the partner side. Thai PDPA (Personal Data Protection Act B.E. 2562), EU GDPR, and where applicable Korean PIPA (Personal Information Protection Act) data subject rights are observed for client content. This is one substantive verification dimension procurement evaluation panels test as part of vendor due diligence on partner-routed engagements.

Korean operates across multiple register tiers — similar in substantive structure to Thai. Formal-written (격식체 / haeyo-che written variant) for corporate documents and regulatory filings, highly formal / written-only (하십시오체 hasipsio-che) for government submissions and high-formality contractual documents, semi-formal-corporate for board minutes and internal communications, plus technical-legal register for legal documents. Mismatched register signals amateur work to Korean institutional readers — particularly to Korean chaebol corporate counsel and KEXIM project boards.

The partner-routed engagement-tier production applies register-tier matching to the substantive document type. Bangkok-side QA cycle at stage 04 verifies register-tier alignment against the engagement-letter scope. For Korean EPC contractor matters, the formal-written register applies; for KEXIM project board materials, the highly formal register applies; for Big Law contract documentation, technical-legal register applies. Register matching is operationally part of the engagement-letter discipline, not an after-the-fact stylistic concern.

Yes — this is the substantive Annual Programme bundle structure for EN/TH/KR trilingual clients. See How We Quote · Annual Programme for the substantive bundle documentation. The bundle records: EN/TH lockstep in-house deliverables across the 8 deliverable categories (see Thai-English Translation), KR partner-routed engagement-tier production for the trilingual deliverables, ESG advisory bundling if applicable (IFRS S2, GRI, AA1000AS, SET ESG, K-ESG parallel), and ad-hoc capability across the sector verticals.

Bundle benefits operationally: continuous termbase governance across EN/TH/KR within the bundle, bench-stability per engagement letter, audit-trail consolidation at Bangkok, one-NDA discipline (engagement-letter NDA + back-office sub-NDA), and indicative-pricing structure aligned to annual rather than per-deliverable scoping. For Korean EPC contractors with multi-year Thai project deployment, KEXIM-financed project sponsors, and Korean chaebol Thailand subsidiaries, the Annual Programme bundle is the substantive engagement structure.

Three pathways depending on procurement stage — see Contact · 4 Engagement Pathways for the substantive routing. Pre-RFP exploration: Pathway 02 · 30-minute scoping call with bench input on the partner-routing structure, scheduled within 2 BD of NDA execution. Formal RFP: Pathway 01 · capability brief request with named bench specialist match plus partner network capability disclosure plus anonymised case studies plus references at scoping tier within 3–5 BD under mutual NDA. Procurement evaluation: Pathway 03 · reference disclosure for procurement panel evaluation.

The substantive scoping intake covers: which of the 8 use case scenarios apply, which of the 6 sector verticals apply, language combination (EN/KR, TH/KR, or EN/TH/KR trilingual), substantive scope (deliverable count, page volume range, project cycle alignment for EPC/KEXIM matters, target timeline), and engagement structure (ad-hoc deliverable, programme-stage component, Annual Programme bundle). Engagement-tier NDA from first email means substantive scoping content exchange is protected from initial contact. Email [email protected] with subject prefix “Korean Translation —” or call +66 02-859-2145 during Bangkok office hours.