The eSourcing tools, explained.

Quotation and RFQ tools for below threshold spend

The quotation tool is the workhorse most authorities underuse. It exists to run a short competition for a requirement that is already specified, without dragging an officer through the full tender machinery. A good one lets you describe the requirement, pick suppliers from the existing supplier record, attach a structured pricing schedule, set a deadline and issue to everyone at once. Two clicks should not become two hours.

The pricing schedule is the part that decides whether the tool earns its keep. Free text pricing produces quotes that cannot be compared: one includes delivery, one prices a longer term, one has assumed a higher specification. A schedule with defined lines, units, quantities and stated inclusions forces like for like responses and lets the system rank them automatically rather than leaving an officer to normalise figures in a spreadsheet.

Below threshold work also needs its own light governance. The tool should record the value estimate, the route chosen against your standing orders, who was invited and why, and the reason for the award. That record is what auditors ask for and what officers rarely produce from memory. Because these buys are high in volume, the evidence has to fall out of doing the work rather than being assembled afterwards.

Tender and ITT builders: document packs and versioning

The tender builder assembles the competition itself: the notice, the specification, the terms, the questionnaire and the pricing model, held together as one versioned pack. The important word is versioned. When a specification changes mid competition, the system must know which suppliers received which version, publish the change to all of them, and prevent a quiet swap of a document that has already been issued. Without that, a challenge becomes very hard to answer.

Templates are the second half of the tool. A mature setup holds approved question libraries, standard terms, scoring descriptors and timetable patterns for each category and route, so that a new competition starts at eighty per cent complete rather than blank. This is where consistency across a devolved organisation actually comes from. It also stops evaluation criteria being written after the questions, which is one of the most damaging habits in public buying.

Structure the questionnaire deliberately. Separate selection stage matters, which are about whether a supplier is fit to be considered at all, from award stage questions, which are about the merits of the offer. Keep price in its own envelope. Mark each question as scored, pass or fail, or information only, and set word or character limits so evaluators are comparing responses of similar length.

• One locked version set per issue, with a change log visible to all bidders
• Question library with approved wording and agreed scoring descriptors
• Clear split between selection, award and pricing sections
• Response limits and file type rules stated at the point of upload
• Timetable template covering clarification window, deadline and standstill

The supplier portal, registration and onboarding

The supplier portal is where your market meets your process, and it has a direct commercial effect. If registration is heavy, smaller suppliers abandon it, competitions thin out and you pay for that in price and quality later. The test is simple: how long does it take a small firm with no bid team to register, find the documents, ask a question and submit a first response.

Onboarding should collect information once and reuse it everywhere. Company details, insurances, certifications, policies, financial evidence and self declarations against exclusion grounds belong in a supplier record that carries forward into every competition, with expiry dates tracked and renewal prompts issued automatically. Asking a supplier for the same insurance certificate three times in a year is the clearest sign that the tools are not joined up.

Assurance is the other half. The record should show what has been verified, when, by whom and against what evidence, and should flag lapses before a competition goes live rather than after award. For categories with safeguarding, building safety or security requirements, that expiry tracking is not administrative tidiness. It is the control that stops an unqualified supplier being invited by accident.

Clarifications: the Q and A log, anonymisation and publish to all

The clarification log is a small tool with outsized legal weight. Every question a supplier asks, and every answer given, sits in one place with a timestamp. The default behaviour should be to publish the answer to all participants, because information given to one bidder and not the others is where equal treatment fails most often, and it usually fails through helpfulness rather than intent.

Anonymisation matters because questions reveal strategy. A bidder asking whether a particular accreditation is acceptable is telling you something about their solution, and telling competitors too if the question is published with their name on it. The tool should strip identifying detail before publication, and the buyer should reword where the question itself would expose the asker. Where a question is genuinely commercially confidential, answer it privately and record why.

Discipline around the log is cultural as well as technical. If officers answer questions by email and then paste them into the system afterwards, timing is lost and some answers never make it. Route everything through the log, publish promptly rather than in one batch on the final day, and hold the clarification window open long enough that late answers do not force suppliers to rewrite a submission overnight.

Sealed submission, deadline control and controlled opening

Sealed submission is the tool that makes an electronic competition defensible. Responses are encrypted on upload and cannot be read by anyone in the authority, including administrators, until the deadline passes and opening is performed. That is a meaningfully different position from files landing in a shared mailbox, where the question of who could have seen what and when has no clean answer.

Deadline control should be absolute and visible. The clock is the system clock, it is shown to suppliers, and the submission route closes when it closes. Suppliers benefit from a tool that lets them upload progressively and shows what has been received, because most late submissions are caused by a large upload started too close to the deadline. Where an authority has a policy for handling a demonstrable system failure, that policy should be written down before it is needed.

Controlled opening records who opened what, when, and in whose presence. Envelopes are separated so that quality can be opened and scored before price is visible, which protects evaluators from anchoring their judgement on cost. The opening record, listing which submissions were received and their receipt times, is one of the first documents anyone asks for when a competition is questioned.

Evaluation, scoring, moderation and conflicts of interest

The evaluation tool holds the criteria, weightings and scoring descriptors that were published, and presents each evaluator with the responses they are responsible for. Independent scoring comes first: evaluators should not see each other's marks or comments before entering their own, because visible scores pull a panel towards the first opinion expressed. The system should enforce that rather than relying on people to behave.

Moderation is where consensus is reached, and it is the record that matters most in a debrief or a challenge. A consensus score with no written rationale is close to worthless. Good practice is to capture why the mark landed where it did, referenced to what the response actually said, and to note where an individual score moved and on what basis. That text then becomes the feedback issued to unsuccessful bidders, rather than something written fresh weeks later under pressure.

Conflict of interest declarations belong in the same tool, not in a side email. Each evaluator declares before seeing submissions, declarations are recorded against the competition, and any mitigation such as removal from a lot is logged. Under the Procurement Act 2023 conflicts assessment is an explicit expectation, and it is far easier to evidence when the declaration sits next to the scores it relates to.

• Scoring descriptors written as observable evidence, tested on a sample answer
• Independent scoring locked before consensus discussion opens
• Moderation notes explaining every mark, not only the disputed ones
• Price envelope sealed until quality scoring is complete
• Declarations and mitigations recorded per evaluator per competition

eAuctions: formats, and when an auction is the wrong tool

An eAuction is a live, time bounded bidding event run after evaluation of the non price elements, in which qualified suppliers compete on price or on a price and quality index. The English reverse auction is the familiar format: prices fall, bidders see their position, and a small extension is triggered by a late bid so the event is not won by the fastest connection. Japanese auctions instead announce descending price levels and ask each bidder whether they will remain in at that level.

Ranked auctions show a bidder their position rather than the leading price, which sustains competition without publishing a competitor's exact number. Multi lot auctions run several related lots at once, which suits categories where suppliers want to bid for a combination and where lotting decisions materially affect the price they can offer. The choice of format is a commercial decision and should be made with the market in mind, not by habit.

Auctions work when the specification is genuinely fixed, the market is competitive with enough credible bidders, the switching cost is understood and price is the remaining variable. They are the wrong tool where quality differentiates the offer, where there are few suppliers, where the requirement is complex or novel, or where a supplier relationship matters more than a marginal saving. Running an auction into a thin market damages trust and rarely produces a durable price.

Award, standstill and contract award notices

The award tool turns the moderation record into the correspondence and notices the regime requires. Successful and unsuccessful suppliers are notified, each unsuccessful bidder receives feedback drawn from the consensus rationale, and the standstill period runs on a recorded timetable rather than in someone's diary. Because the assessment summary is generated from the evaluation record, the letter says the same thing the file says, which is not always true when feedback is written by hand.

Standstill exists so that a supplier who believes the decision was wrong can raise it before the contract is signed. The tool should hold the clock, record when notices were sent to each supplier, and block contract signature until the period has run. Sending notices at different times to different bidders, which happens easily in a manual process, muddies when the period actually started.

After standstill comes the contract award notice and the contract details record, then the handover into contract management: key dates, milestones, KPIs, variations and expiry alerts. A competition that ends at award and leaves the contract to a spreadsheet loses most of the value it just spent months creating. The award record should be the opening entry of the contract file, not the closing entry of the tender file.

Which tools run a Dynamic Market

Dynamic Markets replaced Dynamic Purchasing Systems when the Procurement Act 2023 came into force on 24 February 2025, and they place different demands on the tooling. A dynamic market is permanently open, so applications arrive continuously rather than in one qualification round. Membership cannot be capped, applications must be assessed within a reasonable time, and a pending application must be considered before a competition concludes. Software built around an open then closed supplier list cannot meet that without workarounds.

In practice three tools carry the load. The application workflow assesses each applicant against the published conditions of participation and records the decision and reason. The assurance tool keeps member evidence current through automated expiry prompts, so the pool stays qualified without an annual manual audit. The competition tool then runs call offs among members, which can be short because qualification has already happened at the front door.

One control deserves particular attention: the check that no pending application is overlooked when a competition is closing. That is a legal requirement and the easiest one to breach accidentally on a busy desk, so it should be a system prompt rather than a personal habit. Sector rules differ too. Utilities in water, energy and transport may charge suppliers membership and award fees and may run member only tenders, while general contracting authorities may not charge membership fees, and the platform should hold both rule sets.

The audit trail and reporting layer underneath

Every tool above writes to the same activity log, and that log is the real product. It records who did what and when: documents published and revised, questions asked and answered, submissions received, envelopes opened, scores entered and changed, moderation agreed, notices issued. The test of a system is whether you can export a complete evidence pack for one competition without reconstructing anything by hand.

Permissions and retention sit alongside it. Role based access means finance, legal, service leads and external advisers see exactly the part of a competition they need and no more, which matters particularly where an external adviser supports evaluation. Retention rules should be set once and applied automatically, so records are kept for the required period and disposed of afterwards rather than accumulating indefinitely in personal drives.

The reporting layer answers the management questions that individual competitions cannot: cycle times by route and category, where spend is fragmenting, how many suppliers bid and how many were small or local, which evaluators are consistently outside panel consensus, and how social value commitments made at award are performing in delivery. eSourcing Data brings these tools together across source to contract with UK data residency and GDPR compliance, and public buyers can procure the software through RM1557.15 G-Cloud 15, where 28 software services are listed on the Digital Marketplace alongside cloud support services, bought as call off contracts.