Official UK procurement notice
Preliminary Market Engagement – Third-Party Risk Management (TPRM) Platform
Authority: Development Bank of Wales (Central government)
What is being bought
Published requirement descriptionDevelopment Bank of Wales is undertaking a Preliminary Market Engagement exercise to better understand the market for Third-Party Risk Management (TPRM) platforms.
The purpose of this exercise is to engage with potential suppliers and gather information on available solutions, functionality, delivery and implementation approaches, integration capabilities and indicative commercial models.
Development Bank of Wales is particularly interested in understanding the capabilities of solutions across third-party risk management and monitoring, including how platforms differentiate themselves from solutions focused primarily on cyber-risk monitoring.
Suppliers are invited to provide information regarding their proposed solution and to indicate whether relevant functionality is available as standard, through configuration, integration or customisation, or is included within the supplier's product roadmap. Suppliers should also identify any relevant dependencies, limitations, additional modules, third-party data sources and associated costs.
This Preliminary Market Engagement exercise is being undertaken to inform Development Bank of Wales' understanding of the market and its consideration of potential future requirements and procurement options.
Participation in this exercise does not constitute a formal tender process and does not guarantee that a subsequent procurement exercise will be undertaken. Any future procurement opportunity will be advertised separately in accordance with the applicable procurement requirements.
Suppliers wishing to participate should access the Preliminary Market Engagement exercise through the eTenderWales eTendering Portal and submit their response in accordance with the instructions provided.
PQQ_33940 - Preliminary Market Engagement – Third-Party Risk Management (TPRM) Platform
Deadline for responses: 10:00 on 26 November 2026.
Background and purpose
Development Bank of Wales (DBW) is seeking to understand the market for Third-Party Risk Management (TPRM) platforms. The primary driver is the planned replacement of DBW’s existing third-party cyber risk monitoring capability. Rather than undertake a like-for-like replacement, DBW wishes to explore whether a broader TPRM platform could provide additional value across Information Security, Risk, Compliance, Procurement and Operational Resilience.
This market evaluation is intended to:
- Understand current market capabilities and solution approaches.
- Assess platform maturity, functionality and delivery models.
- Identify which capabilities are included as standard and which require additional modules or services.
- Inform budget planning and the development of a future procurement specification.
Target outcomes
- Improved visibility of third-party risk.
- A proportionate, risk-based approach to supplier oversight.
- Reduced duplication of assurance activity across DBW functions.
- Centralised, auditable reporting and evidence.
- Better collaboration between Security, Risk, Compliance and Procurement.
- Actionable supplier risk intelligence and remediation tracking.
Capability areas
Third-Party Cyber Risk Intelligence
MANDATORY - DBW requires an effective replacement for its existing third-party cyber risk monitoring capability.
- Continuous monitoring of supplier external attack surfaces and internet-facing assets.
- Discovery and transparent attribution of supplier-owned assets.
- Identification of vulnerabilities, misconfigurations and exposed services.
- Monitoring of publicly disclosed breaches, leaked data and credential exposure.
- Supplier cyber risk ratings, trends and material change notifications.
- Evidence-based findings that distinguish confirmed and inferred risks.
- Management of disputed findings, false positives and shared infrastructure noise.
Supplier Due Diligence and Assessment
DESIRABLE - DBW wishes to understand how platforms support proportionate supplier assurance.
- Configurable questionnaires and assessment workflows.
- Collection and retention of evidence, documents and attestations.
- Assessment history, approvals, exceptions and accepted risks.
- Scheduled and event-driven reassessments.
- Secure supplier engagement and response management.
Supplier Inventory and Tiering
DESIRABLE - DBW wishes to understand how platforms enable risk-based supplier management.
- Supplier inventory or integration with an authoritative supplier register.
- Risk, criticality and business-impact tiering.
- Identification of critical suppliers and links to important business services.
- Differentiated monitoring, due diligence and reassessment by supplier tier.
- Ability to reassess and reclassify suppliers when risk or criticality changes.
Risk, Compliance and Operational Resilience
MANDATORY - DBW requires cross-functional assurance, governance and auditability.
- A common assurance view combining assessments, evidence, findings, decisions and actions.
- Mapping to internal, regulatory and assurance frameworks.
- Clear audit trails for assessments, approvals, exceptions and reassessments.
- Identification of assurance gaps, stale evidence and incomplete information.
- Support for regulatory compliance and financial crime as mandatory risk domains.
- Support for operational resilience, data protection and other desirable domains where available.
Workflow and Remediation
MANDATORY - DBW requires clear accountability for supplier risk treatment.
- Creation, assignment and tracking of findings, actions and remediation plans.
- Configurable approvals, escalation routes, reminders and notifications.
- Recording of accepted, mitigated, transferred or escalated supplier risks.
- Reassessment or workflow activity following material changes in risk.
- Supplier collaboration and secure exchange of remediation evidence where available.
Reporting and Assurance
MANDATORY - DBW requires reporting suitable for operational, executive, audit and assurance use.
- Detailed findings, supporting evidence and supplier-level risk history.
- Executive and portfolio reporting covering critical and high-risk suppliers.
- Reporting of overdue reviews, expired evidence and outstanding actions.
- Exportable assessment histories, audit trails and assurance evidence.
- Data access suitable for DBW reporting and analytics platforms.
Advanced and Future Capabilities
DESIRABLE - DBW wishes to understand additional value available beyond the core requirement.
- Fourth-party and wider supply-chain visibility.
- Concentration risk analysis.
- Financial health and credit-risk intelligence.
- AI and emerging technology risk assessment.
- Reputational risk monitoring and assessment.
- Supplier sustainability information, evidence and reporting relevant to public-sector procurement.
- Advanced analytics identifying connected or emerging supplier risks.
Integrations and data portability
Integrations are not assigned a single classification because necessity depends on the integration and the business outcome. Suppliers should describe native connectors, APIs, automated exports, licensing dependencies and implementation effort.
Confidentiality, information governance and conflicts
Suppliers should clearly identify information they consider genuinely commercially sensitive and explain the basis for that designation. DBW cannot guarantee that information marked confidential will be withheld where disclosure is required by law, including under applicable freedom of information, transparency or audit obligations. Suppliers should not include unnecessary personal data in their responses.
Suppliers must disclose any actual or potential conflict of interest connected with this engagement, including any involvement in advising DBW on the requirement or procurement approach. DBW will assess and manage identified conflicts and any risk of unfair advantage in accordance with the Procurement Act 2023.
DBW welcomes responses from small and medium-sized enterprises and other suppliers who can contribute relevant market insight. Suppliers may provide equivalent evidence, alternative delivery approaches or proportionate examples where these demonstrate the relevant capability. Nothing in this market engagement is intended to create an unnecessary barrier to participation.
CPV: Compliance software package · IT services: consulting, software development, Internet and support · Software package and information systems
The lotProcurement structure
single lot · no lot value publishedPipeline intelligence · planning stage: how this market runs before the tender is published
How Development Bank of Wales buys Compliance software package (CPV 4817), and who usually turns up
Development Bank of Wales’s published record next to the market for the same work. Frameworks and DPS are left out: they draw different bid counts. Whole-market view: Compliance software package (CPV 4817) →
How the contest usually goes
Winner shares use published awards; bid and price charts use contested lots.
i
How often small and medium firms win.
Share of awards where the winner’s size is known.
The counts under this question show how many awards have a known supplier size.
Small firms have won here. Neither number says whether you qualify; it describes who has been winning.
i
How often local firms win similar work.
Winners with a registered address in the delivery region, out of awards with a known address.
Local means the winner is registered in the region where that award was delivered.
A local branch does not count if the registered address is elsewhere.
Most of this buyer’s recorded winners were registered in the region where that award was delivered.
i
How long buyers here take to decide after bids close.
Middle value in days from the bid deadline to the award date, on competitions that published both.
Only decided tenders count, so slow ones still waiting are not in.
Half of these awards have an award date within 25 days of the bid deadline.
i
How often work is awarded with no recorded rival.
Direct awards and tenders where every published lot count shows one bid.
Both shares are minimums: some awards have no bid count.
Thin markets produce this too; it is not proof of a tailored specification.
Direct awards or one recorded bid are common here. Check the route before spending time on a bid.
How many bids did past lots attract?
i
How many bids past lots received.
Each colour is a bid-count range. Only competed lots with a published count are included.
Past bids do not predict this tender.
1 bid6% / 16%
2–325% / 31%
4–631% / 32%
7+38% / 22%
How did awards compare with estimates?
i
Where winning prices landed against estimates.
Each colour shows awards below, close to or above the published estimate, one lot at a time.
Past prices are a guide, not a bid price.
Below estimate29% / 55%
Within ±2%57% / 25%
Above estimate14% / 20%
Assess each lot i
What past awards tell you about each lot.
See the forecast, this buyer’s earlier suppliers and firms with relevant wins.
No supplier is confirmed as a bidder.
i
What past awards tell you about each lot.
See the forecast, this buyer’s earlier suppliers and firms with relevant wins.
No supplier is confirmed as a bidder.
Open a lot for its forecast, this buyer’s previous supplier and possible competitors, from published award history, not a bid list
Lot #1CPV 4817No real estimate
i
How many bids this lot may attract.
The forecast uses similar past competitions. The bar shows either that forecast or past bid counts; the line below says which.
Each lot shows its own forecast based on its own category; forecasts for different lots of the same notice are not comparative. The bar shows 377 past lots.
A forecast, not a list of bidders.
1 bid16%
2–331%
4–632%
7+22%
i
Where the award price may land.
The forecast uses similar awards and the buyer’s estimate. The band covers the middle half of likely prices.
No comparable awards for this lot yet.
A statistical guide from past awards, not a price to bid.
Who has supplied this buyer on similar work? i
Who has done similar work for this buyer.
Past contracts are matched by buyer, title and type of work.
A past supplier may not bid again.
i
Who has done similar work for this buyer.
Past contracts are matched by buyer, title and type of work.
A past supplier may not bid again.
No earlier contract of this buyer matches this lot on the published record.
Who could compete for this lot? i
Who could compete for this lot?
Firms with relevant past wins. On a framework, we show firms on that agreement.
None is confirmed as a bidder.
i
Who could compete for this lot?
Firms with relevant past wins. On a framework, we show firms on that agreement.
None is confirmed as a bidder.
Candidate suppliers for this notice have not been worked out yet, so this is not a verdict that nobody fits.
About this data
- Source. Official UK public procurement notices (Find a Tender), reused under the Open Government Licence v3.0. New notices arrive through the day; the figures are rebuilt nightly.
- Two views, kept apart. The authority’s own track record and the wider market for the same kind of work sit side by side and are never mixed. Where the local picture is too thin, a figure widens to a broader market and says which one it used.
- Forecasts are labelled. The price forecast and its range, possible competitors and the earlier-work matches are our estimates from past awards: not published facts, not win chances and not price advice. Official notices do not say who is bidding.
- Every figure shows what it rests on. Not every notice publishes a bid count, a value or a delivery region, so each figure carries the number of records behind it, and one built on few records is marked as such. The on a figure explains it; the counting rules are in the methodology. Spotted something wrong? Tell us.
Procedure terms & legal framework
From the official record- Legal basis
- UKPGA · 2023/54 Procurement Act 2023
- Procurement category
- Services
- Notice status
- Planned procurement
- Procurement threshold
- Above threshold (FTS publication)
- Regulatory regime
- Standard
- Commercial structure
- Stand-alone contract (no framework)
- Competition type
- Competitive procedure
- GPA / WTO covered
- Unspecified in notice
- Recurring procurement
- Unspecified in notice
- First published
- 29 Oct 2026, 14:37 GMT
- Last source update
- 29 Oct 2026, 14:37 GMT
- Authority reference
DBW00229.00- FTS notice number
2026/S 000-102703- Latest notice
- Preliminary market engagement notice (UK2)
- Classification (CPV)
- Delivery area
- Official registry OCID
ocds-h6vhtk-0793afFind a Tender
How it was run
Official notice- Submission deadline
- —
Timeline
29 Oct 2026 → 1 Apr 2027 · 4 dates- Planning notice published6h ago29 Oct 2026, 14:37 GMT
- Today29 Oct 2026
- Market engagementin 28 days26 Nov 2026, 23:59 GMT
For each capability area, suppliers should explain their available functionality and identify whether it is:
- Fully supported as standard.
- Supported through configuration.
- Supported through integration.
- Supported through customisation or professional services.
- Partially supported.
- A roadmap item.
- Not supported.
Responses should also identify relevant dependencies, implementation assumptions, limitations, additional modules, third-party data sources and additional costs.
Responses must be submitted through [eTenderWales/portal] by 10:00 on Thursday 26 November. Responses received after the deadline may not be considered.
Any clarification questions must be submitted through the portal by 12:00 on Tuesday 17 November. Suppliers should not contact DBW employees directly regarding this exercise. Clarification questions must be anonymised and must not include the names of any personnel, suppliers or organisations, or any other identifying details. DBW may decline to respond to questions that include such information. DBW may publish clarification questions and responses on an anonymised basis where they are relevant to other participants.
Responses should be targeted around the supplier’s product offering and should clearly explain how it addresses the capability areas, market evaluation questions, and commercial and delivery information set out in this document. Responses should not exceed 10 pages, excluding appendices containing pricing schedules, technical documentation or supporting evidence.
Responses will not be formally evaluated, scored or ranked and will not be used to shortlist or select suppliers. They will be reviewed solely to support DBW’s understanding of the market and inform any future procurement approach.
DBW may invite suppliers to demonstrations, clarification meetings or other follow-up engagement where this would support its understanding of the market. Any such engagement will be conducted on a fair and consistent basis. DBW will take proportionate steps to ensure that participation does not confer an unfair advantage, including making relevant information available in any future procurement and allowing appropriate time for suppliers to prepare tenders.
Market evaluation questions
- What differentiates the platform from cyber-risk-only monitoring solutions?
- Which capabilities are included in the core platform, and which require additional modules, data sources or professional services?
- How does the platform combine externally observed intelligence with supplier-declared information and assurance evidence?
- How can the platform coexist or integrate with a separate supplier and contract management solution?
- How does the platform address financial crime, reputational risk and supplier sustainability?
- How are asset attribution, false positives and shared infrastructure handled?
- What implementation approach is recommended for an organisation transitioning from cyber monitoring to broader TPRM?
- Which relevant capabilities are roadmap items rather than generally available?
- Tender notice expectedin 81 days18 Jan 2027, 23:59 GMT
- Contract startsin 153 days1 Apr 2027, 00:00 BST
Notice history
1 event · 1 release on Find a Tender- Preliminary market engagement notice published29 Oct 2026, 14:37 GMTUK2
Commercial outcome & contract awards
Pipeline notice- Awards (0)
- No award published
- Contracts (0)
- No contract published
- Bid statistics
- No aggregate bid statistics published
Contracting authority & participating public bodies
Official documents & specifications (1)
Official links; attachments are not copiedNotices published for this procedure
- Preliminary market engagement notice Preliminary market engagement notice on Find a Tender