Every deal runs on its own vocabulary. This glossary defines the terms behind RFPs, proposals, and modern sales workflows, in plain language, for the teams who live them.
Vendor selection is the stage of a buying process where an organization chooses between shortlisted suppliers, scoring them against defined criteria and making a defensible decision. It is the point where evaluation ends and commitment begins.
By selection, the arguments are made. What decides the outcome is how a committee weighs criteria they agreed weeks earlier, applied to documents you cannot change. Sellers who understand the mechanics compete on the right things. Sellers who do not spend the final weeks reinforcing a strength the scoring sheet barely rewards.
The other reason to understand it is risk. Selection decisions get challenged, audited, or second-guessed internally, so buyers need a decision they can defend. A supplier who makes the defensible choice easy is competing on better ground than one who is merely preferred.
Most processes score four groups. Functional fit against the requirement, which is the obvious one and rarely the decisive one once a shortlist is drawn. Commercial: price, but also total cost, payment terms, and how costs behave as volumes change. Risk: financial stability, security posture, compliance, and continuity. And delivery credibility: implementation approach, resourcing, and past performance on comparable work.
Weightings are where the decision actually lives, and in formal processes they are published in advance. A buyer weighting risk at 30 percent is telling you something different from one weighting price at 50. Non-scored factors still operate too: how easy a supplier was to deal with during the process is read as a preview of the contract.
Procurement is the whole function and the whole cycle, from defining a need through to managing the supplier years later. Vendor selection is one stage inside it, and a short one: the evaluation and decision between shortlisted candidates.
Confusing the two leads sellers to engage at the wrong moment. Selection is nearly the end. The stage that determines who reaches it is the requirement definition, which happens earlier and involves different people. Arriving in time for the selection is arriving in time to be compared, not in time to shape what you are compared on.
A retailer shortlists three suppliers for a workforce platform, scoring 40 percent functional fit, 25 percent price, 20 percent implementation, and 15 percent risk. Two suppliers score within a point on function. The winner takes it on implementation, with a named delivery lead, a phased rollout matched to the retailer's trading calendar, and two comparable references who had already been briefed to expect a call.
The material a selection panel scores was produced weeks earlier by several people under deadline. Whether it holds together, whether the delivery plan matches the price, whether the references are current, is decided at production time and cannot be fixed at the point of scoring. Cobl generates the response set from one deal workspace, so the documents a panel compares are internally consistent rather than reconciled in the final week.
The submitted document is the whole of your case. Everything after it is other people reading.
Typically two to six weeks from submission deadline to decision in the private sector, and longer in public procurement where standstill periods and approvals apply. Panels almost always take longer than the published timeline, and follow-up clarification questions are common.
A scoring grid listing criteria, weightings, and each shortlisted supplier, used to compare bids consistently and to document why the winner won. Formal processes publish the criteria and weightings in advance, and evaluators often score independently before comparing.
Only through what is in your submission and any sanctioned presentation or clarification. Contact outside the stated channel can disqualify a bid, especially in public procurement. The influence available at this stage is a fraction of what was available before the requirement was written.
Cobl reads the RFP and generates the full response set: go/no-go, answers, technical proposal, pricing, and slides, built on your own rules.