Identify the final need
Start with the garment or fabric milestone that matters: trial cloth, sample garment, bulk dispatch or arrival. Give date, location and purpose. Keep buyer target dates distinct from supplier-confirmed dates so the plan does not imply a commitment that has not been made.
List the required outputs
Break the project into brief, candidate selection, colour, garment trial, quotation and order tasks as applicable. Each task should produce an identifiable result such as a scoped review or current offer. Do not use an activity label alone when no completed output exists.
Connect the dependencies
Record which output a task requires before it can start. Material selection may precede garment trial, while a colour change can require a renewed review. Ask the supplier which conditions apply to their programme rather than imposing a generic production sequence.
Assign decision owners
Name the person responsible for each approval or answer. Distinguish the requester, evaluator and final decision-maker. A task without an owner can remain unresolved while the calendar appears complete. Record who receives the result and what they must do next.
Use sourced timing statements
Attach the supplier's actual stage duration, starting event and applicable quotation or item. Do not turn a sample estimate into a bulk or arrival guarantee. Update the plan when a quantity, material or approval changes the applicable conditions.
Plan alternatives with their cost
Identify a fallback candidate or revised sequence and the reviews it would require. State its differences instead of assuming equivalence. A fast alternative may still need garment, colour or evidence approval, so the plan must include those actual tasks.
Your dependency worksheet
Illustration: the bulk plan is waiting on a colour decision owned by design. The buyer identifies that decision and asks how a delayed approval affects the supplier's stated sequence. Use the sheet below to focus the next conversation on the actual blocker.
Task | Required prior output | Decision owner | Buyer target | Supplier stated timing/start | Status | Next action [one row per applicable task] Final milestone and destination: [details] Current unresolved blocker: [entry] Evidence for timing statements: [references] Alternative and additional review required: [details] Changed dependencies since last version: [list] Schedule revision and review date: [entry]
Work through a buying problem: An approval loop hides the real critical path
Consider this illustrative situation: sampling is called complete although one decision still blocks the order. It is a worked buying example, not a report of a completed customer order. Start by defining which decision is blocked and which people need the answer. Keep the garment reference, sample identity and relevant date together so that a later reply cannot silently refer to a different item.
The tempting shortcut is: add a fixed number of days to an unconfirmed starting point. Before accepting it, ask what would change if the assumption proved wrong after the next handover. Use a small, clearly scoped check first; record the original condition and the revised condition separately. This makes it possible to distinguish a genuine resolution from a change in the question being asked.
For this case, the useful comparison is: compare the planned sequence with the earliest unresolved dependency. Agree who interprets the result and who authorises the next step. A person who sends an attachment may not be the person able to approve its commercial or technical use. Close the issue with the evidence reference and a precise statement of the permitted action, rather than an unexplained “OK”.
Evidence and decision record
| Point to resolve | What this case requires | How to make the response usable |
|---|---|---|
| Observed problem | sampling is called complete although one decision still blocks the order | Identify the affected item and the stage at which the difference appears. Keep the original observation separate from an explanation that has not yet been checked. |
| Shortcut to avoid | add a fixed number of days to an unconfirmed starting point | Write down the consequence of this shortcut. A quick answer is useful only when it resolves the actual buying decision rather than moving an uncertainty to another team. |
| Evidence needed | a milestone chain with inputs, owners and release conditions | Give the evidence a sample, document or revision identifier. Ask who can supply the missing item and whether it represents the material or transaction now being discussed. |
| Comparison to make | compare the planned sequence with the earliest unresolved dependency | Keep the basis of comparison the same. If a condition changes, describe that change beside the result so that a different outcome is not attributed to the wrong cause. |
| Pause condition | a required input or release owner is missing from the schedule | Name the step that must wait, the person who owns the unresolved point and the information needed to restart. A pause on one decision need not stop unrelated preparation. |
| Release condition | the owner confirms the input and updates dependent milestones | Record who reviewed the evidence and exactly what can proceed. A release for the stated purpose does not automatically approve a different colour, lot, construction or commercial condition. |
| Boundary of the decision | a duration estimate is not a confirmed calendar completion date | Retain this limitation beside the decision. Other readers should be able to see what remains open without reconstructing a conversation from separate messages or unlabelled attachments. |
| Next question | Which unresolved decision actually controls the next milestone? | Ask for a specific response and its supporting reference. When the answer is conditional, capture the condition instead of replacing it with an unconditional approval in the handover. |
Questions when the answer is still incomplete
Which unresolved decision actually controls the next milestone?
Use this evidence as the starting point: a milestone chain with inputs, owners and release conditions. First confirm that its identifier and stated conditions match the question. If they do not, request the missing link before drawing a conclusion. Keep a provisional interpretation labelled as provisional; it should not become a final order instruction just because it was copied into a later message.
What if two teams interpret the evidence differently?
Apply the pause condition: a required input or release owner is missing from the schedule. Ask each team to state the observation it accepts and the specific point it disputes. The release condition is: the owner confirms the input and updates dependent milestones. Keep the agreed outcome and any remaining exception in one record, with an owner for the exception. A vote or a vague assurance does not replace the evidence needed for the disputed point.
What should the follow-up actually request?
Make the next action explicit: ask for the dependency, required evidence and next review date. Retain this boundary: a duration estimate is not a confirmed calendar completion date. If Fred Textile is the intended counterpart, use the official website to discuss the identified fabric programme and attach the relevant references. A guide, worksheet or public collection description cannot confirm current stock, a price, test performance or a delivery commitment.
Affected garment / item and reference: ____________________ Observed difference and current decision: ____________________ Evidence ID / source / conditions: ____________________ Comparison and result: ____________________ Step on hold / owner: ____________________ Permitted next step / approver: ____________________ Unresolved exception / follow-up: ____________________ Revision / date / recipients: ____________________
Diagnose the difference before changing the requirement: Working days need an agreed calendar
Use this illustrative exercise when a schedule uses days without saying whether they are working or elapsed days. Start by naming the decision affected, not by assigning fault. Keep the material reference, document revision and observation together so that a later reply can be traced to the same question. The exercise describes a buying problem; it does not report a customer result, an available product or a supplier commitment.
The tempting shortcut is to compare durations that count different calendars. That can hide a different explanation: approval time, production time and transit use different bases. Treat the explanation as a possibility to investigate, rather than a diagnosis. Record what would distinguish it from the original assumption. An attractive photograph, a familiar material name or a confident reply cannot replace the missing comparison.
Begin with this check: identify how the stated period is counted. Obtain dated estimate, counting basis and relevant working calendar. Write down which information is directly observed, which comes from a document and which is still inferred. If two references disagree, retain both originals and identify the precise conflicting field. Correcting your working summary should not silently alter a supplier record or create agreement that nobody has given.
The proposed comparison is to ask each owner to state the calendar and dependency behind the milestone. Keep the question narrow enough for the reviewer to describe the method, the conditions and the observed difference. Preserve this limit: a calendar clarification does not guarantee production capacity or arrival. If the proposed work cannot answer the buying question, revise the plan before requesting more specimens or treating another file as conclusive. A useful next step should remove a stated uncertainty.
A bounded comparison plan
| Decision step | Case-specific action or condition | How to interpret the result |
|---|---|---|
| First check | identify how the stated period is counted | Check this against the identified source: dated estimate, counting basis and relevant working calendar. Record a missing item as open, with an owner, rather than filling it from memory. |
| Another possible explanation | approval time, production time and transit use different bases | This is an alternative to examine, not a conclusion. Ask which observation would support or weaken it before changing the material requirement. |
| Controlled comparison | ask each owner to state the calendar and dependency behind the milestone | Keep inputs and conditions explicit. A difference observed after several simultaneous changes cannot, by itself, identify which change caused it. |
| Keep this action on hold | the duration basis is unresolved | Do not let an unrelated deadline close the question. Continue independent preparation, but keep the dependent instruction visibly on hold. |
| Condition for continuing | the project records a dated sequence with qualified estimates | Name the permitted next action and its limits. Preserve the comparison and the reviewer’s actual wording with the handoff. |
Questions that resolve this particular problem
Does ten days always mean ten consecutive calendar days?
Ask the owner which basis applies. Do not assume a working-day estimate and an elapsed-day estimate describe the same interval.
Should transit and production durations be merged without explanation?
Keep the components and their dependencies visible. The project needs the owner’s current sequence, not a total that hides different calendars and starting events.
What if an approval arrives outside the stated cutoff?
Request a current estimate tied to the actual approval status and applicable cutoff. Do not assume the earlier slot or date automatically remains available.
Give the next team a usable decision
For this case, the receiving team needs to repeat each milestone’s calendar and starting event. Give that team the current reference and the comparison result together, with any unresolved condition beside the instruction. A short read-back should state what may proceed, what still waits and which version governs. Acknowledging receipt of a file is only the start of that check.
The prefilled record below is an exercise, not a completed order document. Replace its examples with project facts and name the reviewer before using it. Keep original evidence separately, date the actual outcome and retain superseded instructions as history. Discuss a Fred Textile programme through the official website; this worksheet does not confirm prices, certification, availability or delivery.
Illustrative diagnostic handoff: replace with project facts: Working days need an agreed calendar Identified evidence: dated estimate, counting basis and relevant working calendar First check: identify how the stated period is counted Alternative explanation to examine: approval time, production time and transit use different bases Bounded comparison: ask each owner to state the calendar and dependency behind the milestone Dependent action waiting: the duration basis is unresolved Condition for continuing: the project records a dated sequence with qualified estimates Receiving team read-back: repeat each milestone’s calendar and starting event Owner / date / actual result: ____________________