Real-Time Claims Tracking Dashboards for Corporate Risk Managers India

For most Indian corporates, the standard rhythm of claims information is a quarterly loss run from the broker and an annual claims experience statement from the insurer at renewal time. This cadence made sense when a company might file three or four claims in a year and when each claim was managed by a single policy. It does not work for a mid-market manufacturer running 12 active policies across fire, marine, machinery breakdown, employer liability, product liability, and group health, with 20 to 40 claims open at any given moment across locations in four states.

The cost of lag becomes concrete when an open reserve inflates next year's premium. Under IRDAI's experience rating framework, a company's claims history over the preceding three policy years directly influences the renewal rate on fire, engineering, and marine lines. A claim that was intimated in November but not yet surveyed by March, simply because no one was tracking the surveyor's engagement status, may not be adequately reserved in time for the insurer to close it before the reference date used for renewal pricing. The resulting inflated open reserve becomes part of the experience rating calculation, driving up the renewal premium even though the actual loss may ultimately be settled at a fraction of the reserve.

Beyond pricing, live visibility matters for cash flow management. Indian companies typically carry deductibles ranging from INR 5 lakh for SME policies to INR 2-5 crore for large industrial programmes. Understanding when a settlement cheque is expected, versus when the surveyor has only submitted a preliminary report, affects treasury planning. A plant that has suffered a INR 15 crore machinery breakdown loss cannot wait for a quarterly report to learn whether the insurer has approved interim relief under the advance payment provision available to policyholders under IRDAI's Guidelines on Claims Management.

The shift to real-time tracking is not a technology project alone. It requires a deliberate decision about which data flows the risk management function will own, which will be sourced from the broker's portal, and which must be negotiated directly with each insurer.

A well-constructed claims dashboard for an Indian corporate risk manager organises data across five analytical layers: portfolio status, aging and velocity, financial adequacy, counterparty performance, and reinsurance recovery.

Portfolio Status is the baseline view. It shows every open claim across all lines of business, indexed by policy, claim reference number, date of loss, date of intimation, peril, location, and current status. Status categories should map to IRDAI's defined stages: intimated, survey assigned, survey completed, assessment pending, offer made, accepted, and closed. The count of claims in each stage, broken down by line of business, tells the risk manager where bottlenecks are accumulating. A dashboard showing 14 claims in 'survey completed, assessment pending' for more than 45 days is a signal that the insurer's internal processing is the constraint, which is actionable information for broker escalation.

Aging Analysis applies a time-based lens. IRDAI's Guidelines on Claims Management (2023 revision) specify that insurers must settle admitted claims within 30 days of receiving all necessary documents. For claims requiring investigation, the insurer must communicate the decision within 45 days. Surveyor appointment must occur within 72 hours of intimation for large commercial losses. The dashboard should flag every claim that has breached these regulatory timelines with a red indicator and display the exact number of calendar days elapsed. This aging view is the risk manager's primary tool for prioritising broker escalations.

Reserve vs. Incurred Analysis tracks the financial adequacy of what the insurer has reserved against each claim. The reserve is the insurer's estimate of ultimate payout; the incurred is the amount already paid plus the current reserve. For a risk manager, the gap between the reserve and the actual repair or replacement cost estimate from the company's own engineers is a critical watch item. Where the company's internal estimate of loss is materially higher than the insurer's reserve, there is an early warning of a potential settlement dispute that should be flagged before the surveyor's final report is submitted.

Days to Settlement is the velocity metric. It measures the average number of calendar days from date of loss to final settlement, broken down by line of business and by insurer. Tracking this metric over 12 to 24 months allows the risk manager to trend-spot: if average days to settlement on fire claims has moved from 62 days to 94 days over two years, it signals a structural change in how that insurer is processing claims, which is directly relevant at renewal time when the risk manager is deciding whether to maintain or switch that insurer.

Surveyor Status is an underappreciated dashboard element. The Insurance Surveyors and Loss Assessors (Licensing and Operations) Regulations, 2015 require licensed surveyors to submit their reports within 30 days of appointment, extendable to 90 days with justification. Knowing which claims are awaiting surveyor reports and how long those surveys have been in progress allows the risk manager and broker to apply pressure at the right point. In large industrial claims, the surveyor is frequently the rate-limiting step between loss occurrence and settlement offer.

Reinsurance Recovery Status is the dashboard layer that most Indian corporate risk managers currently lack. Where the claim exceeds the primary insurer's retention and triggers reinsurance recovery, the risk manager needs visibility into whether the lead insurer has placed the reinsurers on notice, whether the facultative reinsurer has acknowledged liability, and what the expected recovery timeline is. Delays in reinsurance recovery are a common cause of settlement delay on large Indian industrial losses, and the policyholder's broker should be tracking this on behalf of the client.

Assembling a real-time claims dashboard for an Indian corporate typically requires pulling data from three to five separate sources, none of which were designed to talk to each other.

The first source is the insurer's own claims portal. Most Indian public sector insurers (New India Assurance, United India, Oriental) have web portals where policyholders can view claim status. The data available on these portals is often limited to claim number, current status flag, and surveyor name. Reserve amounts and internal assessment notes are rarely visible to the policyholder. Private insurers such as ICICI Lombard, HDFC ERGO, and Bajaj Allianz have invested more in portal functionality, with some offering reserve visibility and document upload capabilities, but data standardisation across insurers is absent. A company with six insurers has six separate logins, six different data formats, and no consolidated view.

The second source is the broker's claims management system. IRDAI-registered direct brokers and composite brokers are required to maintain claims registers for their clients. Larger Indian broking houses such as Aon, Marsh, Willis Towers Watson, Prudent Insurance Brokers, and Howden have proprietary client portal systems that consolidate claims data across all insurers for a given client. The quality of these systems varies materially. Some provide near-real-time updates; others are updated monthly from insurer feeds. The risk manager should explicitly negotiate access rights and update frequency as part of the broker appointment terms.

The third source is the company's own loss register. Internal data captured by the plant safety team, production team, or finance department at the time of an incident is often richer in operational detail than what appears in the insurer's system. The company's internal cost estimate, the business interruption revenue loss calculation, and the reinstatement timeline are all data points that the risk manager's team captures and which must feed into the dashboard for the reserve-versus-incurred comparison to be meaningful.

The fourth source, relevant for group health and personal accident claims, is the TPA (Third Party Administrator) system. Indian group health policies are predominantly administered by TPAs approved by IRDAI. TPA portals provide claim-level data including diagnosis, treatment cost, and settlement status. For a risk manager managing a group health programme for 3,000 to 10,000 employees, the TPA data is the primary source for health claims analytics including hospitalisation frequency, average claim size, disease pattern, and network hospital utilisation.

The Insurance Information Bureau of India (IIB) publishes industry-level claims benchmarking data by line of business. While this data has a publication lag of 6 to 12 months, it is the most reliable source of peer comparison for settlement timelines and claims frequency rates. A risk manager whose fire claims are settling in 110 days against an industry median of 70 days has objective data to put in front of the insurer at the next service review meeting.

For corporates willing to invest in a purpose-built solution, API-based integration with insurer portals is possible but requires negotiation with each insurer individually. IRDAI's Bima Sugam digital platform, which began operational rollout in 2025-26, is expected to standardise policy and claims data exchange between insurers, brokers, and policyholders over time, though the commercial lines integration timeline remains the least certain aspect of the rollout.

Indian corporate policyholders have a clearer set of regulatory rights around claims timelines than many risk managers realise. Understanding these rights transforms the claims dashboard from a passive monitoring tool into an active enforcement mechanism.

The IRDAI (Protection of Policyholders' Interests) Regulations, 2017 and the subsequent Claims Management Guidelines establish the following binding timelines for insurers. Acknowledgement of a claim intimation must occur within 24 hours of receipt. Appointment of a surveyor or investigator for commercial losses must occur within 48 to 72 hours. Surveyor reports must be submitted within 30 days of appointment (extendable to 90 days with documented justification, with the insurer required to inform the policyholder of the reason for extension). Final claim decision (settlement or repudiation) must be communicated within 30 days of receipt of the surveyor's report and all supporting documents. Payment of settled claims must occur within 7 days of settlement agreement. Repudiation letters must state the specific grounds for denial and the policyholder's right to appeal.

Breach of these timelines by the insurer entitles the policyholder to interest on the delayed payment at 2 percentage points above the bank rate published by RBI. For a INR 10 crore claim delayed by 60 days beyond the regulatory deadline, the interest entitlement is approximately INR 13-15 lakh at current bank rates. Most Indian corporates do not claim this interest because they are unaware of the entitlement or are reluctant to antagonise the insurer. A claims dashboard that flags timeline breaches with the interest accrual amount makes this entitlement visible and actionable.

The IRDAI Grievance Redressal Regulations, 2023 require insurers to resolve complaints within 14 days of receipt. If the insurer fails to resolve within this period, the policyholder can escalate to the Insurance Ombudsman under the Insurance Ombudsman (Amendment) Scheme, 2021, which covers commercial disputes up to INR 50 lakh. For claims above this threshold, IRDAI's Integrated Grievance Management System (IGMS) and, ultimately, civil court or arbitration remain the recourse. The dashboard should include a column flagging the appropriate escalation path for each claim based on its current status and age.

For multi-location programmes under a single fire or engineering policy, the risk manager should also track whether each claim has been intimated under the correct policy section and whether the deductible allocation between locations is consistent with the policy terms. Errors in claim intimation routing, such as intimating a loss under a machinery breakdown section when the loss is covered under a fire section, can delay the surveyor assignment and create avoidable disputes.

Indian risk managers face a build-vs-buy decision when setting up a claims dashboard. The two main paths are using the broker's proprietary client portal and building an internal management information system (MIS) using Excel, Power BI, or a dedicated risk management information system (RMIS).

Broker portals offer the fastest time-to-value. A corporate insured with a single broker for the majority of its programme can typically get access to a consolidated claims view within a few weeks of requesting it. The leading Indian broking firms and multinationals operating in India have invested significantly in portal capability. These portals typically include claim status tracking, document storage, surveyor contact details, and, for some brokers, benchmarking data from their broader client portfolio. The limitation is dependence on the broker's data feeds from each insurer, which are only as current as the insurer's own system allows. For clients with multiple brokers, no single broker portal provides the consolidated view.

DIY dashboards built on Power BI or Tableau, fed by manual data entry or periodic exports from insurer and TPA portals, are the most common approach for mid-market Indian corporates with insurance programmes between INR 2 crore and INR 15 crore in annual premium. The risk manager or the finance team maintains a master claims register in a shared spreadsheet or a simple database, updated weekly from each insurer's portal. This approach is labour-intensive but gives the risk manager full control over data fields, dashboard design, and metric definitions. The key discipline required is consistency of data entry, particularly for reserve amounts and expected settlement dates, which must be explicitly obtained from the broker or insurer rather than estimated.

Dedicated RMIS platforms such as Origami Risk, Ventiv, or locally-developed alternatives are used by large Indian corporates with insurance spend above INR 20 crore annually, conglomerates with 10 or more subsidiaries, and listed companies with formal risk committee reporting requirements under SEBI LODR Regulations, 2015. These platforms integrate with insurer APIs where available, provide structured claims workflows, and generate risk committee reports automatically. Implementation costs for a mid-tier RMIS in India range from INR 40 lakh to INR 2 crore depending on scope, making them economically viable only at larger programme sizes.

Regardless of the platform chosen, the risk manager should establish a claims data governance protocol: who updates the register, at what frequency, what sources are authoritative for reserve figures (insurer's stated reserve vs. broker's estimate vs. company's own calculation), and who reviews the dashboard before each risk committee meeting. Without this governance, even a sophisticated platform produces unreliable output.

The Insurance Information Bureau of India (IIB), established under IRDAI, collects and publishes claims data across all non-life insurers in India. Its Annual Report and industry statistics provide claim frequency rates, average claim sizes, and claim settlement ratios broken down by insurer and by line of business. While these datasets are public, few Indian corporate risk managers actively use them for insurer performance benchmarking.

The primary utility of IIB data for a risk manager's claims dashboard is as a baseline for days-to-settlement comparison. IIB data shows, at the industry level, what the median settlement duration is for fire claims, marine cargo claims, and engineering claims in India. If the risk manager's own data shows that claims against Insurer A are settling in an average of 85 days while the IIB industry median for fire claims is 65 days, the 20-day lag is measurable and presentable at a service review meeting without relying on subjective qualitative comparisons.

IIB also publishes Claims Settlement Ratio (CSR) data for each insurer, defined as the number of claims settled in a year divided by the number of claims registered. A CSR below 90% for a commercial insurer is a flag; it suggests a meaningful proportion of registered claims are not being resolved within the year, which may indicate disputes, investigation delays, or capacity constraints in the claims function. Monitoring this ratio for the risk manager's own insurer portfolio, updated annually when IIB data is published, provides an early warning if an insurer's operational quality is deteriorating.

For reinsurance recovery timelines, IIB does not publish granular data. The risk manager must rely on the broker's market intelligence and, for Lloyd's-backed risks, the Lloyd's Market Association's published performance data for treaty and facultative settlement timelines in India.

One limitation of IIB data is the publication lag: the most recent detailed breakdown typically covers the fiscal year ending two years prior to publication. This means IIB data is most useful as a structural benchmark rather than as a real-time comparator. For real-time insurer comparison, the risk manager's best source remains their own historical claims register and the broker's portfolio-level benchmarks from comparable clients.

A claims dashboard is only as useful as the performance targets it measures against. Indian risk managers should negotiate explicit claims service KPIs with their insurer and broker at inception or renewal, documented in the policy schedule or in a service level agreement with the broker.

The following KPI set is appropriate for a mid-to-large Indian corporate programme. Survey appointment SLA: surveyor assigned within 48 hours of claim intimation for losses above the agreed threshold (typically INR 25 lakh for property claims). Surveyor report SLA: preliminary report within 15 days, final report within 30 days of appointment, with written notification required for any extension beyond 30 days. Settlement offer SLA: formal settlement offer within 21 days of receipt of final surveyor report and all supporting documents. Payment SLA: cheque or NEFT transfer within 7 days of settlement acceptance, consistent with IRDAI's regulatory requirement. Rejection SLA: if the insurer declines to admit the claim, written repudiation with detailed grounds within 30 days of receiving all documents.

For business interruption and consequential loss claims, which are inherently more complex, adjusted KPIs apply. The risk manager should negotiate a phased settlement approach: an interim advance payment of 50 to 70% of agreed BI loss within 60 days of loss occurrence, with final settlement within 90 days of the business resuming normal operations and providing the final accountant's certificate.

For group health claims managed through a TPA, standard KPIs include: cashless authorisation within 30 minutes for planned hospitalisation and within 1 hour for emergency admission; reimbursement claim settlement within 14 days of submission of complete documents; and TPA query response (when additional documents are requested) within 72 hours.

These KPIs should be reported on the claims dashboard with a RAG (red, amber, green) status indicator for each open claim and for aggregate performance by insurer over the trailing 12 months. The aggregate view feeds the broker performance scorecard and the renewal insurer selection process. An insurer whose aggregate KPI compliance rate falls below 80% across material claims is a renewal conversation about either service improvement commitments or market change.

Finally, the risk manager should track recovery rate, defined as amounts actually recovered from insurers divided by amounts claimed. A recovery rate below 85% on non-disputed claims suggests either systematic under-reservation by the insurer, deductible miscalculations, or documentation deficiencies in the company's own claim submissions. Each of these failure modes is correctable once identified, and the claims dashboard is the tool that makes them visible.