How Do You Ask for a Production Timeline You Can Quote Against?

Most buyers ask for a lead time and receive a number. That is the wrong question asked in the wrong form, and it produces an answer that cannot be checked, compared or enforced. This piece is the request to send instead: the exact content, the order to put it in, and how to read what comes back. It is written to be copied into an email and sent.

Why Does the Form of the Request Matter?

Because a single question invites a single number, and a single number is not a plan. Six questions in one message force the vendor to hold six constraints at once, which is exactly what their schedule does. Asked one at a time over a fortnight of messages, the same six produce six individually reasonable answers that do not reconcile, and the buyer spends another fortnight discovering that.

The form also signals what kind of buyer is asking. A request that names a code letter and asks about the re-check branch is a request from somebody who has done this before, and it is answered differently from a request that asks how fast they can make 500 bags. That difference is worth more than any clause in the eventual contract.

What Exactly Should the Message Say?

1

What starts your clock, and what date would you put on it today?

2

What does your number end at: ex-works, on board, discharge port, or delivered and entered?

3

Which stages are inside the scope and which are outside? Please list them in days.

4

What sample size and accept/reject pair does the inspection run at?

5

What happens to the date if the first submission fails?

6

What document do I receive at the end of each week of production?

Six lines, one message, and the reply becomes comparable with the reply from the next vendor. Send the same six to both and the comparison is arithmetic rather than impressionistic, which is the only version of it that means anything.

Who Should Send the Request, and When?

That table is the answer to a question buyers rarely ask themselves: how much of the quoted window is actually ours. On most first programmes the honest figure is four to eight days, spread across approvals, dip responses and the deposit. None of it is visible in the vendor number and all of it is on the critical path.

What Should You Send With the Request?

Four attachments, because a timeline request without a specification is a request for a guess. The tech pack with dimensions and materials, the artwork with print positions and colours, the hardware references or a statement that stock hardware is acceptable, and the quantity with the colourway split. A fifth is useful: the date the goods need to be on board.

The fifth attachment changes the nature of the reply. A request with a date in it comes back as either a plan that reaches the date or a statement that it does not. A request without one comes back as a number, and the buyer discovers the gap later. The 15-field RFQ template sets out the fields that make the first four complete.

There is a sixth question worth adding when the programme has a fixed launch behind it, and it is the one that separates a vendor who plans from one who sells: what would you take out to reach this date. Asked politely, it produces an honest list of controls being removed, and the buyer can then decide whether the trade is acceptable. A vendor who answers "nothing, we will just work faster" has not understood the question.

How Do You Read the Answer?

For internal consistency before anything else. Add up the stage list and compare it with the headline number. Check that the end point matches the Incoterm you asked for. Check that the inspection answer contains a code letter and an accept/reject pair rather than an adjective. A reply can be fluent and still fail all three.

Then read it for what is missing, which is usually more informative than what is present. A stage list without dyeing on a dyed-to-order programme has omitted the longest thread. A weekly artefact list without a pre-production sample has omitted the control that protects the bulk run. Omissions are rarely deliberate; they are the shape of a vendor usual offer.

What If the Vendor Will Not Answer the Six?

That is itself the answer, and it is worth taking seriously. A vendor who will not say what starts the clock is a vendor who has not decided, and a vendor who will not name an inspection standard is a vendor whose inspection is an opinion. Both are workable for a reorder of a known product and both are risky on a first custom run.

A second reading is worth applying to the timeline itself rather than to the tone of the reply. A schedule in which every stage is the same length is a schedule that was written rather than measured, because real stages are not equal: dyeing is longer than cutting, and inspection is longer than packing. Uneven, awkward numbers are a sign somebody looked at a calendar.

There is a legitimate reason for a short reply, and it should be handled fairly: a small programme desk may not have a written schedule to hand and may need a day to produce one. Ask for it by a date and see whether it arrives. The distinction is between a vendor who cannot answer yet and one who has never thought about it.

A third pattern is worth preparing for, because it is common and it is not dishonest: the reply answers four of the six questions thoroughly and skips the inspection standard and the weekly artefact list. That is the profile of a capable production team with no written quality system, and it is workable if the buyer supplies the missing two. Send the required standard and the required artefact list as part of the order rather than as a request.

How Does the Request Change for a Reorder?

It shortens to three questions, because tooling, patterns and the sealed sample already exist. What starts the clock, what the slot is, and what the dye-lot reference is. The third is the one buyers forget and the one that decides whether the fifth run matches the first.

On a reorder the useful request is actually a statement: here is the sealed sample revision, here is the dye-lot number, here is the shade band, and here is the carton count from last time. Sending the reference with the request removes the negotiation about what matching means, which is the argument the guide on keeping a reorder identical to the first run is written to end.

What Does the Reply Cost You to Obtain?

An hour of writing and a day of waiting, which is less than the cost of not asking. The six questions are the least expensive due diligence available in bag sourcing: no audit, no visit, no third-party fee, and an answer that separates a milestone schedule from a fast number more reliably than any document a vendor will volunteer.

There is also an effect on the reply itself that is worth naming. A vendor who has answered the six questions in writing has, in effect, drafted the schedule they will be held to. That is why the request works: it does not ask for a promise, it asks for a plan, and a plan has dates in it that are hard to walk back from later.

What Should the Answer Be Turned Into?

A schedule with nine milestones, owners, artefacts and float, which is the table in Building a Production Schedule. The six questions are the request; the schedule is the deliverable. Converting one into the other is an hour of work and it is the hour that decides whether the rest of the programme is checkable.

Then put the trigger and the end point into the contract, which is the subject of Locking a Delivery Date. A schedule agreed in email has force; the same schedule with the trigger and the end point named in the order has more, because the two fields that cause most disputes are the two that writing down costs nothing to fix.

What Does a Good Reply Contain End to End?

• A named trigger with a date on it, not a phrase about receiving the order.
• A stage list in days that adds up to roughly the headline number.
• An end point that matches the Incoterm you asked to be quoted on.
• A code letter, a sample size and an accept/reject pair rather than an adjective about quality.
• A stated consequence for a failed submission, because a branch is the difference between a plan and a hope.
• A weekly artefact list, because a schedule that produces documents can be checked.

There is one property that outranks the other five, and it is the weekly artefact list. A vendor who will commit to sending a mill confirmation, dip cards, a pre-production sample, a cut count, a daily output and a signed report has committed to being checked, and every other answer in the reply follows from that. A vendor who sends a full stage list but no artefacts has described a process without agreeing to be accountable for it.

Six properties, and a reply with all of them is worth more than a reply with a number three weeks shorter. We do not promise the fastest 20 days. We promise a delivery date you can calculate. The six questions are how you find out whether the number you were given is the first kind or the second.

Frequently Asked Questions

People Also Ask