Vietnam's UTC+7 Time Zone: A Practical Guide to Follow-the-Sun Engineering

The UTC+7 Schedule and the No-DST Advantage

Vietnam uses a single time zone nationwide — ICT, defined as UTC+7 — and does not observe daylight saving time. The practical implication for engineering planning is significant. Offshore engagements with regions that toggle DST twice a year (the United States, the European Union, Australia) suffer a one-hour shift in overlap window for a few weeks each spring and autumn. Teams have to re-publish meeting cadences, update on-call schedules, and re-check SLA clocks. With Vietnam, the offset is constant. A 09:00 standup in Ho Chi Minh City is always 03:00 in Berlin, always 11:00 in Tokyo, always 18:00 the previous day in New York. For engagements that span three or more regions — a common configuration for enterprises with US product leadership, EU compliance review, and VN engineering — that fixed offset removes one variable from an already complex scheduling matrix. The downstream cost is real: misaligned DST transitions are a frequent source of missed handoffs and delayed releases in distributed teams.

Overlap Windows by Client Region

ICT's position on the global clock creates three distinct overlap profiles. For Asia-Pacific clients — Singapore, Hong Kong, Tokyo, Seoul, Melbourne, Sydney — Vietnam sits inside the same business-day window. Singapore and Hong Kong are one hour ahead; Tokyo and Seoul are two hours ahead; Sydney is three hours ahead during AEST and two hours ahead during AEDT. Daily standups, pair-programming sessions, and live design reviews happen during normal working hours for both sides. This is the easiest configuration and rarely requires async scaffolding beyond standard engineering hygiene. For European clients — Germany, France, the Netherlands, the Nordics, the United Kingdom — Vietnam is five to six hours ahead. The window is partial but useful: a 09:00–11:00 ICT standup and ceremony block lands in late afternoon in CET, and a 14:00–17:00 ICT deep-work block overlaps with EU morning. Most EU-VN engagements standardize on a single 30-minute sync during the EU afternoon. For North American clients the overlap is effectively inverted. US Eastern Time is 12 hours behind ICT during EST; US Pacific is 15 hours behind. Real-time collaboration windows are narrow (typically 08:00–09:00 PST = 23:00–24:00 ICT) and most teams shift to an asynchronous model with one weekly sync.

Designing the Follow-the-Sun Handoff

The follow-the-sun model — where unfinished work is handed off between geographies each cycle to compress calendar delivery time — has been formalized in global software engineering literature since at least the mid-2000s. Wikipedia's overview of follow-the-sun frames it as a sub-discipline of globally distributed software engineering. The pattern works only when three conditions are met. First, work units must be small enough to start, progress, and hand off inside a 24-hour cycle; large features that require sustained shared context break the model. Second, handoff artifacts must be written, not verbal — a brief that captures current state, blocked decisions, and next actions. Third, ownership must actually transfer: the receiving team has authority to merge, deploy, or escalate without waiting for the handing-off team to wake up. Without that authority, handoffs degrade into status-passing rituals that compress nothing. The practical pitfalls Uptime Labs documents — particularly severity-tier mismatch, where regions classify incidents differently and handoffs stall on definition disagreement — are the most common failure mode in production environments.

Daily Ceremony Cadences That Work

The most effective VN-engagement schedules anchor on a single daily sync that hits the overlap window. For APAC clients, that is typically a 10:00 ICT standup with afternoon pair-programming slots. For EU clients, a 15:00 ICT sync (09:00 CET) is a common configuration; the EU team starts the day with the VN team's end-of-day context, and the VN team's morning block produces reviewable artifacts before the EU team logs off. For US clients, the weekly sync is usually 08:00 PST / 23:00 ICT on Wednesdays — late enough in the US workday to have the week's progress ready, early enough in the ICT day to action feedback before the weekend. A pattern that works across all three configurations: reserve the overlap window for decisions that genuinely require real-time discussion (design tradeoffs, incident triage, roadmap debates) and push everything else to async channels. Teams that try to fit standup, retro, grooming, and pair-programming into a 60-minute overlap window end up doing none of them well. The complete offshore development guide covers the broader engagement-setup checklist.

Async-First Engineering Practices

Async-first engineering is what makes the time-zone model scale beyond a single overlapping meeting. Three practices consistently differentiate teams that ship reliably across time zones from those that stall. First, pull request descriptions are written as if the reviewer was not on the call that produced them: context, decision rationale, screenshots or recordings, test plan, and explicit reviewer questions. Second, architectural decisions are captured as written ADRs (Architecture Decision Records) in the repository, not as chat threads — chat history is unsearchable after a few months on most plans, and a decision that lives only in chat effectively does not exist for the next engineer who joins. Third, demos and walkthroughs are recorded once and watched many times: a five-minute recorded walkthrough of a new feature, a migration plan, or an incident postmortem reaches every region on its own schedule. Tools matter less than the discipline of producing these artifacts consistently. GitHub Issues, Linear, Jira, and Asana all support the pattern. What fails is the assumption that synchronous discussion is a substitute for written context — an assumption that breaks the moment a region joins the engagement that has zero overlap with the others.

Where the Model Breaks Down

The follow-the-sun model has known failure modes that engineering leaders should plan for. Blocked pull requests are the most common: a VN-authored PR that needs review from a US-based tech lead sits idle for 12–16 hours unless a reviewer in an intermediate region (EU or APAC) is empowered to approve. Without that empowered intermediate reviewer, cycle time inflates by a full business day per round of review. The second common failure is on-call coverage gaps: if severity-tier definitions differ between regions, an SEV-2 in one region may be treated as an SEV-3 in another, and the handoff stalls on disagreement rather than action. The third is context loss at the handoff boundary: a partially-completed task handed off without a written brief almost always requires the receiving engineer to re-derive the context from the code, which often costs more than the time saved. The offshore partner evaluation checklist covers the questions to ask a vendor about handoff structure, reviewer authority across regions, and severity-tier definitions.

Building an Engagement Model That Fits Your Time Zone

Designing a Vietnam engineering engagement around the ICT schedule is less about finding the lowest hourly rate and more about engineering the overlap windows, handoff artifacts, and reviewer-authority model that let distributed work actually compound across time zones. APAC clients get near-full overlap with minimal async overhead; EU clients get a useful partial window; US clients get a follow-the-sun configuration that demands disciplined async practices but can compress delivery cycles when executed well. For teams that want help structuring a Vietnam-based engineering pod — including ceremony cadence, async-first engineering practices, and cross-region reviewer authority — Retech Solutions builds dedicated teams that ship across APAC, EU, and US time zones.