What Do You Ask For When Requesting a Schedule From Sample Approval?

Every buyer asks for a delivery date and most buyers get one, which is the source of the problem. A date with no trigger, no end point and no stage list behind it is a statement of intent, and when it slips there is nothing to point at. This piece is the six fields, the wording that produces them, and the four replies that tell you whether what you have been sent is a schedule or an assurance.

What Are You Actually Asking For?

A model of the order rather than a date for it. The distinction matters because the two requests produce different documents. Asked for a date, a production team answers with the date it hopes to meet, which is usually the short end of its own range. Asked for the stages and the days, the same team has to produce the arithmetic, and the arithmetic will either support the date it quoted or show that it does not.

The request also changes the conversation that follows. A date can only be defended or abandoned; a stage list can be examined, and examining it is where the useful work happens. Two days saved on the dye-house thread is a real saving and it is only visible on a schedule that shows the thread. That is the whole argument for asking for the model rather than for the answer.

Which Six Fields Does a Schedule Have to Name?

The third field is the one least often supplied and the most useful to have. A schedule that names its critical thread tells the buyer where to apply pressure and, just as importantly, where not to. Pressure on a short thread achieves nothing and costs goodwill that is needed later, and the only way to know which thread is short is to ask.

The sixth field is the one that protects the buyer later. Without a change rule, every specification change becomes an argument about whether the date still holds; with one, the argument is replaced by a sentence that was agreed before the change was made. It costs nothing to include and it is the field most often omitted.

How Do You Word the Request So It Produces a Document?

Ask for the fields rather than for the answer. One sentence is enough: a request for the production schedule with its stages in days, named from written sample approval, ending at the named place, with the inspection and its reserve and the change rule. That sentence is specific, it is answerable in an hour, and it does not invite an assurance.

What the sentence should not contain is a demand. A request that says the date is fixed and non-negotiable invites a document that agrees with it regardless of the arithmetic, which is worse than no document at all. Ask for the schedule and, once it arrives, negotiate the date. Doing it in that order is what makes the negotiation about numbers rather than about willingness.

What Does a Usable Schedule Contain When It Arrives?

It can be added up. That is the whole test, and it takes ten minutes. Take the stage list, note which stages run in parallel, and check that the longest chain equals the window quoted. Where the two disagree, one of three things is true and each of them is a legitimate answer worth hearing: the stages overlap in a way not yet explained, the clock starts somewhere other than sample approval, or a stage is missing.

It also names the artefact each stage produces. A schedule that lists a stage and no document at the end of it is a schedule with no way to check whether the stage happened, which is the same weakness a milestone calendar has when its milestones carry no evidence. The nine-milestone version of this is set out in the piece on Building a Production Schedule, and the two documents are meant to be read together.

How Do You Tell a Schedule From a Promise?

The second row is the most common and the easiest to correct. A window counted from the purchase order can be several weeks longer than the sample approval that actually starts it, and the difference is invisible until somebody counts. Restating the trigger moves the date, and it usually moves it honestly rather than favourably.

The fourth row is the one that tells the buyer most. A stage list that adds to fifty against a quoted date of thirty-five contains an assumption that has not been stated, and the assumption is usually that two long stages run in parallel. Some do; the dye-house queue and the tooling chain frequently do not, because both are queues with other orders ahead of them.

What Should You Do When the Schedule Arrives Without Dates?

Send it back once, with the fields listed and the missing ones marked. That is not a difficult message and it is surprising how often it works, because a production team that has been asked for a date for ten years and for a schedule once will usually produce the schedule when asked directly. The fields are not a secret; they are just rarely requested.

Where the second request also returns an assurance, treat that as information about the relationship rather than about the order. A partner who will not name the stages is not going to honour a date based on them, and the useful response is to price the risk into the plan: hold the selling window wider, or book the material earlier. Asking a third time costs less and changes nothing.

How Do You Ask for Updates Without Asking for Percentages?

Ask for the artefact belonging to the stage. A percentage complete is a number nobody can check, because forty per cent of the panels cut, forty per cent of the cartons packed and forty per cent of the calendar elapsed are three different places to be. The mill confirmation, the dip cards, the first-off photographs and the daily output count are documents, and each of them can be checked or not produced.

The habit is worth building because it does not depend on interpretation. A stage that has produced its document has happened; a stage that has not, has not, whatever percentage is attached to it. This is the same discipline the QC documentation and reports post applies to inspection evidence, and it works on the production side for the same reason: documents are countable, impressions are not.

What Should the Schedule Say About Changes?

That any change after approval restarts the clock, and that the restart is issued in writing with a new date. That sentence covers three kinds of change and all three of them move the date: a specification change, a material change and a buyer-side decision that was late. Naming all three is what stops the conversation about whose fault it was, which is a conversation with no commercial value.

It should also say who issues the revised schedule and by when. A change note with no response window attached is a request rather than a requirement, and the response window is what makes the revised date arrive while it can still be acted on. One working day for the acknowledgement and two for the reissued schedule is a workable window, and it is short enough to be honoured.

When Should the Schedule Be Reissued?

At every milestone and after every change, with a version number on each edition. A schedule that is reissued without a version number produces two documents in circulation and an argument about which one governs, and the argument happens at exactly the moment the buyer least needs it. Number the editions and the governing one is the highest number.

The five milestones worth reissuing at are material release, shade approval, the pre-production sample, the mid-run gate and packing. Each of them resolves an uncertainty that the previous edition carried as an assumption, which is why each edition is shorter and more accurate than the one before it. Five editions across a run is not bureaucracy; it is the record the final week will be argued over.

How Do You Use the Schedule in a Negotiation?

By negotiating the stages rather than the date. A buyer who accepts the model and then argues about the date is arguing about the output of an arithmetic already agreed to, which is a weak position and it is visible as one. A buyer who argues about a stage — the dyeing can be removed with a stock shell, the tooling can be removed with a stock pull — is changing the input, and the date then moves because the arithmetic changed. That is the only negotiation on a lead time that produces a real improvement.

It also converts the conversation about the price. Every removal has a cost in appearance or in branding, and those costs belong to the buyer to weigh rather than to anybody else to hide. A schedule with its stages named lets the two be traded against each other honestly: six days against a branded pull, nine against a dyed shade, four against a second colourway. Without the stage list there is nothing to trade, and what is left is a date being promised.

What Does a Schedule Cost to Ask For?

One email and about an hour of somebody else's time, which is the entire price of the most useful document in a bag programme. The return is a date that can be checked, a critical thread that can be pressured, and a record that makes a late shipment a matter of dates rather than of recollection. There is no other artefact in the programme with that return on it.

There is a second return, which is behavioural. A production team asked for a schedule at quotation produces one at quotation, and the discipline of counting the stages before quoting them changes the number it quotes. Asking is not only a way of finding out; it is a way of being quoted honestly, which is worth more than the document itself.

Clock trigger

Written sample approval plus receipt of the deposit

Stage list

Every stage, in days, with the parallel ones marked

Critical thread

Named, with the float on each of the others

End point

An Incoterms place, FOB Xiamen unless agreed otherwise

Inspection

AQL 2.5, ISO 2859-1, Level II, with a three-day reserve

Change rule

Every change restarts the clock, in writing, within two working days

Six fields and the request becomes a specification rather than a question. We do not promise the fastest 20 days. We promise a delivery date you can calculate. The document that comes back is the one that decides whether the date can be held, and it is the only thing in the file that does.

Frequently Asked Questions

People Also Ask