How do you calculate an order complexity score?

Multiply the impact, likelihood, and detection difficulty scores using a consistent scale. With impact 8, likelihood 6, and detection 5, the raw product is 240; the calculator reports a normalized order complexity risk score of 6.55 on its scale.

What is a good order complexity score?

Lower is better. Score every comparable RFQ on the same scale and set an action threshold from your own data - jobs in the top quartile typically warrant engineering review or a risk premium before you commit a price.

How is this different from a standard FMEA RPN?

The math is the same multiplicative logic - impact times likelihood times detection - but the failure mode here is order complexity (tolerances, materials, scope, schedule) rather than a part defect, applied at quote time instead of on the line.

Why multiply the three scores instead of adding them?

Multiplication amplifies orders that are bad on multiple dimensions at once. A high-impact problem that is also likely and hard to detect compounds into a much larger number than any single high factor, which is the risk you most want flagged.

What does the detection difficulty score capture?

How hard it is to catch the complexity problem before it causes damage - through review, prints, prototypes, or inspection. A high score (here 5) means the issue could slip through quoting and surface mid-production when it is expensive to fix.

Can I use this to decide whether to no-bid an order?

Yes. Set a threshold above which the order either gets a risk premium, mandatory engineering sign-off, or a no-bid. Consistent scoring makes that gate objective rather than reliant on whoever shouts loudest.

Contract Manufacturing, Job Shop Quoting & Make-to-Order calculator

Order Complexity Score Calculator

Order Complexity Score adapts the FMEA risk-priority-number method to job-shop quoting, turning the fuzzy sense that an order is hard to execute into a single comparable number. It multiplies how badly a complexity problem would hurt the job (impact), how likely it is to occur (likelihood), and how hard it would be to catch before it bites (detection difficulty). Estimators and sales engineers use it during RFQ triage to decide which make-to-order jobs need engineering review, a risk premium, or a polite no-bid. Because it uses a consistent scale across orders, it stops the loudest customer rather than the riskiest order from setting priorities.

What this calculator does

Score complexity risk for a make-to-order customer job.
prioritizing engineering review, estimator attention, and production planning for difficult jobs
It computes an order complexity risk score by multiplying impact, likelihood, and detection difficulty on a common scoring scale.

Formula used

order complexity risk score = order complexity impact score × complexity likelihood score × complexity detection difficulty score
Use the same scoring scale across comparable customer orders, RFQs, and make-to-order jobs.

Inputs explained

Order complexity impact score:
Complexity likelihood score:
Complexity detection difficulty score:

How to use the result

Use it during RFQ triage and order acceptance to rank make-to-order jobs by risk and decide which ones need engineering review or a risk premium.
Multiplicative RPN-style scores are ordinal, not linear - a 200 is not literally twice as risky as a 100, and equal scores can hide very different risk profiles, so review the component scores, not just the product.

Current U.S. benchmarks

The U.S. prime lending rate is 6.75% (Federal Reserve via FRED, 2026-07-02). Payback and financing math should start from today's rate, not a remembered one.

Common questions

How do you calculate an order complexity score? Multiply the impact, likelihood, and detection difficulty scores using a consistent scale. With impact 8, likelihood 6, and detection 5, the raw product is 240; the calculator reports a normalized order complexity risk score of 6.55 on its scale.
What is a good order complexity score? Lower is better. Score every comparable RFQ on the same scale and set an action threshold from your own data - jobs in the top quartile typically warrant engineering review or a risk premium before you commit a price.
How is this different from a standard FMEA RPN? The math is the same multiplicative logic - impact times likelihood times detection - but the failure mode here is order complexity (tolerances, materials, scope, schedule) rather than a part defect, applied at quote time instead of on the line.
Why multiply the three scores instead of adding them? Multiplication amplifies orders that are bad on multiple dimensions at once. A high-impact problem that is also likely and hard to detect compounds into a much larger number than any single high factor, which is the risk you most want flagged.
What does the detection difficulty score capture? How hard it is to catch the complexity problem before it causes damage - through review, prints, prototypes, or inspection. A high score (here 5) means the issue could slip through quoting and surface mid-production when it is expensive to fix.

Last reviewed 2026-05-12.