RFQ Checklist for Planetary Gearhead OEM Projects: From Drawing to Pilot Lot

In recent OEM RFQ cycles, the biggest delay driver was not supplier response speed. It was assumption drift between buyer documents and supplier interpretation.

When two suppliers quote against different boundaries, the comparison table looks complete but the decision quality is weak. This page is the workflow we use to prevent that failure mode.

Executive Summary

A ready package has four properties:

• all suppliers quote on the same technical baseline
• acceptance is measurable before PO, not interpreted after delivery
• schedule risk is expressed as a range, not a single promise
• compliance documents are requested before commercial lock

If one of these is missing, quote comparison quality drops quickly.

1) Define the application boundary first

Send operating boundary, not only part names.

Minimum boundary fields:

• axis function and motion profile
• duty cycle and ambient conditions
• peak and continuous load windows
• service life target and maintenance strategy
• installation limits (space, orientation, cable path)

If these are missing, each supplier fills gaps differently and quote comparison becomes noisy.

2) Freeze interface revision and matching assumptions

Before requesting final commercial terms, provide a frozen technical interface set:

• flange standard and drawing revision ID
• shaft interface tolerance baseline
• motor model or NEMA compatibility target
• connector/cable assumptions if assembly is included

If interface revision is still floating, first-round quotes are often non-comparable by design.

3) Include a measurable acceptance package

At RFQ stage, define pass/fail evidence explicitly:

• backlash target window and method ID
• repeatability target and cycle count
• noise/vibration boundaries where applicable
• incoming/outgoing inspection evidence format

A quote without acceptance criteria is only a temporary estimate.

4) Add execution and commercial signals early

Technical fit alone does not protect schedule or landed cost. Include execution signals now:

• forecast rhythm and lot-size cadence
• prototype, pilot-lot, and MP timing plan
• packaging and shipment constraints
• customs/document package needed before PO release

This reduces late renegotiation on delivery and compliance scope.

5) RFQ gate flow (engineering + procurement)

6) RFQ readiness scorecard (buyer-side gate)

Use this as a pre-send gate. Target score: >= 85/100.

If your score is below 85, delay sending and fix gaps first.

7) Threshold matrix with owner and action

This table turns a "good practice" checklist into an executable gate.

8) Quote comparability matrix (use in supplier review)

Require suppliers to answer in the same structure.

A standardized matrix usually removes one full round of clarification.

9) Worked example: packaging line axis RFQ rescue

Scenario:

• application: indexing axis in packaging line
• target: pilot lot in 10 weeks
• first RFQ wave: 4 suppliers, all gave different assumptions

Initial score on the readiness card:

• boundary definition: 18/25
• revision control: 12/20
• acceptance criteria: 8/20
• schedule definition: 10/15
• compliance pack: 5/10
• response format: 6/10
• total: 59/100 (no-go)

Corrective actions in 4 business days:

• freeze drawing revision and interface references
• add backlash + repeatability method IDs
• enforce common quote template with deviation section
• require lead-time in min/typical/p95 format

Second-wave score: 89/100.

Observed outcome from the buyer team:

• quote loop rounds reduced from 3 rounds to 1 round
• technical comparison meeting reduced from 2 hours to 45 minutes
• shortlist decision moved ahead by 9 calendar days

10) Typical red flags and immediate action

11) RFQ email skeleton and PO clause snippet

Use this structure for faster first-pass quotes:

Subject: RFQ - Planetary Gearhead Program - [Project Code] - [Due Date]

1) Program scope
- Application: [axis function]
- Timeline milestone: [prototype date] / [pilot-lot date] / [MP date]

2) Technical package
- Drawing revision: [rev]
- Interface standard: [spec]
- Motor/NEMA target: [model or frame]

3) Performance and acceptance
- Ratio window: [x to y]
- Backlash target: [value + method]
- Repeatability target: [value + cycle count]

4) Quantity and delivery
- Prototype qty: [ ]
- Pilot-lot qty: [ ]
- MP cadence: [ ]

5) Compliance and documents
- Required statements: [origin, classification, test reports]

6) Quote response template required
- Unit terms + lead-time min/typical/p95 + deviation list

Suggested PO clause (short form):

Supplier quotation and acceptance remain valid only under RFQ package [ID-REV].
Any technical or compliance deviation must be listed in writing before PO award.
If deviation is undisclosed and found later, buyer reserves re-quote and delivery renegotiation rights.

12) Where to continue on PrecisionGearhead

• Products
• NEMA Compatibility
• Inertia Matching Calculator
• OEM Capabilities

When your package is ready, send it through Contact / RFQ.

13) Internal review worksheet (copy for your RFQ gate meeting)

Use this in a 30-minute cross-functional review before releasing RFQ.

Project:
RFQ Package ID-REV:
Meeting Date:
Owner:

1) Boundary completeness (0-25):
- Missing items:
- Action owner:
- Due date:

2) Revision and interface lock (0-20):
- Current drawing/BOM revision:
- Any unresolved drift:
- Action owner:

3) Acceptance method lock (0-20):
- Backlash method ID:
- Repeatability method ID:
- Open method gaps:

4) Quantity and timing clarity (0-15):
- Prototype qty/date:
- Pilot qty/date:
- MP cadence:

5) Compliance/doc completeness (0-10):
- Origin/classification declared:
- Missing documents:

6) Quote template consistency (0-10):
- Template sent to all suppliers:
- Deviation field mandatory:

Total score:
Decision: GO / NO-GO

14) Field Notes from Buyer Calls (Anonymized)

Q: We only have target ratio and annual quantity. Can we still send RFQ this week?

Yes, but send it as an assumption quote round only. Mark it as non-binding and set a 48-hour deadline to provide missing motion, duty, and acceptance inputs.

Q: Supplier writes "equivalent interface" without drawing revision. Is that acceptable?

Not for shortlist comparison. Treat it as a deviation until the supplier maps every interface point to your current revision ID.

Q: Our readiness score is 78, but the project is urgent. Should we proceed anyway?

If you proceed, clearly label this as pre-check only. Do not use that round for award decisions; close missing items and run one aligned comparison round first.

15) Anti-Patterns to Avoid

• comparing prices before revision and method are aligned
• mixing prototype assumptions and MP commitments in one quote table
• accepting one promised lead time without min/typical/p95 range disclosure

16) Failure Postmortem: Why a 2-Week RFQ Became a 7-Week Loop

Observed pattern from a packaging-axis project:

• week 1: RFQ released with ratio target but no acceptance method ID
• week 2: three suppliers returned quotes with different test assumptions
• week 3: procurement selected lowest quote, engineering rejected comparability
• week 4-6: re-quote rounds after revision and method alignment
• week 7: shortlist decision finally became usable

What would have prevented the slip:

• gate score threshold enforced before first RFQ release
• quote template with mandatory deviation field
• explicit no-comparison rule for quotes missing revision references

Sources and Last Verified

• AIAG Quality Core Tools (APQP, PPAP, FMEA, MSA, SPC)
• ISO 9001:2015 - Quality management systems requirements
• ISO 10007:2017 - Guidelines for configuration management

Last verified: May 11, 2026.

Final CTA

If you want a program-level review, email [email protected] or message WhatsApp +8618857971991.

To get a usable first response, include:

• application and axis function
• duty cycle and ambient conditions
• drawing revision and interface constraints
• target timeline and forecast quantity

FAQ

What is the biggest reason RFQs stall?

Missing boundaries and acceptance definitions force suppliers to quote with different assumptions, so buyers cannot compare apples to apples.

Should buyers send target ratio only?

No. Ratio-only requests create technical and commercial ambiguity that usually causes re-quote loops.

What should be frozen before pilot lot?

Freeze revision, CTQ checkpoints, sampling logic, and document ownership before pilot-lot release.

What score should block RFQ release?

Below 85/100, the package should be treated as no-go and corrected before supplier release.