How to Write a Surety Bond Clause for Government Tenders: GFR 2022 Compliance Guide
- Rajeev Chari
- Jul 1
- 12 min read
TL;DR
GFR Rules 170 and 171 require insurance surety bond acceptance: The February 2022 DoE amendment placed insurance surety bonds on equal legal footing with bank guarantees. A tender restricting security to bank guarantees only is now non-compliant.
Most tender documents have not caught up: The September 2024 DFS directive made acceptance mandatory for all central government departments, but Standard Bidding Documents in active circulation often predate this requirement entirely.
A compliant performance security clause needs ten specific components: Missing the IRDAI licensing requirement, non-revocability language, DLP-linked validity, or an extension mechanism creates grounds for rejection or enforcement failure.
Verification matters as much as drafting: A bond from an unlicensed insurer or one executed on incorrect stamp paper is unenforceable, regardless of what the tender clause says.
More than 120 government entities now accept insurance surety bonds. Approximately ₹60,000 crore has been issued to date, with NHAI alone crossing ₹10,000 crore, according to axiTrust's research on insurance surety bonds for MSMEs. The DFS directive of September 2024 instructed all central government departments to accept them as a matter of compliance, not discretion.
None of that has automatically updated a single tender document.
A contractor can hold a perfectly valid, IRDAI-licensed insurance surety bond and have it rejected at tender evaluation. Not because the bond is wrong, but because the Standard Bidding Document does not mention surety bonds at all, or mentions them without the language needed to accept and verify one.
The bottleneck is the clause, not the instrument. This guide covers what a compliant clause must say, why each component matters, how requirements differ across bond types, and what to check when a bond is submitted.
What GFR 2022 Actually Changed in Performance Security Clauses
The GFR 2022 amendment, issued as DoE Office Memorandum No. F.1/1/2022-PPD dated 02.02.2022, inserted "insurance surety bond from an insurer licensed by the Insurance Regulatory and Development Authority of India" into the list of acceptable instruments under both Rule 170 and Rule 171. The change applied immediately to all central government procuring authorities.
What the amendment did not do:
Rewrite the SBDs already in circulation
Issue updated format templates
Create an enforcement mechanism for departments that failed to update their documents
It changed the rule. It did not change the paperwork. That task falls to the procurement and contract management teams handling individual tenders.
A subsequent DoE OM No. F.1/2/2023-PPD dated 01.01.2024 clarified the performance security quantum for goods procurement, setting the range at 3 to 5% of contract value. The September 2024 DFS directive then converted a permissive rule into an operational mandate. A central government department that refuses a valid insurance surety bond submitted by a contractor is not exercising discretion. It is acting outside the directive.
Rule 170 vs Rule 171: Two Instruments, Two Clause Contexts
These two rules govern different instruments at different stages of a contract. Procurement officers need to distinguish them before drafting any clause.
Rule 170 (Bid Security) | Rule 171 (Performance Security) | |
Applicable stage | Tender submission to contract signing | Contract execution through DLP |
Quantum range | 2 to 3% of estimated contract value | 3 to 10% for works; 3 to 5% for goods |
Trigger events | Withdrawal, refusal to sign, failure to furnish performance security | Contractor default during execution or DLP |
Validity period | Tied to bid validity period | 60 days beyond DLP |
Clause complexity | Lower | Higher |
Most of this guide addresses Rule 171, because that is where drafting errors carry the greatest consequence.
Why Most Tender Documents Still Get This Wrong
Three failure modes account for most clause problems in circulation. Each one has a distinct consequence for the contractor and the procurer.
Failure Mode 1: Total omission
The performance security clause lists bank guarantee, fixed deposit receipt, and demand draft. Insurance surety bonds do not appear at all. A contractor who submits one has no textual basis to argue acceptance. The evaluation committee rejects it as non-compliant. The contractor must then arrange a bank guarantee at the worst possible moment, locking working capital just before mobilisation.
Failure Mode 2: Incomplete mention
The clause says "bank guarantee or insurance surety bond" and stops there. It does not specify:
That the issuing insurer must hold a valid IRDAI surety licence
That the bond must be non-revocable
Any validity standard tied to the Defect Liability Period
The evaluation committee receives a bond but has no checklist to verify it. With no stated standard, procurement officers default to what they know. They ask for a bank guarantee. The MSME either provides one or loses the tender.
Failure Mode 3: Internal contradiction
The performance security section of the SBD permits insurance surety bonds. The General Conditions of Contract elsewhere in the same tender document defines "performance security" only as "bank guarantee." This contradiction gives the evaluation committee grounds to reject a bond even when the SBD technically permits one. It is common in large infrastructure tenders where the SBD and GCC are updated by different teams working off different templates, with neither aware of the inconsistency.
If your organisation is updating tender documents to reflect GFR 2022 requirements, our consulting team can review your existing SBD language and identify gaps before they become rejection grounds. Talk to our team.
The Ten Components of a Compliant Performance Security Clause
A performance security clause that enables insurance surety bond acceptance and withstands evaluation scrutiny requires ten components. Each is covered below with the required language, the reason it matters, and the regulatory basis.
1. The Inclusion List: Naming Surety Bonds Correctly
What the clause must say:
"The Performance Security shall be furnished in any one of the following forms:
(a) Account Payee Demand Draft
(b) Fixed Deposit Receipt from a scheduled bank
(c) Bank Guarantee from a scheduled bank
(d) Insurance Surety Bond issued by an insurer duly licensed by the Insurance Regulatory and Development Authority of India (IRDAI) to underwrite surety insurance"
Why it matters:
The IRDAI licensing requirement is not optional phrasing. Approximately 10 of 30 general insurers currently hold surety underwriting authorisation, according to axiTrust’s research. A clause that says "insurance surety bond from an insurer" without naming IRDAI creates a gap the evaluation committee cannot close at the verification stage.
2. Penal Sum: Quantum and Base Value
What the clause must specify:
The quantum as a percentage of contract value
The base to which it applies: tendered value, final contract price, or value as varied under price escalation clauses
Why it matters:
For works contracts, the applicable range is 3 to 10% under GFR Rule 171. For goods procurement, the DoE OM of 01.01.2024 sets the range at 3 to 5%. Insurers issue bonds for a fixed penal sum. If the contract value increases through scope variation and the clause does not address this, the procurer is under-protected against the incremental exposure.
3. Validity Period: Covering the Defect Liability Period
What the clause must say:
"The bond shall remain valid and enforceable until 60 days after the satisfactory completion of all contractual obligations including the Defect Liability Period."
Why it matters:
A bond that expires before the Defect Liability Period ends leaves the procurer unprotected when construction or equipment defects are most likely to surface. The DLP reference must be consistent with the relevant clause in the GCC. If the GCC defines the DLP elsewhere, the performance security clause must cross-reference it rather than state a fixed calendar date that may later become inconsistent.
Regulatory basis: IRDAI (Surety Insurance Contracts) Guidelines, 2022, Section 4
4. Extension Mechanism: When the Contract Period Is Extended
What the clause must say:
"In the event of an extension of the contract period, the contractor shall, within [X] days of the extension order, furnish an extension of the bond or a fresh bond for the extended period. Failure to do so shall entitle the [procuring authority] to encash the existing bond."
Why it matters:
This is one of the most commonly omitted elements in current tender documents. Without an explicit extension clause:
The procurer has no contractual basis to demand bond renewal when a project overruns
There is no automatic trigger to encash if the contractor does not comply
Enforcement leverage disappears precisely when projects are under the most stress
5. Non-Revocability: The Language IRDAI Requires
What the clause must say:
"The bond shall be irrevocable and shall not be cancelled, varied, or revoked during its period of validity without the written consent of the [procuring authority]."
Why it matters:
Section 4 of the IRDAI (Surety Insurance Contracts) Guidelines, 2022 requires non-revocability as an essential feature of a valid surety bond. Including this language in the tender clause gives the procurer an explicit contractual basis to enforce non-revocability if the insurer or contractor disputes the bond’s terms.
6. Insurer Eligibility: The IRDAI Licence Requirement
What the clause must say:
"The issuing insurer must hold a valid licence from IRDAI to underwrite surety insurance as at the date of issuance and shall provide documentary evidence of such licence upon request."
Why it matters:
Insurer eligibility is a dynamic condition, not a permanent one. Two things make this clause element essential:
The "as at the date of issuance" language protects against later disputes about whether the insurer was authorised when the bond was issued
The documentary evidence provision gives the evaluation committee a concrete verification mechanism rather than relying on general knowledge of which insurers are licensed
7. Stamp Paper: The Compliance Requirement Nobody Mentions
What the clause must say:
"The bond shall be executed on non-judicial stamp paper of appropriate value as per the Stamp Act applicable in the state in which the contract is to be performed, or by way of e-stamp where permitted under applicable state law."
Why it matters:
An under-stamped bond is not legally enforceable. Procurement officers should verify the applicable rate under the relevant state Stamp Act before issuing the tender, as rates vary by state and change over time. The e-stamp provision matters because several states now permit electronic stamping, which simplifies compliance for both contractors and insurers. Without this clause, the evaluation committee has no stated standard to apply when verifying a submitted bond.
8. Invocation Mechanism: Where Most Clauses Break Down
What the clause must say:
"Upon written notice of default by the [procuring authority], the insurer shall pay the demanded amount within [15/30] days of receipt of such notice, without demur and without reference to the contractor, provided that such demand is received prior to the expiry of the bond."
Why it matters:
Insurance surety bonds under the IRDAI framework are typically conditional instruments. The insurer assesses the validity of a default claim before paying. This differs from a bank guarantee, where the bank pays on a compliant written demand.
SECI and NHAI tender formats address this by using language that creates a near-unconditional payment obligation within a defined notice window. This constrains the insurer’s investigation period rather than eliminating it. Procurement officers who want this level of enforcement certainty should replicate that language structure.
For a detailed explanation of conditional versus unconditional mechanics, see our guide on conditional versus unconditional surety bonds.
9. Governing Law and Jurisdiction
What the clause must say:
"This bond shall be governed by and construed in accordance with the laws of India, and disputes arising in connection with this bond shall be subject to the exclusive jurisdiction of courts at [location of procuring authority]."
Why it matters:
The Indian Contract Act, 1872 (Sections 126 to 147) provides the statutory framework for contracts of guarantee that the IRDAI Guidelines explicitly invoke. Specifying jurisdiction in the tender clause avoids ambiguity about venue in the event of a dispute, particularly for contracts executed across state lines.
10. Subrogation Acknowledgement
What the clause should say:
"The [procuring authority] acknowledges that upon payment under this bond, the insurer shall be subrogated to all rights of the [procuring authority] against the contractor to the extent of the payment made."
Why it matters:
Without this, the procurer risks being drawn into post-invocation disputes between the insurer and the defaulting contractor. Including it upfront clarifies the three-party relationship after payment and reduces the risk of the insurer disputing the scope of its recovery rights in a way that pulls the procurer back into proceedings.
How the Clause Changes for Each Bond Type
The ten components above apply to a standard performance security bond under GFR Rule 171. Each bond type has clause-level differences that affect what procurement officers need to draft. For a detailed explanation of how each bond type is structured, see our guide to the types of surety bonds.
Bid Bond (EMD Replacement under GFR Rule 170)
Key clause differences from a performance bond:
Quantum: typically 2 to 3% of the estimated contract value
Validity: tied to the bid validity period, with an automatic extension clause if bid validity is extended
Trigger language must specify exact encashment events: withdrawal of the bid after the submission deadline, refusal to sign the contract upon award, or failure to furnish performance security within the stipulated period
A vague default provision will not hold in enforcement. The specificity of the trigger language is what makes a bid bond clause enforceable.
Performance Bond (GFR Rule 171)
Key clause considerations:
Quantum: 3 to 10% for works contracts, 3 to 5% for goods procurement
Validity: 60 days beyond the Defect Liability Period
Partial completion: the clause should address what rights the procurer holds if the contractor completes a significant portion of the contract before defaulting
The partial completion question is not settled by GFR or IRDAI guidelines alone. It should be addressed as a specific drafting consideration with legal input rather than left to general contract default language.
Advance Payment and Mobilisation Advance Bond
Key clause considerations:
Quantum: equals the mobilisation advance amount
Validity: reduces pro-rata as the advance is recovered; the reduction mechanism must be specified explicitly
A fixed-sum bond for a mobilisation advance creates over-collateralisation as the advance is progressively recovered from running bills
NHAI Policy Circular No. 3.1.41/2025 governs this instrument for highway contracts and provides a reference format for the reducing clause. Procurement officers working on highway or road projects should align their clause language with that circular.
Retention Money Bond
Key clause considerations:
Quantum: equals the retention amount withheld under the contract
Validity: runs to the end of the Defect Liability Period
The clause must explicitly substitute the bond for cash withholding and specify what happens if defects are identified during the DLP and the contractor fails to rectify them
If the substitution language is absent, the contractor may have submitted a bond while the procurer has also withheld cash, creating unintended double-security that complicates both accounting and enforcement.
Seven Checks to Run When a Bond Is Submitted
When a contractor submits an insurance surety bond against a tender requirement, the evaluation committee needs a structured process to verify it. These seven checks cover the full compliance scope.
1. Verify the insurer’s IRDAI surety licence
Check the issuing insurer’s name against the IRDAI public register of surety-licensed insurers. Approximately 10 of 30 general insurers currently hold this authorisation. A bond from an unlicensed insurer is invalid regardless of its face value and must be rejected.
2. Verify bond language against the tender clause
Confirm all of the following:
Non-revocability is stated on the face of the bond
The penal sum matches the required quantum
The validity period is correct including the DLP extension
The invocation mechanism is consistent with what the tender clause specifies
3. Verify stamp paper compliance
Check the applicable state Stamp Act for the state in which the contract is to be performed. Confirm the bond is executed on correctly stamped paper or via e-stamp where that state permits it. An under-stamped bond is unenforceable regardless of its other terms.
4. Verify insurer signatory authority
The bond must be signed by an authorised official of the insurer holding power of attorney for surety issuance. Request the power of attorney document if it is not included with the submission. A bond signed without proper authorisation can be challenged by the insurer in an enforcement proceeding.
5. Verify through NeSL or the insurer’s e-verification portal
NeSL (National e-Governance Services Limited) provides digital authentication for surety bonds. Where available, use it. Digital verification reduces fraud risk and creates an auditable record that supports any future enforcement action.
6. Verify the bond contains no side conditions
Check that the bond does not include conditional language creating implicit payment prerequisites beyond what the tender clause specifies. Language such as "subject to the principal maintaining a valid insurance policy" is a red flag and grounds for rejection.
7. Verify the bond covers the correct contract
The bond must reference the correct tender number, contract description, and procuring authority. A bond issued for a different contract, or with an incorrect contract reference, does not provide valid security under the tender being evaluated.
We provide digital bond verification infrastructure that allows procuring authorities to confirm bond validity, insurer eligibility, and term compliance in a structured workflow. Visit our site - www.axitrust.com.
Where the Central Mandate Applies and Where It Does Not
This section matters because the mandate’s reach is frequently overstated:
Central government departments and CPSEs: Fully bound by GFR Rules 170 and 171 as amended and by the September 2024 DFS directive. There is no discretion to restrict acceptance to bank guarantees.
State government bodies and state PSUs: Operate under state-specific procurement rules. GFR does not automatically apply. Several states have not yet updated their financial rules to reflect surety bond equivalence. Procurement officers at the state level must verify the applicable state financial rules before updating tender clauses.
GeM: Surety bond acceptance is being operationalised across categories, but implementation is not uniform across all order types. Central GFR rules apply where GeM has updated its category formats. This should be confirmed category by category rather than assumed.
The Clause Is the Policy
The regulatory intent is clear. Adoption data confirms market momentum. The instruments are available from licensed insurers across the country.
What slows adoption at the transaction level is almost always the document: a tender clause last updated before GFR 2022 existed, or one that mentions surety bonds without the language required to accept, verify, or enforce them.
Updating the clause is not a complex exercise. It is ten specific components, each traceable to a regulatory source, each expressible in concrete language. The compliance question is whether the procurement team has the guidance to write them correctly.
axiTrust works with procuring authorities, PSUs, and contract management teams to support surety bond adoption operationally. This includes reviewing existing tender language against GFR and IRDAI requirements and providing digital bond verification infrastructure for evaluation committees. The consulting layer is built specifically for the gap between policy intent and document reality.
If your organisation is updating Standard Bidding Documents or building an acceptance framework for insurance surety bonds, talk to an axiTrust Consultant to review your existing clause language before your next tender goes out.
