When a buyer sends an RFQ to suppliers, the quality of the supplier response depends heavily on how clearly the buyer has described what should be delivered.
If the specification is unclear, suppliers will make assumptions. If the specification is too narrow, competition may be reduced. If the specification is too technical without explaining the real need, the buyer may block better supplier solutions. If the specification is too general, the buyer may receive quotations that cannot be compared.
This is why specification work is one of the most important parts of sourcing.
At Learn How to Source, we use three practical document types to explain how a buyer can define what should be delivered:
- Technical Specification
- Statement of Work
- Service Description
These documents all help define the buyer’s requirement, but they are not the same. The professional buyer needs to understand when to use each one.
LHTS procurement framework
Role: Tactical procurement
Supporting role: Operative procurement
Process: Need definition, RFQ preparation, sourcing documentation, supplier evaluation
Level: Basic
Related course: RFQ Template
Quick answer: what is a Technical Specification?
A Technical Specification is a procurement document that describes the technical requirements for the product, component, material, system, or technical service the buyer wants to purchase.
It can include dimensions, materials, standards, performance levels, tolerances, testing requirements, certificates, packaging, labelling, safety requirements, quality requirements, and acceptance criteria.
A Technical Specification is most useful when the buyer knows what technical result is needed and must ensure that all suppliers quote against the same defined requirement.
Why specifications matter in procurement
A specification is not just a technical document. It is a sourcing tool.
It helps the buyer explain the need to the market, makes quotations easier to compare, reduces misunderstanding, supports supplier evaluation, and becomes a reference point during contract execution.
CIPS defines a procurement specification as a document that details the requirements for a product or service, often provided as an amendment or schedule to a contract.
A good specification helps suppliers understand what is required and submit relevant quotations. A weak specification can lead to wrong deliveries, poor service, wasted time, insufficient supplier responses, and potential legal or safety consequences.
For a buyer, the specification is therefore part of the bridge between business need, supplier market, RFQ, quotation evaluation, contract, and delivery.
The three LHTS ways to define what the buyer wants delivered
At LHTS, we use three specification-related document types to help buyers think clearly about the requirement.
They are:
- Technical Specification
- Statement of Work
- Service Description
The names may vary between organizations, but the logic is useful in most procurement work.
1. Technical Specification
A Technical Specification is used when the buyer needs to define technical characteristics.
It is often used for:
- components
- materials
- products
- machinery
- spare parts
- systems
- technical equipment
- packaging
- manufactured items
- technical installation requirements
- regulated or safety-critical products
A Technical Specification may include:
- drawings
- dimensions
- material requirements
- standards
- tolerances
- performance requirements
- testing requirements
- inspection requirements
- quality levels
- documentation requirements
- certificates
- environmental or safety requirements
- packaging and labelling requirements
- delivery or installation requirements
- acceptance criteria
This type of specification is especially useful when the buyer needs comparable supplier quotations and clear technical compliance.
CIPS describes a technical specification as a form of conformance specification that outlines the standards a product or service must meet. Conformance specifications are more prescriptive and can include drawings, samples, brands, recipes, technical standards, materials, or production methods.
The buyer should use a Technical Specification when technical precision is necessary. But the buyer must also be careful not to over-specify.
2. Statement of Work
A Statement of Work, often called a SoW, is normally used when the buyer purchases a project, assignment, or defined work package.
It is often used for:
- consulting assignments
- engineering projects
- installation projects
- development work
- maintenance projects
- implementation projects
- project-based services
- construction-related work packages
A SoW usually defines:
- background and purpose
- scope of work
- activities
- deliverables
- milestones
- timetable
- roles and responsibilities
- assumptions
- dependencies
- reporting requirements
- acceptance criteria
- change control
- project governance
CIPS describes a Statement of Work as a type of specification commonly used for projects or services, usually consisting of activities, deliverables, delivery timescales, and other factors required to produce the product or service.
The SoW is useful when the buyer needs to define work to be performed, not only a product to be delivered.
3. Service Description
A Service Description is used when the buyer wants to describe a recurring or ongoing service.
It is often used for:
- cleaning services
- security services
- IT support
- logistics services
- facility management
- customer support
- maintenance services
- managed services
- outsourced business processes
A Service Description usually defines:
- service scope
- service users
- service hours
- service levels
- response times
- responsibilities
- interfaces
- exclusions
- reporting
- escalation paths
- KPIs
- governance meetings
- continuous improvement expectations
A Service Description is usually more output-oriented than a Technical Specification. It should explain what service must be delivered and how performance will be measured.
Government Commercial Agency guidance distinguishes input specifications, which set out exactly what is required, from output specifications, which define the outcomes or outputs that the supplier is expected to deliver. Output specifications can give suppliers more flexibility to develop solutions.
This is why a Service Description is often better than a Technical Specification for recurring services. The buyer should describe the service result, not unnecessarily prescribe every supplier activity.
How to choose between Technical Specification, SoW, and Service Description
The buyer should start with the business need and then choose the document type.
| Situation | Best document type | Reason |
|---|---|---|
| You are buying a defined product, component, material, or technical item | Technical Specification | You need technical clarity and comparable supplier responses |
| You are buying a project or defined work package | Statement of Work | You need activities, deliverables, milestones, and acceptance criteria |
| You are buying an ongoing service | Service Description | You need service scope, service levels, roles, KPIs, and governance |
| You need supplier innovation | Service Description or performance-based SoW | You should define the outcome rather than prescribe the method |
| You need strict technical compliance | Technical Specification | You need standards, tolerances, testing, and evidence |
| You need to evaluate project execution capability | SoW | You need to assess method, team, timeline, and deliverables |
In practice, an RFQ package may include more than one document. A project could include a SoW plus a Technical Specification. A service RFQ could include a Service Description plus a technical appendix. A product RFQ could include a Technical Specification plus a testing protocol.
The important point is that the buyer should make a conscious choice.
Technical Specification as part of an RFQ
A Technical Specification is often one of the most important attachments in an RFQ package.
The RFQ normally explains the commercial process: what suppliers should submit, when to submit, how prices should be presented, what terms apply, and how the buyer will evaluate the quotations.
The Technical Specification explains the technical requirement.
Together, they help suppliers prepare quotations that can be compared fairly.
The LHTS RFQ Template course explains the information required in an RFQ, how sourcing tactics affect RFQ design, and how the RFQ can support supplier responses, negotiation position, and long-term supplier relationships.
A good RFQ should therefore not only ask for a price. It should create a structured basis for supplier comparison.
What should a Technical Specification include?
The content depends on what is being purchased, but a strong Technical Specification often includes the following sections.
1. Background and purpose
Explain why the product, system, or technical service is needed.
This does not need to be long, but it helps suppliers understand the context.
Example:
“The buyer requires corrosion-resistant brackets for outdoor installation in a coastal environment.”
This gives the supplier more useful information than only saying:
“Supply brackets according to drawing.”
2. Scope
Define what is included and what is excluded.
This avoids misunderstanding.
For example:
- Is installation included?
- Is testing included?
- Is training included?
- Is documentation included?
- Is packaging included?
- Are spare parts included?
- Is delivery to site included?
Scope clarity prevents later disputes.
3. Technical requirements
This is the core of the Technical Specification.
It may include:
- dimensions
- weight
- materials
- tolerances
- capacity
- power requirements
- environmental conditions
- compatibility
- interface requirements
- system requirements
- durability
- safety requirements
- chemical or physical properties
- drawings or part numbers
The buyer should separate mandatory requirements from preferred requirements.
4. Performance requirements
A Technical Specification should not only describe what the item is. It should also describe what it must do.
Performance requirements may include:
- output
- speed
- reliability
- accuracy
- lifetime
- efficiency
- load capacity
- resistance
- response time
- operating temperature
- noise level
- energy consumption
UK Government guidance explains that functional requirements describe what goods, services, or works must do, while performance requirements describe how well they must perform.
This distinction is useful for buyers. A dimension tells the supplier what something is. A performance requirement tells the supplier what it must achieve.
5. Standards and regulations
Include relevant standards, legal requirements, and industry norms.
Examples may include:
- ISO standards
- IEC standards
- EN standards
- safety regulations
- environmental regulations
- industry-specific certifications
- quality management requirements
- packaging or transport regulations
The buyer should only include standards that are relevant and proportionate.
UK Government guidance explains that technical specifications can drive quality through recognized standards and evidence such as certification, conformity assessment, and accreditation.
If standards are used, the RFQ should also explain what evidence the supplier must provide.
6. Sustainability requirements
Sustainability can be included in a Technical Specification when it is relevant to the purchase.
This may include:
- restricted substances
- recycled content
- energy efficiency
- repairability
- packaging reduction
- emissions requirements
- lifecycle performance
- waste handling
- ecolabel criteria
- end-of-life instructions
The European Commission explains that Green Public Procurement criteria can be incorporated into procurement procedures for goods, services, or works to reduce environmental impact.
For the buyer, the key is to connect sustainability requirements to the subject of the purchase and make them measurable.
7. Testing, inspection, and validation
A requirement is only useful if it can be verified.
The Technical Specification should explain how compliance will be checked.
This may include:
- factory acceptance test
- site acceptance test
- sample approval
- inspection before shipment
- certificates
- laboratory testing
- test reports
- calibration records
- conformity declarations
- audit rights
- approval of first article or prototype
The buyer should define who performs the test, when it is performed, what standard is used, and what happens if the result is not accepted.
8. Documentation requirements
Suppliers should know which documents must be delivered.
Examples include:
- drawings
- manuals
- certificates
- test reports
- safety data sheets
- installation instructions
- maintenance instructions
- spare part lists
- compliance declarations
- warranty documentation
- training material
Documentation requirements should be part of the RFQ, not discovered after delivery.
9. Packaging, labelling, and delivery requirements
A product can meet the technical requirement and still create problems if packaging, labelling, or delivery is wrong.
Include requirements for:
- packaging type
- pallet requirements
- barcode or labelling
- batch number
- serial number
- shelf-life marking
- handling instructions
- transport conditions
- delivery location
- delivery documentation
- Incoterms, if relevant
UK Government guidance notes that technical specifications may include packaging, marking, and labelling requirements.
10. Acceptance criteria
Acceptance criteria define when the buyer will consider the delivery approved.
This is one of the most important sections.
Examples:
- all mandatory technical requirements are met
- test results are approved
- required certificates are submitted
- documentation is complete
- packaging and labelling are correct
- delivered quantity matches the order
- non-conformities are resolved
Acceptance criteria reduce ambiguity when the supplier delivers.
Example: Technical Specification for AAA alkaline batteries
A simplified Technical Specification for AAA alkaline batteries could include:
Product: AAA alkaline battery
Chemistry: Alkaline
Nominal voltage: 1.5 V
Size: AAA
Dimensions: According to relevant IEC standard
Application: General consumer use in electronic devices
Shelf life: Minimum defined shelf life from date of manufacture
Leakage resistance: Battery must not leak under normal use and storage conditions
Safety: Supplier must provide relevant safety and handling information
Environmental requirements: Compliance with applicable battery and hazardous substance regulations
Packaging: Defined pack size, barcode, batch marking, and transport packaging
Labelling: Battery type, polarity, date or batch code, safety warnings
Quality evidence: Certificate of compliance and test report upon request
Acceptance: Delivery accepted only when product, packaging, labelling, and documentation meet the specification
This example shows the logic. The buyer must adjust the details depending on market, regulation, application, and internal quality requirements.
The buyer’s role in specification development
The buyer does not need to be the technical expert in every detail. But the buyer must manage the specification process.
The buyer should make sure that:
- the business need is clear
- the right stakeholders are involved
- the right type of specification document is chosen
- requirements are clear and measurable
- unnecessary supplier restrictions are avoided
- standards are relevant
- evaluation criteria match the specification
- suppliers receive the same information
- commercial and technical requirements do not conflict
- the final specification supports fair comparison
CIPS recommends cross-functional specification development so stakeholder and operational requirements are considered, including input from end users, finance, technical departments, and procurement.
This is a key procurement point. The technical expert may write many of the technical details, but procurement must ensure the specification works in the sourcing process.
Best practice when writing a Technical Specification
Start with the need, not the solution
Before writing technical details, clarify the underlying need.
Ask:
- What problem are we solving?
- What must the product or service achieve?
- What is mandatory?
- What is only preferred?
- What flexibility can we give suppliers?
- What would make quotations comparable?
This prevents the buyer from copying old specifications without questioning whether they still reflect the real need.
Avoid unnecessary over-specification
Over-specification can increase cost, reduce competition, and block supplier innovation.
Government Commercial Agency guidance warns that over-specifying can add cost and that buyers should be sure the “gold-plated” option is really needed.
A good buyer challenges unnecessary requirements.
Ask:
- Is this requirement necessary?
- Can the supplier meet the need in another way?
- Does this requirement reduce competition?
- Is this based on habit or real need?
- Does this requirement create value?
Use functional and performance requirements where possible
A specification does not always need to prescribe how the supplier must solve the problem.
Sometimes it is better to define what the product must do or how well it must perform.
UK Government guidance states that procurement documents should refer to performance or functional requirements rather than design or descriptive characteristics, unless that is not appropriate.
For buyers, this means:
- Use technical details where precision is needed.
- Use performance requirements where supplier solutions can vary.
- Use output requirements where innovation is welcome.
- Use standards where compliance must be assured.
Make requirements measurable
Avoid vague words such as:
- high quality
- robust
- user-friendly
- best in class
- durable
- fast
- sustainable
- easy to maintain
These words may be useful in conversation, but they are weak in a specification unless they are defined.
Better examples:
- minimum operating temperature: -20°C
- response time: less than 2 seconds
- warranty period: 36 months
- delivery accuracy: 98%
- recycled content: minimum 30%
- noise level: maximum 60 dB
- service availability: 99.5%
Government Commercial Agency guidance recommends making the specification enforceable and measurable and being clear about what success and failure look like.
Avoid supplier bias
A Technical Specification should not be written to fit one supplier unless there is a justified reason.
Avoid unnecessary references to:
- brand names
- trademarks
- proprietary systems
- supplier-specific processes
- unique part numbers
- unnecessary certifications only one supplier has
UK Government guidance states that technical specifications should not unnecessarily narrow the competitive pool or give unfair advantage to particular suppliers.
If a specific brand or standard is needed, consider whether equivalent solutions should be accepted.
Align specification and evaluation criteria
The specification and evaluation model must work together.
If a requirement is mandatory, the buyer must know how to check compliance. If a requirement will be scored, the RFQ should explain how suppliers can receive higher or lower scores.
For example:
- Mandatory: “The product shall comply with standard X.”
- Scored: “Additional points will be awarded for energy consumption below Y level.”
- Evidence: “Supplier shall provide test report from accredited laboratory.”
This alignment helps avoid confusion during bid evaluation.
Common mistakes when writing Technical Specifications
Mistake 1: Copying an old specification without review
Old specifications may contain outdated standards, obsolete materials, unnecessary details, or supplier-specific wording.
Always review before reuse.
Mistake 2: Writing the specification alone
A buyer should not write technical requirements without input from the user, technical expert, quality, operations, or other relevant stakeholders.
Cross-functional input improves accuracy and acceptance.
Mistake 3: Mixing needs, requirements, and solutions
A need explains the problem.
A requirement explains what must be achieved.
A solution explains how it will be achieved.
Good procurement work keeps these separate.
Mistake 4: Over-specifying
Too much detail can reduce competition and increase cost.
Do not specify the supplier’s method unless the method is truly required.
Mistake 5: Under-specifying
Too little detail creates unclear quotations and delivery risk.
If suppliers must guess, the buyer has not done the job properly.
Mistake 6: Using vague language
Words such as “high quality” or “good service” need measurable definitions.
Mistake 7: Forgetting acceptance criteria
If acceptance is not defined, disputes may occur after delivery.
Mistake 8: Ignoring lifecycle cost
The cheapest compliant product may not be the best value if it has poor energy performance, short lifetime, high maintenance cost, or difficult disposal.
UK Government guidance states that technical specifications can support value for money when requirements take whole-lifecycle cost and other considerations into account.
Practical checklist for buyers
Before sending the RFQ, check the specification against these questions:
- Is the business need clear?
- Have we chosen the right document type: Technical Specification, SoW, or Service Description?
- Are the mandatory requirements separated from preferred requirements?
- Are requirements measurable?
- Are standards relevant and current?
- Have we avoided unnecessary brand or supplier-specific wording?
- Have technical, operational, quality, finance, and procurement stakeholders reviewed the document?
- Can suppliers prepare comparable quotations?
- Have we defined required evidence?
- Are testing and acceptance criteria clear?
- Are sustainability and compliance requirements included where relevant?
- Does the evaluation model match the specification?
- Is the document written clearly enough for suppliers to understand without assumptions?
If the answer is no to several of these questions, the RFQ should not yet be sent.
How this connects to the tactical procurement role
Technical Specification work belongs mainly to the tactical procurement role.
The tactical buyer is responsible for preparing sourcing events, engaging stakeholders, understanding the supplier market, building the RFQ package, managing supplier questions, and supporting evaluation.
The buyer may not own every technical detail, but the buyer owns the procurement quality of the specification.
That means making sure the specification:
- supports the sourcing strategy
- allows fair competition
- enables comparable quotations
- supports negotiation
- connects to evaluation criteria
- can be used in the contract
- protects the business need
- does not create unnecessary risk
This is why specification work is a core skill for tactical buyers.
Where this fits in the procurement process
A Technical Specification appears mainly in the sourcing process, but it starts before the RFQ is issued.
It connects to:
Need definition
The buyer and stakeholders clarify what must be achieved.
Market analysis
The buyer checks whether the market can meet the requirement.
Sourcing strategy
The buyer decides whether to use a Technical Specification, SoW, Service Description, or a combination.
RFQ preparation
The specification becomes part of the RFQ package.
Supplier questions
Suppliers may ask clarification questions before quoting.
Bid evaluation
The buyer evaluates supplier compliance against the specification.
Contracting
The final specification becomes part of the contract or order documentation.
Delivery and acceptance
The specification is used to check whether the supplier delivered what was agreed.
Related course: RFQ Template
The recommended LHTS course for this article is RFQ Template.
This course explains what should be included in a successful request to the market and how RFQ design is affected by sourcing tactics, supplier responses, negotiation position, and supplier relationship goals.
It is especially relevant because a Technical Specification is not a standalone document. It becomes powerful when it is connected to the RFQ letter, price model, contract template, selection criteria, and evaluation model.
FAQ
What is a Technical Specification in procurement?
A Technical Specification is a document that describes the technical requirements for what the buyer wants to purchase. It may include dimensions, materials, standards, performance levels, testing, quality requirements, documentation, packaging, and acceptance criteria.
Is a Technical Specification part of an RFQ?
Yes. A Technical Specification is often attached to an RFQ so that suppliers understand the requirement and can submit comparable quotations.
What is the difference between a Technical Specification and a Statement of Work?
A Technical Specification defines technical characteristics and requirements. A Statement of Work defines project work, activities, deliverables, milestones, responsibilities, and acceptance criteria.
What is the difference between a Technical Specification and a Service Description?
A Technical Specification is usually better for products, components, systems, or technical requirements. A Service Description is better for ongoing services where the buyer needs to define scope, service levels, responsibilities, KPIs, and governance.
Should a buyer write the Technical Specification?
The buyer should manage the specification process, but technical experts and users should contribute to the technical content. Procurement ensures that the specification supports competition, supplier comparison, evaluation, and contract execution.
What is the biggest mistake in a Technical Specification?
The biggest mistake is writing a specification that is either too vague or too restrictive. A vague specification creates unclear quotations. An over-restrictive specification can reduce competition and block better supplier solutions.
Should a specification describe the solution or the outcome?
It depends. If strict technical compliance is required, the buyer may need to describe the solution in detail. If supplier innovation is possible, the buyer should describe the required function, performance, or outcome instead.
Conclusion
A Technical Specification is one of the most important documents in the RFQ process. It helps the buyer define what should be delivered and helps suppliers prepare relevant and comparable quotations.
But a Technical Specification is not always the right document. At LHTS, buyers should understand three practical ways to define what they want delivered: Technical Specification, Statement of Work, and Service Description.
The professional buyer starts with the business need, chooses the right specification type, involves the right stakeholders, writes measurable requirements, avoids unnecessary restrictions, and connects the specification to evaluation and contract execution.
That is how specification work becomes more than documentation. It becomes a sourcing skill.
