Scope creep — the change-control protocol that stops ₹50L turning into ₹3 crore

What the FA is actually asking

The literal question: "What stops scope creep here?" The FA's real concern is institutional memory. They have seen the pattern repeat: contract sanctioned for ₹50L, six months later the first supplementary ₹15L, twelve months later another ₹40L, two years in the project is at ₹3Cr and CAG is flagging it as cost overrun.

The FA wants to see governed evolution rather than uncontrolled drift.

Why thin responses fail

Standard failure: a fixed-scope clause and silence. This works for the first review. Then a real-world change request arrives — a new compliance requirement, a department reorganisation, a new minister's priority. There is no mechanism in the contract to handle it cleanly. So one of three bad things happens:

1. The vendor agrees verbally and bills later — file shows uncontrolled change
2. The vendor refuses without a supplementary — project stalls
3. A supplementary sanction is rushed through — every supplementary is a fresh FA review and CAG flag

The shape of a holding response

Part 1 — Change-control protocol with explicit thresholds

Define the change-management ladder upfront in the contract:

• Type-A changes (≤2% of contract value): standing committee can approve; recorded in monthly status report
• Type-B changes (2–10% of contract value): Director-level approval; written change-request and approval memo
• Type-C changes (10–25%): Joint Secretary / Director-level board approval
• Type-D changes (>25%): full Competent Authority + FA review + supplementary sanction

The protocol means most real-world changes flow through Types A and B without re-opening the FA review.

Part 2 — Baseline scope document

Precise enough to make scope-creep visually obvious. Common failure: SOW says "build a custom HRMS" — anything is then arguably in or out. Better: SOW lists modules, sub-modules, screens, business rules, integrations, with acceptance criteria for each.

When a change request arrives, you can point to the baseline and say "this is in" or "this is out" with no ambiguity.

Part 3 — Per-module pricing schedule

Modular pricing instead of a single lump-sum. When a new module is added, its price is already known from the contract — no re-negotiation needed. Vendors resist this because it caps their upside; the FA loves it because it eliminates the "one big surprise number" pattern.

Part 4 — Cumulative-spend tracker

A single spreadsheet (or a small dashboard) tracking: original sanction, all approved Type-A/B/C/D changes, cumulative spend, balance available. Updated monthly by the PMU. Visible to the FA, the indenting officer, the partner-vendor.

By month 18 of a 36-month contract, you can show on a single screen: 76% of budget consumed, 12 Type-A and 3 Type-B changes approved, on-track for completion within sanction.

Part 5 — Pre-vetted contract-amendment template

For the inevitable Type-C / Type-D change, the contract-amendment document is pre-templated and pre-vetted by the FA. When the change is needed, you fill the template, run it through the predefined approval ladder, and the amendment is signed in days — not the typical 6–12 weeks.

The legal anchors

• GFR Rule 142 — Variation in contract; thresholds and approvals
• GFR Rule 167 — Modifications to contracts
• Manual for Procurement of Consultancy 2021 §6 — Change management chapter
• CVC Circular on contract variations — vigilance perspective on supplementaries
• CAG audit framework — cost-overrun lens; the "10% rule" for triggering audit attention
• Your departmental DFPR — variation thresholds usually department-specific

Typical FA pushback patterns

• "What if the vendor refuses changes priced at our schedule?" — make the per-module schedule binding for 24 months in the contract
• "Where is the baseline if SOW is high-level?" — attach a detailed module/screen-level baseline annexure
• "Who maintains the cumulative tracker?" — assign to the PMU; sample template included in our pack
• "What about urgent changes that can't wait for committee?" — Type-A threshold should accommodate small urgent changes; document the urgency in the monthly report

What we hand you

• A change-control protocol document with the four-tier threshold matrix, customisable to your DFPR
• A baseline-scope template at module/screen/business-rule level, populated for your project
• A per-module pricing schedule binding for the contract life
• A cumulative-spend tracker (Excel or web-based) for the PMU
• A contract-amendment template pre-formatted for fast Type-C/D approval
• A second-round pushback pack for the four most common FA scope-creep challenges

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