Tracking Policy Warranty and Condition Compliance to Stop Claim Repudiation in India 2026

When a factory fire or a warehouse burglary claim is declined in India, the reason is rarely proven fraud. It is far more often a warranty or condition-precedent breach that the insured could have avoided with a logbook and a routine. A hot-work permit that was never issued, a hydrant pump that failed its weekly test three weeks before the loss, a night watchman who was withdrawn to cut costs. The peril was covered. The claim still failed, because the insured could not evidence that a warranted control was in place at the material time.

The conduct around these declines has tightened. The IRDAI (Protection of Policyholders' Interests) Regulations, 2024 require insurers to settle or communicate a decision on claims within defined timelines and to give reasons in writing, and they push surveyor appointment and claim decisions onto a clock. That regime does not stop a repudiation founded on a genuine warranty breach. It only removes the excuse of silence and delay. The insurer must state the ground, and if that ground is a breached warranty, the insured needs contemporaneous evidence to rebut it.

This post deliberately sits on the operations side of the problem. The wording question, how a clause is characterised as a warranty, a condition precedent or a bare condition, is covered in our companion piece on warranties and conditions precedent in policy wording. Here the concern is different: given the warranties already in your wording, how does a risk manager run the site so that compliance is continuous, dated and provable. The goal is a claims file that is built before the loss, not reconstructed after it, so that an insurer's first defence collapses on the paperwork you already hold.

Most operational warranties in Indian commercial policies are inherited from the erstwhile All India Fire Tariff and its standard warranty schedule, which insurers continue to attach even in the detariffed market. A risk manager should be able to list, for each policy, which of these are actually in force, because each converts a routine task into a condition of cover.

The recurring ones on a manufacturing or storage risk are predictable:

• The hot work permit warranty, requiring a written permit system for any welding, cutting or grinding, including contractor work.
• The hydrant and fire-extinguishing appliances warranty, requiring hydrants, pumps and portable appliances to be maintained in efficient working order and tested.
• The watch and ward warranty, requiring a stated number of security personnel on the premises, often around the clock.
• The housekeeping and storage warranties, covering removal of oily waste, height and spacing of stored goods, and clear gangways.
• Electrical, smoking-prohibition and no-storage-of-hazardous-goods warranties specific to the occupancy.

The distinction that trips up insureds is timing. Some warranties are tested only at inception, but the operational ones above are almost always continuing warranties, requiring compliance throughout the policy period. Under warranty law derived from the Marine Insurance Act, 1963 and applied by analogy to non-marine covers, strict and literal compliance is required, and a breach can discharge the insurer from liability from the date of breach, whether or not the breach caused the loss.

That is why a warranty on the floor is more dangerous than an exclusion in the wording. An exclusion only bites on the specific uninsured cause. A breached continuing warranty can defeat an entirely unrelated claim. A watch-and-ward lapse can be argued against a fire loss, not merely a burglary. The register that follows exists to close exactly this gap.

A condition precedent compliance register is a single controlled document, or a module in your risk management system, that turns every warranty and condition precedent in your policy schedule into a tracked, evidenced obligation. It is the operational spine of this whole discipline.

Structure it so that each row is one warranty and the columns force accountability:

1. The exact warranty or condition wording and the policy and endorsement number it sits in.
2. Whether it is tested at inception only or is a continuing obligation, and its required frequency (daily, weekly, monthly).
3. The named owner, by role, responsible for compliance, and the deputy.
4. The evidence artefact that proves compliance, for example the permit book, pump test log, security muster or AMC certificate.
5. The last completed date, the next due date and an exception field for any lapse and its remediation.

The register does three things a memo cannot. It makes latent warranties visible, so that a clause buried in an endorsement is not discovered for the first time by a surveyor after a loss. It fixes ownership, so a control is not quietly dropped when a plant head changes or a cost review cuts headcount. And it produces a dated audit trail, which is the single most persuasive rebuttal to a repudiation.

Review cadence matters as much as the register itself. Reconcile it monthly against actual logs, and at every renewal re-map it to the new schedule, because insurers routinely add, delete or reword warranties year on year. A register that tracks last year's wording is a false comfort.

If one warranty deserves a dedicated workflow, it is hot work. Welding, gas cutting, grinding and open-flame work are a leading proximate cause of Indian industrial fires, and the hot work permit warranty is correspondingly the most frequently invoked in fire repudiations. The failure is almost never the absence of a permit form. It is that the permit was not raised, not signed, or not extended to a contractor who lit the spark.

A defensible hot work permit system has a fixed shape. A written permit is raised before any hot work begins, valid for a stated shift or task and not open-ended. It names the location, the person doing the work, the authorising officer and a fire watch. It records the pre-work checks: combustibles removed or covered within the prescribed radius, a charged extinguisher and, where required, a running hose at hand. The fire watch continues for a defined period after work stops, commonly 30 to 60 minutes, because smouldering ignition is delayed. The permit is closed and retained.

In the register, hot work should not be a single monthly tick. It should reference the permit book itself, so that the number of permits raised can be reconciled against known maintenance and project activity. A month of heavy fabrication with two permits on file is a red flag a surveyor will find, and it is far better found by your own audit. Retain closed permits for the full policy period plus the limitation window, since a hot work loss can surface as a claim long after the shift ended.

Fire protection warranties fail on evidence more than on hardware. Most insured premises have a hydrant ring, a fire pump and often a sprinkler system. The hydrant testing warranty and the maintenance-of-appliances warranty do not merely require these to exist. They require them to be maintained in efficient working order, and that is proven by a dated testing record, not by the equipment standing in place.

Build the evidence around the tests a surveyor will ask for:

• Weekly running of the main and jockey fire pumps, with churn or flow readings and the duration logged and signed.
• Periodic hydrant flow and pressure checks across the ring, not only at the pump house.
• Sprinkler system checks aligned to the standard the discount was granted on, with the annual maintenance contract certificate on file. Our note on the fire sprinkler discount explains how a lapsed test can unwind both the premium credit and the claim.
• Portable extinguisher refill and pressure-test dates, tracked against expiry.

Two failure modes recur. The first is the gap. A pump log that runs weekly for ten months then stops six weeks before the loss invites the insurer to argue the appliance was not being maintained at the material time. The second is the impaired system that no one flagged. If a pump is down for repair or a sprinkler valve is shut for modification, that is an impairment, and many wordings require the insurer to be notified. A silent impairment converts a routine repair into a warranty breach.

The register should carry the next-due date for each test and an impairment field that is populated the moment a system is taken offline. Pair it with a standing instruction that any impairment beyond a short window triggers written notice to the insurer through the broker. That single habit defeats a large share of fire-protection repudiations.

The quietest breaches come from warranties that require a state of affairs to persist unbroken. These are where cost pressure and staff turnover do their damage, because nothing visibly breaks on the day the warranty lapses.

The watch-and-ward warranty is the classic example. A policy may warrant a specified number of security guards on the premises at all times, or around the clock. When a plant reduces night shifts or a security contract is renegotiated to fewer heads, the warranty is breached silently, and it stays breached until a loss exposes it. Because it is a continuing warranty, an insurer can raise it against a fire as readily as a burglary, arguing the insured was in breach at the moment of loss. The defence is the daily security muster, retained, showing the warranted strength was actually deployed each shift.

Housekeeping and storage warranties are similar. Warranties on removal of oily waste and cotton waste, on stacking height and spacing, and on keeping gangways clear, all require a persistent condition that a busy operation erodes over weeks. The evidence is the housekeeping inspection round, logged with date and observations, and dated photographs where practical.

The reason these unglamorous warranties deserve the same rigour as fire protection is doctrinal. Continuing warranties do not require the insurer to prove the breach caused the loss. Under strict warranty doctrine the breach alone can discharge liability, which is why immaterial-looking lapses, a withdrawn guard or an uncleared waste bin, are worth tracking as carefully as a pump test.

For these warranties the register earns its keep through cadence rather than complexity. A short, dated daily or weekly log against each continuing warranty, owned by a named person and spot-audited by the risk manager, is what stands between a paid claim and a repudiation argued on a condition the insured forgot was even in the policy.

A compliance register only defeats a repudiation if it is joined up with the broker and the wording. The risk manager owns the site evidence, but the broker owns the interface with the insurer, and the two have to be aligned before any loss.

The broker's contribution is threefold. At placement and renewal, extract every warranty and condition precedent from the schedule and endorsements and hand the risk manager a plain-language list to load into the register, so no clause is latent. During the year, route every impairment notice and material change to the insurer promptly and in writing, since a warranted control taken offline without notice is a breach waiting to be pleaded. And where a warranty is impractical for the operation, negotiate it before binding, seeking a causal-connection qualifier or a held-covered provision rather than accepting a strict continuing warranty the insured cannot realistically keep.

When a claim does arrive, the register becomes the first exhibit. Under the IRDAI (Protection of Policyholders' Interests) Regulations, 2024, the insurer must state its ground for repudiation in writing. If that ground is a warranty breach, dated permits, pump logs and security musters produced on day one frequently close the argument before it reaches the surveyor's report or the Ombudsman.

Doing this well depends on knowing exactly how each insurer drafts and attaches its warranties, because the same control can be a strict continuing warranty in one wording and a qualified condition in another. Sarvada gives commercial insurance brokers structured, searchable access to insurer policy wordings and the intelligence around them, so you can identify every warranty and condition precedent across a client's programme and map it into a compliance register with confidence. Request Access to make warranty tracking a standing part of how you place and service commercial risk.