A project manager needs to explain a delayed sample to a homeowner who prefers another language. AI can draft the translation, but the manager still needs to know whether it preserves the distinction between a sample arriving, a finish being approved, and an order being placed.

Datum recommends starting with routine client updates that a qualified bilingual reviewer can check. Give the assistant a clear source message and a small, reviewed terminology list. Keep the original and translated versions together until the reviewer confirms that the client will receive the same facts, requests, and commitments.

Resolve unclear wording before translating it

Write the source message as though a new employee must act on it. Replace internal shorthand, identify which product you mean, and state who needs to answer. If “next Friday” could refer to different dates, have the project manager confirm the intended date before translation. Do not ask the assistant to guess.

Use the client’s stated language preference. Do not infer it from a name or address. Choose an AI environment your company has approved for client information, and supply only the details needed for this message.

Separate the customer-facing message from instructions to the assistant. For example, an internal note asking the translator to flag uncertainty should remain outside the text that staff might copy into an email.

Build a terminology list around the actual message

Google Cloud’s current Translation documentation describes glossaries as custom dictionaries for domain-specific terms. Its examples include keeping product names unchanged and choosing the intended meaning of an ambiguous word. It also documents limits: some terms are ignored as stopwords, and matches are case sensitive by default.

That documentation describes a particular Google Cloud feature. A glossary pasted into a general AI chat is an instruction to the model, with no assurance that it will behave like that feature. In either case, review the resulting message.

For a remodeling update, Datum suggests having a bilingual reviewer establish preferred wording for the terms that affect the client’s next decision. Include enough context to distinguish a physical finish sample from a finished installation. Keep manufacturer names, model numbers, and finish codes in their original form so the client can match them to the selection record.

  • Term and meaning: what the phrase means in this project, with a sentence showing its use.
  • Reviewed translation: the wording approved for this language and audience, or an explicit unresolved question.
  • Exact identifiers: names and codes that must remain unchanged.
  • Review record: who checked the terminology, when, and which version was used for the message.

Check the decision the client is being asked to make

Consider this hypothetical source message: “The supplier expects the finish sample to arrive on October 12. Please review it before approving the finish. We have not placed the cabinet order.” The translation must retain the expected date, the request to review a sample, and the fact that the order has not been placed.

A smooth sentence saying the cabinets will arrive on October 12 would change both the object and the certainty of the message. A version that drops the final sentence could also leave the client with a different understanding of the project’s status. These are review cases, not observed results from a translation test.

Have the reviewer compare each sentence with the original. Ask them to identify the product, the date and its level of certainty, the requested response, and anything explicitly not yet approved or ordered. Then ask whether the wording is natural for the client. Accurate details and readable language both belong in the review.

Translating the draft back into the original language may help staff notice a discrepancy. Datum would not use that step as the sole release check: the person sending the message needs a review of the actual words the client will read. If nobody qualified can check them, arrange language support before sending consequential project instructions.

Test with past messages before making it routine

Choose redacted client updates whose intended meaning your project manager can explain. Include a tentative delivery date, an unapproved selection, and a message containing similar product names. Have a bilingual reviewer assess the drafts without relying on the assistant’s own claim that they are accurate.

Record omissions, changed commitments, altered identifiers, and the time needed to correct each draft. Keep natural wording corrections separate from errors that could change a client’s decision. Save the corrected examples and terminology for the next trial; do not treat this proposed test as evidence that your process already works.

When a reviewed message is sent, retain its source, translation, and reviewer record with the project correspondence. Route the client’s reply through the same language review where needed. A translated reply should enter the normal selection or approval process before anyone treats it as authority to order.

Bring a redacted client update and an example of wording your team finds hard to translate to a conversation with Adam. Datum’s Training work helps your own staff build and check AI tools around tasks they understand.

Sources Read

Next step, if this note maps to a problem on your desk: book a conversation with Adam. Thirty minutes, weekday evenings, Eastern time.

Related Field Notes