Working across China and overseas teams: what to set up before you start

Before your first week in a China-based role that connects to colleagues in another region, settle four mechanics on your own: the hours you will deliberately share, which choices need a live conversation versus a written note, what record both sides can read without confusion, and how a task moves from you to someone asleep without waiting for you to wake. The sections below turn each into a checklist you can act on before anyone asks you to join a call.

Decide the overlap before you accept the meeting rhythm

When your base city and your teammates' city sit far apart, a casual "let's sync tomorrow" hides a real cost. Someone gives up a morning or an evening. Name that cost early, because the unspoken default usually falls on the person in the smaller group.

Write down the core working hours your employer expects in your location. Write down the core hours of the overseas group. Mark where they cross. If the crossing is under two hours, that slice is your only live window — guard it and push everything else into written form. If they do not cross at all, treat the relationship as fully asynchronous and design as if live meetings will rarely happen.

The trade-off is straightforward but easy to dodge: moving your own start time buys overlap but shortens your evening; asking the other side to move shortens theirs. Neither choice is wrong. What fails is leaving it unstated and letting quiet frustration build.

The exchange below is fictional, written only to show the method. It does not describe any real employer and is not a sample of how organizations in China handle scheduling.

Example: a worker in Shanghai notes their team expects the standard local office hours. An overseas group works a normal day in a zone seven hours behind. Their shift patterns leave part of the afternoon in Shanghai inside both teams' working day. The worker decides to keep that shared stretch free of deep-focus tasks and moves all other coordination to written updates.

Put each decision in the right channel

Not every question needs a meeting. Across time zones, live time is the scarce resource, so spend it on the items that genuinely need it and move the rest to writing.

Use a live conversation when: the path is unclear and you need to hear hesitation, the decision changes what several people will do next, or a relationship is new and trust is still forming. Use written form when: the answer is factual and checkable, the recipients sit in more than two time zones, or you need a record that survives the conversation.

A useful habit is to state the channel in the request itself. "I need a short call to choose between options A and B" tells the reader the stakes. "Please confirm the date in the thread" tells them a reply will do. This small clarity saves a round-trip that, across zones, can cost a full day.

Response-time expectations are part of the same choice. If the overseas side believes a message gets a prompt reply and you are asleep, the gap reads as silence. State your responsive window in writing: for instance, "I read messages twice a day, in the morning and mid-afternoon China time; anything urgent should say URGENT in the subject." This converts an invisible absence into a known schedule.

What to ask your manager before you start: which decisions are yours to make alone, which need sign-off from the overseas side, and which are made at a level above you. You cannot guess this from the org chart alone, and asking early prevents a wrong assumption that only surfaces weeks later.

Keep one written record both sides can use

A record only helps if the person who reads it at 2 a.m. in another country understands it without a translator or a colleague. The goal is not more writing; it is writing that travels.

Make each record answer four questions: what was decided, who owns the next step, when that step is due (with a time zone named), and where the background lives if someone needs it. A note that says "sorted with the EU team" fails all four. A note that says "Ship the export fix by 09:00 China time Thursday; Maria owns it; context in the shared spec" passes.

Language matters. If your teammates do not read Chinese, write the shared record in the working language of the team, not in the language of your local office. If local documents exist only in Chinese, add a short plain-language summary in the working language rather than assuming the other side will translate. This is a practical bridge, not a comment on anyone's skills.

Keep the record in one place everyone already opens, not in a personal file. The test is simple: if you were unavailable, could the overseas colleague find the status without messaging you? If the answer is no, the record is not shared yet.

Version awareness matters more across zones than in a single office, because people read the same page at different moments. Put the date and a short status word at the top — open, blocked, done — so a reader who opened it yesterday can tell at a glance whether anything moved. Resist rewriting history; add a new line instead. A thread that shows how a decision evolved is more useful than a clean page that hides it.

The template below is fictional, for demonstration only. It does not represent any real employer and is not a sample of China market practice.

Status note — fictional example: Decision: pause the migration until the test suite passes. Owner: you. Due: end of day Wednesday, China time. Background: see the test report in the shared space. Next check: overseas colleague reviews at their Thursday morning.

Run a handover that does not need you awake

The hardest part of a time-zone split is the moment a task leaves your day and enters the other side's night. If the handover depends on you being online to explain it, the whole system stalls for half a day.

Build the handover as a written packet, not a conversation. It should contain the current state in one line, the exact next action, the definition of done, and the one risk that would make the other person stop and wait rather than proceed. Anything the reader must ask you to understand is a gap in the packet.

A clean trade-off: writing a thorough packet takes focused time you could spend elsewhere, but it prevents a pre-dawn call that pulls you out of sleep and still leaves the other side blocked. Across weeks, the written packet scales; the early call does not.

Set a rule with the overseas side about what counts as "wait for me" versus "proceed and flag." New relationships tend to wait too much; mature ones proceed and flag. State the default up front so nobody guesses.

For genuinely urgent items that cannot wait for the packet, agree on a single escalation path — one named person and one channel — rather than broadcasting. A broadcast at 3 a.m. your time wakes everyone and trains the team to ignore alerts. A named escalation respects sleep and still moves fast.

What is out of your hands

Some things you cannot set by yourself, and pretending otherwise wastes energy. The company's choice of collaboration tools, a fixed all-hands time if leadership mandates it, and the contract terms that govern your role are decided above you. Your move is to learn them, not to redesign them on day one.

What you can check before you start: confirm with the employer which tools are standard, whether there is an existing norm for cross-region handovers, and who on the overseas side is your counterpart. These are reasonable questions for an accepted offer; you are not expected to know them already.

One caution worth stating plainly: local rules about working hours, rest, and cross-border data can differ from what you knew before. This article describes working method, not legal obligation. For anything that touches your contract, visa, or local compliance, confirm the current published stance with the employer or the relevant authority and treat their answer as the live version.

Pre-start checklist

• Write your local core hours and the overseas core hours; mark the overlap.
• Pick one live window and protect it; move the rest to writing.
• State your responsive window in writing so absence reads as schedule, not silence.
• Ask your manager which decisions are yours, which need overseas sign-off, and which are above your level.
• Choose a single shared space for records and test whether someone else can find status there without you.
• Write every record with: decision, owner, due time and zone, background link.
• Build handovers as written packets with state, next action, definition of done, and stop-and-wait risk.
• Agree on one escalation path for true emergencies instead of broadcasting.
• Ask the employer for the standard tools, the handover norm, and your overseas counterpart.
• For any contract, visa, or compliance question, get the current answer from the employer or authority rather than assuming.

Set these up before the first meeting and the China-based role stops feeling like a constant game of catch-up with a clock on the other side of the world.