Requirement SpecificationThe Foundation of Effective Procurement

Functional versus technical specification

With a functional specification, only the outcome the procured item must achieve is described – e.g. load capacity, service life or efficiency. The route to the solution remains open, giving suppliers room for their own proposals and buyers room for negotiation. The technical specification, by contrast, prescribes design, materials, tolerances and standards in a binding manner. It restricts supplier competition but secures interchangeability and reproducibility, especially for series and safeguarding parts.

• Functional specification: outcome-oriented, high design freedom for bidders
• Technical specification: standard- and drawing-bound, little latitude
• Hybrid forms combine both approaches, often for custom machine components

Distinction from RFQ and client's requirement specification

The client's requirement specification describes the client's requirements from the user's perspective; the contractor's specification describes the technical implementation by the contractor. The requirement specification is the overarching term in the procurement context and, depending on the procured item, may correspond to a client's requirement specification, a material list or a bill-of-materials position. It is transmitted to the market in the RFQ and referenced in a binding manner in quotations, framework agreements and purchase orders.

• Requirement specification = technical requirements description by the requisitioner
• RFQ = transmission of the specification to selected suppliers
• Purchase order/framework agreement = contractual fixing of the specification

Legal and procedural significance

The specification defines what constitutes fulfilment of the delivery obligation and is thus the reference point for incoming goods inspection, complaints and warranty. Incomplete or contradictory information frequently leads to change requests and price renegotiations. A final review by procurement is advisable, in particular for manufacturability, procurability and cost drivers, before the RFQ is released.

Requirement capture and clarification

The starting point is the structured recording of the requirement: quantities, deadline, context of use, interfaces and environmental influences. Checklists help capture forgotten requirements such as certifications, material traceability or packaging and palletisation requirements. For unclear points, a brief alignment discussion is recommended rather than repeated written correspondence – this noticeably shortens lead times.

• Checklist for technical, logistical and regulatory requirements
• Binding quantity and deadline information including planning horizon
• Question catalogue for interfaces to existing plant and systems

Standardisation instead of one-off production

Before any new specification, it should be checked whether an existing standard part, a series part or an existing specification can be reused. Standardisation reduces article variety, improves the negotiating position through higher pooling volumes and reduces inspection effort. A supplier landscape analysis complements this approach by showing which suppliers already fulfil comparable specifications economically.

• Reuse of existing drawings and material specifications
• Bundling similar requirements into a single RFQ
• Reconciliation with existing framework agreements before a new tender

Formalisation and data transfer

Specifications should be maintained in uniform templates with clear version control. Digital procurement systems transfer parts of the specification via catalogue data; an ETL procurement process (Extract, Transform, Load) transfers article and specification data from source systems to the procurement platform and reduces manual input. For standardised catalogue items, this often also increases the catalogue rate in practice, which reduces approval effort and misordered items.

Specification quality and return rate

The key metric is the proportion of rejected or revised specifications among all submitted requirements. In practice, values below ten per cent are considered a good target level; significant deviations indicate that requisitioners are inadequately trained or templates are incomplete. A regular deviation analysis across categories reveals systematic gaps.

• Return rate as a percentage of submitted requirements
• Number of clarification queries per specification
• Proportion fully transferred via system (without manual reworking)

Lead time and first-pass rate

The time from requirement notification to a ready-to-send RFQ (first-pass rate or lead time) shows how efficiently the process works. Long lead times often cause time pressure, which in turn impairs negotiating position and supplier selection. Procurement process optimisation starts here, for example through clear approval levels, mobile approval (P2P) for simple requirements and standardised templates.

• Lead time from requirement intake to RFQ issue in days
• First-pass yield: proportion of specifications approved without revision
• Proportion of RFQs generated automatically from catalogue data

Impact on procurement results

Good specifications have a measurable impact on downstream metrics: fewer claims for additional costs, lower complaint rates and better comparability of quotations. For capital goods, a cost driver analysis based on the specification can show which requirements cause which share of costs – the basis for a function-based cost analysis and, where appropriate, a value-analysis revision.

Typical sources of error

Common problems are overly ambitious tolerances, missing approvals, contradictory standard references and unclear inspection criteria. Logistical requirements are also often forgotten: delivery format, Incoterms (e.g. EXW or CIF), packing list requirements and packaging specifications belong in the specification, not only in the purchase order instruction. Unclear material traceability later leads to expensive recall and audit problems for safety-critical parts.

• Over- or under-defined tolerances and material specifications
• Missing information on approvals, standards and inspection documentation
• Forgotten logistics, packaging and delivery terms

Controls and the four-eyes principle

A structured review before approval – at least for critical requirements – significantly reduces errors: review by quality, possibly production and procurement, for feasibility, procurability and unambiguity. Critical specifications should be combined with a long-term supplier declaration (LLE) for relevant materials where regulatory documentation obligations exist. Documented approvals create transparency and keep complaints processes short.

• Four-eyes principle for critical requirements
• Checklist of mandatory information per commodity group
• Version control and change history for every specification

Market-related risks

Specifications that force a single product or process create supplier dependency and weaken competition. A market model analysis before drafting shows whether several suppliers can meet the requirements and where alternatives exist. For existing dependencies, a bow-tie analysis can help systematically assess the failure risks of the specified supply path and derive countermeasures.

Data-based and AI-supported specification

Modern systems suggest suitable specification building blocks from historical requirements, catalogue data and master data. Similarity search detects when an identical requirement has already been procured and avoids duplicates. This shortens creation, increases consistency and facilitates later evaluation through deviation analyses.

Sustainability and regulated supply chains

Sustainability requirements are making their way into the specification: requirements on recycled content, pollutant limits or a documented life cycle assessment (LCA) are increasingly becoming part of technical requirements. Packaging reduction can also be controlled via the specification, for example through requirements for reusable containers or material-saving packing instructions. Supplier declarations on materials and compliance, such as the long-term supplier declaration (LLE), are referenced as mandatory annexes.

• LCA and material documentation as mandatory annexes for critical commodity groups
• Anchoring packaging and palletisation requirements in the specification
• Maintaining compliance declarations with version control

Integration into procurement and finance processes

Specification data increasingly flows directly into ordering, goods receipt and finance processes. For larger investments and long-term procurement structures, financing models such as supply chain finance can be linked to defined specification and acceptance points. Supplier classification based on fulfilled specification requirements also helps steer the supplier base strategically.