Skip to main content
SearchEnquiry basket
OfficesIndia · UAE

Public procurement

Software on GeM, specified so that bids are comparable

Most public software procurement goes wrong before any supplier is involved — in a specification that names a product instead of a requirement, or omits the licence term, or counts workstations where the software is licensed to people. This is what to settle first.

The routes, and when each applies

Government e-Marketplace (GeM). The default channel for central and state purchases. Sellers list against product categories and buyers purchase either from a catalogue or through a bid. For a defined item — an office suite, a design subscription, a server operating system — GeM is normally the straightforward route, because the thing being bought is a product rather than a scope of work.

Direct purchase. Below a threshold set by the General Financial Rules a department may purchase without a competitive process; above it a competitive route applies, and above a further threshold a formal bid or reverse auction is required. Those thresholds are set by rule, have been amended, and are read against your own delegation of financial powers — so confirm the current figures from the GFR rather than from any supplier's website, including this one.

Tender. For composite requirements where licences come with migration, deployment or support. The specification carries the whole risk here: a tender written around one publisher's product names will either be challenged or will produce a single compliant bid.

Existing rate contracts and frameworks. Where a framework already covers the product, using it is faster and easier to defend.

Before bids open

The five lines that decide whether bids can be compared

  • Licence basisNamed user, device, or physical core — they are not interchangeable
  • TermPerpetual, one year or three; otherwise quotes are not comparable
  • Quantity by typeLicence counts, not headcount or workstation counts
  • Client accessServer CALs stated separately; core licences alone do not serve users
  • Support and deploymentScoped separately, or explicitly included in the licence line

Where public software purchases usually fail

The specification names a product rather than a requirement. Where a specific product genuinely is required — because an existing archive must open correctly, or a certified process depends on a fixed version — the justification belongs on the file at the time, not reconstructed after a challenge.

Named users are procured as devices. Most current design and productivity software is licensed to a person. A department buying one licence per workstation will either over-buy or find the licences cannot be deployed as planned.

Client Access Licences are omitted. A server priced on core licences alone is not a working server. CALs must also match the server version; older CALs do not cover a newer release, and on a refresh the CAL line is often larger than the server line.

Renewal is nobody's budget line. A perpetual purchase has no renewal. A subscription has one every year, and an unbudgeted renewal is the most common cause of an avoidable procurement emergency.

Academic eligibility is assumed. Academic programmes have criteria that are checked. A department is not automatically eligible because it is public.

After award

What the file should contain

  • InvoiceRaised to the department's own name, with GST
  • Purchase order and acceptanceBoth, against the award
  • Agreement or enrolment numberFor volume licences, with portal access
  • Term and renewal dateRecorded where a person will see it in time
  • Assignment recordWhich licences are deployed where, or to whom

A product key is not proof of licence

A key activates software; it establishes nothing about who is licensed. What does is the invoice in the department's name, the agreement number, and the licensing portal access. An audit, a CAG query or a successor officer will ask for those, and assembling them two years later from a supplier's records is possible and unpleasant.

Questions departments ask

GeM is a procurement channel, not a provenance check. What establishes genuineness is the documentation: an invoice in the department's name, the agreement or enrolment number, and portal access showing the entitlement against your organisation.

It can where there is a recorded justification — file-format compatibility with an existing archive, or a certified process that depends on a fixed version are the usual ones. Without a justification on the file at the time, a product-named specification invites a challenge and tends to produce one compliant bid.

Multi-year terms are generally available from the publishers and usually cost less per year. Whether a department may commit across financial years is a question for its own financial rules and delegation of powers, not for the supplier.

By licence type and count — for example, a number of named-user subscriptions of a stated product and term. Headcount and workstation counts both produce the wrong number, in opposite directions.

For server products there is usually a licensing route that covers external users without counting them individually. State the external access requirement in the specification so bidders price the right thing.

Send us the draft before bids open

The licence basis, the term and the quantity lines are where a specification is easiest to get wrong and hardest to fix once bids are open. We will read a draft and say what we think will produce incomparable bids.

Get a written quotation

Tell us the product and the number of users. We reply with an itemised quotation and a GST invoice follows the order. Nothing is ordered or charged by sending this.

Prefer to talk? Call 9711492098

What you need

In your own words — “laptops for the design team”, “Adobe Acrobat”.

Optional — term, renewal date, existing licences, a tender to answer.

Who to come back to

Sending this places no order and commits you to nothing.