When collaborating remotely across Lahore, Dubai, and London, the easiest mistake is not miscalculating a single time difference; it is mixing the meeting date, daylight saving time, work hours, and each participant’s personal schedule. Lahore uses Asia/Karachi, Dubai uses Asia/Dubai, and London switches between GMT and BST depending on the date. The same Taipei-time invitation can correspond to different local times in London in different months. This article offers a repeatable check before sending an invitation, on the meeting day, and when rescheduling. It does not guarantee that offices, transport, or internet services in any city will be available on a particular date.
Set the meeting date and participant cities first
Before creating a meeting, list each participant’s city rather than recording only a country. Lahore and other parts of Pakistan generally use the same time zone, but a colleague who is traveling may already be in Dubai, London, or another city. Ask everyone to confirm the city where they will actually be on the meeting date and the working hours they can accommodate. If someone is departing from or returning to the Lahore city page or Taipei, check both the origin and destination separately; do not apply a time-zone change during travel directly to a fixed office schedule.
Lock in the full date, including the year, before scheduling—for example, October 20, 2026—instead of writing only “next Tuesday.” Meetings near a month or year boundary or a daylight-saving change need especially clear dates. If team members use calendars with different regional settings, the organizer should create the event in one standard time zone first, then ask each invitee to check how it appears in their own calendar.
Use time-zone names instead of checking only the offset
In the meeting details, include the city, time-zone identifier, and local time together, for example: “Lahore 09:00 (Asia/Karachi), Dubai 10:00 (Asia/Dubai), London 06:00 (confirm GMT or BST for the date).” This is more durable than saying “Lahore is three hours ahead of London,” because London’s daylight-saving time changes the difference by date. Dubai generally does not observe daylight saving time, but still verify the time-zone data for the meeting date rather than copying a past conversion into a new invitation.
You can refer to the IANA Time Zone Database for city identifiers, then cross-check with timeanddate’s Lahore information and the corresponding Dubai and London pages. These sources provide background for checking; they do not mean the meeting platform, phone, or company calendar necessarily uses the same settings. The date and time shown in the invitation preview should be the final check.
Map shared working hours as an overlap window
Write down the available working hours in each of the three cities separately, then find the actual overlap. If the Lahore and Dubai teams can both work in the morning locally while London prefers morning through afternoon, the shared window may be narrow. Do not choose an hour simply because it looks neat on the clock. Put each city’s lunch break, commute, prayer time, caregiving duties, or nighttime limits in one table so the team can see which times are technically possible but unsuitable for regular use.
If there is not a long enough shared window, divide the work between a short live sync and asynchronous tasks. Use the live meeting only for issues that need an immediate decision; put the rest in a shared document with an owner and deadline. Rotating early starts or late finishes is fairer than always asking the same city to adjust. For quarterly meetings, alternate between a time that suits Lahore and one that suits London.
Include the date and local time in invitations and reminders
Put the topic and reference time zone in the invitation title. In the body, list the local time and date for all three cities, along with the meeting link. Do not rely on a time-zone conversion screenshot: it will not update when the meeting changes and may lead a phone notification to display another date. If there is a dial-in, slide rehearsal, or pre-meeting document deadline, list those times in the same format and state who is responsible for confirming them.
After sending the invitation, the organizer should open its preview from a participant’s perspective and check at least once whether the date crosses midnight, whether London uses the correct seasonal time, and whether each occurrence of a recurring meeting is correct. A reminder can repeat the three cities’ times the day before, but it does not replace complete details in the original invitation. If the team uses different calendar services, ask everyone to confirm the date and time they received, not just to say “got it.”
Plan for date changes, daylight saving, and rescheduling
When London enters or leaves daylight saving time, recalculate the entire meeting series instead of changing only the first session. Lahore and Dubai may keep the same clock times while London’s date or time changes. If the meeting falls late at night in Lahore, at midnight in Dubai, or early in the morning in London, discuss switching to an asynchronous update first. When a meeting crosses midnight, write “the previous day” or “the next day” and include the complete date.
If someone has to travel unexpectedly, there is a power outage, or the internet is unstable, decide in advance what order to use for cancellation, recording, written updates, and rescheduling. Creating a new event when rescheduling can make the audit trail clearer than dragging the old event, but either way, check the date in all three cities again. Do not turn an unsuitable night-time slot into a regular arrangement without confirming with the participants.
Further reading and sources
Event dates, opening hours, and transport services may change. Check official updates before you travel.
