Define what matters in the first reply
State the part function and acceptance gate first. A useful reply requires clear expectations for fit, tolerance, finish and timing.
Build a minimum complete file stack
Share one clear file set and key metadata. Overloading an intake with incomplete files makes review slower, not faster.
Set process and quality boundaries
Mark whether this is prototype, pilot, repeat order or supplier rescue and what quality documents are expected after quote.
Define revision logic
If the response will need a second version, list the first acceptable change window and owner responsibility.
| Input | Why it matters |
|---|---|
| Function | Cosmetic, structural, protective or assembly-linked usage determines priority. |
| Geometry | Dimensions, holes, bend requirements and interfaces. |
| Materials and finish | Material, surface treatment and cosmetic expectations. |
| Risk and timing | Tolerance certainty, timeline and launch pressure. |
| Sample goal | Whether first sample validates fit, function or visual impact. |
Next step
Use the guide to prepare a cleaner inquiry, then attach the best available files through the RFQ form. If an item is unknown, say so directly so the first reply can separate quote assumptions from confirmed requirements.