UK supplier guide
Sample RFP for Software:
Worked Outline and Free Builder
A software RFP should state the outcome, requirements, implementation, price, evaluation and exit. Use the worked sections below, then build and copy an outline with your own details.
Build and copy the software RFP →Checked against primary sources40 sources linked below
- Start with the user need
- Choose the purchase shape
- Ask for testable evidence
- Compare the whole-life offer
The outcome leads the outline
Describe what changes for users before specifying features.The whole cost needs a schedule
Include implementation, support and exit.The template is editable content
Adapt the legal procedure separately before issue.
What belongs in a sample RFP for software?
Start with the result you need, then state requirements, service, price and how offers will be assessed.
Software purchase
- Describe the users, problem and intended change.
- Separate must-have constraints from scored preferences.
- Ask for licence, delivery, support and exit costs.
- Tell suppliers how the response will be assessed.
Which starting shape matches the software purchase?
Buying an existing product, commissioning a build and renewing support need different schedules.
| Purchase | Specify | Do not overlook |
|---|---|---|
| SaaS or existing software | Users, configuration, migration, interfaces, service levels | Subscription increases and data export |
| Bespoke development | Outcomes, phases, acceptance, code ownership | Discovery findings and ongoing maintenance |
| Implementation | Migration, integration, training, rollback | Responsibilities of the product supplier |
| Support renewal | Incidents, patching, releases and service measures | Handover and exit |
How do you move from a software outline to a comparable offer?
Set the outcome, the evidence and the assessment before asking vendors to invest in a proposal.
- Start with the source01
Start with the user need
Name the users, problem and change the purchase needs to deliver. - Define the scope02
Choose the purchase shape
Separate an existing product, a bespoke build, implementation and support. - Read the evidence03
Ask for testable evidence
Write functional, data, accessibility and security requirements vendors can answer consistently. - Make the decision04
Compare the whole-life offer
Consider delivery, support, commercial terms and exit alongside the licence price. - Name the next action05
Test the completed pack
Check evaluation weights, response formats and buyer instructions before issuing the outline.
A supplier’s review sequence, based on the primary sources below. It is not a measured outcome or a prescribed buyer timetable.
What does a real software procurement ask beyond licences?
Energia’s published CRM and billing procurement also describes implementation and ongoing support.
Published 9 March 2026; used here to show separate scope lines, not as a completed template or endorsement.
The utility estimates £150 million excluding VAT for the procurement and an initial seven-year term, with three optional annual extensions at its discretion.
The requests-to-participate deadline was 15 April 2026 at noon; this historical case is not an invitation to bid now. Read the published value, term and deadline.
- Energia Group NI Holdings Limited publishes the procurement.
- The notice describes a SaaS CRM and billing platform.
- Systems implementation services are included.
- This is a historical tender example, not a claim that bidding remains open.
Can you build and copy your own software RFP?
Yes: choose a starting shape, complete the buyer’s details and set evaluation weights that add to 100%.
Sample wording remains editable. The output stays in this browser until you copy it; it is an outline, not legal approval or a published notice.
Buying an off-the-shelf or cloud product as a UK public body: every section on, and social value at the PPN 002 floor for central government.
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
Price 30% · quality 60% · social value 10%
Software RFP: Your software procurement
01Introduction and background
[organisation] invites proposals for [project name]. This request for proposal (RFP) sets out what we need, how we will evaluate responses and the commercial terms that will apply.
We currently use [current system], which [reaches end of support on date / no longer meets our needs because …]. The new system will be used by around [number] staff across [number] sites, and by [members of the public / partners] where stated below.
- Organisation background: [size, sector, locations]
- Current systems landscape: [the systems this must work alongside]
- Key stakeholders and governance: [sponsor, product owner, evaluation panel]
02Scope of work
The contract covers the supply of the software and the services needed to put it into use. Anything not listed as in scope is out of scope unless we agree a change in writing.
- In scope: subscription licences for [number] named users, configuration, data migration, integration with [systems], training and support for [3] years, with an option to extend by [1 + 1] years
- Out of scope: [hardware / network changes / business process redesign]
- Optional extras, priced separately: [additional modules, extra environments]
03Business objectives and outcomes
We are buying outcomes, not features. Proposals should explain how the solution will achieve each outcome below and how progress will be measured.
- Reduce the time to [process a case] from [x days] to [y days] within [12] months of go-live
- Retire [number] spreadsheets and [legacy system] by [date]
- Give managers live reporting on [measures] without manual collation
04Functional requirements
Respond to every line of the requirements matrix (Annex A). For each requirement state whether it is met out of the box, met by configuration, met by customisation, on the roadmap (with a date) or not met, and give evidence. The priority column uses MoSCoW: Must, Should, Could, Won't this time.
| Ref | Requirement | Priority | Response | Evidence |
|---|---|---|---|---|
| FR-001 | Staff sign in with our identity provider using single sign-on (SAML 2.0 or OpenID Connect) | Must | Met / Partly / Not met | [explain] |
| FR-002 | Managers see live dashboards of open cases by team and age | Must | Met / Partly / Not met | [explain] |
| FR-003 | Users can export any report to CSV and PDF | Should | Met / Partly / Not met | [explain] |
| FR-004 | The interface is available in Welsh | Could | Met / Partly / Not met | [explain] |
05Non-functional requirements
- Performance: pages load in under [2] seconds for [95]% of requests with [number] concurrent users
- Availability: [99.9]% monthly, excluding agreed maintenance windows notified [5] working days ahead
- Accessibility: meets WCAG 2.2 AA; the supplier provides an accessibility statement and fixes reported issues within [timescale]
- Compatibility: current versions of Edge, Chrome, Safari and Firefox, and [mobile platforms]
- Scalability: supports growth to [number] users and [volume] records without re-procurement
06Security and data protection
The supplier will process personal data on our behalf and must meet UK GDPR. Describe how the service protects our data, where it is hosted and how you will support our data protection impact assessment.
- Hold Cyber Essentials Plus, ISO/IEC 27001 or an equivalent, and keep it current for the life of the contract
- Host and back up our data in [the UK / a location we approve]; list every sub-processor
- Explain how the service meets the NCSC cloud security principles
- Commission an independent penetration test [annually] and share the summary findings
- Notify us of any security incident affecting our data within [24] hours
07Integration and data migration
- Integrate with [finance system], [HR system] and [identity provider] using documented APIs
- Provide a documented, versioned API for our own reporting and future integrations
- Migrate [number] records from [legacy system], with a trial migration, a reconciliation report and our sign-off before cut-over
08Implementation, training and change
- An implementation plan with milestones, dependencies on us and named roles
- Configuration workshops and a test environment for our user acceptance testing
- Training for [number] end users and [number] administrators, and materials we can reuse
- Go-live criteria, a rollback plan and [4] weeks of post-go-live hypercare
09Service levels and support
Support is available [08:00–18:00 UK time, Monday to Friday] with a [24/7] route for Priority 1 incidents.
| Priority | Definition | Respond within | Resolve within |
|---|---|---|---|
| P1 | Service unavailable or data at risk | [30 minutes] | [4 hours] |
| P2 | Major function unavailable, workaround exists | [2 hours] | [1 working day] |
| P3 | Minor fault | [1 working day] | [5 working days] |
| P4 | Question or change request | [2 working days] | [agreed plan] |
10Commercial terms and pricing
Complete the pricing schedule (Annex B) in full. We will evaluate the total cost over [5] years, including every cost we would pay to use the service as proposed. Prices are in pounds sterling, excluding VAT.
| Cost element | Year 1 | Year 2 | Year 3 | Total |
|---|---|---|---|---|
| Licence or subscription | ||||
| Implementation and configuration | ||||
| Data migration | ||||
| Training | ||||
| Support and maintenance | ||||
| Total |
11Exit, data return and termination
- On exit, return all our data in [CSV / an open format we agree] within [30] days, then delete it and confirm in writing
- Provide an exit plan within [3] months of the contract starting, and keep it up to date
- Co-operate with any replacement supplier during a handover period of up to [3] months
12Social value
Social value is [10]% of the total score. Choose [one] outcome from our social value model, describe what you will deliver in this contract and how you will measure and report it. Commitments you make become contract terms or key performance indicators.
13Evaluation criteria and weighting
Quality answers are scored 0–4 against the published descriptors by each panel member and moderated to a consensus score. Price is scored as the lowest total whole-life cost divided by the bidder's total, multiplied by the price weighting.
| Criterion | Weight | What is assessed |
|---|---|---|
| Functional fit | 25% | Requirements matrix, demonstration |
| Technical and security | 15% | Architecture, integration, security, accessibility |
| Implementation and support | 15% | Plan, migration, training, service levels |
| Supplier experience | 5% | Relevant customers, references |
| Social value | 10% | One outcome from the social value model |
| Price | 30% | Total whole-life cost over the contract |
| Total | 100% |
14Procurement timetable
The dates below are our plan. We may change them, and will tell every supplier at the same time if we do.
| Stage | Date |
|---|---|
| RFP issued | [date] |
| Clarification questions close | [date] |
| Responses due | [date: at least 25 days after issue where responses go in electronically and every document is issued at once] |
| Demonstrations for shortlisted suppliers | [dates] |
| Award decision and contract award notice | [date] |
| Standstill ends (at least 8 working days) | [date] |
| Contract start | [date] |
15Response format and instructions
- Answer each quality question in no more than [1,000] words; text over the limit will not be read
- Complete Annex A (requirements matrix) and Annex B (pricing) in the templates provided, unaltered
- Submit through [portal] by [time] on [date]; late responses will not be accepted
- Send clarification questions through the portal only; we will publish questions and answers to all suppliers, anonymised
16Supplier information and references
- Company profile, ownership and financial standing [or confirm your record on the Central Digital Platform]
- Three references from customers of similar size using the proposed product, at least one live for over a year
- The team who will deliver the implementation, and their availability
Paste the Markdown into Word, Google Docs or your e-tendering portal’s editor. Square brackets mark what only you can fill in.
Which requirements make software proposals comparable?
Write observable outcomes and constraints rather than asking every vendor for its longest feature list.
Comparable answers
- State the user need, priority and acceptance test.
- Define migration, access, processing and export.
- State the accessibility requirements and validation expected.
- Specify the assurance needed for this service.
What should the buyer settle before issuing the RFP?
Resolve scope, assessment, timetable and contract terms before asking suppliers to invest in a response.
- Before you start01
Use the current documents
Check the primary publication and later changes before using the sequence below. - Check 202
Confirm the outcome
Obtain sponsor and user agreement on what needs to change. - Check 303
Separate gates from preferences
State essential constraints and the evidence requested. - Check 404
Publish the assessment
Explain relative importance, demonstrations and price comparison. - Follow through05
Test the pack
Check that a supplier can prepare a complete, comparable offer.
An editorial order of work, not a buyer's fixed timetable. The current notice and documents determine participation and submission.
Can a template determine the procurement procedure?
No: the authority, scope and commencement date determine which rules apply.
Content and process
Procurement Act
New procurements from 24 February 2025 in England, Wales and Northern Ireland, subject to scope and exceptions.Scotland
Devolved Scottish authorities follow separate Scottish procurement legislation.
- New procurements from 24 February 2025 in England, Wales and Northern Ireland, subject to scope and exceptions.
- Devolved Scottish authorities follow separate Scottish procurement legislation.
- A procurement already started under earlier regulations keeps the relevant earlier regime.
- Relevant healthcare services commissioned by relevant authorities can fall under the PSR.
What effort does this pack ask suppliers to spend?
Estimate preparation and review hours before setting the response burden.
This is an illustration of effort, not a market average; supplier time is a design constraint for the pack.
Your bid effort
Starting figures are an illustration, not a measured average or a saving promised by RFP Quest.
£4,000 and 80 team hours each month if you prepare every bid.
Use the estimate to decide how much work to authorise before drafting starts.
It excludes software fees and external costs.
- This bid£2,000
- Other bids this month£2,000
How should evaluation weights and commercial detail be used?
Make the scoring method visible and ask every supplier to price the same scope.
| Element | State explicitly |
|---|---|
| Quality | Questions, evidence, assessment method and relative importance |
| Price | Volumes, contract term, options, implementation and exit |
| Social value | Apply the relevant buyer policy and published model, where applicable |
| Security | Assurance, responsibilities and contract obligations |
| Timetable | Questions, demonstrations, award and implementation |
Which sample requirements fit your software category?
Use the category examples to adapt the outline; they are sample requirements rather than published buyer demands.
The examples cover common product categories and explain what to ask for; replace placeholders with your actual users, interfaces, measures and commercial terms.
Enterprise software
ERP software sample RFP
An enterprise resource planning RFP spans departments, so it lives or dies on integration and on how much of today's process the product can absorb without customisation.
- Functional requirements across finance, HR and operations
- Integration specifications with existing systems
- Data migration requirements and timeline
- Change management and training needs
One requirement, worded
FR-014 (Must): The system posts approved purchase orders to the general ledger in real time, with a full audit trail of who approved each order and when.
MoSCoW priority, an ID and a response column turn this into a line of the requirements matrix.
Enterprise software
CRM software sample RFP
A customer relationship management RFP should describe the customer journeys you run, not a list of screens.
- Sales automation requirements
- Marketing integration capabilities
- Customer service functionality
- Reporting and analytics needs
One requirement, worded
FR-006 (Must): An agent sees every contact a customer has had with us, across phone, email and web forms, on one record.
MoSCoW priority, an ID and a response column turn this into a line of the requirements matrix.
Healthcare software
Electronic health records sample RFP
A clinical system is judged on interoperability and data protection before features.
- Clinical documentation requirements
- Interoperability standards (HL7, FHIR)
- UK GDPR and the NHS Data Security and Protection Toolkit
- Patient portal functionality
One requirement, worded
NFR-003 (Must): The supplier completes the NHS Data Security and Protection Toolkit and keeps it current for the life of the contract.
MoSCoW priority, an ID and a response column turn this into a line of the requirements matrix.
Healthcare software
Telemedicine platform sample RFP
A telehealth RFP has to cover the consultation itself and everything around it.
- Video consultation requirements
- Remote monitoring integration
- Prescription management
- Eligibility and funding checks
One requirement, worded
FR-021 (Should): A patient can join a video consultation from a link, on a phone browser, without installing an app.
MoSCoW priority, an ID and a response column turn this into a line of the requirements matrix.
Financial services
Core banking system sample RFP
Regulation shapes the requirement: compliance is a gate, not a score.
- Transaction processing requirements
- Regulatory compliance (PSD2, Open Banking)
- Risk management functionality
- Multi-channel banking support
One requirement, worded
FR-002 (Must): The platform exposes account information and payment initiation through APIs that meet the Open Banking standard.
MoSCoW priority, an ID and a response column turn this into a line of the requirements matrix.
Financial services
Payment processing software sample RFP
Card data sets the security bar for the whole contract.
- PCI DSS compliance requirements
- Fraud detection capabilities
- Multi-currency support
- Settlement and reconciliation
One requirement, worded
NFR-008 (Must): The solution is PCI DSS compliant and card data never touches our own systems.
MoSCoW priority, an ID and a response column turn this into a line of the requirements matrix.
Manufacturing
Manufacturing execution system sample RFP
Shop-floor software is bought on real-time data and on what happens when the network drops.
- Production scheduling and planning
- Quality management integration
- Real-time data collection
- OEE reporting capabilities
One requirement, worded
FR-011 (Must): Operators can keep recording production for at least [8] hours if the connection to the central server is lost, with automatic sync on reconnection.
MoSCoW priority, an ID and a response column turn this into a line of the requirements matrix.
Manufacturing
Supply chain software sample RFP
Forecasting claims are easy to make and hard to test, so ask for them to be tested on your data.
- Demand forecasting
- Inventory optimisation
- Supplier collaboration portals
- Transportation management
One requirement, worded
FR-004 (Should): The supplier runs the forecasting model on [24] months of our historical data during evaluation and reports its error against actual demand.
MoSCoW priority, an ID and a response column turn this into a line of the requirements matrix.
A comparable proposal starts with an outcome the supplier can price and prove.
The outcome leads the outline
Describe what changes for users before specifying features.The whole cost needs a schedule
Include implementation, support and exit.The template is editable content
Adapt the legal procedure separately before issue.
Review and adapt the outline before issuing it.
What else should you know about sample RFP for software?
Check these points before committing your team’s time.
What should an RFP for a software purchase include?
How long should a software RFP be?
Should I include a budget in my RFP?
How many vendors should I invite?
What's the difference between an RFP and an RFI?
Can I use these templates for public sector procurement?
Are these templates free to use?
Do I need different templates for different procurement procedures?
How do I ensure my RFP is legally compliant?
What format should my RFP be in?
How can I get vendors to take my RFP seriously?
Can I use this template for Agile projects?
Is this template OJEU/Find a Tender compliant?
Should I use this for SaaS procurement too?
How detailed should my requirements be?
Where can I see real software RFP examples?
Where can you check the evidence?
Read the primary publication and the buyer’s current documents before acting.
| Source | What it supports |
|---|---|
| Procurement Act: section/21 ↗ | Tender notice and associated documents. |
| Procurement Act: section/22 ↗ | Conditions of participation. |
| Procurement Act: section/23 ↗ | Award criteria and assessment method. |
| Procurement Act: section/54 ↗ | Time limits and exceptions. |
| Procurement Act: section/51 ↗ | Standstill and exceptions. |
| Cabinet Office: competitive procedures ↗ | Open and competitive flexible procedure guidance. |
| Cabinet Office: AI use: PPN 017 ↗ | Supplier AI use, optional disclosure and confidentiality. |
| Cabinet Office: 2026 thresholds: PPN 023 ↗ | Current threshold amounts by contract type. |
| Cabinet Office: time periods ↗ | Different minima for participation and tendering. |
| Northumbrian Water official notice record ↗ | Framework estimate, lots and expressions-of-interest deadline; snapshot 12 October 2026. |
| www.dsptoolkit.nhs.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gca.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gca.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gca.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.iso.org · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.legislation.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.legislation.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.legislation.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.ncsc.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.ncsc.gov.uk · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| www.w3.org · reference publication ↗ | Retained primary reference from the previous guide; source-specific detail requires checking the current publication. |
| Energia · CRM and billing platform procurement ↗ | Historical tender published 9 March 2026; SaaS product plus implementation and support. |
Which guide answers your next question?
Follow the part of the bid you need to work on next.