Free to read · no account needed

12 min · writing

HK bilingual workday: English default, Chinese when needed

Goal: Switch Chinese/English without machine-translate voice—two passes plus a HK-reader feel; freeze proper nouns and numbers first.

Best for: Hong Kong (and bilingual) teams mailing in English by default, with Chinese for specific audiences.

Default to English for cross-team threads; switch to Chinese when the reader needs it—never mid-sentence salad. Two passes beat one-shot “Move between EN and ZH without machine-translation”

Why beginners skip this

Skipping the two-pass method and mashing ZH/EN feels like one less step—both readers suffer. Faithful translate first, then local voice.

Step 1 — Pick the day’s default language

Many HK workplaces default to English for cross-team mail; Chinese fits local partners—pick one language per thread.

  • Default EN: external multi-national threads, docs that will be searched later.
  • Switch to ZH: reader prefers Chinese; legal/consumer copy for local audience; WeChat/WhatsApp with local ops.
  • Keep product/UI proper nouns stable across languages.

Step 2 — Two passes (meaning, then local voice)

Pass A keeps meaning; Pass B drops machine-translation tone—do not do both in one shot.

Pass A — faithful
Translate / draft in [EN or ZH]. Keep meaning. Mark idioms you are unsure about with [?]. Do not marketize yet.

Pass B — local voice
Rewrite for [HK office peer / mainland partner / bilingual manager].
Natural phrasing; short sentences; keep legal names and numbers unchanged.
List 5 changes you made and why.
Avoid: stacked abstractions, fake 成语, and “empower/synergy” sludge in either language.
Example

Filled prompt

EN source: “Please cascade this initiative to relevant stakeholders ASAP.”
Pass A ZH (faithful, still stiff): “请尽快将此举措传达给相关干系人。”
Pass B ZH (local office): “请今天内把这件事同步给需要知情的同事，并回我已知晓。”
Why B wins: concrete timing, human “同事”, clear reply ask—no empty 举措/干系人 stack if your team does not talk that way.

What good output looks like

  • Matches outline/voice freeze for “Move between EN and ZH without machine-translation”
  • No AI-slop openers; one concrete proof from your notes
  • Numbers/names frozen — polish does not invent
  • Pass/fail: phone-skim 20s still clear

Step 3 — One real HK-shaped day

Take one mail you must send to Hong Kong readers today through translate, then localize.

09:30 EN mail to regional PM (facts freeze + polish in Claude/ChatGPT)
12:10 ZH WhatsApp to local venue vendor (Pass B: short, polite, one ask)
15:00 EN meeting notes → actions (no invented owners)
17:40 ZH internal note for mainland teammate: localize EN bullets, keep ticket IDs in EN

If a thread mixes languages messily, ask the model to produce two clean versions rather than one scrambled paragraph—see multilingual-without-muddy-mix.

Second scene: EN update → ZH for mainland teammate

Example

Filled prompt

Pass A: faithful ZH of EN bullets (keep ticket IDs ENG-104, ENG-110).
Pass B: for a mainland eng teammate on WeChat—short, plain 书面语, no HK slang, one ask: confirm freeze date.
List 5 wording changes.

What good output looks like

  • No AI-slop openers; one concrete proof from your notes
  • Numbers/names frozen — polish does not invent
  • Pass/fail: phone-skim 20s still clear
  • Matches outline/voice freeze for “Move between EN and ZH without machine-translation”
Example

Filled prompt

Live artifact this week for: Move between EN and ZH without machine-translation tone—using a two-pass habit and local r
Name real files/people. No invented facts; label Unknowns; stop before send/delete.
Return working prompt + one pass/fail check I can mark in a minute.

What good output looks like

  • Numbers/names frozen — polish does not invent
  • Matches outline/voice freeze for “Move between EN and ZH without machine-translation”
  • Pass/fail: phone-skim 20s still clear
  • No AI-slop openers; one concrete proof from your notes

Red flag

Translate without freezing facts; HK localize changing numbers—freeze first.

Save this card

Card: Freeze facts; translate meaning; then localize for HK readers. Keep this beside the tool; read before you start.

Before you start

Name the reader and freeze facts on paper for “Move between EN and ZH without.” If outline bullets do not exist yet, stop before prose. Guide: writing-bilingual-hk-workflow. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.

How to use this week

This week run a real draft through pass A faithful translate + pass B localize; check HK vs mainland wording separately.

Pitfalls

PitfallBetter
One-shot “translate to Chinese” sendPass A then Pass B; you skim B
Forcing Cantonese spellings in formal mailFormal written 白话 unless the channel is casual
Localizing legal terms creativelyKeep counsel-approved wording frozen
Assuming mainland readers want HK slangAsk audience; prefer clear 普通话书面语 when unsure
Example

Filled prompt

Temptation: skip the habit for writing-bilingual-hk-workflow to save five minutes.
Job still: Move between EN and ZH without
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.

What good output looks like

  • Names the shortcut refused (specific to writing-bilingual-hk-workflow)
  • Still delivers checkable output for “HK bilingual workday: English default,”
  • Unknowns labeled; draft-only
  • Pass/fail: refuse-line dated (writing-bilingual-hk-workflow #4)

Practice now

Particle check: one ZH particle/tone fix that EN cannot mirror (Asia/Shanghai).

Term bank: three terms locked EN↔ZH before drafting (Asia/Shanghai).

Tone bridge: one EN formal ↔ ZH polite pair for the same ask (Asia/Shanghai).

HK bilingual drill: one EN↔ZH pair; note what must stay local (names, tone) (Asia/Shanghai).

Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.

Tonight run a real draft through pass A faithful translate + pass B localize; check HK vs mainland wording separately.

Buffer line: name the artifact path you used (Asia/Shanghai).

Ship-check: artifact path ___ · refuse-line dated Asia/Shanghai ___ · never-do ___

Close the loop

Write one line: next time I skip the two-pass method and mash languages, I refuse send.

One sentence takeaway

Faithful translate first, then local voice; check HK vs mainland wording apart.

Next

Translate→localize · Multilingual · Email · Outline before prose

← Back to home · Learn · Tools · Compare · Start