Exit terms — the 14-clause annexure that survives any vendor scenario

What the FA is actually asking

The literal question: "What are the exit terms?" The FA's real concern is succession risk. The vendor relationship will end someday — termination, expiry, acquisition, bankruptcy. On that day, can the department:

• Get its data out cleanly?
• Run the system without vendor cooperation?
• Onboard a successor without a year-long transition?
• Avoid the pattern of a 6-month "limbo" where citizens / employees suffer?

Why thin responses fail

The standard failure: a 30-day notice clause and a sentence saying "all data belongs to purchaser". Both are technically correct and operationally meaningless. On termination day:

• The "data" is in a proprietary format only the vendor's tools can read
• The infrastructure is in the vendor's cloud account
• The credentials are in the vendor's password manager
• The original engineers are not contractually obligated to support transition
• The vendor has financial-distress incentives to delay

The shape of a holding response — 14 clauses

The annexure structure

1. Defined exit-management plan attached to the contract from day 1
2. Data export formats — open standards, machine-readable, full-fidelity, with sample exports tested at acceptance
3. Source code & documentation handover protocol — quarterly during contract, full at exit
4. Infrastructure credentials transfer — process documented, tested annually
5. Knowledge transfer to successor vendor — costed weeks of overlap, billed at agreed rates
6. Running-system handover — successor takes over a working system, not a frozen snapshot
7. Exit-cooperation obligation — survives termination; binding for 6 months post-exit at agreed rates
8. Service continuity — vendor must maintain SLA through the transition period
9. Service-continuity bond — sized to project value, released after successful exit
10. Vendor financial-health monitoring — quarterly attestation; trigger conditions for early intervention
11. Acquisition-scenario clause — if vendor is acquired, contract assignability and successor obligations
12. Bankruptcy-scenario clause — escrow trigger, immediate code release, succession framework
13. Reference rights — vendor can publicly reference work post-public-launch
14. Survival-of-clauses schedule — which clauses outlive contract termination (IPR, escrow, exit cooperation)

The legal anchors

• Indian Contract Act 1872 — termination, performance, frustration, novation
• Insolvency and Bankruptcy Code 2016 — scenarios when vendor enters CIRP
• Companies Act 2013 — assignability on acquisition
• GFR Rule 167 — modifications and termination of contracts
• NeGD model exit-clause provisions
• CAG audit framework — succession-risk lens; flagging contracts without exit annexures

Typical FA pushback patterns

• "What is the cost of the exit-cooperation period?" — pre-negotiate rates and include in the contract
• "What if the vendor refuses to cooperate at exit?" — answer: service-continuity bond is forfeited; escrow code releases; legal recourse documented
• "Who pays for successor onboarding?" — typically successor's contract; the exiting vendor cooperates without additional fee for the agreed weeks
• "Has this been tested?" — annual DR drill should include a partial vendor-exit simulation
• "What about post-exit IP usage by vendor?" — clarify in IPR clause; vendor retains pattern, not product

What we hand you

• The 14-clause exit-management annexure as a Word document, customised for your contract
• A data-export specification with sample formats and acceptance test
• A source-escrow agreement template (cross-link with IPR pack)
• A knowledge-transfer plan with successor-onboarding schedule
• A service-continuity bond clause sized to your project
• A vendor financial-health monitoring framework with quarterly reporting template

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