How to run a follow-the-sun audit cycle across US–India timezones

Follow-the-sun gets pitched as magic — hand off work at 5pm, wake up to a finished draft. It is not magic. It is a protocol, and most firms that try it without one end up with the opposite of the promise: a US senior waiting on a reply that doesn’t come until their own evening, because nobody defined what “handoff” actually means. This is the protocol we run on audit support engagements between US firms and a Chennai-based team, written down because the difference between a working follow-the-sun cycle and a frustrating one is almost entirely procedural, not talent-related.

The clock, stated plainly

Chennai (IST, UTC+5:30) is 10.5 hours ahead of US Eastern during standard time and 9.5 hours ahead during daylight saving; 13.5 / 12.5 hours ahead of Pacific. In practice: a file sent from the US at end of business (5–6pm ET) lands as the start of the India team’s next working day. A file the India team finishes by their end of day (6–7pm IST) is sitting in the US inbox before the US team’s day starts. The overlap window — where both teams are plausibly at a desk at the same time — is roughly 7–9am ET / 5:30–7:30pm IST, which is narrow and should be spent on synchronous items only: nothing that can be handled by written review notes should be scheduled into that window.

The PBC list is the whole game

More audit engagement delay traces back to a disorganized prepared-by-client (PBC) list than to any technical issue. A follow-the-sun cycle collapses immediately if the PBC list isn’t disciplined, because there’s no same-day recovery window when a US team member goes home for the night and the item they were supposed to chase down is still outstanding.

What we require before a PBC list enters the offshore workflow:

One line per item, one owner, one due date — not a bundled request like “AR support and confirmations” covering four separate documents with different sources.
Status field updated same-day, not batched at week’s end: received / outstanding / client says N/A (with reason) / escalated.
A hard cutoff for “aging” items — anything outstanding more than 5 business days gets flagged to the engagement manager automatically rather than sitting in the list unremarked. On most engagements we run, roughly 15–20% of PBC items are the source of over half the schedule slippage, and they’re identifiable early if someone is actually watching the aging column instead of just adding new rows.
Version control on the list itself. A PBC tracker that lives in email attachments, re-sent as “PBC list v4 FINAL FINAL,” is a guaranteed source of someone working from stale information. Use a shared, single-source tracker (a shared spreadsheet with locked structure, or a PBC module inside the audit platform) — the tool matters less than there being exactly one current version.

The handoff protocol

Every file that crosses the US–India boundary follows the same structure, logged, not just emailed:

What’s being sent — specific workpaper or schedule reference, not “the AR stuff.”
What’s expected back — a completed lead schedule, a set of review notes cleared, a reconciliation tied out. Ambiguity here is where a 9pm-ET sender and a 7am-IST recipient lose a whole day to a clarifying question that could have been answered in the handoff itself.
By when — tied to the receiving team’s end of day, not a vague “soon.”
Open questions flagged inline, at the point in the workpaper they apply to — not as a separate list disconnected from the file, which forces the receiving preparer to hold two documents in their head at once.

A completed handoff gets acknowledged within the first hour of the receiving team’s day — not completed, acknowledged — so the sending side knows by their own morning whether the file was received intact and understood, rather than finding out at end of day that a question sat unanswered for eighteen hours.

Review notes: the part that actually determines cycle speed

Slow follow-the-sun cycles are almost never a speed-of-work problem. They’re a review-note clarity problem. A vague note — “please review this” — sent at 6pm ET produces a guess by the India team, which produces another vague note back, which burns a full 24-hour round trip on something that should have taken ten minutes.

The standard we hold reviewers and preparers to:

Every review note references a specific cell, tick mark, or line item — never a general comment on a tab.
Every note states what’s wrong or unclear and what resolution would look like, not just a flag (“this doesn’t tie” is not a note; “this doesn’t tie — bank statement shows $42,150, workpaper shows $41,850, difference likely the outstanding check on line 14, please confirm” is).
Notes get cleared with a visible trail (who cleared it, when, what the resolution was) rather than deleted once addressed — this matters as much for the engagement partner’s final review as for the preparer’s own accountability.

Firms that adopt this standard typically see review rounds drop from three or four to two within the first several weeks, purely from cutting the round trips caused by ambiguous notes.

Tools that actually matter here

The tool stack matters less than the discipline above, but three things genuinely change outcomes:

A cloud-based audit platform with real-time status (Caseware Cloud or equivalent) over anything that requires a file to be checked out and emailed — file version conflicts are the single most common technical failure in a cross-timezone engagement, and they are entirely avoidable with a shared cloud file.
A single tracker for PBC status and open review notes, visible to both teams, updated in real time rather than reported in a weekly status email that’s stale by the time it’s read.
Asynchronous video for anything genuinely hard to explain in writing — a 90-second screen recording walking through a reconciliation logic explains what would otherwise take four rounds of written back-and-forth, and it doesn’t require both parties awake at once.

One line worth remembering when a firm is deciding whether to invest in this properly: a follow-the-sun cycle is not free speed, it’s traded synchronicity — you get a working day back, but only if the handoff at each end of it is precise enough that nobody has to wait for the other side to wake up and ask what was meant.

Q&A

How much time overlap do we actually need between the US and India teams? Less than firms assume. A 1.5–2 hour window is enough for the items that genuinely need a live conversation, provided everything else runs through a disciplined written handoff and PBC tracker. Trying to force more synchronous overlap usually just erodes the after-hours advantage the arrangement is meant to provide.

What’s the single biggest cause of a follow-the-sun audit cycle running slow? Ambiguous review notes and an undisciplined PBC list — not working speed. A note that doesn’t specify the exact discrepancy and expected resolution burns a full 24-hour round trip on something that should take minutes once the platform and tracker are set up properly.

Does this work for a full statutory audit, or only for support work like workpaper prep? It works well for audit support — workpaper preparation, reconciliations, PBC chasing, first-level tie-outs — under the review of the US engagement team, which retains all judgment calls, sign-off, and opinion responsibility. It is not a substitute for the US firm’s own review and reporting responsibility on the engagement.