How to Procure IT Services on GeM Without a Weak Bid

Quick answer: To procure IT services on GeM, first check whether a standard service category fits, then pick the route by value: direct purchase up to Rs 50,000, L1 purchase up to Rs 10 lakh, and bid or reverse auction above that, as revised in July 2024. Write a measurable scope, SLAs and milestones before the bid goes live.

Buying a laptop on the Government e Marketplace (GeM) takes minutes. Buying a citizen portal, a data centre upgrade or a year of IT helpdesk support is another matter. Many departments run a correct GeM process and still end up with a vendor who cannot deliver, because the bid described the need in one vague paragraph and price decided everything after that.

This guide is for procurement officers, IT nodal officers and heads of offices. It explains how to procure IT services on GeM step by step: the rules, the buying routes, the scope and SLA details that decide quality, and the checks that keep the file clean for audit.

What the Rules Say About Buying on GeM

Rule 149 of the General Financial Rules (GFR) 2017 makes it mandatory for central government ministries and departments to procure goods and services on GeM when they are available there. The value limits under this rule were revised by the Department of Expenditure through an Office Memorandum dated 10 July 2024:

Estimated value	Buying route on GeM	What it means for IT services
Up to Rs 50,000	Direct purchase from any available seller who meets the requirement	Small, well-defined jobs such as a one-time configuration or a short support visit
Above Rs 50,000 and up to Rs 10 lakh	L1 purchase from the lowest priced seller among at least three sellers or manufacturers who meet the requirement	Standard catalogue services such as basic AMC, website hosting or a fixed manpower role
Above Rs 10 lakh	Bid or reverse auction on GeM	Most software development, portal, system integration and managed service projects

Older guides, and some department circulars, still quote the earlier limits of Rs 25,000 and Rs 5 lakh. Use the current limits, and check whether your ministry or state has issued its own orders. State governments are not bound by the GFR directly, but many have made GeM mandatory or preferred through their own notifications.

Why IT Service Bids on GeM Go Wrong

Problems in GeM service procurement rarely come from the portal. They come from what goes into the bid.

• The scope is copied from an old tender. It carries outdated technology choices and misses current needs such as mobile access, security audits or data protection duties.
• Requirements describe technology, not outcomes. Vendors quote on different assumptions, and the L1 bidder is often the one who assumed the least.
• SLAs are missing or unmeasurable. "Prompt support" cannot be enforced. "Critical issues resolved within 4 hours" can.
• Ownership is not stated. Source code, data and domain names stay with the vendor, which makes it hard to change vendors later.
• The contract ends at go-live. No budget is kept for patches, hosting or user support, so the system decays within a year.

The Fix: How to Procure IT Services on GeM Step by Step

Follow these steps in order. Each one also leaves a record that helps during audit.

1. Check availability on GeM: search for a service category that matches your need, such as cloud services, website development, IT manpower or hardware maintenance, and record the search result and the reason for your chosen route.
2. Estimate the value and pick the route: prepare a reasoned cost estimate, then choose direct purchase, L1 purchase, bid or reverse auction according to the current Rule 149 limits and your department's orders.
3. Write an outcome-based scope: describe the problem, the users, the functions, the integrations, the hosting location, languages, security requirements and the deliverables, including source code and documentation.
4. Define milestones, SLAs and payment terms: link payments to checkable milestones such as requirement sign-off, user acceptance testing, security audit and go-live, and write SLAs for uptime, response and resolution times.
5. Set proportionate eligibility and evaluation criteria: ask for experience and turnover that match the project size, and choose an evaluation method permitted by your rules that fits the complexity of the work.
6. Use a custom bid where no category fits: if the standard categories cannot describe the work, use GeM's custom bid option for services and attach the detailed scope document.
7. Manage the contract after award: hold a kick-off meeting, sign off the detailed requirements, run regular reviews with minutes, involve real users in testing, and collect source code, documentation and credentials at hand-over.

Writing a Scope Vendors Can Price Accurately

The scope of work decides whether bids are comparable. A useful structure for IT services:

• Background: what problem the system solves and who will use it.
• Functional needs: modules, workflows, reports, user roles and approval levels.
• Technical needs: hosting, integration with existing systems, supported browsers and devices, and languages such as English, Hindi and Marathi.
• Compliance: accessibility and design standards for government websites, such as the GIGW 3.0 guidelines, and a security audit before go-live.
• Deliverables: source code, documentation, training material, admin credentials and a hand-over plan.
• Support: warranty after go-live, then any maintenance period with its own SLAs.

When you are not sure how to describe a technical need, describe the outcome. "Citizens must be able to apply and track the status of an application on a mobile phone" is clearer, and easier to test, than a list of technologies.

Choosing the Right Evaluation Method

The evaluation method should match the type of service. The table below is a general guide; always follow the methods your rules permit.

Type of IT service	Typical approach	What to get right
Standard, well-defined services (hosting, AMC, fixed roles)	L1 after technical qualification	Exact specifications and SLAs so the cheapest bid is still fit for purpose
Software development or portals	Bid with strong technical qualification, or quality and cost based selection where permitted	Detailed scope, demo or presentation stage, clear acceptance criteria
Managed services and helpdesk	Bid with SLA-linked payments	Measurable service levels, penalties that are realistic, reporting format
Cloud and hosting	Bid or catalogue route based on value	Hosting policy, data location, empanelment requirements and exit terms

For hosting, many departments must use government or empanelled cloud providers. See our note on MeitY empanelled cloud service providers before you write that section of the bid.

SLAs and Penalties That Work

For ongoing IT services, the SLA is the contract. Keep it simple and measurable:

• Uptime: a monthly percentage for the application or service, with planned maintenance windows defined.
• Response and resolution times: separate targets for critical, high, medium and low priority issues.
• Reporting: a monthly SLA report in an agreed format, reviewed in a meeting.
• Penalties: a small deduction for each breach, capped at a reasonable share of the monthly fee, with a termination clause for repeated failure.

Penalties that are too harsh discourage capable vendors from bidding. Penalties that are too light are ignored. A cap with a clear escalation path usually works best.

Audit-Ready Checklist

• GeM availability search done and recorded.
• Cost estimate prepared with its basis noted.
• Route chosen according to current Rule 149 limits and department orders.
• Scope covers function, technology, security, compliance and hand-over.
• Milestones and payments linked to checkable deliverables.
• SLAs and penalties defined for ongoing services.
• Eligibility criteria proportionate to project size.
• Ownership of code, data and domain stated in the bid.
• Security audit planned before go-live. Our guide to CERT-In empanelled security audits explains what to ask for.

Frequently Asked Questions

Is GeM mandatory for state government departments?

GFR Rule 149 applies to central government ministries and departments. Many states have issued their own orders making GeM mandatory or preferred. Check the current orders of your state's finance or industries department.

What are the current GeM purchase limits?

Under the Office Memorandum of 10 July 2024 revising GFR Rule 149, direct purchase is allowed up to Rs 50,000, L1 purchase from at least three sellers up to Rs 10 lakh, and bid or reverse auction is used above Rs 10 lakh. Check for any later revisions before you start.

Can we buy a custom software project on GeM?

Yes. If no standard category fits, GeM supports custom bids for services. The quality of your scope document matters even more in this case, because it is the only basis vendors have for pricing.

What if the lowest bidder cannot deliver?

This risk is best handled before the bid, through clear technical eligibility, a detailed scope and realistic milestones. After award, use the contract's review, penalty and termination clauses and record every issue in writing.

Should hosting be part of the same bid?

It can be, if your hosting policy allows it. State the hosting requirement clearly so that every vendor quotes on the same basis. Some departments buy hosting separately through an empanelled provider. For a related look at digital tendering, see our post on e-tender management systems.

How Affix Center Can Help

Affix Center builds and supports e-governance platforms for public bodies, including citizen portals, workflow systems and secure hosting. We can help departments turn a need into a clear technical scope, plan realistic milestones and SLAs, and deliver and support the system after award. Our IT AMC services cover hardware, network and server support and helpdesk. If your department is preparing an IT procurement on GeM, contact our team to discuss the requirement.