Requirements AnalysisThe Foundation of Every Efficient Procurement Decision
Procurement glossary · Updated · 7 min read
Also known as: Bedarfsermittlung, Bedarfsplanung, Bedarfsrecherche, Demand Analysis, Bedarfsfeststellung
Short answer
- Requirements analysis is the systematic identification and assessment of a company's procurement requirements.
- It clarifies the type, quantity, timing and quality of the requirement and checks its economic and technical plausibility.
- It forms the basis for specification, enquiry, ordering and replenishment planning across the entire procurement process.
Requirements analysis is the systematic process of identifying, structuring and assessing a company's specific procurement requirements. It stands at the beginning of every procurement chain and largely determines which materials, services or capital goods are needed, when, in what quantity and on what terms. Without a sound requirements analysis, businesses risk excess stock, emergency purchases at premium prices and unnecessary tied-up capital. Particularly in the B2B environment with long lead times and complex bills of materials, it is therefore a key control instrument for procurement.
Key facts
- Requirements analysis identifies the type, quantity, timing and quality of the requirement to be procured and is the preliminary stage of every ordering process.
- Typical sources are replenishment planning data, production plans, service requirements and investment projects.
- It distinguishes between primary (customer-driven) and secondary demand as well as consumption and additional requirements.
- In practice, a sound requirements analysis frequently reduces urgent orders and small-volume orders significantly and stabilises delivery dates.
- Digitalised requirements analyses use master data, consumption figures and forecasts rather than isolated spreadsheets.
- From a legal perspective, requirements analysis forms the basis for the specification and requirement specification document in the subsequent enquiry process.
Contents
- Definition: requirements analysis
- Methods and approach of requirements analysis
- Key KPIs and assessment of a requirements analysis
- Risks, sources of error and controls
- Requirements analysis and demand flow: operational implementation
- Current developments: digitalisation and AI in requirements analysis
- Typical metrics
- Practical example
- Conclusion
- Frequently asked questions
Definition: requirements analysis
Requirements analysis refers to the structured identification and assessment of a company's entire or partial procurement requirements within a defined period. It involves clarifying what is needed, in what quantity, by what deadline, at what quality and with what urgency.
Distinction from requirement identification and requirements planning
Requirement identification usually refers to the technical data basis, such as bill of materials explosion and consumption figures. Requirements planning translates this data into time-based planning horizons. Requirements analysis sits upstream: it checks whether the reported requirement is genuine, correctly specified and economically viable. It also answers the question of whether a requirement should be procured externally at all or alternatively covered by in-house production – here it directly touches upon the question of vertical integration.
Primary, secondary and additional demand
Primary demand results from sales planning, customer orders and framework call-offs, for example via a delivery schedule structure with series suppliers. Secondary demand follows from the bill of materials explosion: for each production lot, upstream products, purchased parts and packaging are required. Additional requirements cover samples, inspection equipment, maintenance and consumables. In practice, cleanly separating these requirement types is often the biggest pitfall, as otherwise service and production requirements collide in the same planning line.
Position within the procurement process
Requirements analysis is the first building block of the requisition logic: requirement identification, requirement confirmation, specification, enquiry, comparison, order. It provides the input data for order process optimisation and for subsequent supplier evaluation. Without a validated requirement, a Request for Proposal (RFP) comes to nothing because specification and quantity are unclear.
Methods and approach of requirements analysis
In practice, a multi-stage approach has proved its worth: identify requirement sources, validate data, consolidate requirements and translate them into decision-ready documentation. The method depends on the requirement type – consumables require different methods from capital goods or individual parts.
Data-based analysis for series and C parts
For series requirements, the analysis draws on inventory records, open orders, consumption figures from past periods and production programme data. Classic replenishment methods such as the reorder point or materials requirements planning logic derive point-in-time and quantity requirements from this. It is important to cleanse the data of obsolete stock, legacy parts and overstock from previous periods, otherwise historical errors are analysed along with everything else.
Project and capital investment requirements
For capital goods, plant and equipment or one-off projects, qualitative characteristics dominate: technical specification, acceptance criteria, installation and commissioning requirements. Here the requirements analysis often begins with a structured requirement specification in which the requisitioner and procurement jointly define requirements, boundary conditions and evaluation criteria. Only then is the procurement strategy derived.
Requirement consolidation and bundling
A key lever is consolidation across locations, projects and periods. Minimum requirements from several plants can be bundled into framework quantities, which improves negotiating leverage and minimum order quantities. Sustainability goals also come into play: for the sustainable category of packaging, for example, it is worthwhile taking a consolidated view of material specification, load carrier management and packaging reduction rather than individual site-based analyses.
Make-or-buy within requirements analysis
For every significant requirement, it should be assessed whether procurement or in-house production is the better option. Methods such as clean-sheet costing help to obtain a realistic cost picture of external production and compare it with own marginal costs. This assessment is part of the requirements analysis, not of supplier selection.
Key KPIs and assessment of a requirements analysis
The quality of a requirements analysis can be measured: via completeness, schedule adherence, stock development and the proportion of unplanned purchases. The following KPIs have established themselves in practice as meaningful control variables, although target values vary considerably by industry and replenishment type.
Requirement and inventory KPIs
Key figures are forecast or requirement adherence (deviation between planned and actual requirements), inventory coverage and the proportion of emergency or urgent orders of all orders. High urgent order ratios typically indicate inadequate requirements planning rather than supplier problems. The goods receipt lead time also provides feedback on whether planned delivery dates were realistic.
Process KPIs
At process level, the key figures are the duration from requirement notification to requirement confirmation, the proportion of fully specified requirement notifications and the cycle time to order release. In practice, long-planned requirements should be validated within a few working days; obstacles frequently arise from incomplete master data or repeated queries between the requesting department and procurement.
Risks, sources of error and controls
Faulty requirements analyses have an impact on several levels: incorrect quantities cause inventory costs or supply bottlenecks, incorrect specifications lead to returns and complaints, and unclear deadlines destabilise the entire supply chain. Controls should therefore take effect early and in a structured manner.
Typical sources of error
Common problems are excessive safety stock resulting from bad experiences, uncleansed legacy requirements, duplicate requirement notifications from different systems and technically over-specified parts that allow more expensive suppliers to qualify. Incorrectly maintained master data in inventory management also distorts the analysis in the long term. In the worst case, procurement orders parts that were long since replaced by design changes.
Controls and safeguards
Effective controls include the four-eyes principle for requirement confirmation, plausibility checks against consumption history and open customer orders, and regular cleansing of legacy and obsolete stock. For critical items, it is advisable to define safety time buffers and replenishment rules per category. For recurring supply problems, it should additionally be checked whether escalation levels such as a delivery reminder or delivery date monitoring form part of the downstream process.
Taking the supplier perspective into account
A realistic requirements analysis also takes account of supply capability: minimum order quantities, lead times, the availability of qualified sources on the Approved Vendor List (AVL) and capacity limits at suppliers. Requirements that cannot be met with suitable sources should be re-planned before the enquiry stage – not after failed bid negotiations.
Requirements analysis and demand flow: operational implementation
From the analysed requirement to stable procurement, the route leads via replenishment rules, call-off mechanisms and the structured ordering process. Requirements analysis provides the parameters with which operational systems can work automatically.
Call-off and replenishment mechanisms
For recurring requirements, the call-off order is a good option: partial call-offs are triggered from a framework agreement depending on actual requirements. The reorder point governs order timing for consumables, while safety time buffers absorb delays in replenishment. Requirements analysis provides the input parameters – consumption figures, replenishment lead times, lot sizes – for these mechanisms.
Interfaces to enquiry and ordering
The validated requirement flows into the ordering process and – for new parts or larger volumes – into the enquiry process. Here, the quotation, evaluation criteria and supplier list are defined on the basis of the specification. After award, requirements analysis indirectly also accompanies goods receipt, as the expected quantity and delivery date govern the incoming inspection and palletisation. In the event of deviations or quality defects, the returns process may follow, whose frequency also allows conclusions to be drawn about the quality of the original specification.
Current developments: digitalisation and AI in requirements analysis
Requirements analysis is becoming increasingly digitalised: requirement forecasting systems, AI-supported forecasts and automated master data maintenance reduce manual effort and improve forecast quality. Buyers are shifting from data collectors to data interpreters.
Forecasting systems and AI support
Modern systems combine consumption figures, order backlogs, seasonality and external signals into automated requirement forecasts. AI assistants now also support the preparation of enquiries and specifications from unstructured requirement information – for example when setting up an enquiry from text or drawing input. The underlying principles remain the same: consistent master data and clean process chains.
Integration across the supply chain
Increasingly, supplier signals also feed into requirements analysis: reported capacity bottlenecks, lead time changes or material alerts. Digital connections to suppliers and digital catalogues shorten the route from requirement notification to validated order. Sustainability data – for example on CO₂ factors, packaging requirements or load carrier management – is also being integrated into requirement assessment at an early stage rather than only being checked at the end of the ordering process.
Typical metrics
| Metric | Benchmark | Context |
|---|---|---|
| Requirement adherence | typically > 90 % | Proportion of requirement items without subsequent changes to quantity or delivery date |
| Urgent order ratio | typically < 5 % | Proportion of unplanned urgent orders of all orders; a high value indicates planning gaps |
| Requirement confirmation time | commonly 1–5 working days | Time from requirement notification to validated release |
| Proportion of obsolete stock | typically < 10 % of inventory value | Indicator of excessive or outdated requirements planning |
Typical practical benchmarks – they vary by industry, part and contract.
Practical example
A mid-sized mechanical engineering company with around 200 employees repeatedly reported excessive urgent order ratios and growing special stock levels for purchased parts. A systematic requirements analysis revealed: three plants were independently ordering identical standard components, and a significant proportion of the reported requirements stemmed from outdated bills of materials.
- Consolidating all standard part requirements from the three plants into bundled framework quantities
- Cleansing outdated bills of materials and introducing a central requirement confirmation based on the four-eyes principle
- Converting recurring individual quantities into call-off orders with a defined reorder point and safety time buffer
- Deriving a structured requirement specification for new parts in order to avoid specification queries during the enquiry process
Conclusion
Requirements analysis is the foundation of every economically sound procurement activity: it determines whether downstream processes such as enquiries, negotiation rounds and ordering are built on reliable data. Those who identify, validate and bundle requirements systematically reduce inventory costs, avoid emergency purchases and improve their negotiating position vis-à-vis suppliers. At the same time, it is not a one-off exercise but a continuously maintained process with clear controls. With increasing digitalisation and AI support, it is becoming a data-based control instrument – yet its quality remains tied to master data hygiene and process discipline. For mid-sized companies, it is therefore one of the most efficient levers in procurement management overall.
Frequently asked questions
What is requirements analysis in procurement?
Requirements analysis is the systematic identification and assessment of a company's procurement requirements. It clarifies the type, quantity, timing and quality of the requirement and checks whether it is genuine and economically justified. It forms the preliminary stage of enquiry, order and stock replenishment planning.
What is the difference between requirements analysis and requirements planning?
Requirements analysis assesses and validates what requirements actually exist and whether they are correctly specified. Requirements planning translates this validated requirement into time-based and quantity-based planning horizons. In practice the two go hand in hand, but they have different tasks.
How does a requirements analysis work step by step?
Typically in five steps: identify requirement sources (orders, production plan, service requirements), validate and cleanse the data, consolidate requirements, carry out a make-or-buy assessment and translate the analysed requirement into specifications and procurement strategy. This is followed by requirement confirmation and release into the ordering process.
What methods are available for requirements analysis?
For series and consumption requirements, data-based methods dominate, such as consumption analysis, replenishment rules and reorder-point logic. For capital investment and project requirements, qualitative methods take priority, in particular the requirement specification and clean-sheet costing. The two are frequently combined.
Which KPIs are measured in requirements analysis?
Key KPIs are requirement and forecast adherence, the urgent order ratio, inventory coverage, the proportion of obsolete stock and the lead time from requirement notification to order release. They show whether the analysis delivers realistic requirements or is systematically distorted.
Why is requirements analysis important for small and medium-sized enterprises?
Especially without large replenishment planning systems, the absence of requirements analysis quickly leads to tied-up capital, emergency purchases and wrong buying decisions. Even simple methods – requirement consolidation, master data maintenance, the four-eyes principle – deliver measurable improvements in stock levels and delivery dates in practice.
