How Do Time Zones Change Approval and Sampling Windows?

A buyer in Manchester and a production desk in Fujian share very few working hours, and the ones they share are at the wrong end of the day for the buyer. A question sent at five in the afternoon in the United Kingdom arrives the following morning in China; the answer arrives that evening; the buyer reads it the next morning. One exchange, two days, and most of the second day is gone before anyone acts on it.

The interesting part is where those days are lost. They are not lost in production, which runs on its own schedule regardless of the buyer inbox. They are lost in the gates the buyer owns: the brief, the material decision, the artwork release and the sample approval. A programme that loses two days per exchange across four gates has lost a working week before a single unit is cut, and no amount of urgency at the end recovers it, because urgency applies to production and the loss was in decisions.

This piece sets out the arithmetic of the overlap, the three habits that remove most of the latency, and the rules that stop a question from stalling a run. It is a short set of practices and it is the difference between a programme that feels slow for no visible reason and one that moves.

How Much Overlap Is There Really?

China observes a single national time at UTC+8 and does not change for daylight saving, which makes the arithmetic stable for half the year and worse for the other half. For a buyer in Western Europe the overlap is a few hours in the European morning. For a buyer on the eastern seaboard of North America it is the previous evening. For a buyer on the west coast it is the middle of the night. For a buyer in Australia it is generous.

Why Does One Question Cost Two Days?

Because an exchange needs the production day to happen in the middle of it. The question has to be read, the answer has to be found — which usually means asking someone else, measuring something, or checking a material — and the reply has to be written. None of that is instant even when the desk is awake. A question that could be answered from a document is answered in an hour; a question that needs a physical check is answered the next day.

The second reason is that questions arrive in the wrong order. A buyer asks about a trim shade on Monday, a stitch density on Tuesday and a label position on Wednesday. Each is individually quick, and together they consume three production days and three of the buyer own days, which is the loss that nobody sees on a plan. Asking all three on Monday consumes one of each.

There is a second cost that is easy to miss because it is small each time: the partial answer. A question answered incompletely produces a follow-up, and the follow-up is another production day. So the rule is not only to ask everything at once, it is to ask everything completely — with the drawing attached, the revision number quoted and the due date stated — so that the answer can be complete the first time.

What Is the One-List Rule?

Subject

The style, the revision number and the date

Section 1

Decisions needed today, numbered, with a due date on each

Section 2

Questions that need a physical check, numbered

Section 3

Confirmations of what was received and understood

Section 4

The next gate and its date

Rule

One message per day, sent at the start of the production day

Rule

No new question is sent outside the message without a reason

Rule

Every numbered item gets a numbered answer

Rule

An item with no answer by its date falls to a standing decision

Rule

The message is the record; calls are summarised into it

The numbered-answer rule is the one that makes the format work. A reply that addresses three of five questions in prose leaves the buyer unsure which two were skipped. A reply numbered to match the questions shows the gaps immediately, and the gaps are what later become a sample that is wrong in a way nobody can trace.

What Is a Standing Decision?

An answer agreed once, in writing, for a class of question that recurs. A thread shade within a stated tolerance, a stitch density within a stated range, a minor placement tolerance, a substitution of an equivalent trim from an approved list. Each of those will be asked again on every run, and each can be answered once for the programme instead.

The value is not the time saved on any single question, although that is real, it is the compounding across a programme. A programme that converts five recurring questions into standing decisions removes five potential two-day stalls from every run, and it removes them without the buyer having to be awake at the right moment.

How Should Approvals Be Structured Across the Gap?

With a date and a default. An approval request carries a due date, and the rule states what happens if the date passes: the sample is approved, or the run holds and says so. Both are better than the drift where a sample sits unapproved while the window it was made in runs out, which is the single most common way a programme loses a week.

A second structural point applies specifically to the sample: approve it against the specification, not against an aspiration. A sample judged against a document is approved or declined in a day; a sample judged against an idea that was never written down is rejected for reasons nobody can action, and the next one fails the same way.

The second structural point is who approves. A committee that has to convene will take longer than the overlap window allows, twice over. A named individual with authority, who can answer from a phone, takes a day. Where a committee is unavoidable, give it a single representative empowered to decide at the meeting rather than after it.

What Should Be Written Rather Than Spoken?

What Does Language Do to the Exchange?

It costs more than the time zone does, on average, because a time zone delay is predictable and a language delay is not. Plain English, short sentences, no idiom, numbers in numerals and units written in full — each of those removes a class of misreading, and none of them costs anything. The two habits that cause most trouble are the idiom, which translates into nonsense, and the abbreviated unit, which translates into a different unit.

The second habit worth adopting, and it costs the least of any of them to start, is the drawing. A dimensioned drawing needs no translation and answers in one image the question that three sentences argue about. Every specification question that can be answered with a marked-up drawing should be, and the drawing then becomes part of the record rather than an illustration of it.

How Do Public Holidays on Both Sides Affect the Calendar?

More than buyers expect, because the two calendars do not align and the production-region closures are longer than the published holiday. The lunar new year closes production for a period that includes travel on either side of it, and the autumn national holiday does the same on a shorter scale. A buyer who checks only their own calendar will book a sampling window that starts on a day nothing is running.

The practical step is to put both calendars on the plan at the start of the year. Both are published well in advance, and the exercise takes ten minutes. A plan that carries them can be read at a glance in any week: is the production end open, is the buyer end open, and what happens to a gate that falls across a closure.

How Can You Tell Whether an Item Is Urgent?

Rare, genuine, and routed differently. An urgent item is one that stops production or stops a shipment: a critical defect found in process, a document that is wrong on the day of booking, a safety question. Everything else is a question, and questions wait for the daily message. A buyer who marks everything urgent trains the other side to ignore the flag.

The routing for a genuine urgent item should be agreed in advance: a named channel, a named person on each side, and an out-of-hours expectation that both have accepted. Without that agreement an urgent message arrives at three in the morning and is read at nine, which is the same as no urgency at all.

How Do You Keep a Record Without Adding Work?

By making the record the by-product of the routine rather than an extra task. The daily message is the record; the numbered answers are the record; the revision number on the tech pack is the record. Nothing has to be written up afterwards because everything was written at the time, which is the only version of this that survives a busy month.

The one addition worth making is a monthly summary: a short note of what was decided that month, sent to both sides. It takes ten minutes, it catches the decisions that were made verbally and never confirmed, and it becomes the index to the archive that a reorder will need. A programme that runs one of those a month can answer any later question about what was agreed without searching a thread.

How Should Meetings Be Handled Across the Gap?

Rarely, and always with an agenda sent in advance and minutes sent afterwards. A meeting across a time zone costs a working day of overlap, and the value has to justify that. Most routine coordination is better done in the daily message, where it produces a record for free.

What does justify a meeting is a decision that needs discussion rather than an answer: whether to accept a substitution, how to recover a slipped gate, whether to change a material. Those benefit from voices, and the minutes sent afterwards are what carry the outcome. A meeting without minutes is a conversation, and a conversation does not survive to the reorder, which is the only place the record is ever needed.

What Does Good Communication Cost and Save?

It costs discipline at the buyer end, which is the scarce resource. Consolidating questions into one message a day means thinking about the programme once rather than reacting to it eight times, and it is genuinely harder than sending messages as thoughts occur. What it saves is a working week per run, which on a seasonal programme is the difference between hitting the date and explaining the miss.

It also saves the thing buyers notice a year later. A programme run on a daily written record has an archive: what was asked, what was answered, what was decided, and when. A programme run on calls and instant messages has a thread, and a thread is not a record. The Managing Remote Production note sets out the gate structure that the messages support.

Frequently Asked Questions

People Also Ask