Source-to-contract software, one connected record.

What source to contract actually means

Source to contract, usually shortened to S2C, covers everything from identifying a requirement to managing the resulting contract. It sits before purchase to pay, which handles requisitions, orders, invoices and payment. The distinction matters because the two solve different problems: purchase to pay controls transactions, while source to contract controls commitments. Almost all of the value and almost all of the risk in public procurement is created at the commitment stage, months or years before the first invoice.

The stages are familiar even where the labels differ: category and demand analysis, market engagement, specification, route to market, competition, evaluation and award, contract creation, supplier onboarding and assurance, contract and performance management, and renewal or exit. Each stage produces data the next one needs. When they run in separate systems, that data is re entered, degraded and eventually contradicted.

It also spans the whole spend profile, not just major tenders. Below threshold quotes, framework call offs, Dynamic Market competitions and direct awards are all source to contract activity, and by volume they are most of it. A platform that only handles set piece tenders leaves the majority of activity outside the system, which is why so many authorities have excellent records for a few procurements and very little for everything else.

• Pipeline, demand analysis and category planning
• Market engagement and specification development
• Route to market selection: open competition, framework, Dynamic Market, below threshold
• Notices, tender documents, clarifications and sealed submissions
• Evaluation, moderation, award and standstill
• Supplier onboarding, assurance and master data
• Contract register, obligations, variations and performance
• Reporting, governance and audit across all of the above

Why one connected platform beats point tools

Point tools are usually bought one crisis at a time. An e tendering system after a challenge, a contract register after an audit finding, a supplier portal after a fraud incident. Each solves its problem and each adds an integration, a login, a data owner and a version of supplier truth. Within a few years the organisation has more systems than it has procurement staff, and the effort of keeping them aligned exceeds the effort they were meant to save.

The connected argument is not really about convenience. It is about traceability. In one platform you can follow a single thread from the entry in the forward plan, through the notice, the tender pack, the clarifications, the submissions, the scores, the moderation, the award, the contract, the obligations and the performance record. That thread is what an auditor, an internal challenge or a serious incident review actually asks for, and it cannot be reconstructed across four systems with different identifiers.

There is a second, quieter benefit. Connected data lets each stage improve the next. Evaluation data tells you which criteria never separate bidders. Contract performance tells you which suppliers to invite next time. Supplier assurance status stops an entity with expired cover being invited at all. Bid commitments become contract obligations without anyone retyping them. None of that is available when the stages are strangers to each other.

The regime: procuring under the Procurement Act 2023

The Procurement Act 2023 came into force on 24 February 2025 and reshaped how the lifecycle is expected to run. Procurement is organised around a sequence of notices that follow a requirement from planning through award and into contract performance, with transparency as the default rather than as an occasional publication duty. The practical consequence is that an authority now produces more linked artefacts, and those artefacts must agree with each other.

The Act also gives more design freedom. The competitive flexible procedure lets an authority build a process suited to the market rather than forcing everything into a fixed procedure, including multiple stages, dialogue or negotiation. That freedom is only usable safely if the process you published can be enforced by the system you run it in, because the published process is the one you are bound by. Freedom without control simply increases exposure.

Supplier conduct and performance sit inside the regime too, through exclusion grounds, a central debarment list and expectations around recording poor performance. That draws supplier management and contract management into what used to be a purely sourcing conversation. It is difficult to consider past performance in an award decision if performance is recorded, when it is recorded at all, in a spreadsheet held by one service.

Dynamic Markets in the lifecycle

The Act replaced the Dynamic Purchasing System with Dynamic Markets, and replaced utilities qualification systems with utilities dynamic markets. A Dynamic Market is permanently open, membership cannot be capped, applications must be assessed within a reasonable time, and any pending application must be considered before a competition concludes. That last requirement links two activities that were previously independent: your rolling assessment queue and your live competition timetable.

Dynamic Markets are the clearest example of why a joined up platform matters. Membership assessment is supplier assurance. Running a competition from the market is sourcing. The resulting call off is a contract. If those three live in different systems, the market becomes an administrative burden that quietly falls behind, and falling behind is precisely the failure mode the rules do not permit. Run in one place, it is simply a queue with visibility.

Utilities have additional latitude. Water, energy and transport authorities may charge suppliers membership and award fees and may run member only tenders. General contracting authorities may not charge membership fees. Both models need the same underlying discipline: published conditions of membership, assessments made against those conditions and recorded, and a clear picture of which members are eligible for which competitions.

Below threshold and the long tail

Ask a procurement team where their risk sits and they will describe the major tenders. Ask where the value leaks and the honest answer is the long tail: single quotes, informal renewals, direct awards made because a service was under pressure, and spend with suppliers nobody assured. It is high volume, low individual value and invisible, which is exactly the combination that resists policy solutions.

The only thing that works is making the compliant route the easiest route. A service manager who needs a contractor next week will follow a guided workflow that takes ten minutes and produces a compliant result. They will not follow a process that requires reading a manual and emailing the procurement inbox. Proportionate below threshold workflows, with the notice and record keeping handled automatically, convert the long tail from a blind spot into data.

That data then feeds the rest of the lifecycle. Aggregation opportunities become visible, forward pipelines populate from real expiry dates, local and small business spend becomes measurable, and category managers can see where a framework would replace fifty separate quote exercises. Most authorities find more improvement in the tail than in re running their largest contract.

Sector realities: councils, NHS, housing, education, charities and utilities

Councils need breadth and delegation: dozens of services buying very different things, with a small central team that cannot review everything. The lifecycle argument lands hardest here because the alternative is a different practice in every directorate. NHS bodies operate within collaborative structures and shared frameworks, with clinical involvement in specification and evaluation, and with provider selection rules for certain health services sitting alongside the Act.

Housing associations run heavy repairs, planned works and compliance programmes where supplier assurance, building safety competence and contract performance are effectively one continuous obligation rather than three stages. Education trusts have minimal central capacity and rely on frameworks, so the value of a lifecycle platform is mostly in automation and alerting rather than in process sophistication.

Charities and grant funded organisations often procure under funder conditions and have to evidence value for money to a third party, which makes the audit trail the primary deliverable. Utilities in water, energy and transport work under the specific rules for utilities dynamic markets, including the ability to charge membership and award fees and to run member only tenders, and they typically manage long, capital heavy contracts where the post award stage dominates.

Implementing source to contract without a two year programme

Whole lifecycle implementations fail when they are attempted all at once. The sequence that works starts with the supplier master record, because everything else attaches to it and because cleaning it exposes duplication and assurance gaps you need to know about anyway. Sourcing follows, because new competitions can start in the new system immediately without migrating anything. Contracts come next, and the register populates itself from awards while historic contracts are added by expiry date rather than in bulk.

Below threshold workflows are worth bringing forward rather than leaving until last. They deliver visible relief to service teams, they generate the data that makes everything else more useful, and they build goodwill with the people whose cooperation you need. Advanced analytics should wait until there is enough clean data to be worth analysing, which is usually two or three quarters in.

Configuration decisions matter more than software features: your document templates, scoring models, approval thresholds, delegation limits, assurance requirements by category, and renewal lead times. These encode how your organisation actually works, and getting them approximately right at the start avoids the far harder job of changing them once several hundred procurements have run through them.

• Start with the supplier master record and de duplication
• Run new competitions in the new system rather than migrating live ones
• Populate the contract register from awards, add history by expiry date
• Bring below threshold workflows in early for adoption and data
• Agree templates, thresholds and delegations before go live

Buying source to contract software and what to ask

Public buyers can buy eSourcing Data software through RM1557.15 G-Cloud 15, with 28 software services listed on the Digital Marketplace plus cloud support services. Framework purchases are made as call off contracts, so the route is a framework call off run in line with the framework rules rather than a full open competition. For most authorities that is the difference between having a platform this financial year and having one the year after.

The questions worth asking a supplier are practical. Can a below threshold quote be run in ten minutes by someone who is not a procurement professional? Can Dynamic Market applications be assessed as a managed queue with visibility against live competitions? Do bid commitments become contract obligations without re keying? Where is the data held? Can you export everything if the relationship ends? How is the audit trail generated, and is it automatic?

Be sceptical of demonstrations built on clean sample data. Bring a real, awkward requirement of your own: a competition with lots, a price model with an outlier, a supplier with a group structure, a contract with variations. Systems look similar in a scripted walkthrough and behave very differently on a real case, and the gap between the two is where implementation pain comes from.

How eSourcing Data delivers source to contract

eSourcing Data covers the full source to contract lifecycle in one platform: sourcing and tendering, supplier onboarding and assurance, evaluation and moderation, contract management, governance and audit, analytics and reporting, and below threshold workflows. It is built for the Procurement Act 2023 regime, with Dynamic Markets, notice workflows and the competitive flexible procedure treated as everyday activity rather than as exceptions bolted onto an older model.

Because the stages share one record, the traceability is real: a forward plan entry becomes a notice, a notice becomes a competition, a competition becomes an evaluation, an evaluation becomes an award and a contract, and the contract carries the obligations the supplier was actually scored on. Data is held with UK data residency and the platform is GDPR compliant, which matters for information governance sign off as much as for procurement.

On the supplier side, sister platforms support the other half of the market: WinAContract offers free UK tender search at winacontract.co.uk, and BidWriter provides AI assisted bid writing at bid.winacontract.co.uk. For buyers, the Procurement Library at /resources/library sets out the official guidance under the Act, the Procurement Policy Notes and the commercial playbooks that sit behind the process described here.