Cross-Timezone Scheduling for Indian Consultants: A Practical Playbook
The IST-EST gap is 10.5 hours. Here is how Indian consultants and freelancers working with US and UK clients can schedule across timezones without the mental arithmetic.
If you are an Indian consultant or freelancer working with clients in the US or UK, you have done the timezone arithmetic so many times it is almost automatic. They say "let's do 2pm EST" and you immediately think: that is 12:30am IST. Which means you are either staying up late or asking them to move the call. Which means another round of back-and-forth.
The IST-EST gap — 10.5 hours in winter, 9.5 hours in summer — is the most persistent scheduling friction in the Indian professional services market. It is not going away. But it is manageable, and most people manage it worse than they need to.
This is a practical playbook: the overlap windows, the rules of thumb, the booking link mistakes that make things harder, and the email language that makes things easier.
The math: IST overlap windows with major timezones
Before anything else, it helps to know the actual numbers. These are the overlap windows between IST (UTC+5:30) and the timezones your clients are most likely to be in.
IST and US Eastern (EST/EDT):
- Winter (EST, UTC-5): IST is 10.5 hours ahead. A 9am–6pm EST workday corresponds to 7:30pm–4:30am IST.
- Summer (EDT, UTC-4): IST is 9.5 hours ahead. A 9am–6pm EDT workday corresponds to 6:30pm–3:30am IST.
- Practical overlap: 6:30pm–9pm IST (when the US East Coast is still in their afternoon). This is your window.
IST and US Pacific (PST/PDT):
- Winter (PST, UTC-8): IST is 13.5 hours ahead. A 9am–6pm PST workday corresponds to 10:30pm–7:30am IST.
- Summer (PDT, UTC-7): IST is 12.5 hours ahead. A 9am–6pm PDT workday corresponds to 9:30pm–6:30am IST.
- Practical overlap: 9pm–11pm IST (when the US West Coast is in their morning). Tight, but workable.
IST and UK (GMT/BST):
- Winter (GMT, UTC+0): IST is 5.5 hours ahead. A 9am–6pm GMT workday corresponds to 2:30pm–11:30pm IST.
- Summer (BST, UTC+1): IST is 4.5 hours ahead. A 9am–6pm BST workday corresponds to 1:30pm–10:30pm IST.
- Practical overlap: 2:30pm–6pm IST (afternoon IST, morning UK). Comfortable.
IST and Australia Eastern (AEST/AEDT):
- Winter (AEST, UTC+10): IST is 4.5 hours behind. A 9am–6pm AEST workday corresponds to 4:30am–1:30pm IST.
- Summer (AEDT, UTC+11): IST is 5.5 hours behind. A 9am–6pm AEDT workday corresponds to 3:30am–12:30pm IST.
- Practical overlap: 9am–1:30pm IST (morning IST, afternoon Australia). Also comfortable.
The hardest timezone to work with is US Pacific. The overlap window is genuinely small, and it requires late evenings on the Indian side. If you have Pacific Coast clients, set expectations early about your availability window.
The IST evening rule
For US clients — which is the most common case — the practical rule is simple: 7pm–10pm IST is your sweet spot.
Here is why:
- 7pm IST is 8:30am EST / 5:30am PST. East Coast clients are starting their day. West Coast clients are early risers who can make this work.
- 9pm IST is 10:30am EST / 7:30am PST. This is the most comfortable window for both sides — mid-morning for the US, manageable evening for India.
- 10pm IST is 11:30am EST / 8:30am PST. Still reasonable, though later evenings start to feel like a sacrifice.
Beyond 10pm IST, you are asking yourself to work at midnight or later. That is sustainable for occasional calls but not as a regular pattern.
The implication for your booking page: if you work with US clients, set your available slots to 7pm–10pm IST. Do not offer your full working day — that will result in clients booking 9am IST calls that are 10:30pm EST, which works for neither of you.
For UK clients, your afternoon (2pm–6pm IST) is their morning. This is a much more comfortable overlap and does not require any evening sacrifice on your part.
The booking link mistake that makes everything harder
The most common timezone mistake Indian consultants make with scheduling tools is not setting their timezone correctly on their booking page.
Here is what happens: you set up a booking page, configure your availability as 9am–6pm, and share the link. A US client opens it and sees slots in their local time — but if your tool is not handling timezone conversion correctly, they might see your IST slots displayed as if they were EST slots. They book "9am" thinking it is 9am their time. You get a booking for 9am IST, which is 10:30pm EST for them. Nobody shows up.
Or the reverse: your tool converts correctly, but you have not thought about which slots make sense for cross-timezone clients. You offer 9am–6pm IST, which converts to 10:30pm–7:30am EST. Your US client sees only late-night and early-morning slots. They cannot book anything reasonable.
The fix is to create a separate event type for cross-timezone clients, with availability set to your IST evening window (7pm–10pm IST). When a US client opens this link, they see it in their local time — 8:30am–11:30am EST — and can book a normal morning slot. You get an evening call. Everyone is happy.
A good scheduling tool handles the host-timezone vs invitee-timezone logic automatically: it stores your availability in your timezone, displays it to the invitee in their timezone, and sends confirmations with both timezones clearly stated. If your current tool does not do this, that is the source of most of your timezone confusion.
How Kaien handles this automatically
Kaien's booking pages detect the invitee's timezone from their browser and display your availability in their local time. The confirmation email shows the meeting time in both timezones — yours and theirs — so there is no ambiguity.
You set your availability in IST. A client in New York opens your link and sees it in EST. A client in London sees it in GMT. The same booking page works for all of them without any configuration on your part.
You can also create separate event types for different client geographies — a "US client call" event type with 7pm–10pm IST availability, and a "UK client call" event type with 2pm–6pm IST availability. Each link shows the right slots for the right audience.
This is the core of what a scheduling tool should do for cross-timezone work. If you are currently managing this manually — converting times in your head, specifying timezones in every email — a tool that handles it automatically is worth the switch. See the homepage for more on how Kaien works, or the coaches and consultants page and freelancers page for audience-specific detail.
Email language that works
Even with a good booking tool, the email you send alongside the link matters. Here are phrasings that work for cross-timezone scheduling:
The transparent approach:
"I'm based in India (IST). To save us both the timezone maths, here's a booking link that'll show my availability in your local time — just pick what works for you: [link]"
This is the most effective framing. You are being transparent about your location, explaining why the link is useful, and making it easy for them to act. Most clients appreciate the clarity.
The availability-first approach:
"I'm free Tuesday and Wednesday evenings IST — that's Tuesday and Wednesday morning your time. Here's a link if you'd like to pick a specific slot: [link]"
This works well when you want to signal your availability window without making the client do the conversion. You are doing the work for them.
The async-first approach:
"Given the timezone difference, I find it easiest to use a booking link — it handles the conversion automatically. Here's mine: [link]. If none of the slots work, just reply with a few times that suit you and I'll convert."
This acknowledges the timezone challenge directly and offers a fallback. It is particularly good for clients who are not comfortable with booking tools.
What to avoid:
- Specifying times in only one timezone ("I'm free at 8pm") without clarifying which timezone. Always say "8pm IST" or "8pm your time."
- Sending a link without any context. A bare link with no explanation feels impersonal and can be confusing for clients who have not used scheduling tools before.
- Offering your full IST working day to US clients. They will see only late-night slots and assume you are unavailable.
When to use video vs async
Not every cross-timezone interaction needs to be a live call. For Indian consultants working with US and UK clients, the timezone gap is actually an argument for more async communication, not less.
Use a live call when:
- You are in the early stages of a client relationship and need to build rapport
- The topic is complex enough that real-time back-and-forth is genuinely more efficient than written exchange
- There is a decision to be made that requires both parties to be present
- The client specifically prefers calls
Use async when:
- You are providing an update, a deliverable, or a status report
- The question has a clear answer that does not require discussion
- The timezone gap makes scheduling a call genuinely inconvenient for one or both parties
- You want to give the other person time to think before responding
The practical implication: not every "can we get on a call?" request needs to result in a call. A well-written email or a Loom video often serves the same purpose with less scheduling friction. Reserve live calls for situations where they are genuinely more valuable than the alternatives.
When you do need a live call, the booking link handles the scheduling. When you do not, async saves everyone the timezone arithmetic entirely.
Conclusion
Cross-timezone scheduling is a solvable problem. The IST-EST gap is real, but the 7pm–10pm IST window gives you a workable overlap with US East Coast clients, and the afternoon window works well for UK clients.
The practical steps:
- Know your overlap windows and set your booking page availability accordingly — do not offer your full IST working day to US clients.
- Use a scheduling tool that handles timezone conversion automatically, so your clients see your availability in their local time.
- Create separate event types for different client geographies if your availability windows differ.
- Use the email phrasings above to introduce your booking link in a way that explains the timezone logic.
- Default to async for updates and status reports; reserve live calls for situations where they are genuinely more valuable.
The timezone gap is not going away. But with the right setup, it stops being a source of confusion and becomes just a fact of how you work.
IST offset figures are approximate and vary with daylight saving time changes in the US, UK, and Australia. IST does not observe daylight saving time.