Ask for the facts the estimator needs first

Make the minimum package easy to send

Require a buyer name and email, a part or project reference, a revision if one exists and at least one release quantity. Ask material and finish with a useful unknown option that creates a follow-up question rather than forcing an invented answer. Separate quote due date from required delivery date. A buyer can have both a near-term sourcing decision and a later production need. Capture annual usage as optional context, while keeping the quantity per release explicit so a forecast is not mistaken for a firm order.

Choose the attachment route deliberately

The sample collects filenames locally and saves a summary without uploading the drawings anywhere. A website administrator must connect an approved receiving service before offering real attachment submission. Selecting the controlled-data flag clears the local file selection and stops this ordinary route, directing the buyer to the shop’s approved contact. That checkbox is a routing aid, not a classification or security guarantee. Confirm permitted file types, size limits, access, notifications and record retention in the actual implementation; a public form should not promise a compliance status it cannot establish.

Leave qualification questions for the right stage

Do not demand banking details, a complete supplier survey, a long tolerance questionnaire or an exact annual forecast before a buyer can ask about a part. The drawing can carry many technical requirements, and an estimator can ask targeted questions after review. The field map can be copied into a form builder, including Google Forms, but technical-file receipt must use the shop’s approved storage and access process. Test a sample RFQ end to end so the named estimator receives the files, quantities and next action rather than a notification with no usable package.

• Review the package before committing price and date