- Industry
- Insure AI
- Department
- Content
- Team
- Content Production
- Kind
- Assistant
- Approver
- Compliance Officer
- Code
- CON-06
It adapts policy documents, claims guides and marketing pages for the insurer's other markets and languages, using the translation memory for defined terms and keeping each market's own regulatory disclosures. It sends anything with legal effect, such as a policy wording or a key facts document, for native legal review before release.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the document and correspondence system: the translation memory, termbase and each target market's mandatory disclosures and complaint wording..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Compliance Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the document and correspondence system: it saves each locale's version as a draft linked to the source document. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The approved locales, the translation memory and termbase for insurance terms, each market's mandatory disclosures and complaint-route wording, and the localisation style guides.
Reads from
the document and correspondence system: the translation memory, termbase and each target market's mandatory disclosures and complaint wording.
Acts in
the document and correspondence system: it saves each locale's version as a draft linked to the source document.
Hands back
A list with one entry per locale, each with locale, text, tm_reuse_percent, disclosures_replaced (a list), new_terms (a list), length_change_percent and needs_legal_review (true or false).
Asks a person when
The content is a policy wording, key facts document or complaint text, a market difference changes cover or price, or a term is missing from the termbase.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Locales it may produce | en-US, es-US, fr-CA, ar-AE, hi-IN | Comma-separated. Other locales are refused. |
| Translation memory match to reuse (%) | 85 | Segments at or above this match reuse the approved translation. |
| Transcreate marketing copy | On | When on, marketing lines are rewritten for the market instead of translated word for word. |
| Most text growth (%) | 30 | App and portal text growing more than this is shortened. |
| Legal documents need native legal review | On | When on, policy wordings, key facts and complaint text are held for a native-speaking legal reviewer. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Produce only en-US, es-US, fr-CA, ar-AE, hi-IN.
- Translate defined policy terms only from the termbase; never coin a new term for excess, sum insured or an exclusion.
- Replace the regulator, complaint route, cooling-off or free-look period and mandatory disclosures with the target market's own, never translate the source market's.
- Reuse translation memory at or above 85 percent match.
- When on is true, transcreate marketing copy, and keep app text within 30 percent growth.
- When on is true, hold policy wordings, key facts and complaint text for native legal review.
See the Localization Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.