One eSourcing platform, end to end.

Platform or point tool: the distinction that decides everything else

A point tool solves one problem well. A tender portal takes submissions. A contract register holds expiry dates. A questionnaire product collects supplier evidence. Each is defensible in isolation, and many authorities have accumulated three or four of them without ever making a decision to do so. The cost appears later, in the seams: the same supplier exists three times with three different names, and nobody can say with confidence which record is current.

A platform makes the opposite bet. It accepts more configuration effort at the start in exchange for a single identity for every supplier, contract and person, so that activity in one module is visible and usable in another. When a contract manager records poor performance, the sourcing team sees it before the recompete. When an insurance certificate lapses, the market a supplier belongs to knows about it. Those connections are the product, not a feature list.

The honest test is whether you are buying integration work or avoiding it. If your team is small and your category spread is narrow, a well chosen point tool may serve you for years. If you run competitions across directorates, hold hundreds of live contracts and answer to internal audit, the reconciliation effort between separate tools will eventually exceed the price difference. Decide that question deliberately rather than arriving at an answer by accident.

Reference architecture: the five layers worth understanding

Under the marketing, most credible platforms share the same anatomy. Understanding it lets you ask better questions in a demo, because you can probe each layer rather than watching a scripted journey. The layers are the data model, identity and access, the workflow engine, the document store and the notification and audit layer. Weakness in any one of them shows up as manual work somewhere else.

The data model is the foundation. It defines what a supplier is, what a contract is, how a lot relates to a competition and how a framework call off relates to its parent agreement. A thin data model forces information into free text fields, and free text cannot be reported on, filtered or audited. When a vendor cannot show you an entity diagram or explain how a supplier record survives a company name change, that is a meaningful signal.

The workflow engine is what enforces sequence and separation of duties: deadlines that cannot be moved quietly, price envelopes that stay sealed until quality is locked, approvals that must happen in order. The document store must hold immutable published versions alongside working drafts. The notification and audit layer records who did what, when, and what they saw at the time, and pushes prompts before deadlines rather than after them.

• Data model: suppliers, competitions, lots, contracts, frameworks, markets, users, and the relationships between them.
• Identity and access: single sign on, role based permissions, external user accounts, delegated and time limited access.
• Workflow engine: stages, gates, approvals, sealed envelopes, deadline enforcement, separation of duties.
• Document store: versioned publication, working drafts, retention rules, exportable evidence packs.
• Notification and audit: activity logging, immutable records, expiry prompts, escalation to named owners.

Identity, single sign on and access control

Access control is where information governance reviews concentrate, and rightly so. A procurement platform holds commercially sensitive bids, supplier financial evidence and personal data about named individuals. The baseline expectation is single sign on against the authority's own directory, so that joiners, movers and leavers are handled by existing processes rather than by someone remembering to deactivate an account after a colleague leaves.

Internal roles need to be genuinely granular. A category manager, a finance approver, a legal reviewer, a service lead scoring a technical question and an external adviser brought in for one competition all need different views of the same record. Role based permissions should let you grant exactly that, and time limited access matters for advisers and interim staff who should not retain visibility once their engagement ends.

External identity is a separate problem. Suppliers manage their own accounts, often with several people from one organisation working on a single response. The platform needs to keep those users tied to a verified organisation record, handle the case where the person who registered has left, and avoid locking a bidder out at four in the afternoon on submission day. Ask specifically how supplier account recovery works before you buy.

The module set across source to contract

Source to contract runs from identifying a need through to managing the resulting contract and feeding what you learn back into the next competition. eSourcing Data covers that span: sourcing and tendering, supplier onboarding and assurance, evaluation and moderation, contract management, governance and audit, analytics and reporting, and below threshold workflows. Few teams switch everything on at once, but the estate should be understood before purchase because retrofitting a missing capability is rarely cheap.

The modules divide into two temperaments. Sourcing modules manage a bounded event: it opens, it runs, it awards, it closes. Assurance and contract modules manage a continuous state, where the work is keeping records current and catching things before they expire. Platforms built by sourcing specialists often handle the first well and the second thinly, and the gap only becomes visible about eighteen months in, when the first wave of contracts needs managing.

Below threshold workflow deserves particular attention because it carries the highest transaction volume and usually the weakest evidence. Officers across service areas will only use a light process, so a quote request that records who was asked, what came back and why the award was made is worth more than an elaborate one nobody adopts. Analytics then sits across all of it, turning activity into pipeline visibility, cycle times and supplier participation data.

Integration: finance, ERP, contract registers and national data

Integration is where platform projects most often disappoint, usually because it was described in a sentence and scoped in an afternoon. The important connections are outbound to finance and inbound from national sources. Outbound, an award needs to become a supplier record and a purchase commitment in the finance or ERP system without anyone retyping it, and contract values need to reconcile with actual spend so that variations and overspend are visible rather than discovered at year end.

Inbound, supplier data is increasingly available centrally. Under the Procurement Act 2023 regime, core supplier information is held once on the Central Digital Platform and reused across competitions, and opportunity and award notices are published through Find a Tender. A platform that can consume that data reduces the amount you ask suppliers to retype, which directly improves participation from smaller organisations who abandon repetitive registration processes.

Existing contract registers, spend analysis tools and case management systems in social care or highways may also need connections. The practical advice is to name every integration in the contract, specify the direction, frequency and owner of each, and agree what happens when a field does not map cleanly. Ask whether integration is delivered by documented API, by scheduled file exchange or by a bespoke build, because the answer determines who maintains it for the next five years.

Hosting, UK data residency and security

Most authorities now expect a cloud hosted platform with UK data residency, and eSourcing Data operates on that basis and is GDPR compliant. Residency answers only part of the question, though. Information governance teams will also want to know where backups sit, whether support staff can access production data, how that access is logged, and which subprocessors are involved in email delivery, document conversion or analytics.

Security questions worth asking are practical rather than theoretical. How are bids encrypted before the opening date, and who technically could read one early. How long are audit logs retained, and can they be altered. What is the tested recovery time if the service is unavailable during a live submission window, and what is the documented process for extending a deadline in that circumstance. Vendors that have thought about failure will answer these quickly.

Retention and exit deserve equal attention and usually get none. Public bodies hold procurement records for years and must be able to produce them long after a supplier relationship ends. Establish before signature how records are retained, how personal data is removed when retention expires, and what an exit export actually contains: whether it is usable structured data with its relationships intact, or a folder of files with no context around them.

Dynamic Markets under the Procurement Act 2023

The Procurement Act 2023 came into force on 24 February 2025 and replaced the Dynamic Purchasing System with Dynamic Markets, and utilities qualification systems with utilities dynamic markets. The change is architectural rather than cosmetic. Dynamic markets are permanently open, membership cannot be capped, applications must be assessed within a reasonable time, and pending applications must be considered before a competition concludes. A platform designed around lists that open, fill and close cannot support that without workarounds.

What that requires in practice is continuous processing rather than periodic exercises. Applications arrive at any time and must be assessed consistently against published conditions of participation. Supplier evidence must stay current through automated expiry prompts rather than an annual spreadsheet audit. And when a competition is approaching award, the system needs to surface any pending application so that it is considered, because overlooking one is a legal failure that is very easy to commit on a busy desk.

There is a sector split to configure correctly. Utilities operating in water, energy and transport may charge suppliers membership and award fees and may run member only tenders. General contracting authorities may not charge membership fees. If your organisation spans both, the platform must hold both rule sets structurally rather than relying on an individual remembering which regime applies to which market.

Implementation and the first ninety days

Implementation timelines depend far more on your readiness than on the software. The work divides into configuration, data, templates, permissions and people, and it is almost always the templates and the people that set the pace. A team with clean supplier data, agreed evaluation models and a named internal owner moves quickly. A team migrating a decade of contract records held inconsistently across directorates should plan in stages around the live pipeline.

A sensible shape for the first month is discovery and configuration: agreeing the data model against your structures, designing roles and permissions, connecting single sign on and settling which integrations are in scope. The second month is usually template rebuild and migration, plus training the core team, with a deliberately chosen first live competition. Pick something real but not politically critical, and run it end to end rather than piloting fragments.

By the end of the third month the goal is not full adoption. It is a competition awarded through the platform with a complete evidence trail, a contract record live in contract management, supplier assurance running automatically, and a decision made about the rollout sequence for the rest of the organisation. Resist the temptation to migrate everything at once. Departments that go live after seeing a colleague succeed need far less persuasion.

Total cost and commercial routes including G-Cloud 15

Licence cost is the visible part of a smaller total. Build the full picture before you compare vendors: implementation and configuration effort, data migration, integration development, training, internal time from procurement, IT and information governance, and the ongoing cost of whoever administers the system. A platform that is cheaper per year but requires a dedicated administrator is not necessarily cheaper. Pricing models vary by user, by spend, by module or by competition volume, and each rewards different behaviour.

Watch for models that penalise the behaviour you want. If suppliers or evaluators are charged per head, teams quietly limit panel sizes and involve fewer service colleagues, which weakens evaluation. If competitions are metered, below threshold activity migrates back to email. Ask how the price moves if your activity doubles, and what happens at renewal, because the second term is where the real commercial position becomes clear.

On route to market, public buyers can access eSourcing Data software through RM1557.15 G-Cloud 15, where 28 software services are listed on the Digital Marketplace alongside cloud support services. Framework purchases are made as call off contracts, which for many authorities is the shortest compliant path from decision to deployment. A framework listing is a route to market and nothing more, so still assess the platform against your own requirements and run your own due diligence.