Work backwards from the promised delivery date using stage durations, quantities and same-day cut-offs. Keep confirmed delay separate from missing confirmation. Show confirmed and unknown quantities, the latest safe handover, an owner and the next evidence deadline; do not invent a delay probability.
“In process” is not a delivery plan
For a fabric unit using outside dyeing and finishing, an order can be moving and still miss its promise. A useful morning review shows the last completed stage, the remaining route and the person who can resolve the next block.
The example here follows grey fabric through outside processing, inspection and dispatch. Weaving or garment assembly needs its own route. Do not apply a dyeing-stage checklist to a stitching line merely because both serve textile customers.
ERPNext's work-order documentation separates planned dates, material quantities and operation status. Those are useful inputs to a manual exception board too; a single percentage-complete field cannot replace them.
Calculate the latest acceptable handover
Illustrative dates: a buyer expects delivery on Friday 18 September 2026. The team plans one day for transport and one day for inspection and packing. Assuming the booked services operate on those days, processed fabric must reach the unit by Wednesday 16 September.
| Order | Confirmed receipt of remaining fabric | Latest acceptable receipt | Decision today |
|---|---|---|---|
| F-101 | 16 September | 16 September | No spare day; reconfirm quantity and vehicle |
| F-102 | 17 September | 16 September | One day late; evaluate a revised plan |
| F-103 | Not confirmed | 16 September | Obtain a dated commitment |
F-103 is uncertain, not automatically safe or late. F-101 has no buffer. A delayed receipt or inspection hold could move its dispatch. Keep that distinction visible rather than colouring both orders green.
Check quantities at the stage that matters
Suppose F-102 needs 600 accepted metres. The processor reports 450 completed, but only 400 have reached your unit, passed the required release check and been packed. The dispatch-ready position is 400, leaving 200 metres to clear. “75% processed” does not mean 75% ready to deliver.
Ask whether the customer can use a partial quantity and whether the remaining transport is practical. Split delivery is an option to agree, not a promise to make on the customer's behalf. Do not remove a quality check to make the date look achievable.
Give every exception an owner and a checkpoint
- Material: quantity, lot and availability date; purchasing owns a missing receipt confirmation.
- Processing: latest confirmed stage and remaining quantity; production follows up with the named processor.
- Quality: accepted, held and rejected quantities; the responsible checker records the release decision.
- Dispatch: packing readiness, booked pickup and customer receipt promise; dispatch confirms transport.
Use a short next step: “Production to confirm the remaining 200 metres by 2 pm.” The owner then records the answer, not simply “called.” For a small unit, these may be the same person wearing several hats; the checkpoints still matter.
Update the customer from the checked plan
“400 metre ready hain. Baaki 200 metre ki confirmation 2 baje milegi. Uske baad complete delivery date confirm karenge.” This is more useful than repeatedly saying the order is under process.
Save the original promise as well as the latest plan. Otherwise, moving the expected date can erase the delay from next month's review. Look for repeated causes—late material, unconfirmed processing or transport gaps—before deciding where to spend effort.
Use cut-off times and confirmation states
A calendar date is incomplete when dispatch, processor receipt or transport booking has a same-day cut-off. Record the relevant time zone and cut-off beside the latest acceptable handover. If a stage can finish after the carrier closes, count it against the next feasible movement, not the earlier date.
Separate confirmed delay from missing confirmation. “Processor has not replied” is not proof that processing is late. It is an evidence gap with an owner, contact action and response deadline. If a quantity is partly confirmed, show the confirmed and unknown quantities separately.
| Order | Promised delivery | Latest safe stage handover | Confirmed quantity | Unknown quantity | State | Owner and next check |
|---|---|---|---|---|---|---|
| SO-1842 | 18 Sep, customer location | 15 Sep 14:00 IST | 700 m ready | 300 m awaiting processor confirmation | Confirmation missing; delay not yet proven | Production owner to confirm by 12 Sep 16:00 IST |
If the cut-off passes without evidence, update the customer from the checked plan and state what remains unknown. Do not add a made-up probability score. This guide does not establish live delay prediction or automatic customer notification.
Questions you might ask
How can I spot textile orders that may be late?
Compare the confirmed stage dates and accepted quantities with the remaining route to the promised delivery. Treat absent confirmations as exceptions needing follow-up.
Should I use percentage complete to promise delivery?
Use it only alongside stage, quantity and date evidence. Processed material may still require inspection, packing and transport.