A familiar scene in many Tier-2 and Tier-3 suppliers: a customer RFQ arrives with a tight deadline. Sales enters the basics into Excel, pings engineering for feasibility, asks procurement for material pricing, and forwards the drawing to the plant for a cycle-time estimate.
Two days later, nobody is “late” yet—but the quote still can’t be sent.
Not because the part is difficult. Because the quote package is incomplete: the latest drawing revision is unclear, the BOM assumptions aren’t aligned, the coating specification is missing, and the internal approval chain is waiting on someone who is on a shift, in a workshop, or simply not sure which version is valid.
In other words: RFQs don’t get stuck on pricing. They get stuck on documents, decisions, and exceptions.
The uncomfortable truth: RFQ turnaround is a workflow problem, not a competence problem
Most German automotive suppliers between 20 and 500 employees have the technical ability to quote well. They know their processes, machines, and suppliers. They understand tolerances, scrap risks, and capacity constraints. They’ve lived through enough customer escalation calls to know what happens when you commit to the wrong assumptions.
So why do RFQs still drag on?
Because the operational reality is that RFQ processing is rarely a defined end-to-end workflow. It is a chain of loosely connected tasks across departments—Sales, Engineering, Quality, Procurement, Plant, sometimes Finance—held together by email forwarding, file shares, and personal memory.
The quote is treated as a “commercial document.” In practice, it’s a manufacturing decision made under time pressure, based on document completeness and internal alignment.
And that is where the bottleneck hides.
Where quote turnaround really breaks down: the handoffs you don’t measure
Ask three people why RFQs take too long and you’ll get three answers:
- Sales: “Engineering is overloaded.”
- Engineering: “We don’t have clean inputs.”
- Procurement: “Supplier feedback takes time.”
- Plant: “We only see the drawing after two days.”
- Quality: “We’re asked too late about special characteristics.”
All of them can be true. But the common pattern is this: each department is working, yet the RFQ still waits—because it waits between departments.
Typical waiting points in German automotive suppliers:
- Document clarification loops: “Is this the latest drawing?” “What’s the applicable specification?” “Where is the customer standard?”
- Assumption misalignment: different interpretations of the same RFQ, different scrap rates, different batch sizes, different logistics assumptions.
- Version control friction: multiple PDFs with similar names; attachments spread across Outlook, Teams, shared drives.
- Approval latency: margin approval, investment approval (tooling, gauges), deviation approval from standard routings.
- Supplier response dependency: raw material, heat treatment, surface finishing, packaging; often requested ad hoc with incomplete specs.
- Capacity and feasibility checks: a quick “yes” becomes a “yes, but” after a plant review—requiring rework of cycle time and costing.
None of these issues are exotic. What’s striking is how often they are accepted as normal: “RFQs are just messy.”
They are messy—but much of that mess is process design.
The hidden cost isn’t just a lost RFQ. It’s the RFQ you answered with the wrong assumptions
Decision makers often evaluate RFQ performance in two ways:
- Did we win?
- Did we respond on time?
Both are incomplete.
The real financial risk is the quote that is sent quickly, wins business, and later turns into margin erosion because the quote was based on incomplete or wrong documentation. The quote that drifts through engineering and procurement without a clear audit trail tends to produce exactly the kind of surprises CFOs dislike:
- tooling costs underestimated or not contractually covered
- manual secondary operations not included in the routing
- test and inspection effort (especially for safety-related features) missing from the cost model
- packaging and labelling requirements overlooked
- special process approvals (PPAP timing, IMDS, traceability) not included
- transport assumptions wrong for call-off patterns
- energy or alloy surcharge mechanisms not reflected in terms
In a high-volume environment, a small error in cycle time or scrap can become a structural problem. In low-to-medium volume, the risk is different: engineering hours and change loops eat the margin.
What makes this particularly dangerous is that the error often starts with a document gap at RFQ stage.
Why manufacturers accept slow RFQ turnaround (and why it’s getting worse)
RFQ processing becomes “accepted pain” for three reasons.
1) It sits between departments, so it belongs to nobody.
Sales is measured on responsiveness and win rate. Engineering is measured on design work and production support. Procurement is measured on cost and delivery. Quality is measured on compliance and audit readiness. The RFQ workflow cuts through all of them, so the delays fall into the cracks.
2) The cost is mostly invisible.
The hours are distributed across many people: a few minutes here, an hour there. Nobody books “RFQ exception handling” as a cost center. Yet the total time is significant—especially when RFQ volume rises or when customers compress deadlines.
3) The document burden increases every year.
Even for relatively simple parts, customer requirements have expanded: traceability expectations, documentation retention, special characteristics, increasingly formal supplier onboarding requirements, and stricter PPAP expectations. Add to that ESG reporting questions and more frequent engineering changes.
The RFQ is no longer just “price and lead time.” It is a compliance and capability statement, backed by documents.
The practical bottleneck: RFQ data is unstructured, but your costing process expects structure
Most RFQs arrive as a bundle of unstructured inputs:
- PDF drawings, often scanned or with layers
- CAD files in different formats
- Excel sheets with price break tables
- customer standards, sometimes linked, sometimes attached
- email text with critical assumptions (“material to EN 10204 3.1 required”)
- last-minute clarifications sent in follow-up emails
- supplier specifications referenced by number, not attached
Your internal processes—routing, costing, margin review, feasibility checks—require structured data:
- material grade, tolerances, surface requirements
- annual volume, SOP/EOP, call-off pattern
- special characteristics and inspection effort
- process chain (e.g., turning + heat treatment + grinding + washing + packaging)
- required certificates (CoC, EN 10204), traceability level
- required approvals (PPAP level, run@rate, capability studies)
- logistics and packaging requirements
If the RFQ workflow doesn’t convert unstructured customer input into structured internal assumptions quickly and consistently, people compensate manually. They read, retype, copy/paste, interpret, and chase.
That is where turnaround time disappears.
Symptoms you can see on the shopfloor and in the month-end close
RFQ delays are often discussed as “commercial.” The operational consequences show up elsewhere.
In operations and plant management:
- last-minute feasibility checks that interrupt production support
- costing based on “standard cycle times” that don’t reflect actual constraints
- late involvement of process engineering, leading to rework after nomination
- tooling or gauge needs discovered too late, stretching launch timelines
In procurement and supply chain:
- supplier requests sent without complete specifications, triggering back-and-forth
- unplanned freight assumptions because packaging and logistics were unclear
- missing supplier documentation expectations (CoC, material certificates), causing later receiving/quality friction
In quality:
- PPAP planning starts with unclear requirements because RFQ assumptions weren’t documented
- special characteristics not flagged early, creating inspection and measurement surprises
- traceability obligations underestimated (label content, batch tracking, retention)
In finance:
- margin approvals pushed to the last minute, increasing risk of underpricing
- inconsistent cost models across plants or product lines
- later commercial disputes because quote assumptions weren’t captured in an auditable way
RFQs are upstream. When the upstream process is inconsistent, downstream departments pay for it—often months later.
What “good” looks like: RFQ processing as a controlled manufacturing workflow
The strongest RFQ processes in the German supplier landscape share a mindset: quoting is treated like a production workflow—standardized, measured, and designed for exceptions.
Not every RFQ needs the same effort. But every RFQ needs the same control points.
A pragmatic target state usually includes:
- a defined RFQ intake and classification (standard vs. complex vs. high-risk)
- a single place where the RFQ package lives (not in personal inboxes)
- clear ownership of assumptions (who decides, who approves, who documents)
- standard checklists tied to part families and processes
- measurable KPIs that reveal where waiting occurs
This is less about software and more about discipline.
Step 1: Classify RFQs early to avoid treating everything like a special case
A common waste pattern is running every RFQ through the “gold-plated” path.
Instead, classify within hours, not days:
- Repeat / similar part: reuse routing templates, standard material logic, known suppliers
- Variant with limited change: focus engineering only on the deltas (tolerances, material, coating)
- New process or new customer requirement: full feasibility and risk review
- High compliance load: higher involvement of quality and documentation early (PPAP, traceability, certificates)
The purpose is not to reduce diligence. It is to match effort to risk.
Step 2: Standardize the quote package—especially the assumptions
Many disputes and margin surprises begin with undocumented assumptions.
A robust RFQ workflow forces a short list of explicit assumptions, such as:
- applicable drawing revision and customer standard list
- material specification and certificate requirement (e.g., EN 10204 3.1)
- inspection scope (including special characteristics)
- packaging and labelling requirements
- logistics model (Incoterms, call-off pattern, delivery frequency)
- tooling and gauging scope and payment terms
- PPAP level and timeline expectations
These assumptions should be visible to everyone involved and included in the quote response, where appropriate.
Step 3: Replace email forwarding with structured handoffs
Email is not a workflow tool. It is a messaging tool.
In many suppliers, RFQ work is effectively a relay race run through Outlook:
- Sales forwards to engineering
- engineering forwards to plant
- plant replies with a number
- procurement is copied late
- quality is asked when the deadline is near
The predictable result: missing context, repeated questions, and version confusion.
Structured handoffs can be simple:
- a single RFQ record with assigned tasks and deadlines
- one controlled folder or workspace per RFQ
- clear naming conventions for files (drawing revision included)
- a standard form for cycle-time estimates and routing assumptions
If your ERP environment is SAP, Microsoft Dynamics, proALPHA, abas, APplus or a mix with DATEV on the finance side, the key is not to force every RFQ detail into the ERP too early. The key is to ensure that the information feeding ERP costing and item creation is consistent and traceable.
Step 4: Build a supplier response mechanism that doesn’t depend on heroics
Procurement often becomes the pacing item because supplier feedback is uncertain. But suppliers can only respond fast when they receive complete inputs.
Two practical improvements:
- Standard supplier request templates tied to categories (material, heat treatment, surface finishing, packaging). Include the same minimum data every time.
- Defined lead times for supplier quotes and an escalation rule when they are missed.
This is not about squeezing suppliers. It’s about reducing rework by sending a complete specification once.
Step 5: Use KPIs that identify waiting time, not just throughput
Many companies track RFQ volume and win rate. Fewer track where time is lost.
Useful KPIs for RFQ processing include:
- RFQ turnaround time (received to quote sent), segmented by RFQ type
- Engineering response time (task assigned to feasibility completed)
- Procurement response time (supplier request sent to supplier quote received)
- Exception rate (RFQs requiring rework due to missing/changed inputs)
- Clarification loop count (how many times customer or internal teams had to clarify)
- Quote rework hours (time spent after “first complete draft”)
- Approval latency (time waiting for internal approvals)
These KPIs are not for blame. They are for identifying systemic bottlenecks.
The “accepted normal” that deserves to be challenged
In many suppliers, slow quote turnaround is treated as inevitable because “customers are chaotic.”
But the bigger issue is internal: manufacturers often run RFQs with the same informal document habits they used 15 years ago, while the documentation burden has doubled.
The accepted normal looks like this:
- “We’ll start with what we have and fill the gaps later.”
- “Engineering will figure it out.”
- “Procurement will chase the suppliers.”
- “Quality will review at PPAP.”
That approach can work—until it doesn’t. Typically, it fails when RFQ volume rises, when a key person is absent, or when customers compress decision cycles.
The companies that improve are not necessarily the ones with the most staff. They are the ones that reduce the dependency on individual knowledge by tightening the document and decision flow.
Practical possibilities: tightening the RFQ workflow without overengineering it
For companies in the 20–500 employee range, the most reliable improvements are often “unsexy”:
- a single RFQ intake channel (not five different email addresses)
- one RFQ owner accountable for completeness, not just submission
- a clear definition of what “RFQ complete” means internally
- standardized templates for routing/costing inputs
- an agreed escalation path when deadlines are at risk
- a short weekly RFQ review that focuses on stuck items, not on status presentations
These measures reduce exception handling. And in RFQs, exception handling is the real cost driver—because it interrupts engineering and plant work that should be focused on production support and continuous improvement.
Where automation actually fits: reduce manual reading, retyping, and chasing
Once the workflow is defined, a modern approach can reduce the most time-consuming manual steps: extracting data from messy RFQ packages, checking completeness, and routing tasks to the right people with the right context.
This is where manufacturing document automation becomes relevant—not as a replacement for engineering judgment, but as a way to reduce avoidable admin work:
- reading and classifying incoming RFQ documents (drawing, BOM, spec, email text)
- extracting key fields (part number, revision, quantities, material spec references)
- flagging missing documents (e.g., referenced standards not attached)
- matching customer requirements to internal checklists (e.g., CoC, EN 10204 certificates, PPAP level)
- keeping version history and an auditable trail of what changed and when
Some suppliers are also exploring AI-assisted document understanding to speed up the “first pass” on RFQ packages—so engineers spend their time on feasibility and risk, not on hunting for the right PDF.
Platforms such as OtoDocs are one example of how document intelligence can support RFQ processing when integrated into a controlled workflow. If you want to understand the broader approach, the team behind OtoLab’s document intelligence work provides context on how manufacturing documents can be captured, interpreted, and routed without turning the process into an IT project that never ends.
The key point is simple: automation only helps after you have agreed what “good” looks like. Otherwise, you risk automating the same chaos—just faster.
When RFQ workflows are treated with the same seriousness as production workflows—clear inputs, clear owners, measurable exceptions—faster and more accurate responses become a repeatable operational outcome, not a last-minute sprint driven by individual heroics.
Hashtags