Coordinating vendors across three time zones.

The hardest part of three-time-zone vendor coordination isn’t the logistics. It’s the handoff. The shipment is fine. The supplier is responsive. The client is reasonable. The work fails in the moments between — the twelve-hour windows where everyone is asleep and the document people are relying on is wrong.

I’ve spent the last few years coordinating across roughly that span — a supplier in Manila, our team in Bali, a client in London. What I learned is that the work is less about working harder during your overlap hours, and more about leaving better artifacts behind when you stop.

One status doc, updated daily.

Not one per project, not one per vendor — one. A single page that anyone, in any time zone, can open and immediately understand what’s happening, what’s stuck, and what’s expected next.

I keep the format ruthlessly simple. Three columns: status (green, amber, red), the line item, and the next action with an owner. No commentary. No history. History lives in the linked thread; the doc itself is for orientation, not explanation.

One owner per vendor. Never duplicate.

The fastest way to lose a shipment is to have two people on your team both emailing the same supplier — one asking for an update, one approving a change, neither aware of the other. The vendor sees contradictory instructions and does what humans do under contradiction: nothing, or the wrong thing.

Every vendor relationship gets one owner. Anyone else on the team who needs something from that vendor goes through the owner. This sounds bureaucratic until you’ve watched it prevent a problem twice.

In any system of distributed work, ambiguity about who is responsible is the most expensive form of waste.
— PETER DRUCKER, THE EFFECTIVE EXECUTIVE

The 24-hour acknowledgment rule.

When a vendor or stakeholder sends something, the rule is: acknowledge within 24 hours, even if you don’t have an answer. “Got it, looking into it, back to you Friday.” That’s all.

Two reasons. The first is courtesy: people who feel heard wait patiently. People who feel ignored escalate. The second is procedural: an acknowledgment gives the other side a deadline they can plan around. Silence is the operational equivalent of a leak.

Templates for the four common requests.

The same handful of conversations come up over and over in vendor coordination. Status check. Shipment delay. Quality issue. New spec or change request. I keep one short template for each, kept in a place I can paste from in under five seconds.

These are not autoresponders. They’re starting points. The template gives me the structure — greeting, context, specific ask, expected next step — so I can spend my real attention on the part that matters: the actual situation. Without templates, I rewrite the structure every time, and the structure is the part most prone to error when I’m tired.

A small example.

For a shipment delay, the structure I default to is:

1. Acknowledge the delay specifically, with the dates affected
2. State what we now know and what we don’t
3. Name the next concrete action and the date it happens by
4. Offer one clear thing the recipient can do, if anything

Four lines. No apologies past the first one. No vague reassurances. The clarity is what makes the situation feel handled, even when the situation itself is still in motion.

What this is really about.

Cross-time-zone coordination looks like a logistics problem, but it’s a documentation problem dressed up as one. The people involved are competent. The systems are usually fine. What goes wrong is the moment between handoffs, when one person stops working and another picks up the thread — and the thread is missing.

Better artifacts fix this. Not more meetings, not more software. A single status doc that’s true. One owner per vendor. A culture of acknowledging within a day. Templates for the conversations you already know are coming.

That’s most of it. The rest is showing up.