The 8 FA objections that kill government IT projects — and how a healthy file pre-empts each

If you are a government or PSU officer reading this, we already know what your week looks like. You found a vendor whose work fits your requirement better than anything on GeM. You want the project to succeed because it matters — to your department, to the citizens you serve, to the year you have left in your posting. You've drafted the noting. You've sent the file up.

And then it lands on the FA's desk.

The Financial Adviser is not your enemy. The FA is doing exactly what the rule book says — protecting the public exchequer, asking the questions that vigilance and CAG will ask three years from now. The problem is that the FA's checklist is largely invisible to most vendors and most indenting officers until the objection comes back. By then the file is wounded; another two months of back-and-forth begin; and somewhere in there, you get transferred or the budget head expires.

This article names the eight objections we see most often, in roughly the order they appear on the file. For each, we explain why the FA raises it, what a thin response looks like, and the shape of a response that holds. We deliberately stop short of the full playbook — every department's circumstances differ, and a templatised response is exactly the kind of thing CAG underlines in red. But by the end of this article, you will know whether your current file is healthy or wounded, and whether your vendor knows what they're doing.

The 8 objections — at a glance

Below — what each one actually looks like in your file, why most vendor responses fail, and the shape of a response that holds.

1. Cost reasonableness

This is the first question on every FA's checklist and the one most files fail. The FA wants to see that you have established a market rate and that your proposed expenditure sits inside it — or, if outside, that you have a specific, defensible reason.

The thin response: a single competitor's quote attached, or worse, a vendor's own claim that "this is industry standard". The FA crosses it out.

The shape of a holding response: a multi-source benchmark covering at least three live comparable engagements (with redacted attribution where confidentiality applies), a line-item cost build-up showing person-days × billed rate × team mix, a delta analysis against the comparables explaining each material variance, and a per-user/per-transaction unit economics view that survives the CAG audit framework.

→ Read the full deep-dive on this objection

2. Single-vendor / nomination justification

If your file proposes a Rule 161 nomination, this is where 70% of files die. The FA's question is precise: has competition been foreclosed lawfully, and is the chosen vendor uniquely capable?

The thin response: "Vendor has prior experience" or "Vendor's product is best in market". Both are inadmissible. The first is unranked; the second is unevidenced.

The shape of a holding response: a documented capability gap analysis showing why GeM-listed vendors don't meet specific technical requirements (with the GeM seller list and your evaluation matrix attached), the vendor's uniqueness evidence pack (product demos, prior installations at peer departments, technical certifications, source-code review by your IT cell), the market test showing the bid is competitive against comparable engagements, and the approval ladder traceback showing the right competent authority signed under the right delegation.

→ Read the full deep-dive on this objection

3. IPR transfer & source-code escrow

This objection looks simple but has killed more PSU IT projects than any other. The FA's question: at the end of the engagement, what does the government own, and what can it do with it?

The thin response: a one-line clause saying "all IPR vests in the purchaser". The vendor signs. Three years later, when the system needs a security patch, the source code is incomplete, the documentation is thin, the dependencies are pinned to deprecated versions, and the original engineers have moved on. The "ownership" is technical, not operational.

The shape of a holding response: a layered IPR clause covering source code, documentation, build scripts, infrastructure-as-code, design files, third-party licence inventory, and ongoing maintenance access; a source-code escrow agreement with a recognised escrow agent and a defined release-trigger schedule; a knowledge-transfer plan with structured weeks of overlap between vendor and client engineers; a code-quality acceptance test performed before final payment; and an auditable build pipeline the department can rerun independently.

→ Read the full deep-dive on this objection

4. Scope creep / cost overrun protection

FAs have seen too many ₹50-lakh contracts grow into ₹3-crore supplementaries. They will ask: what stops this from happening here?

The thin response: a fixed-scope clause and silence. This works on paper for six months, then collapses the moment a real-world change request comes in.

The shape of a holding response: a change-control protocol with explicit thresholds (e.g. ≤2% of contract value flowing through standing committee, 2–10% through Director, >10% through Competent Authority); a baseline scope document precise enough to make scope-creep visually obvious; a per-module pricing schedule so additions price themselves out without re-negotiation; a cumulative-spend tracker the department's PMU monitors monthly; and a contract-amendment template already pre-vetted by the FA so amendments don't require fresh financial-adviser review.

→ Read the full deep-dive on this objection

5. Hosting — on-prem vs cloud vs NIC vs hybrid

The hosting question now has three new layers: data-residency obligations under DPDP 2023, sectoral data-classification rules (CERT-In, RBI, IRDAI, MeitY), and the political optics of "where does the citizen's data live".

The FA wants to see: has the right hosting model been chosen for the right reason, and is the cost defensible across the contract life?

The thin response: "AWS / Azure / GCP — pay-as-you-go". The FA flags it for cost-uncertainty and data-residency.

The shape of a holding response: a hosting decision matrix covering on-prem, NIC cloud, MeghRaj, NICSI co-located, AWS/Azure GCC India, hybrid models — scored against your department's data-classification, latency needs, peak load, total-cost-of-ownership over 5 years, and disaster-recovery requirements; a capacity-planning document with usage assumptions; an AMC clause with locked rates for 3+ years; and a migration-portability annexure so you can leave the chosen provider without a rewrite.

→ Read the full deep-dive on this objection

6. Exit terms / vendor lock-in

The FA's question: what happens if the vendor underperforms, gets acquired, goes bankrupt, or simply walks away?

The thin response: a 30-day notice clause and "all data belongs to purchaser". This is technically true and operationally meaningless.

The shape of a holding response: a defined exit-management plan annexed to the contract, including data-export formats (open standards, machine-readable, full-fidelity), source-code & documentation handover protocol, infrastructure-credentials transfer process, knowledge-transfer to a successor vendor (with mandatory weeks of overlap costed in), running-system handover where applicable, and a contractual exit-cooperation obligation that survives termination; service-continuity bonds sized to your risk; and a vendor-financial-health monitoring mechanism so the file is never blindsided.

→ Read the full deep-dive on this objection

7. "Why not NIC / NICSI / CDAC / NeGD?"

This is the single objection that catches the most files unprepared. Every government IT project must demonstrate, on file, that the in-house national agencies were considered first. Skipping this is a procedural error CAG flags routinely.

The thin response: silence, or a one-liner saying NIC was unable to take up the project. The FA returns the file asking for NIC's written response.

The shape of a holding response: a formal NIC consultation — written request to your nodal NIC officer, written response from NIC (capacity, timeline, fit), with the response forming an annexure to your file; if NIC declines or proposes a multi-year wait, a comparative analysis against NIC's standard offerings (eHRMS, eOffice, eProcurement, eHospital, eGramSwaraj etc.) showing where the gap lies; the same exercise for NICSI, CDAC, and NeGD; and finally a recommendation note citing why a private vendor is the appropriate choice for this specific requirement, this specific timeline, this specific budget head.

→ Read the full deep-dive on this objection

8. MSME / GeM / Make-in-India preference

The Public Procurement Policy for MSEs, the Make in India Order 2017, the GeM preference framework — all of these create preferences the FA must verify before signing off. Skipping the verification (even in a non-GeM procurement) leaves the file procedurally weak.

The thin response: silence on the preference framework.

The shape of a holding response: a preference-screen note showing the procurement category, the applicable preference (Class-I/II local supplier, MSE preference, women-led MSE preference, startup preference), evaluation of available preferred vendors, the application or written exclusion of each preference with reasoning; the vendor's own preference status (Udyam registration, GeM seller status, NSIC SPRS, Startup India recognition) attached as evidence; and the procurement-route-to-preference mapping documenting why your chosen route honours the preference framework.

→ Read the full deep-dive on this objection

The 9th unstated objection — "is this vendor safe to work with"

Every FA also asks an unstated question: if this goes wrong, will this vendor disappear, sue us, or embarrass the department? The form does not have a column for this. Your file should answer it anyway.

The shape of a holding response: a vendor due-diligence pack covering CIN + GST history, latest ITRs and audited financials, key-personnel CVs, prior government clientele with verifiable references, ongoing litigation status, vigilance/blacklisting record (clean), and a partner-led account commitment (the partner you spoke to is the partner who will be on the project, not someone who disappears after signing).

Why this article exists

Most vendors will sell you a product. We sell you a file that survives. After 18 years of building software for Indian organisations, our hard-earned conviction is this: the difference between a successful PSU IT project and a stalled one is almost never technical. It is almost always procedural-financial. The vendor's code is fine; the FA file is wounded. The department's intent is sincere; the noting is incomplete.

We started the Government & PSU programme to fix that — to bring the procurement-savviness that small specialist vendors typically lack, into the room before the file is drafted, not after the FA returns it.

This article is a teaser. The actual playbook is co-written with your file, your noting officer, your IT cell and your FA's preferences. We don't templatise — we tailor.

What a free file health-check actually looks like

A 30-minute Zoom or in-person session with one of our partners. You bring your draft noting (or current FA objections). We score it against the 8-objection checklist. You walk away with a written one-page diagnostic — what's strong, what's wounded, what to add before the file goes back. No sales pitch. No follow-up nag emails. Many departments use the diagnostic and proceed independently — that is fine; the country gets a stronger file either way.

If you decide our engagement is the right fit for the next stage, we discuss commercials and route. If not, you keep the diagnostic and our blessings.

Frequently asked questions

What is an FA in government procurement?

FA stands for Financial Adviser - the officer in every Indian government department or PSU who scrutinises every procurement file for cost reasonableness, procedural compliance, and vigilance/CAG audit-readiness before competent authority sanction. FAs apply the General Financial Rules 2017, the department's DFPR (Delegation of Financial Power Rules), and CVC/CAG audit standards. Their objections are the single biggest reason small custom-software files get stuck in government for months.

What is the most common FA objection on a government IT file?

Cost reasonableness is the first objection on every FA's checklist - and the one most files fail. The FA wants documented market benchmarking under GFR Rule 173 with at least three comparable engagements, a line-item cost build-up (person-days x billed rate x team mix), a delta analysis explaining each variance, and per-user/per-transaction unit economics. A vendor's own quotation is not market evidence.

Can a single-vendor nomination under GFR Rule 161 actually clear the FA?

Yes - if the file documents four things: (1) capability gap analysis showing why GeM-listed vendors don't meet specific technical requirements with attached evaluation matrix; (2) uniqueness evidence pack - product demos, peer-installation references, technical certifications; (3) market test (price benchmarked against three comparable engagements even though not competitively tendered); and (4) approval ladder traceback to the right Competent Authority under your DFPR. Without these, ~70% of Rule 161 files die at FA review.

How long does an FA review typically take?

For a healthy file (all 8 standard FA objections pre-empted with annexures): 2-3 weeks. For a file that gets returned with objections: typically 4 months end-to-end as it cycles back-and-forth. The single biggest determinant is whether the file arrives FA-ready or arrives with the noting officer hoping the FA won't ask the obvious questions.

What is GFR Rule 173?

GFR (General Financial Rules 2017) Rule 173 governs the determination of estimated cost in government procurement. It requires the indenting officer to establish a market rate before procurement, typically via market survey, comparable transactions, GeM benchmark prices, or DoE published rate-cards. It is the statutory anchor for the FA's first cost-reasonableness objection.

Why does the FA ask 'why not NIC, NICSI, CDAC or NeGD?'

Because every government IT project must demonstrate on file that in-house national agencies were considered first. Skipping this is a procedural error CAG flags routinely. The defensible response is a formal NIC consultation (written request + written response), a comparative analysis against the closest NIC standard product (eOffice, eHRMS, eProcurement etc.), the same exercise for NICSI/CDAC/NeGD, and a recommendation note explaining why a private vendor uniquely fits this requirement.

Can a vendor not on GeM still serve government departments?

Yes - via at least seven legitimate procurement routes the GFR explicitly contemplates: GFR Rule 155 (three quotations under Rs 2.5 lakh), GFR Rule 161 (single-tender nomination with documented justification), sub-contractor to a GeM-empanelled prime, autonomous body bye-laws (ICAR institutes, state innovation councils, KVKs), innovation/R&D budget procurement (NIF, AIM, BIRAC, DST schemes), state IT empanelment (KEONICS, ELCOT, MahaIT etc.), and the pilot-then-larger-procurement compounding route.

What does 'IPR transfer' mean in government IT contracts and why does the FA care?

Standard contracts say 'all IPR vests in the purchaser' - which is technically true and operationally meaningless. The FA's real concern is whether the department can maintain the system three years on without the original vendor. A holding response includes a layered IPR clause covering source code + documentation + IaC + design files + third-party licence inventory, a tripartite source-code escrow agreement with defined release triggers, a structured knowledge-transfer plan with paid weeks of overlap, and a code-quality acceptance test before final payment.

Related reading

• Big Helpers Government & PSU programme
• 7 legitimate routes when vendor isn't on GeM/MSME
• Vendor lock-in: hidden ₹crores in PSU IT
• NIC eHRMS alternatives
• Custom attendance without forced Aadhaar
• AI-augmented government software development
• Open-source strategy for Indian government IT

Have an objection on your file we haven't covered here? WhatsApp Kashvi at +91 99939 82666 with the objection text and the project context. We'll respond with a written approach within 24 hours — yours to use, no commitment. — Kashvi