A bill of materials contains the core of a request for quotation, but not necessarily every fact needed to contact a supplier. It may identify items and quantities while leaving delivery location, timing, permitted alternatives or the response process unresolved. An assistant can organise the approved facts without filling those gaps with familiar-looking terms.
This article proposes an RFQ drafting workflow with a complete fictional example. Its purpose is a reviewable document. It does not issue a purchase order, decide that a substitution is acceptable or authorise external contact merely because the text looks ready.
Confirm the approved input pack
Start with the bill-of-materials reference, version and approval record. Link each line to its specification and unit of measure. A quantity of four assemblies is not the same as four component pieces; the draft should preserve the approved meaning rather than normalising it casually.
List the other required inputs: project reference, delivery location, required date or window, supplier recipients, clarification contact and the procurement team's approved response instructions. Some may come from different authorised records. Record their provenance and hold any item whose authority or relationship to the project is unclear.
OpenAI's file-search guide describes retrieval from uploaded files with citations. That can help locate specifications, but does not establish that the retrieved version is approved or that all bill-of-materials lines were found. Compare the approved inventory with the proposed RFQ line list. Source: OpenAI file search
Preserve scope and expose missing procurement choices
The agent should not add a brand, performance rating, warranty term or delivery condition that the approved pack does not contain. If the specification refers to an attachment, include the approved reference and check that the recipient may receive it. A source filename alone is not a substitute for the required technical description.
Define how alternatives are handled. If the owner permits suppliers to propose alternatives separately, state that approved instruction. If no decision exists, hold the relevant text and ask the owner. Do not silently allow substitutions to make the quotation process appear more flexible.
Likewise, do not invent a reply deadline. The procurement owner may need to coordinate the request with project timing and the approved supplier-contact process. The workflow should capture that missing input as a decision, not choose a date because an RFQ usually has one.
Reviewable RFQ draft and preparation contract
The following RFQ is a complete fictional example using approved fixture inputs. It is unsent. All organisations, references and requirements are invented for this demonstration.
Subject: Request for quotation: TEST-PROJECT-A approved equipment pack
To: approved test supplier recipient, to be inserted by the procurement reviewer before any send.
Please provide a quotation for the items below for TEST-PROJECT-A. The quantities and specifications come from approved fixture BOM-A version 2 and its linked specification records.
| Item reference | Required item and specification | Quantity and unit | Approved source |
|---|---|---|---|
| BOM-A-01 | Assembly type A meeting the attached fixture specification SPEC-A version 1 | Four complete assemblies | BOM-A version 2, line 1; SPEC-A version 1 |
| BOM-A-02 | Mounting kit B meeting fixture specification SPEC-B version 3 | Two complete kits | BOM-A version 2, line 2; SPEC-B version 3 |
Delivery is requested to the approved fictional Example Site receiving point by 15 November 2026, under the fixture project's confirmed requirement. Please state item prices, currency, tax presentation, delivery charges, availability and any exclusions explicitly. Do not replace the specified items silently. The fixture procurement owner has approved asking for alternatives only in a separate clearly labelled section, with differences from the required specification stated.
Please identify your quotation reference and version, proposed delivery date, offer-validity information and any clarification needed to quote the complete scope. The fixture owner has approved a response date of 10 November 2026 and the designated procurement contact route. These example dates and instructions are scenario inputs, not default terms for other requests.
This is a request for a quotation and does not confirm an order. The organisation's procurement review will assess the response through its approved process.
Preparation record: store project, BOM and specification references; approval evidence; delivery source; approved response instructions; recipient approval; included attachment versions; unresolved questions; draft version; reviewer and release status. Keep the record separate from the supplier-facing text where it contains internal notes.
Missing-input rules: hold any line missing quantity, unit or approved specification. Hold release if delivery information, recipient or response instructions are unresolved. An owner can approve a deliberate omission, but record that decision and its effect rather than pretending the missing input was found.
Acceptance fixtures: the complete example; an absent specification attachment; a quantity/unit conflict; duplicated BOM lines; and an unapproved proposed substitution. The complete case creates an unsent draft matching the input pack. The others produce explicit questions or holds. No fixture sends a message or creates a purchase order.
The output is accepted when the procurement reviewer can trace each requirement to approved input, inspect every attachment and approve the exact draft and recipient. A generated RFQ is not a completed procurement action.
Use structure to prevent unnoticed omissions
OpenAI's Structured Outputs guide documents constrained response formats and refusal handling. A draft-preparation schema can require each line's reference, specification, quantity, unit, source and uncertainty. It does not prove that the correct line was extracted or that the procurement terms are authorised. Source: OpenAI structured outputs
Validate required fields before rendering the RFQ. Compare the final line count and references with the approved BOM, and check quantity and unit together. If the model refuses or a document cannot be read, retain that status and hold the dependent draft rather than creating a polished incomplete request.
A duplicate check should use the approved line identity. Two similar descriptions may represent different items, while a repeated copy of one line should not double its quantity. Where that distinction is uncertain, the BOM owner resolves it before the draft is completed.
Work through normal, missing and duplicate inputs
In the hypothetical normal case, BOM-A provides the two approved lines, their units and linked specifications. The project record provides delivery and response requirements. The assistant prepares the RFQ above, and the reviewer checks its evidence and attachments. The draft remains unsent until the separate release process.
In a missing-specification case, SPEC-B is listed but unavailable. The assistant can identify the missing attachment and hold line two. It should not reconstruct its technical requirements from an older quote or a similarly named kit. The owner supplies the approved source or a recorded alternative decision.
In a duplicate case, the same BOM line arrives through two exports. Preserve the source references but include the line once under the verified identity rule. If the exports disagree on quantity, hold the conflict rather than summing them or choosing the larger figure as a precaution.
Keep sending and purchasing separate from drafting
OpenAI's function-calling guide separates a model's requested operation from application execution and its result. Use that distinction for RFQ release. A drafted email is not a sent message, and a sent RFQ is not an approved purchase. Source: OpenAI function calling
The application should enforce the actual recipient and release approval against the exact document version. Check existing send references before retrying an uncertain operation. If an approved attachment changes, review the affected draft again rather than attaching the new file under an old approval.
FAQ about drafting RFQs from bills of materials
Can the agent choose an equivalent item when the specification is missing?
Not in this proposed workflow. It can record a question or owner-approved alternative, but equivalence is a technical and procurement decision. Missing evidence should remain visible.
Should it copy every internal BOM note into the supplier request?
No. Use the approved supplier-facing scope and reviewed template. Keep internal risk, budget or negotiation notes in the restricted preparation record unless separately approved for the recipient.
What proves that the RFQ is ready to send?
The reviewer confirms approved inputs, exact text, attachment versions and recipient through the release process. Draft completeness alone does not establish communication authority or successful delivery.
If your business needs help defining this process, explore Custom AI agents, the wider AI automation services, and our custom-agent workflow guide. The agents and automation comparison and custom AI agent glossary explain the terms. To discuss your records and approval rules, get in touch.