Field note / Spring RFQ intake

A spring RFQ checklist that preserves what the customer supplied.

The goal is not to make the customer engineer the spring. It is to collect enough attributable information for your team to review the request and own the next decision.

Use this as an intake design reference, not an engineering rulebook. The right fields vary by spring type, application, customer, and your own operating procedure. RFQ/Front keeps that procedure under the manufacturer’s control.

1. Request identity

  • Customer company, contact, and reply path
  • Customer RFQ or project number
  • Requested response date and target delivery context
  • New request, repeat order, replacement, or revision

2. Supplied technical context

  • Spring type: compression, extension, torsion, constant force, wire form, or other
  • Customer-supplied dimensions and units
  • Material or finish when specified by the customer
  • Load, rate, travel, environment, or application details the customer chose to provide
  • Applicable specification, certification, testing, or compliance references

Keep each normalized value linked to the email, form field, drawing note, spreadsheet cell, or other source where it appeared. A supplied value is not the same thing as an approved engineering decision.

3. Files and evidence

  • Drawing, print, CAD file, sketch, or photograph
  • File name, upload time, sender, and content digest
  • Revision identifier visible inside the file
  • Spreadsheet or document containing quantities and commercial notes
  • Earlier revision retained as superseded evidence rather than silently overwritten

4. Quantity and commercial request

  • Requested quantity or quantity breaks
  • Prototype, sample, or production context
  • Packaging, labeling, delivery, or documentation requests supplied by the customer
  • Any explicit target date or commercial constraint—clearly labeled as customer-supplied

5. Intake flags before estimator review

  • A field required by your procedure is absent
  • Two supplied sources disagree
  • The email references a newer revision than the attached file
  • Units are missing or mixed
  • A quantity, date, or specification is ambiguous
  • The request asks for engineering or manufacturability judgment that must be assigned to a qualified person

6. Estimator handoff

A useful handoff should answer: what arrived, which source supports each supplied value, what changed, what is missing or conflicting, who owns the next clarification, and whether your procedure allows estimating work to begin.

It should not silently select material, approve design, certify manufacturability, calculate cost, or issue final pricing.

Sources and scope

This checklist was informed by publicly available quote guidance and request forms from custom spring manufacturers, including Southern Precision Spring, Coiling Technologies, and Master Spring, observed August 5, 2026. It is an intake framework, not a claim that every shop requires the same inputs.