How to Write an RFQ for Automation: A Buyer's Template

By MillBrief Editorial · Published 2026-07-02 · Updated 2026-07-02

A request for quotation is the single document that decides whether your automation project succeeds or turns into a lawsuit. Get it right and every integrator bids on the same scope, so you can compare quotes honestly. Get it wrong and you buy an expensive machine that technically “works” but never hits rate. This guide walks the eight sections a manufacturing RFQ needs, with a copy-usable skeleton at the end. The through-line: specify outcomes and buyoff gates, not just hardware.

Tool: Our free RFQ generator assembles these sections into a ready-to-send document in your browser — no email, nothing stored.

Why does a detailed RFQ matter more than the quote?

A detailed RFQ matters because vague requirements — not price — are what sink projects. By our editorial estimate — consistent with widely cited requirements-engineering research — a majority of project failures trace to poor requirements gathering rather than budget, so ambiguity you leave in the RFQ becomes a change order later, at the integrator’s rates. The RFQ also forces apples-to-apples bidding: without a fixed scope, a low quote usually just means the integrator silently dropped acceptance testing, spares, or training. Follow a traceable path from requirements to buyoff — the well-known GAMP 5 validation model runs User Requirements Specification to FAT to SAT, and your RFQ should mirror that traceability.

How do I describe the current state?

Describe the current state so an integrator who has never seen your plant can quote without a site visit. Document the incoming part flow, upstream and downstream equipment, available floor space and utilities (compressed air, voltage, network drops), existing controls, and the operators who run the area today. If the line is batch or process, reference ISA-88 (S88) terminology so the control architecture is unambiguous. State your current throughput and manual cycle time as the baseline the new system must beat — acceptance targets only mean something against a measured starting point, and this is where a realistic OEE benchmark begins.

How do I specify parts, products, and tolerances?

Specify every part the cell must handle, with drawings, dimensional tolerances, weight, material, and every variant or SKU. This section is where handling systems, grippers, and vision requirements are actually decided, so incomplete part data is the most expensive omission in an RFQ. List the full variant matrix and the required changeover behavior — automatic, tool-assisted, or manual — and the target changeover time. Note allowable input-quality variation (burrs, flash, surface finish), because a cell tuned for perfect parts will jam on real ones. For scale, North American companies ordered 31,311 industrial robots worth $1.963 billion in 2024 (A3, 2025), about $62,700 per arm — useful order-of-magnitude context, but tooling and handling for your specific parts often cost more than the robot.

What cycle time and OEE targets should I set?

Set separate, defensible targets for cycle time, availability, and quality rather than one bundled number. World-class OEE is 85% or above, built from Availability >=90%, Performance >=95%, and Quality >=99.9% (OEE.com/Vorne Industries, 2024) — a benchmark originating with Seiichi Nakajima, the founder of TPM. Typical manufacturing OEE runs closer to 55-60% (OEE.com/Vorne Industries, 2024), so guaranteeing 85% on a brand-new line is often unrealistic; capital-intensive or continuous lines legitimately run lower by design. Define how OEE is measured, over what window, and with whose parts, or the number is unenforceable.

Cycle-time and OEE clauses have teeth because downtime is expensive: unplanned downtime costs the world’s 500 largest companies an estimated $1.4 trillion a year, roughly 11% of revenue, with automotive plants losing up to $2.3 million per hour (Siemens, 2024).

What acceptance criteria and buyoff gates do I need?

Require two named buyoff gates: a Factory Acceptance Test (FAT) at the integrator before shipment, and a Site Acceptance Test (SAT) at your plant after install. FAT verifies the system meets spec under controlled conditions; SAT confirms it survived shipping and runs in your real environment (Fabrico, 2026). A complete FAT covers four pillars — safety and compliance (guarding, electrical codes, ergonomics), performance verification (dry and wet runs, changeovers, stress tests), failure modes (E-stop, sensor block, power recovery), and documentation (schematics, spare-parts lists, manuals) (Fabrico, 2026). Tie payment retention to each gate: hold a meaningful percentage until SAT passes and the line sustains rate over an agreed run. See questions to ask a system integrator for how to probe these commitments during bidding.

What spares, training, and documentation should I require?

Require a recommended spare-parts list, operator and maintenance training, and a full documentation package as line items, not assumptions. Spares should include long-lead and wear items with part numbers and prices so you can stock the ones that would otherwise idle the line. Training must cover operators, maintenance, and controls staff — your in-house cost of that skill is real: U.S. median wages in May 2024 were $63,510 for industrial machinery mechanics and $70,760 for mechatronics technicians (BLS, 2024). Documentation should include electrical and pneumatic schematics, PLC and HMI source code, network diagrams, and O&M manuals. If the integrator will not hand over source code and drawings, treat that as a lock-in red flag.

How should I structure the timeline and commercial terms?

Structure the timeline as phased milestones and the commercial terms as a budget range tied to buyoff. Ask for lead time broken into design, build, FAT, ship, install, SAT, and ramp — a single delivery date hides risk. Robot supply is rarely the constraint: 542,000 industrial robots shipped globally in 2024 (IFR, 2025), with China alone installing 295,000; engineering capacity and your part readiness set the real schedule. On commercial terms, budget realistically — a common rule of thumb is at least 3x the arm price for turnkey delivery, 4x-6x for cells with inline gauging (Robotiq/BCG, 2024). Compare quotes on scope and rate transparency, not headline price. Integrator billing rates vary widely by region and seniority, and published integrator compensation benchmarks (CSIA Salary and Benefits Survey, 2024) are a useful sanity check; a suspiciously cheap quote usually means fewer hours, not better value.

A copy-usable RFQ skeleton

Use this outline as the table of contents for your RFQ; fill each section with your plant’s specifics.

# RFQ: [Project Name] — Automation Cell

## 1. Current State
- Part flow, upstream/downstream equipment
- Floor space, utilities (air, voltage, network)
- Existing controls / standards (e.g., ISA-88 for batch)
- Baseline throughput and manual cycle time

## 2. Parts, Products & Tolerances
- Drawings, dimensions, tolerances, weight, material
- Full variant/SKU matrix
- Changeover requirements + target time
- Allowable input-quality variation

## 3. Performance Targets
- Guaranteed cycle time (sec/part), per variant
- Availability % + how measured, over what window
- Quality: max defect/scrap rate + gauging method
- Combined OEE target (justified vs baseline)

## 4. Acceptance Criteria
- FAT at integrator: safety, performance, failure modes, docs
- SAT at site: run-at-rate over agreed period
- Payment retention tied to each gate

## 5. Spares, Training & Documentation
- Recommended spares list with part numbers + prices
- Operator / maintenance / controls training
- Schematics, PLC & HMI source code, network diagrams, O&M manuals

## 6. Timeline
- Phased milestones: design → build → FAT → ship → install → SAT → ramp

## 7. Commercial Terms
- Budget range, payment schedule tied to buyoff
- Warranty, response-time SLA, rate card for changes

## 8. Bid Format
- Scope-by-scope pricing, assumptions, exclusions, references

What are the most common RFQ mistakes?

The three most common RFQ mistakes are vague scope, missing acceptance criteria, and choosing on price alone. Vague scope leaves the definition of “done” to the integrator, which is why requirements problems drive most project failures. Missing acceptance criteria means you have no contractual basis to reject a line that runs slow or scraps parts — the FAT/SAT gates above are your only leverage. Choosing on price alone rewards the bidder who quietly cut spares, training, or testing. A fourth trap is over-specifying the hardware brand while under-specifying the outcome: tell the integrator the rate and quality you need, and let them own how to hit it. Sometimes the right answer is not to buy at all yet: if your process is unstable, your part quality varies wildly, or volumes are too low to amortize the cell, hold off and fix the fundamentals first — automating a broken process only produces defects faster. Before you even write the RFQ, decide what to automate first, understand what OEE actually measures, and sanity-check pricing against system integrator rates.