How do you calculate an apparel OTD risk score?

Multiply the severity, occurrence, and detection scores together. With severity 6, occurrence 4, and detection 3 you get a risk priority number that flags the order line for review.

What is a good apparel OTD risk score?

Lower is better. On a 1-10 per-factor scale, scores under roughly 100 are usually monitored, while higher scores demand active mitigation. The right threshold depends on the scale and tolerance your sourcing team agrees up front.

What do severity, occurrence, and detection mean here?

Severity is how much a late delivery hurts (markdowns, cancelled orders). Occurrence is how frequently that delay cause shows up. Detection is how likely you are to catch it before it bites; harder-to-detect risks score higher.

Why use FMEA-style scoring for on-time delivery?

It forces a structured conversation about each delay cause instead of reacting to whatever blew up last. The same scale across all order lines lets you Pareto your worst OTD risks and assign owners.

Should detection be scored high or low when we catch problems early?

Score detection low when you reliably catch a problem early, because good detection reduces risk. A high detection score means the problem usually surprises you, which raises the overall RPN.

How is this different from a supplier OTD percentage?

OTD percentage is a backward-looking score of what already shipped late. This risk score is forward-looking: it predicts and prioritizes which causes are most likely to make a future order miss its date.

Textiles & Apparel Manufacturing calculator

Apparel OTD Risk Score Calculator

The Apparel OTD Risk Score is an FMEA-style risk priority number (RPN) for the things that make a garment order ship late, such as fabric lead time, a bottleneck operation, or a missed quality gate. Sourcing managers, production planners, and merchandisers in cut-and-sew operations use it to triage which late-delivery risks deserve mitigation before a season's bookings lock in. By multiplying how bad a miss would be, how often it happens, and how likely you are to catch it early, it turns gut feel about a risky style or vendor into a comparable number. That lets a planning team rank dozens of order-level risks and spend buffer stock and expediting budget where it actually moves the ship date.

What this calculator does

Estimate apparel otd risk for textiles and apparel manufacturing using production-ready inputs so teams can rank risks and decide which issue needs containment, controls, or escalation first.
Use it when apparel otd risk in textiles and apparel manufacturing needs a defensible ranking against other textiles and apparel manufacturing risks for the next review.
It multiplies severity, occurrence, and detection scores into a single apparel on-time-delivery risk priority number.

Formula used

Apparel otd risk score = apparel otd risk severity score × apparel otd risk occurrence score × apparel otd risk detection score
Use the same scoring scale across comparable apparel otd risk risks.

Inputs explained

Apparel otd risk severity score: Score the impact using the same FMEA, quality, safety, delivery, or business-risk scale used by the team.
Apparel otd risk occurrence score: Score how often the issue appears using defect history, field data, maintenance records, or supplier performance.
Apparel otd risk detection score: Score how likely current controls are to catch the issue before shipment, use, or customer impact.

How to use the result

Use it during pre-production planning, vendor onboarding, or seasonal booking reviews to rank which OTD risks to mitigate first.
RPN math means a high score can come from any one factor, and equal scores can hide very different risk shapes, so always read the three inputs alongside the total.

Common questions

How do you calculate an apparel OTD risk score? Multiply the severity, occurrence, and detection scores together. With severity 6, occurrence 4, and detection 3 you get a risk priority number that flags the order line for review.
What is a good apparel OTD risk score? Lower is better. On a 1-10 per-factor scale, scores under roughly 100 are usually monitored, while higher scores demand active mitigation. The right threshold depends on the scale and tolerance your sourcing team agrees up front.
What do severity, occurrence, and detection mean here? Severity is how much a late delivery hurts (markdowns, cancelled orders). Occurrence is how frequently that delay cause shows up. Detection is how likely you are to catch it before it bites; harder-to-detect risks score higher.
Why use FMEA-style scoring for on-time delivery? It forces a structured conversation about each delay cause instead of reacting to whatever blew up last. The same scale across all order lines lets you Pareto your worst OTD risks and assign owners.
Should detection be scored high or low when we catch problems early? Score detection low when you reliably catch a problem early, because good detection reduces risk. A high detection score means the problem usually surprises you, which raises the overall RPN.

Last reviewed 2026-05-12.