How do you calculate an RFQ complexity score?

Multiply the three ratings: severity × occurrence × detection. With 6 × 4 × 3 the raw product is 72, which the tool normalizes to a 4.55 score on its scale for comparison across RFQs.

What do severity, occurrence, and detection mean for an RFQ?

Severity is how much a missed requirement hurts margin, occurrence is how often that complication appears in this kind of work, and detection is how reliably your review catches it before the quote goes out — lower detectability means higher risk.

What is a high RFQ complexity score?

On a consistent scale, the top quartile of scores are your triage candidates. Absolute thresholds matter less than rank order — the highest-scoring RFQs in your queue are the ones to route to senior review.

How is this different from an FMEA RPN?

It uses the same severity × occurrence × detection logic as an FMEA risk priority number, applied to estimating risk rather than failure modes — so the same caveats about scale discipline apply.

Why normalize instead of using the raw product?

The raw product (72 here) spans a wide, uneven range that overweights extreme ratings. Normalizing to a bounded score keeps results comparable and prevents one maxed-out rating from dominating triage.

Should detection be scored high or low for an easy-to-catch issue?

Score detection low when the issue is easy to catch and high when it slips past review — high detectability ratings raise the risk score because the problem is likely to reach the customer in the quote.

Manufacturing Sales Engineering, Estimating & Quoting Operations calculator

RFQ complexity score Calculator

RFQ complexity score adapts FMEA-style risk priority thinking to the quoting front door, ranking each incoming request by how hard and risky it is to estimate accurately. You rate technical severity (how badly a missed detail hurts margin), occurrence (how often that kind of complication shows up), and detectability (how easily your process catches the issue before the quote ships), then multiply them. Sales engineers and estimating leads use the resulting score to triage RFQs — routing the highest-risk requests to senior estimators and engineering review instead of letting them flow through on autopilot. It turns gut feel about a 'nasty quote' into a comparable, defensible number.

What this calculator does

Estimate rfq complexity for manufacturing sales engineering, estimating and quoting operations using production-ready inputs so teams can rank risks and decide which issue needs containment, controls, or escalation first.
Use it when rfq complexity in manufacturing sales engineering, estimating and quoting operations needs a defensible ranking against other manufacturing sales engineering, estimating and quoting operations risks for the next review.
It multiplies severity, occurrence, and detection ratings into a single RFQ complexity risk score so requests can be ranked and triaged consistently.

Formula used

Rfq complexity risk score = rfq complexity severity score × rfq complexity occurrence score × rfq complexity detection score
Use the same scoring scale across comparable rfq complexity risks.

Inputs explained

RFQ technical severity rating:
RFQ occurrence-frequency rating:
RFQ estimating-detectability rating:

How to use the result

Use it at RFQ intake to decide which quotes get senior estimators, engineering review, or a no-quote decision before any costing effort is spent.
Multiplicative scores are only comparable when everyone uses the same rating scale and anchors — undefined scales make scores meaningless across estimators.

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.
U.S. manufacturing runs at 75.6% of capacity (Federal Reserve, May 2026). New factory orders are up 2.3% year over year (Census).

Common questions

How do you calculate an RFQ complexity score? Multiply the three ratings: severity × occurrence × detection. With 6 × 4 × 3 the raw product is 72, which the tool normalizes to a 4.55 score on its scale for comparison across RFQs.
What do severity, occurrence, and detection mean for an RFQ? Severity is how much a missed requirement hurts margin, occurrence is how often that complication appears in this kind of work, and detection is how reliably your review catches it before the quote goes out — lower detectability means higher risk.
What is a high RFQ complexity score? On a consistent scale, the top quartile of scores are your triage candidates. Absolute thresholds matter less than rank order — the highest-scoring RFQs in your queue are the ones to route to senior review.
How is this different from an FMEA RPN? It uses the same severity × occurrence × detection logic as an FMEA risk priority number, applied to estimating risk rather than failure modes — so the same caveats about scale discipline apply.
Why normalize instead of using the raw product? The raw product (72 here) spans a wide, uneven range that overweights extreme ratings. Normalizing to a bounded score keeps results comparable and prevents one maxed-out rating from dominating triage.

Last reviewed 2026-05-12.