eSourcing services - software, or fully run for you.

Why software on its own rarely delivers the benefit

Most disappointing eSourcing deployments are not software failures. The tool works, the licences are paid for, and officers carry on running tenders by email because the system was configured to mirror nobody's process in particular. Default templates that do not match the authority's contract procedure rules, approval steps that route to a post that no longer exists, and a category structure inherited from a demo environment are enough to push people back to what they know.

The second failure pattern is partial adoption. Sourcing moves into the platform, contract management stays in a spreadsheet, supplier assurance stays in a shared inbox, and below threshold activity stays invisible. Each of those gaps breaks the chain that makes the record defensible, because the notice, the evaluation and the contract no longer sit in the same place. Auditors find the seams quickly, and so do challengers.

Services exist to close both gaps. Implementation work makes the system reflect how this organisation actually decides things. Adoption work makes using it the path of least resistance rather than an extra task. Neither is optional if the point of the investment is better outcomes rather than a new place to store documents.

Implementation and configuration, step by step

Implementation begins with discovery rather than with the system. That means reading the contract procedure rules and delegation scheme, mapping who approves what at which value, listing the notice obligations that apply across the contract lifecycle, and identifying the handful of process variations that genuinely need to exist as opposed to the ones that have simply accumulated. The output is a configuration design that a procurement officer can read and recognise.

Configuration then follows in a defined order: user roles and permissions, organisational and category structures, document and question templates, evaluation models and scoring descriptors, approval and workflow routing, notice points, and reporting views. Each is built, reviewed with the people who will use it, and adjusted before the next layer is added. Building everything at once and reviewing it once at the end is how deployments slip.

Data migration runs alongside. Live contracts with values, owners and expiry dates, supplier records with assurance documents and their renewal dates, and any historic procurement files worth retaining are cleansed and loaded. Cleansing is the real work, because most contract registers contain duplicates, missing end dates and contracts that ended years ago. Migrating that unchanged simply moves the problem into a better looking system.

Testing and go live complete the sequence. Structured testing takes real scenarios, an above threshold open procedure, a competitive flexible procedure, a call off from a framework or dynamic market, a three quote below threshold exercise, and runs each end to end including the notices. Go live is then staged, usually by category or by team, with a defined support period and a named person to escalate to.

• Discovery of rules, delegations, thresholds and notice obligations
• Roles, permissions and organisational structure
• Category structures and document and question templates
• Evaluation models, scoring descriptors and moderation settings
• Contract and supplier data cleansing and migration
• Integrations with finance, contract and identity systems
• Scenario based testing, then a staged go live with support

Integrations and the systems around procurement

Procurement never operates alone. The finance system holds the purchase orders and the actual spend, the identity provider decides who can log in, the corporate document store holds the signed contracts, and reporting tools pull it all together for committee papers. Integration work decides how much of that happens automatically and how much depends on someone remembering to rekey a contract reference.

The pragmatic order is usually single sign on first, because it removes an access barrier immediately and puts user administration where IT already manages it. Spend and purchase order data comes next, since a contract register without actual spend against it cannot support category planning. Document and records management links matter where retention schedules are enforced corporately rather than within procurement.

The point of integration work is to remove rekeying, not to build something elegant. Every manual transfer between systems is a place where the contract register drifts from reality, and a register that officers do not trust is one they stop using. Where a full integration is not proportionate, a scheduled export and import is often enough, provided somebody owns it.

Managed and outsourced sourcing services

Some organisations need the competitions run, not just the tooling to run them. Managed sourcing puts an experienced team on defined procurements or a defined portion of the pipeline: preparing specifications with the service, designing the procedure, publishing the notices for the authority to approve, handling clarifications, coordinating evaluation and moderation, and taking the process through standstill to award and mobilisation.

The arrangement only works when the boundary between doing and deciding is explicit. The team can prepare everything, but named officers of the contracting authority approve the procedure, approve the notices, approve the award recommendation and own the reasons recorded against each. Where that boundary is written into the working method at the start, the record supports the decision later. Where it is assumed, it usually does not.

Capacity support of this kind is most valuable against a peak: a wave of expiries landing in the same quarter, a grant funded programme with a spend deadline, or a transformation programme generating far more competitions than the establishment can absorb. It is a poor remedy for structural problems such as specifications arriving late, which slow an external team exactly as much as an internal one.

Category support and market engagement

Before a competition is designed, someone has to decide what is actually being bought and from what kind of market. Category support covers that work: analysing current spend and its distribution, mapping contract expiries against team capacity, testing whether the current lotting structure suits the supply base, and deciding whether a category is better served by its own competition, a framework call off, or membership of a dynamic market.

Preliminary market engagement is the other half. Done properly it tests whether the requirement is deliverable, whether the commercial model transfers risk to suppliers who can carry it, and whether smaller or local providers can realistically bid. Done as a formality it produces a room of incumbents agreeing that the current approach is fine. The difference is usually in who is invited and what they are asked.

Engagement has to be run so that it does not distort the competition that follows. That means publishing the appropriate notice, running open sessions rather than selective conversations, recording what was said and to whom, and making the same information available to everyone at tender stage. Where a participant has gained an advantage, it has to be addressed before the competition, not defended afterwards.

Supplier onboarding, assurance and support

Supplier assurance is where the administrative load quietly builds up. Insurance certificates, health and safety accreditations, financial checks, safeguarding and DBS positions, modern slavery statements, information security and data protection assurances, and equalities and environmental policies all have their own renewal dates. Managed as attachments in an inbox, they expire unnoticed, and the first time anyone checks is after an incident.

Services here cover designing the assurance model in the first place, deciding what is genuinely proportionate for each category and value band, loading the existing supplier base with its documents and expiry dates, and setting the reminder and escalation rules. It also covers the human side: contacting suppliers who have never used a portal, helping them complete their record, and handling the ones who need a phone call rather than an email.

Supplier facing support matters more than buyers expect. Every unanswered supplier query about registration or submission is a potential bid you do not receive, and small suppliers are the ones most likely to give up. A defined support route for suppliers during live competitions, with response times that reflect the tender deadline rather than a general service desk target, protects competition directly.

Training and adoption for buyers, evaluators and suppliers

Training has to be split by audience because the audiences are nothing alike. Regular procurement users need depth: building competitions, managing clarifications, running moderation, handling contract records. Occasional users such as budget holders need a short, specific session on the two or three things they will ever do. Both need to be trained in the organisation's own configured environment, using its own templates, not a generic demonstration tenant.

Evaluators are the group most often neglected and the group where poor practice costs most. Subject matter experts are drafted in from services, score perhaps once every two years, and are rarely told what an audit trail requires. A short practical session on applying the scoring descriptors, writing rationale that supports the score rather than restating the answer, what moderation is for, and what should never be put in an email prevents most common evaluation problems.

Suppliers need something different again: clear guidance on registering, keeping their record current, finding opportunities and submitting before the deadline. Written guidance, short recordings and an occasional open session cost little and reduce both failed submissions and support volume. For authorities with local supplier development commitments, this is also the most practical way to honour them.

Adoption is measured, not assumed. Counting competitions run in the platform versus outside it, the proportion of below threshold activity captured, the share of contract records with reliable expiry dates, and the volume of support tickets by type tells you where the configuration or the training still needs work.

Ongoing support, service levels and continuous improvement

After go live the service shifts from project to operation. That means a defined support route with response and resolution targets, a clear severity model that treats a live tender deadline differently from a cosmetic reporting issue, planned maintenance windows communicated in advance, and a named contact who understands the organisation rather than a queue that starts from scratch each time.

Severity definitions deserve real thought, because procurement has hard deadlines that most service desks do not model. An issue preventing submission an hour before a deadline is not the same class of problem as a report that renders awkwardly, even if both are technically minor. Agreeing that distinction, and the escalation path that follows it, at contract stage avoids arguing about it during an incident.

Continuous improvement is the part that gets dropped and should not be. A periodic review that looks at where processes stall, which templates get edited every time and therefore need changing, which approval steps add delay without adding control, and what new obligations have arrived since implementation keeps the configuration aligned with practice. Without it, workarounds accumulate until the system is describing a process nobody follows.

• Severity model that recognises live tender deadlines
• Response and resolution targets, with escalation named
• A support contact familiar with your configuration
• Release notes and planned change communicated ahead of time
• Periodic configuration review against actual practice

Governance and audit readiness under the Procurement Act 2023

The Procurement Act 2023, in force since 24 February 2025, front loads transparency across the contract lifecycle. Planned procurement and preliminary market engagement notices, tender notices that accurately describe the procedure designed, award and contract details notices, and ongoing information for larger contracts all have to be published in the authority's own name and at the right point. Services should make those points part of the workflow rather than a diary reminder.

The competitive flexible procedure raises the stakes, because the authority designs the procedure and the description published becomes the rulebook it must follow. Configuration work should therefore capture the designed procedure as a defined workflow, and any change to it should require a recorded decision. That is not bureaucracy, it is the evidence that the process followed was the process published.

The practical test of audit readiness is simple: can an officer who was not involved open a completed procurement and understand what happened and why. Scores with rationale, moderation records, clarification logs, shortlisting decisions, conflict declarations, standstill correspondence and the award decision, all attributable to named people and dated. Services that leave that record complete are worth more than any efficiency claim.

Sector specifics and how services are bought

Sectors differ in ways that change the configuration and the training, not just the branding. Councils need delegation schemes, committee cycles and social value practice reflected in workflow. NHS bodies bring clinical engagement, national framework use and their own approval routes. Housing associations carry consumer standards, building safety obligations and heavy repairs and maintenance activity. Education has academy trusts, funding conditions and small teams handling large capital projects.

Charities and voluntary organisations often procure under funder conditions rather than the Act, and need proportionate process that satisfies a funder audit without importing full public sector machinery. Utilities in water, energy and transport sit under a different part of the regime again: they may operate utilities dynamic markets, may charge suppliers membership and award fees, and may run member only tenders, none of which general contracting authorities may do.

Dynamic Markets are where implementation services and legal design meet most directly. Because a Dynamic Market is permanently open, membership cannot be capped, applications must be assessed within a reasonable time, and pending applications must be considered before a competition concludes, the operating model has to handle continuous assessment as business as usual. Configuring intake, assessment and call off competitions in one environment is what makes that manageable rather than relentless.

For public buyers, these services are commonly bought through RM1557.15 G-Cloud 15. eSourcing Data software is listed on the Digital Marketplace with 28 software services, alongside cloud support services covering implementation, configuration, data migration, training and ongoing support. Framework purchases are made as call off contracts, so the buyer runs its own search and evaluation on the Digital Marketplace and awards a call off on the framework terms. Data is held in the UK and the platform is GDPR compliant.

• Councils: delegations, committee cycles, social value practice
• NHS: clinical engagement, national frameworks, internal approval routes
• Housing associations: consumer standards, building safety, repairs volume
• Education: trust structures, funding conditions, small teams
• Charities: funder conditions and proportionate documented process
• Utilities: utilities dynamic markets, supplier fees, member only tenders