What Should a Supplier Response-Time Specification Say?

Almost every sourcing failure has a communication failure somewhere inside it, and almost none of them are caused by people not talking. They are caused by messages going to the wrong channel, answers arriving without a decision attached, and nobody knowing when a question has become an escalation. All three are structural problems, and all three are fixed by a one-page document agreed before anything goes wrong.

The reason the document is rarely written is that it feels unnecessary while things are going well. That is precisely when it should be written, because a protocol agreed during a problem is agreed under pressure and will be shaped by whoever is most annoyed. This piece sets out what goes on the page, how to set response windows that are realistic, how to number an escalation so that it means something, and how to measure the whole thing without a system.

What Is a Communication Protocol For?

Three things. It removes ambiguity about where a message goes, so that a question does not sit with somebody who does not own it. It sets an expectation about how quickly an answer arrives, so that a buyer can plan rather than chase. And it defines what an escalation is, so that the word carries weight when it is used rather than being spent on ordinary urgency.

The third is the most valuable and the least often done. In most relationships escalation is a tone rather than a procedure: somebody writes more firmly and uses capital letters. Where escalation is a numbered level with a named holder and a defined response window, using level two is a specific act with a specific consequence, and because it is specific it is used rarely and taken seriously when it is.

Which Channels Should Be Authoritative?

One channel per message class, and the split that works on most programmes is three. A written channel — email or a shared thread — carries anything that creates a commitment: specification changes, schedule changes, approvals, prices. A fast channel carries coordination: shipping details, meeting times, status questions. A formal channel carries notices: escalation, claims, contractual steps. Mixing classes across channels is how a commitment ends up in a chat thread nobody can find.

The rule that makes the split hold is that a commitment made on a fast channel is confirmed on the written channel within one business day, and that only the written version counts. That rule sounds bureaucratic and it removes an entire class of dispute, because there is then exactly one place where a commitment lives and exactly one document to look at when the two sides remember it differently.

What Response Windows Should Be Written Down?

Two per message class: an acknowledgement window and a substantive answer window. The acknowledgement is short — same working day or one business day — and its only job is to tell the sender that the message has landed and who holds it. The substantive window is longer and depends on whether the question can be answered from a document or requires investigation.

Separating the two is the single most useful thing in the document, because most communication friction is not slowness, it is silence. A question that sits unanswered for three days while somebody investigates feels identical to one that was never received. An acknowledgement sent on day one costs nothing and removes the feeling, which is why the acknowledgement window matters more than the answer window.

How Should Escalation Be Numbered and Named?

Three levels, each with a trigger, a holder and a window. Level one is the working level: the programme contact on each side, with the standard windows. Level two is triggered by a missed window, a schedule risk, or a quality issue that affects a shipment, and is held by a named manager on each side with a shorter window. Level three is triggered by a missed level-two window or by a shipment at risk, and is held by a named owner on each side.

Each level should state what it is and what it is not. Level two is not a complaint and it is not a threat; it is a request for a named person to take hold of an issue. Written that way it can be used early, which is the point, because escalation used late is usually escalation used too late to help.

The confirmation rule deserves one more sentence of detail, because it is the part of the protocol most likely to be ignored in practice. It does not require a long message: a single line naming the commitment, the person who made it and the date is enough. What matters is that it exists in the written channel, because the other outcome is a shared thread in which a commitment was made in passing and two sides later remember the passing differently.

What Belongs in a Weekly Status Note?

Five lines, sent on the same day each week, in the same order: what is in production, what is at the inspection gate, what is waiting on the buyer, what is at risk, and what decisions are needed. Five lines is enough and more than five will not be read. The value is not in the content of any single note; it is in the fact that a note arrives every week, so that an absence is noticeable.

The third line — what is waiting on the buyer — is the one that surprises people. Most programmes assume the delay is on the production side and discover, once the question is asked weekly, that a meaningful share of it sits with the buyer: an approval not given, an artwork not supplied, a decision not taken. A weekly note makes that visible and usually shortens the schedule by more than any pressure on the production side would.

How Do You Handle Time Zones and Public Holidays?

By defining a working day in the document rather than leaving it implicit. A working day for the purposes of the protocol is a day on which both sides are working, which means the overlap between the two calendars rather than either one alone. Where the overlap is short, the windows should be expressed in business days rather than hours, because a four-hour window across a short overlap is not deliverable.

Then record both holiday calendars at the start of each year and circulate them. Public holidays at the production base are the single most common cause of a missed window that nobody caused, and a calendar circulated in January removes the explanation and the irritation together. Where a holiday falls inside a production window, the effect on the schedule should be noted when the order is placed rather than when the window is missed.

What Does Good Communication Look Like When Something Goes Wrong?

Early, specific and without blame attached to the first message. The pattern that works is a short message stating what happened, what is affected, what is being done and when the next update will come — four facts and a date, with no analysis and no attribution. Analysis and attribution can come later; in the first message they cost time and they harden positions.

The second useful pattern is to over-communicate briefly rather than under-communicate thoroughly. A short message every day while an issue is open is far better than a long one at the end of the week, because it lets both sides plan around a moving situation. Buyers who receive a daily two-line update rarely chase; buyers who receive nothing for five days chase daily and get less information.

One further habit separates protocols that survive from those that fade: keep the message log. Not a formal register, just the thread preserved rather than allowed to scroll away in a chat application. A protocol can only be measured against a record, and a record can only exist if somebody decides that the thread is a file rather than a conversation. That decision costs nothing at the start and cannot be made retrospectively.

How Do You Measure the Protocol?

With three counts per quarter, taken from the message log: the proportion of messages acknowledged inside the window, the proportion of substantive answers inside the window, and the number of escalations by level. Three numbers, no system required, and together they describe whether the protocol is operating. These are exactly the counts that feed the communication dimension of the scorecard.

The third count is the interesting one. A rising number of level-two escalations is a warning even where every one was handled well, because it means issues are reaching the escalation route rather than being resolved at level one. A protocol that is being used correctly has few escalations and no surprises; a protocol that is being used as a routine reminder has many and has stopped functioning as an escalation route at all.

How Should the Protocol Be Agreed?

As a document with a version number, exchanged and acknowledged, reviewed annually, and held in the same folder as the specification and the inspection plan. It should be short enough to be read in two minutes and specific enough to be argued from. Where a protocol runs to several pages, it has stopped being a protocol and has become a manual, and manuals are not consulted in a difficult week.

Agree it at the start of a relationship and revisit it after the first problem rather than after the first quarter. The first real problem is the test of every window in the document, and immediately afterwards is the only moment when both sides remember precisely what did not work. A revision made then is worth three made from general impressions later.

1. Channels

Written for commitments, fast for coordination, formal for notices

2. Confirmation rule

A commitment made verbally is confirmed in writing within one business day

3. Acknowledgement window

One business day for any working message

4. Substantive window

Two business days where investigation is required

5. Escalation levels

Three working levels with triggers, holders and windows

6. Working day

A day on which both sides are working; windows expressed accordingly

7. Holiday calendars

Both calendars circulated at the start of each year

8. Review

Annually, and after the first problem each side remembers

A short note on what a protocol cannot do. It cannot substitute for a relationship, and a buyer who relies on escalation windows as the primary mechanism will find that the relationship has become transactional and the goodwill that resolves difficult weeks has gone. The protocol handles the ordinary traffic so that the relationship is spent on the exceptional cases, which is the only sustainable division of labour between the two.

None of this touches the commercial frame. MOQ 500 pcs per style and colourway, sampling 6-10 working days from a signed-off tech pack, bulk production 35-50 days from written sample approval, inspection at AQL 2.5 under ISO 2859-1 General Inspection Level II, T/T 30/70, quoted FOB Xiamen. A communication protocol does not change those numbers; it changes how often a buyer is surprised by them.

A note on language is worth adding, because it costs nothing and changes outcomes. Where the two sides work in different first languages, the protocol should say which language is authoritative for commitments and should require that a commitment be restated in one short sentence by the receiver. That single habit catches most of the misunderstandings that a longer message would have buried, and it is far more effective than requiring both sides to write in a language neither uses comfortably.

One last point that belongs on the page and is usually left off: who is allowed to approve a change. Specification changes approved by someone without authority are a recurring source of cost and rework on both sides, and a single line naming the person or role that can approve a change removes an entire category of dispute. It is one line and it is worth more than most of the rest of the document.

Frequently Asked Questions

People Also Ask