A Request for Quotation, or RFQ, is only as strong as the information included in it.
One of the most common problems in service procurement and project-based sourcing is that buyers ask suppliers for a price before the work is clearly defined. The result is predictable: suppliers quote on different assumptions, prices become difficult to compare, and the buyer may discover after award that the selected supplier did not include everything expected.
This is where the Statement of Work, often shortened to SOW or SoW, becomes important.
A Statement of Work should be included in the RFQ package when the buyer asks suppliers to quote for a service, project, installation, consultancy assignment, development activity, maintenance scope, or other work-based delivery.
The SOW explains what the supplier is expected to do. The RFQ asks the supplier to price and respond to that requirement. Together, they help the buyer create comparable offers, reduce misunderstandings, and build a stronger contract.
LHTS framework connection
Role: Tactical procurement
Supporting roles: Operative procurement and procurement management
Process: Need definition, RFQ preparation, supplier quotation, supplier evaluation, contract negotiation, contract implementation, supplier performance follow-up
Level: Basic
Related course: RFQ template
Supporting learning: Sourcing Process 1, Service Level Agreement, Service Description
Quick answer: What is the connection between a Statement of Work and an RFQ?
A Statement of Work defines the work the supplier must perform. It describes the scope, tasks, deliverables, timelines, responsibilities, standards, assumptions, and acceptance criteria.
A Request for Quotation is the document used by the buyer to request prices and commercial responses from suppliers.
In procurement, the SOW should normally be included in the RFQ package so that all suppliers quote on the same scope of work. This makes offers easier to compare and reduces the risk of disputes after contract award.
The problem: suppliers cannot price unclear work correctly
When a buyer sends an RFQ without a clear Statement of Work, the supplier has to make assumptions.
One supplier may assume a limited scope. Another supplier may include extra project management. A third supplier may exclude documentation, testing, training, travel, reporting, or handover. A fourth supplier may assume that the buyer will provide resources, access, data, or approvals that were never clearly stated.
All suppliers may then submit prices, but the prices do not represent the same work.
This creates several procurement problems:
- supplier quotations become difficult to compare
- the lowest price may be based on missing scope
- important tasks may be excluded
- delivery timelines may be unrealistic
- supplier responsibilities may be unclear
- the buyer may face change requests after contract award
- internal stakeholders may expect more than the supplier has priced
- contract disputes may arise
- supplier performance becomes difficult to measure
A weak SOW often leads to a weak RFQ response. A strong SOW helps the supplier understand the requirement and helps the buyer evaluate the offer.
What is a Statement of Work?
A Statement of Work is a formal document that describes the work a supplier or contractor is expected to perform.
It is often used for services, projects, consulting assignments, technical work, installations, maintenance agreements, development projects, outsourcing, and other assignments where the buyer needs to define more than a product number and quantity.
A good SOW should explain:
- why the work is needed
- what the supplier must do
- what deliverables are expected
- when the work must be completed
- where the work will be performed
- which standards or requirements apply
- who is responsible for what
- how completion will be accepted
- which assumptions and constraints apply
- how changes will be handled
The SOW should be detailed enough for suppliers to understand the assignment and submit a realistic quotation.
What is a Request for Quotation?
A Request for Quotation, or RFQ, is a procurement document used to request supplier prices and commercial responses.
The RFQ normally includes information such as:
- buyer instructions
- scope or specification
- pricing format
- delivery requirements
- contract terms
- evaluation criteria
- deadline for response
- supplier questions process
- required documents
- commercial conditions
For product purchases, the specification may be enough to support the RFQ. For services and project-based work, the RFQ usually needs a Statement of Work to define what the supplier is actually pricing.
Why the SOW should be included in the RFQ package
The SOW should be included in the RFQ package because suppliers need a clear description of the work before they can submit a reliable price.
Including the SOW in the RFQ helps the buyer:
- make supplier offers comparable
- reduce supplier assumptions
- clarify deliverables before pricing
- reduce the risk of scope creep
- evaluate capability, not only price
- identify missing activities early
- improve negotiation quality
- create a stronger contract baseline
- support supplier performance follow-up after award
If the SOW is not included in the RFQ, the buyer may receive prices that look attractive but are not complete.
A low price is not valuable if it is based on an incomplete understanding of the work.
Scope of Work and Statement of Work: what is the difference?
The terms Scope of Work and Statement of Work are often used interchangeably in real life. In smaller projects, this may not create a major problem. In more complex procurement projects, it is useful to separate them.
Scope of Work
The Scope of Work describes the specific tasks, activities, deliverables, timelines, and boundaries of the work.
It answers:
What work must be done?
What is included?
What is excluded?
What must be delivered?
When must it be delivered?
Statement of Work
The Statement of Work is usually broader. It includes the Scope of Work but may also include objectives, background, methodology, roles, responsibilities, assumptions, constraints, performance standards, acceptance criteria, budget principles, and contractual conditions.
In simple terms:
Scope of Work: the detailed work content
Statement of Work: the full work document used to align buyer and supplier
The important point for buyers is not the label. The important point is that the RFQ contains enough information for suppliers to understand the work and quote correctly.
How this connects to the tactical procurement role
The Statement of Work is mainly connected to the tactical procurement role because tactical buyers often manage RFQs, supplier evaluation, negotiation, and contract preparation.
A tactical buyer does not always write the full SOW alone. In many cases, the technical expert, service owner, project manager, or internal stakeholder provides the content.
But the tactical buyer should make sure the SOW is clear enough for sourcing.
The tactical buyer should ask:
- Is the work clearly described?
- Are the deliverables measurable?
- Are timelines realistic?
- Are responsibilities defined?
- Are assumptions visible?
- Are exclusions stated?
- Are acceptance criteria clear?
- Is the SLA included if service levels matter?
- Can suppliers price the work without guessing?
- Can we use the SOW as part of the contract?
This is where procurement creates value. A tactical buyer helps turn a business need into a sourcing document that suppliers can understand and price.
How this connects to operative procurement
Operative procurement may become involved after the contract is signed, especially when purchase orders, call-offs, delivery follow-up, invoice handling, or supplier communication are needed.
If the SOW is unclear, operative buyers may face problems such as:
- unclear purchase order references
- disputes about what is included
- unclear delivery or completion dates
- invoices for extra work
- missing documentation
- unclear acceptance of services
- difficulty confirming whether work has been completed
A strong SOW makes operative follow-up easier because it defines what the supplier should deliver and how completion should be confirmed.
How this connects to procurement management
Procurement management should ensure that the organization has a standard way of working with SOWs.
This may include:
- SOW templates
- RFQ package checklists
- approval rules
- contract attachment standards
- guidance for when SOWs are required
- review of high-risk scopes
- cross-functional responsibility between procurement, legal, technical teams, and business owners
- lessons learned after project completion
For management, the SOW is a governance tool. It reduces ambiguity and supports better control over external spend.
Where the SOW fits in the procurement process
The SOW should be developed before the RFQ is issued, and it should remain connected to the sourcing process through contract award and implementation.
1. Need definition
The internal stakeholder explains the business need. Procurement helps challenge and structure the need so that it can become a clear sourcing requirement.
2. Service description or project description
The buyer and stakeholder define the service or project in practical terms. This may become the base for the SOW.
3. SOW preparation
The SOW is prepared with input from relevant stakeholders. It should describe scope, deliverables, timeline, responsibilities, assumptions, acceptance criteria, and any relevant service levels.
4. RFQ package
The SOW is included in the RFQ package. Suppliers use it to prepare their quotations.
5. Supplier questions
Suppliers may ask questions about the SOW during the RFQ period. These questions are valuable because they reveal unclear areas before contract award.
6. Supplier quotation
Suppliers submit prices, proposed delivery models, assumptions, deviations, and clarifications based on the SOW.
7. Supplier evaluation
The buyer evaluates supplier responses against the SOW. This includes price, technical approach, capability, timeline, risks, and compliance with requirements.
8. Negotiation
During negotiation, the SOW may be clarified or refined. Any changes should be documented so that the final contract reflects the agreed scope.
9. Contract signing
The final SOW should become part of the signed contract, usually as an appendix, schedule, or attachment.
10. Contract implementation and follow-up
The SOW is used to manage delivery, confirm completion, control changes, and evaluate supplier performance.
What should be included in a Statement of Work?
The level of detail depends on the complexity and risk of the purchase. A simple service may need a short SOW. A complex project may need a detailed and structured SOW.
A practical SOW can include the following sections.
1. Background and purpose
Explain why the work is needed and what business problem the work should solve.
2. Objectives
Define what the buyer wants to achieve.
Example:
“The objective is to implement a preventive maintenance program that reduces unplanned machine downtime and improves service documentation.”
3. Scope of work
Describe the work included in the assignment. Be clear about tasks, activities, and boundaries.
4. Out of scope
State what is not included. This is one of the most useful ways to prevent misunderstandings.
5. Deliverables
List the tangible or intangible outputs the supplier must deliver.
Examples:
- report
- installed equipment
- training session
- project plan
- maintenance service
- software configuration
- drawings
- test documentation
- handover package
6. Timeline and milestones
Define key dates, phases, milestones, and delivery deadlines.
7. Roles and responsibilities
Clarify what the supplier is responsible for and what the buyer must provide.
For example, the buyer may need to provide access, internal resources, data, drawings, approvals, or system permissions.
8. Methodology or approach
For more complex work, describe the expected method or ask suppliers to propose their method in the RFQ response.
9. Requirements and standards
List technical, quality, safety, environmental, regulatory, documentation, security, or compliance requirements.
10. Acceptance criteria
Define how the buyer will decide whether the work or deliverable is accepted.
This may include inspection, testing, approval, sign-off, documentation review, user acceptance, or performance verification.
11. Assumptions and constraints
State assumptions that affect the work. Also state known limitations, dependencies, restrictions, or conditions.
12. Change control
Describe how changes to scope, timeline, resources, or cost will be handled.
13. Reporting and communication
Define meeting structure, reports, progress updates, escalation contacts, and communication routines.
14. SLA or performance levels
If the work includes ongoing service delivery, the SOW should reference or include the SLA.
15. Commercial references
The SOW can refer to pricing structure, payment milestones, invoicing rules, or cost breakdowns, depending on how the RFQ and contract are structured.
Practical example: weak SOW versus strong SOW
Weak SOW example
“Supplier shall provide maintenance support for production equipment.”
This is too vague. It does not explain which equipment, what type of maintenance, service hours, response time, spare parts responsibility, reporting, safety requirements, or acceptance process.
Suppliers will have to guess. The buyer will receive offers that are difficult to compare.
Stronger SOW example
“The supplier shall provide preventive and corrective maintenance support for the packaging line equipment listed in Appendix 1. Preventive maintenance shall be performed monthly according to the agreed maintenance plan. Corrective maintenance shall be available Monday to Friday between 07:00 and 17:00. The supplier shall provide service reports within two working days after each visit. Spare parts are excluded unless separately ordered. The buyer shall provide site access, safety instructions, and equipment documentation. Service performance shall be measured according to the SLA in Appendix 2.”
This version is much stronger because it defines scope, frequency, service hours, documentation, exclusions, buyer responsibilities, and SLA connection.
How suppliers use the SOW when answering the RFQ
A supplier uses the SOW to understand what they are expected to price and deliver.
A good supplier response may include:
- confirmation of scope
- proposed method
- project plan
- resource plan
- delivery timeline
- assumptions
- exclusions
- risk comments
- price breakdown
- deviations from the SOW
- references or examples
- acceptance of SLA requirements
This gives the buyer a better basis for evaluation. It also helps identify suppliers who understand the work and suppliers who have only submitted a price.
Common mistakes when using SOWs in RFQs
Mistake 1: Sending the RFQ before the work is defined
If the buyer issues the RFQ too early, suppliers must guess. This creates poor comparability and weak commercial control.
Mistake 2: Confusing a short description with a real SOW
A few sentences may be enough for a simple purchase, but complex services and projects need more structure.
Mistake 3: Forgetting exclusions
Buyers often describe what is included but forget to state what is excluded. Exclusions are important because they reduce later disputes.
Mistake 4: Missing acceptance criteria
If the buyer does not define how the work will be accepted, it may be difficult to decide whether the supplier has fulfilled the obligation.
Mistake 5: Not connecting the SOW to the SLA
For services, the SOW should often be connected to an SLA. The SOW explains the work. The SLA explains the expected performance level.
Mistake 6: Not making the final SOW part of the contract
If the final SOW is not included in the signed contract, it may be difficult to enforce the agreed scope.
Mistake 7: Allowing hidden assumptions
Suppliers may include assumptions that reduce their responsibility. These assumptions should be reviewed carefully before contract award.
Mistake 8: Letting procurement write the SOW without stakeholder input
Procurement can structure and challenge the SOW, but technical and business input is usually needed to define the real work.
Link to related course: RFQ template
If you want to go deeper into how to build RFQ packages that create comparable supplier offers, the Learn How to Source course RFQ template is the most relevant next step.
A Statement of Work is one of the most important parts of the RFQ package when buying services or project-based work. It helps suppliers understand the work, price the requirement correctly, and clarify assumptions before contract award.
This topic also connects naturally to Sourcing Process 1, Service Level Agreement, and Service Description.
FAQ: Statement of Work and RFQ
What is a Statement of Work?
A Statement of Work is a document that defines the work a supplier must perform. It normally includes scope, deliverables, timeline, responsibilities, assumptions, standards, and acceptance criteria.
What is the connection between SOW and RFQ?
The SOW should be included in the RFQ package so suppliers understand the work they are pricing. The RFQ asks for the quotation, while the SOW defines the work behind the quotation.
Should the SOW be part of the contract?
Yes. The final agreed SOW should normally become part of the signed contract as an appendix, schedule, or attachment. This makes the scope easier to manage and enforce.
What is the difference between Scope of Work and Statement of Work?
The Scope of Work describes the detailed tasks and deliverables. The Statement of Work is usually broader and may include objectives, background, methodology, roles, responsibilities, assumptions, performance standards, and acceptance criteria.
What should be included in a SOW?
A SOW should include background, objectives, scope, exclusions, deliverables, timeline, responsibilities, requirements, standards, acceptance criteria, assumptions, change control, reporting, and SLA connection if relevant.
Why is a SOW important for buyers?
A SOW helps buyers create comparable supplier offers, reduce unclear assumptions, avoid scope creep, support negotiation, and create a clear contract baseline.
Is a SOW only used for services?
No. SOWs are most common in services and project-based procurement, but they can also be useful for installations, development work, maintenance, technical assignments, outsourcing, and complex supplier deliverables.
Conclusion: define the work before asking suppliers to quote
A Statement of Work is one of the most important documents in a service or project RFQ.
Without a clear SOW, suppliers will quote based on their own assumptions. This makes price comparison weak and increases the risk of missing scope, change requests, delivery disputes, and poor supplier performance after contract award.
The practical next step is to review your next RFQ package before sending it to suppliers. Ask whether the work is clearly defined, whether deliverables are measurable, whether exclusions are visible, whether acceptance criteria are clear, and whether the SLA is included if service levels matter.
A strong RFQ does not only ask for a price. It gives suppliers a clear and structured work requirement to price.