Machine Shop RFQ Form Planning Kit

KriXis · October 14, 2026. Plan the first request, drawing route and estimator handoff.

Save before closing: entries are not automatically stored after closing. Complete the worksheet, then use Print / Save to PDF. Keep customer and technical data in your approved systems; use non-confidential summaries or internal references here.

1. Purpose and owners

Public service / RFQ page URLBuyer action this route should startInquiry owner / backupEstimator / technology reviewer

Describe the first useful request and what the team should do next.

2. Field inventory

Record eight proposed or existing fields. Explain the decision each supports. Required fields should have a specific purpose; allow uncertainty when appropriate.

Field 1

Visible label / input typeRequired or optional / reason

Routing or review decision supported; allowed unknown answerHelper text, example and validation/error wording

Field 2

Visible label / input typeRequired or optional / reason

Routing or review decision supported; allowed unknown answerHelper text, example and validation/error wording

Field 3

Visible label / input typeRequired or optional / reason

Routing or review decision supported; allowed unknown answerHelper text, example and validation/error wording

Field 4

Visible label / input typeRequired or optional / reason

Routing or review decision supported; allowed unknown answerHelper text, example and validation/error wording

Field 5

Visible label / input typeRequired or optional / reason

Routing or review decision supported; allowed unknown answerHelper text, example and validation/error wording

Field 6

Visible label / input typeRequired or optional / reason

Routing or review decision supported; allowed unknown answerHelper text, example and validation/error wording

Field 7

Visible label / input typeRequired or optional / reason

Routing or review decision supported; allowed unknown answerHelper text, example and validation/error wording

Field 8

Visible label / input typeRequired or optional / reason

Routing or review decision supported; allowed unknown answerHelper text, example and validation/error wording

3. Drawing-sharing route

Supported initial route: verified uploader, portal or prior discussion?Accepted types and size limits — source, test date and reviewerStorage location reference, recipient access and retention ownerValidation, scanning and other controls — technical owner and verification referenceInstructions for buyers without a ready drawing or needing a prior transfer discussion

4. Visitor messages

Opening instructions: scope, preparation and next actionMissing or invalid field messageUnsupported or oversized file messageReceipt message: what happened, what follows and contact alternative

5. Handoff and measurement

Application receipt record — reference and observed successNotification destination — intended owner, backup and observed receiptEstimator assignment — where ownership and next action are recordedTracking events and actual payload review — exclude contact/project/file contents

6. Verification log

Use approved, non-confidential test information. Check each stage separately.

Test record 1

Date / viewport / device or keyboard pathTest case / intended result

Observed result; request reference; unresolved issueNext task / owner / due date / retest result

Test record 2

Date / viewport / device or keyboard pathTest case / intended result

Observed result; request reference; unresolved issueNext task / owner / due date / retest result

Test record 3

Date / viewport / device or keyboard pathTest case / intended result

Observed result; request reference; unresolved issueNext task / owner / due date / retest result

Test record 4

Date / viewport / device or keyboard pathTest case / intended result

Observed result; request reference; unresolved issueNext task / owner / due date / retest result

7. Publishing and maintenance checklist

Primary action and service scope accurately described Every required field has a routing or review reason Optional and undecided answers are clear Visible labels and field associations checked Drawing instructions match the verified route Receipt wording distinguishes application success from review Inquiry owner and backup are assigned Desktop, 390px phone layout and keyboard path checked Missing-field and upload-error behavior checked Authorized request observed at intended destination Tracking payloads reviewed for unnecessary buyer data Review trigger assigned after site, mail or staffing changesHighest priority change / responsible owner / next review date

Read the RFQ form guide · Request a review discussion