Cost reasonableness in government IT — how to answer the FA's first kill question

What the FA is actually asking

The literal question on the file is some variant of: "Is the cost reasonable? Has market rate been established?" But the FA's mental model goes deeper. They are asking three things at once.

First: if I sign this and CAG audits it three years from now, will the audit team find that we paid 2× the going rate? Second: have I covered myself procedurally — is there a paper trail showing market test? Third: if I question this and the indenting officer pushes back, do they have evidence to defend it, or will the file go in circles?

Your file needs to answer all three — not just the literal question.

Why thin responses fail

The most common file failure looks like this: "Vendor's quotation attached. Industry standard rates." No comparables. No build-up. No source. The FA scratches it out within ten minutes.

The next most common failure: a single competitor's quote attached, often from a "friendly" vendor who is known not to be competing seriously. The FA flags it as fake-comparison risk and asks for two more genuine quotes.

The third: a vendor's own pricing sheet claiming "this is the going rate". Vendor's word is not market evidence. The FA returns the file.

The shape of a holding response

A holding response has four moving parts.

Part 1 — Multi-source comparable benchmark

At least three live, comparable engagements — same scope, same scale, same period — with documented attribution. If confidentiality applies, redacted attribution with auditable source. Government tender awards, GeM transaction history, and published case studies of comparable PSU procurements all qualify.

Part 2 — Line-item cost build-up

Person-days × billed rate × team mix. Show senior dev rate, mid dev rate, designer rate, PM rate, QA rate. Show estimated person-days per module. Multiply through. The total should match the quotation. The FA can re-derive your number — that is the whole point.

Part 3 — Delta analysis

Where your bid sits versus the comparables, with material variances explained. "Our cost is 8% above benchmark X because the requirement includes on-prem deployment which adds ₹2.4L; benchmark X assumed cloud." Each variance has a reason. The reasons are auditable.

Part 4 — Per-user / per-transaction unit economics

This is where most files miss. CAG's audit framework is increasingly outcome-based. Cost-per-user, cost-per-transaction, cost-per-document-processed — these are the units a CAG auditor wants. Showing them upfront in your noting is what separates a defensible file from a wounded one.

The legal anchors

The substantive provisions you cite in the noting:

• GFR Rule 173 — Determination of estimated cost; market survey requirement
• GFR Rule 153 — Procurement Manual's pricing-policy chapter
• DoE OM dated [latest] — Department of Expenditure guidance on cost benchmarking
• Manual for Procurement of Consultancy & Other Services 2021 — Annexure on pricing methods
• CVC Manual on procurement — chapter on price reasonableness
• Your departmental DFPR — most have a specific "reasonable rate" provision

Typical FA pushback patterns

Even with a strong response, expect second-round pushback. The patterns:

• "Your benchmark is from 2024 — costs have moved" — answer with quarterly inflation-adjusted comparables and CPI/IT-services-index citations
• "Show GeM rate for similar item" — pre-pull the closest GeM SKU rate and explain why your scope is wider
• "Why not L1 of three quotations?" — if you are not L1, document specifically why (technical floor not met, scope mismatch)
• "Person-day rate above DoE benchmark" — show rate-card delta against published DoE consultancy rate-cards with reasoned justification

What we hand you

When you engage us on a government project, the cost-reasonableness annexure is one of the first deliverables. You receive:

• A 3-comparable benchmark sheet populated for your specific scope
• A line-item build-up structured in your department's noting format
• A delta-analysis writeup explaining each variance with reasons
• A unit-economics table matching CAG's outcome-audit framework
• A citations sheet covering GFR Rule 173, DoE OMs, CVC Manual, your DFPR
• A second-round response pack for the four most common FA pushback patterns above

The full annexure typically replaces what would otherwise be 25 days of officer back-and-forth with the FA. We keep it under 8 pages — long enough to hold, short enough that the FA reads it.

Read the rest of the FA-Objection Field Guide

• The pillar — all 8 FA objections at a glance
• 1. Cost reasonableness — defending the price tag
• 2. Single-vendor / Rule 161 nomination — the 70% kill zone
• 3. IPR transfer & source-code escrow — owning what you bought
• 4. Scope creep & cost overrun — the change-control protocol
• 5. Hosting — on-prem vs NIC vs cloud vs hybrid
• 6. Exit terms & vendor lock-in — the 14-clause exit annexure
• 7. "Why not NIC / NICSI / CDAC?" — the comparison done right
• 8. MSME / GeM / Make-in-India preference — the screen note

Related reading

• Big Helpers Government & PSU programme
• 7 legitimate procurement routes (no GeM, no MSME yet)
• Vendor lock-in: hidden ₹crores in PSU IT
• NIC eHRMS alternatives