Async Communication and Time Zones: Working from IST

When your team is five to thirteen hours away, you cannot fix every problem with a quick call. That can feel like a disadvantage. Done well, it is the opposite: you get long, quiet stretches to do focused work, and the time-zone gap means work can move forward around the clock.

Know your time differences

India Standard Time is UTC+5:30 all year. The US, UK and most of Europe use daylight saving time, so the gap changes twice a year, and the US and Europe switch on different dates. Here are the usual differences for 9:00 am in each place:

• London: 9:00 am is 2:30 pm IST in winter (GMT) and 1:30 pm IST in summer (BST).
• Berlin, Paris, Amsterdam: 9:00 am is 1:30 pm IST in winter (CET) and 12:30 pm IST in summer (CEST).
• New York, Toronto: 9:00 am is 7:30 pm IST in winter (EST) and 6:30 pm IST in summer (EDT).
• San Francisco, Seattle: 9:00 am is 10:30 pm IST in winter (PST) and 9:30 pm IST in summer (PDT).

Plan the overlap

With European teams, your afternoon overlaps their morning, so there is usually a comfortable shared window. With the US East Coast, the overlap is your evening. With the US West Coast, it is late at night for you, and real-time overlap is limited unless someone shifts their day.

1. Agree on a fixed overlap window with your team, for example two hours a day, and keep it free for meetings and quick questions.
2. Use that window for things that genuinely need conversation: decisions with disagreement, sensitive feedback, brainstorming, onboarding.
3. Move everything else to writing: status updates, reviews, questions that can wait a few hours.
4. If the overlap is late in your day, shift your working day rather than adding hours. For example, start at noon and finish at 9 pm, instead of working 9 am to 10 pm.
5. Ask for meeting times to rotate if the whole team is spread out, so the same people are not always the ones staying up late.

Write updates people can act on

Your written update is often the only thing your manager sees of your day. A good one is short, specific and ends with anything you need from someone else. A simple structure that works for most teams:

• Done: what you finished, with links.
• Next: what you are working on next.
• Blocked: anything stopping you, and who can unblock it.
• Decisions needed: a specific question, the options, your recommendation, and when you need an answer.

Example (hypothetical): ‘Done: export feature merged and deployed to staging (link). Next: writing tests for the retry logic. Blocked: need production read access to check the failing job; requested from the platform team (link). Decision needed by your Thursday morning: should retries stop after 3 attempts or 5? I suggest 3, because each retry delays the customer’s report.’

Ask questions that get answered in one round

Across time zones, a vague question can cost a full day: you ask, they reply asking what you mean, you clarify, and a day has passed. Put everything in the first message:

1. Context: what you are working on and why it matters.
2. What you tried and what happened.
3. The specific question, ideally one they can answer with yes, no or a choice.
4. Your best guess at the answer, so they can just confirm it.
5. When you need it by, and what you will do in the meantime.

Documentation habits that save everyone time

• Write decisions down where the team can find them, with the date, the decision and the reason. A decision only spoken on a call is lost to anyone who missed it.
• Take short notes in shared meetings and post them where the team works, including action items with owners.
• At the end of your day, leave a handover note for anything someone in another time zone might need while you are offline.
• Keep READMEs, runbooks or process notes up to date when you change something.
• Prefer links to a single source over copying the same information into many chats.

Use the gap: handoffs

If you finish your day as a US colleague starts theirs, a good handoff means they can pick up exactly where you stopped, and their questions are waiting for you in the morning with answers. Make the handoff a habit: state what is ready for review, what is half-done and where, and the one thing you need from them before you are back online. Ask them to do the same for you. Teams that handle this well often find the time difference speeds work up rather than slowing it down.

Avoid burning out on late-night calls

The most common problem for people in India on US teams is not the work, it is the hours. A few late calls a week can quietly become a full office day followed by a full US day. Protect yourself early:

• Agree your working hours at the offer stage, in writing, in IST.
• Count late meetings as working time and finish earlier on those days.
• Decline or suggest recording for meetings where you are not essential. Offer to send written input in advance instead.
• Keep at least a few evenings a week completely free of calls.
• If on-call or urgent support across time zones is part of the role, ask how it is scheduled and compensated.
• Watch for sleep problems, irritability or constant tiredness. They are signs to renegotiate, not to push harder.

Setting boundaries without seeming unavailable

Boundaries work best when they are clear and predictable. Colleagues accept almost any reasonable schedule if they know what it is. Put your working hours in your chat profile and email signature, use status messages, and say when you will reply. For example: ‘I work 12:00 to 21:00 IST (6:30 to 15:30 UTC). Messages after that get a reply the next morning, my time. For anything urgent, call me.’

Then keep to it. Replying to messages at midnight once in a while is your choice; doing it every night trains everyone to expect it.