SoR (Statement of Requirements)
Buyer document describing the requirement; can be either an alternative term for specification or an early-stage document preceding ITT.
Definition
SoR stands for Statement of Requirements. The term is used in two related but distinct ways. First, as an alternative label for the Specification section of an Invitation to Tender -- the detailed description of what the supplier must deliver. Second, as an early-stage document preceding the formal ITT, sometimes shared with potential suppliers during Pre-Market Engagement for feedback before the procurement is finalised.
How it works in practice
Where SoR is used as a specification synonym the substantive content is the same as a specification: functional requirements, non-functional requirements, performance levels, constraints, and acceptance criteria. The choice between "Specification" and "SoR" is often a buyer terminology preference rather than a substantive difference. Where SoR is used as an early-stage document the content is typically less detailed than a final specification: indicative scope, high-level requirements, and questions where the buyer wants supplier input. SoR feedback in this mode is similar to RFI engagement; suppliers respond with substantive but concise commentary on the proposed scope. Suppliers should match their response shape to the SoR shape: a final-specification-style SoR wants the same kind of detailed bid response as an ITT specification; an early-stage SoR wants higher-level engagement with the scope. The distinction is most relevant in central government and large outsourcing procurement where SoR-style engagement happens before formal ITT issue. In smaller procurements the SoR concept is usually folded into the ITT specification without a separate document.
Common questions
Is SoR the same as a specification?
In many contexts yes; the terms are used interchangeably. Some buyers use SoR specifically to mean an early-stage document preceding the formal specification, used for pre-market engagement and supplier feedback. The buyer's usage is normally clear from context.
How do I respond to an SoR shared at pre-market engagement?
With substantive but concise feedback on the proposed scope: areas you can deliver, areas that need clarification or adjustment, indicative timing and resourcing, any constraints the buyer should factor in. Treat it as a structured conversation rather than a full bid response.
Are SoRs binding on the buyer?
No more than a specification is. The SoR describes the requirement but the buyer can refine it before the formal procurement. Material changes between SoR and ITT are normal; suppliers should respond to whatever is in the formal ITT regardless of earlier SoR content.