Grievance Redressal as a Regulatory Obligation, Not a Courtesy
Many brokers still treat complaints as a relationship matter, handled informally by the producer who manages the account, resolved by a phone call, and never recorded in any system. That treatment is no longer adequate. Grievance redressal is a defined regulatory obligation for insurance intermediaries, with prescribed processes, turnaround norms, integration with the regulator's grievance platform, and an external escalation pathway to the Insurance Ombudsman. A broker without a structured grievance-redressal workflow is non-compliant, exposed at inspection, and blind to the patterns its complaints reveal.
The obligation flows from the IRDAI's grievance-redressal framework for the insurance sector, which applies to insurers and to intermediaries including brokers. The framework requires regulated entities to have a board-approved grievance-redressal policy, a defined grievance-redressal procedure with turnaround norms, a designated grievance redressal officer, integration with the IRDAI's central grievance-management system, and disclosure to policyholders of how to complain and how to escalate. For brokers, the IRDAI (Insurance Brokers) Regulations, 2018 reinforce this through the obligation to serve the client's interest and to maintain proper records, which a grievance process operationalises. The framework is not optional guidance; it is the standard against which an inspection assesses the broker.
The central platform has been rebranded. The IRDAI's grievance-management system, long known as the Integrated Grievance Management System (IGMS), now operates under the name Bima Bharosa. It is the regulator's portal through which policyholders can lodge complaints, through which complaints are routed to the relevant insurer or intermediary, and through which the regulator monitors grievance volumes, turnaround and resolution across the industry. A broker in scope must integrate with Bima Bharosa so that complaints routed to it are received, actioned within the norms, and updated on the platform, and so that the regulator's visibility into the broker's grievance handling is accurate.
The stakes go beyond compliance. Grievance data is one of the clearest signals the regulator and the market have about how an intermediary actually treats its clients. High complaint volumes, slow turnaround, and frequent escalations to the Ombudsman mark a broker out adversely; clean, fast, well-resolved grievance handling marks it out favourably. For the broker itself, the grievance log is a feedback mechanism: the complaints reveal where the broker's service, advice or operations are failing, and a broker that does root-cause analysis on its grievances can fix the underlying problems rather than re-handling the same complaint type repeatedly.
There is also a service-and-retention dimension. A complaint handled well, promptly, fairly, with the client kept informed, often strengthens the relationship; the same complaint handled badly, ignored, delayed, or resolved without explanation, loses the client and may escalate to the Ombudsman or to the regulator. Grievance redressal done to standard is simultaneously a compliance control, a quality-improvement engine, and a retention tool. This post sets out the workflow: the Bima Bharosa integration, the turnaround norms, the escalation matrix, the Ombudsman pathway, the root-cause logging, and the audit trail an inspector will sample and verify.
The Board-Approved Policy and the System That Operates It
A grievance-redressal workflow rests on two foundations the broker must put in place before any individual complaint is handled: a board-approved grievance-redressal policy that defines the obligations and the process, and a system that operates the policy reliably rather than depending on individual diligence. An inspection tests both the policy and whether the firm actually runs it.
The board-approved policy
The framework expects a grievance-redressal policy approved at board level, not a procedure invented in operations. The policy should define what constitutes a grievance, the channels through which grievances are received, the turnaround norms the broker commits to, the escalation matrix, the role and authority of the grievance redressal officer, the Bima Bharosa interface, the Ombudsman escalation pathway disclosed to policyholders, the record-retention and audit-trail requirements, and the reporting of grievance metrics to management and the board. Board approval matters because it places accountability for fair client treatment at the top of the firm and because an inspection treats the absence of a board-approved policy as a structural failing regardless of how complaints are handled in practice. The policy should be reviewed periodically and updated when the framework changes, for example when the IRDAI rebranded IGMS as Bima Bharosa.
Why a system, not a spreadsheet
The policy is only as good as the system that runs it. A grievance process operated through email and a spreadsheet depends on individuals remembering to log complaints, watch the clock, escalate and update the portal, and it fails predictably under load: a complaint sits unlogged, a deadline is discovered missed, a Bima Bharosa item is forgotten. A structured grievance-management system registers every complaint with a unique reference, starts and tracks the turnaround clock automatically, enforces acknowledgement, routes and escalates through the matrix on time and severity, interfaces with Bima Bharosa, and captures the audit trail without relying on the handler to remember to record it. The system is what converts the policy from a document into an operating control.
What the system must enforce
The system should enforce the elements that an inattentive handler would otherwise miss. It should prevent a grievance from being recorded as resolved without a resolution and a communication to the complainant. It should flag grievances approaching their turnaround deadline and surface breaches immediately. It should require classification at intake so the log is analysable. It should reconcile the internal register against the Bima Bharosa status so the two cannot drift apart. And it should produce the management and board reporting from the captured data rather than requiring a manual compilation that lags and errs. System enforcement is the mechanism that makes the turnaround norm reliably met rather than occasionally breached.
Disclosure to policyholders
The policy must translate into clear disclosure to policyholders of how to complain and how to escalate. The broker should publish, on its website and in its client communications, the grievance-redressal contact, the grievance redressal officer as the internal escalation point, the expected turnaround, and the Insurance Ombudsman as the external escalation. Clear disclosure is both a framework expectation and a quality signal; a broker that makes its complaint and escalation routes easy to find demonstrates a fair process, while one that buries or omits them invites the inference that complaints are unwelcome. The disclosure should be kept current with the actual contacts and the correct external escalation references.
What Counts as a Grievance and How It Reaches the Broker
Before designing the workflow, the broker must be clear about what a grievance is, what it is not, and the several channels through which one can arrive, because a complaint missed at intake is a complaint that breaches the turnaround norm before the clock is even noticed.
Defining a grievance
A grievance, in the IRDAI framework, is an expression of dissatisfaction by a policyholder or prospect about the action or inaction, or the standard of service, of an insurer or intermediary, where the complainant expects redressal. The framework distinguishes a grievance from a mere inquiry or a request for information, which are not grievances, and from a commercial dispute that belongs in another forum. For a broker the typical grievances concern the advice given, the placement made, delays in issuance or endorsement, premium and refund handling, claims support and advocacy, and conduct of the broker's staff. The broker should define grievance clearly in its policy so that intake staff can distinguish a grievance (which enters the workflow and the turnaround clock) from an inquiry (which is handled but not as a grievance), without either over-classifying every query as a grievance or, worse, under-classifying genuine complaints to keep the numbers down.
The intake channels
Grievances reach the broker through several channels and the workflow must capture all of them. Direct channels include the broker's own complaint email or address, its website or portal complaint facility, its call centre or relationship managers, and walk-in or written complaints. The indirect and most regulated channel is Bima Bharosa: a policyholder can lodge a complaint on the IRDAI portal, which routes it to the relevant entity, and a broker in scope receives complaints routed to it there. Complaints can also arrive via the insurer (where the policyholder complained to the insurer about a matter involving the broker) and, at the escalation stage, via the Insurance Ombudsman. Each channel must feed into a single grievance register, because a complaint received on Bima Bharosa and the same complaint received by email must not be handled as two unrelated items, and a complaint received on any channel must start the turnaround clock.
Single intake and acknowledgement
The workflow should funnel all channels into one intake point that registers the grievance with a unique reference, records the complainant, the policy, the nature of the complaint, the channel and the date and time of receipt, and issues an acknowledgement to the complainant. The acknowledgement is itself a framework expectation, the complainant should be told their complaint is received, given a reference, and told the expected resolution timeline and how to escalate. Acknowledgement is not resolution, but a missing acknowledgement is an early and visible process failure that a reviewer will flag. The single intake point also ensures the turnaround clock starts at first receipt on any channel, which is the date the norms run from.
Classifying for routing and analysis
At intake the grievance should be classified by type (advice, placement, issuance, endorsement, premium, claims, conduct) and by severity, because the classification drives both the routing (who handles it) and the later root-cause analysis (what categories of complaint recur). Good classification at intake is what makes the grievance log analysable later; a register of unclassified free-text complaints tells the broker little about where its problems lie. The classification scheme should be defined in the policy and applied consistently, with the grievance redressal officer reviewing classification to keep it honest.
Turnaround Norms and the Escalation Matrix
The heart of the regulatory framework is the turnaround norm: the time within which a grievance must be acknowledged, resolved and closed. The broker's workflow must track every grievance against these norms and escalate before they are breached, because turnaround performance is exactly what Bima Bharosa exposes to the regulator.
The turnaround expectations
The IRDAI grievance framework sets specific turnaround expectations for acknowledgement and resolution. Under the regulator's policyholder-protection norms, an entity must acknowledge a grievance within 3 working days of receipt; where it can resolve the grievance within those 3 days, it may communicate the resolution together with the acknowledgement. Where the grievance is not resolved within 3 working days, it must be resolved and a final resolution letter sent within 2 weeks (commonly read as 14 to 15 days) of receipt. If the complaint is not resolved within the prescribed period (typically within about 30 days of escalation to the entity), the policyholder may approach the Insurance Ombudsman. Where a grievance cannot be resolved within the norm, the framework expects the entity to communicate the position and the reason for the delay rather than let the complaint go silent. The broker should encode these acknowledgement and resolution timelines into its workflow as hard deadlines, and treat any approaching deadline as a trigger for action, not a target to be discovered missed after the fact. The discipline is that the clock runs from first receipt on any channel and is visible to the handler and to the grievance redressal officer at all times.
Tracking against the clock
A workable workflow shows, for every open grievance, the receipt date, the acknowledgement status and date, the resolution deadline, the days remaining, and the current owner. Grievances approaching their deadline are flagged for attention; grievances past their deadline are surfaced as breaches requiring immediate action and explanation. This time-tracking is the single most important operational feature of the workflow, because the turnaround norm is the metric the regulator watches and the one a broker most easily breaches through inattention. A grievance handled well but recorded as resolved after the norm is still a turnaround failure on the regulator's view.
The escalation matrix
Grievances should escalate through a defined matrix rather than sit with one handler until they age out. The matrix typically routes a grievance first to the handler responsible for the account or the function complained about, with a defined time for first response; escalates to a senior manager or the grievance redressal officer if the grievance is not progressing or is approaching its deadline; and escalates to senior management for grievances that are serious, that allege misconduct, or that risk regulatory or Ombudsman involvement. The matrix should define, for each level, who handles, within what time, and what triggers escalation to the next level. The escalation is automatic on time and severity, not dependent on the handler choosing to escalate, because a handler who is struggling with a grievance is the least likely to escalate it voluntarily.
The grievance redressal officer
The framework expects a designated grievance redressal officer with responsibility for the grievance process, oversight of turnaround, and the authority to drive resolution across the firm. The officer should have visibility of the whole grievance register, monitor turnaround performance, chair the escalation of difficult grievances, oversee the Bima Bharosa interface, and report grievance metrics to management and the board. The officer's name and contact should be disclosed to policyholders as the escalation point within the broker. A broker that names a grievance redressal officer on paper but gives the role no real authority or visibility has the form without the substance, which an inspection can distinguish.
Bima Bharosa Integration and the Insurance Ombudsman Pathway
Two external interfaces define the regulated grievance process: Bima Bharosa, through which the regulator monitors grievances, and the Insurance Ombudsman, the external redressal forum to which unresolved grievances can escalate. The broker's workflow must interface cleanly with both.
Bima Bharosa integration
Bima Bharosa, the renamed IGMS, is the IRDAI's central grievance-management platform. Complaints lodged on it are routed to the relevant entity, and the entity is expected to receive them, update their status as they are actioned, and record their resolution on the platform, so that the regulator has an accurate, real-time view of grievance volumes and turnaround across the industry. The broker's integration must ensure that grievances routed to it on Bima Bharosa are picked up promptly (not left unactioned on the portal while the clock runs), mapped to the internal grievance register so they are handled through the same workflow as other grievances, and updated on the platform as they progress and close. A mismatch between the broker's internal records and the Bima Bharosa status, complaints shown open on the portal but treated as closed internally, or resolutions not reflected on the platform, is a visible compliance failure because the regulator sees the portal directly. The integration should keep the two in step.
The Ombudsman as the external escalation
The Insurance Ombudsman is the external forum to which a policyholder can escalate a grievance that the insurer or intermediary has not resolved satisfactorily, under the Insurance Ombudsman Rules. The Ombudsman provides a cost-free, accessible alternative to litigation for policyholders, with jurisdiction over defined categories of grievance and monetary limits set by the rules. The policyholder can approach the Ombudsman after exhausting the entity's internal grievance process, or where the entity has not responded within the prescribed period. The broker must understand the Ombudsman's role, jurisdiction and process, because grievances the broker fails to resolve can land there, and the Ombudsman's findings carry weight.
Informing policyholders of the pathway
The framework expects the entity to inform policyholders of the escalation pathway: that if they are dissatisfied with the broker's resolution, or if the broker has not responded in time, they may approach the Insurance Ombudsman, with the relevant contact and process. Disclosing the Ombudsman pathway is not against the broker's interest; it is a compliance expectation and a sign of a fair process, and concealing it is itself a failing. The broker's grievance communications and its public disclosures should set out the internal escalation point (the grievance redressal officer) and the external escalation (the Ombudsman), so the policyholder knows the full path.
Handling an Ombudsman referral
When a grievance reaches the Ombudsman, the broker must respond to the Ombudsman's process: provide its records and position, participate in the proceedings, and act on the outcome. The broker that has run a clean internal process, with a documented grievance file showing how the complaint was handled, the advice given, and the resolution offered, is in a far stronger position before the Ombudsman than one whose handling was informal and unrecorded. The Ombudsman referral is, in effect, an external audit of the broker's grievance handling on that complaint, and the quality of the internal file determines how that audit goes. A pattern of Ombudsman referrals on similar grievances is also a strong root-cause signal that the broker should act on, because it indicates a recurring failure the internal process is not catching.
Root-Cause Logging, Audit Trail and Reporting
A grievance process that resolves complaints one by one without learning from them is incomplete. The framework, and good practice, expect the broker to analyse its grievances for root causes, maintain an audit trail of its handling, and report grievance metrics internally, so that the process improves the firm rather than merely processing complaints.
Root-cause analysis
Each grievance, and the grievance log as a whole, should be analysed for root cause: why did the complaint arise, and what underlying failure does it reveal? An individual grievance about a delayed endorsement points to a possible weakness in the endorsement workflow; a pattern of grievances about premium refunds points to a reconciliation problem; a cluster of advice complaints from one producer points to a training or supervision issue. The classification captured at intake is what makes this analysis possible: with grievances tagged by type and cause, the broker can see which categories recur and address the underlying process rather than re-handling the same complaint type indefinitely. Root-cause analysis turns the grievance log from a record of problems into a source of fixes, which is its real value to the broker.
The audit trail
The broker should maintain a complete audit trail for each grievance: the receipt with date, time and channel; the acknowledgement; the classification; the handling steps with who did what and when; the communications with the complainant; the resolution and its date; and any escalation, Bima Bharosa updates, or Ombudsman involvement. The trail must be retrievable and should be tamper-evident, so the broker can demonstrate, for any grievance, exactly how it was handled and whether the turnaround norms were met. An inspection assessing the broker's grievance compliance will sample grievances and test the trail, and a broker that cannot produce a clean handling record for a sampled grievance has a finding regardless of how well it believes it handled the complaint. Record retention should follow the broker's record-retention policy and the framework's expectations.
Internal and board reporting
The grievance redressal officer should report grievance metrics to management and the board: grievance volumes by type and trend, turnaround performance against the norms, escalation and Ombudsman activity, resolution outcomes, and the root-cause findings with the remediation in flight. This reporting serves two purposes: it gives management and the board visibility of how the firm is treating its clients, which is a governance expectation, and it drives the remediation of recurring problems. A board that sees rising complaint volumes in a category, or persistent turnaround breaches, can direct the resources to fix the cause. Grievance reporting that is buried in operations and never reaches the board leaves the firm's leadership blind to a clear signal of client-treatment quality.
Closing the loop
The mature grievance process closes the loop from complaint to fix to verification: a recurring grievance type is root-caused, a process change is made, and the grievance log is monitored to confirm the change reduced the complaints. This continuous-improvement cycle is what distinguishes a grievance process that genuinely improves client treatment from one that merely meets the turnaround norm on each individual complaint. The framework's underlying intent is fair client treatment, and a broker that uses its grievance data to remove the causes of complaints is serving that intent, not just complying with the form.
The connection to advice quality
A large share of broker grievances trace, directly or indirectly, to the quality of the advice and the placement, a cover that did not respond as the client expected, a sub-limit the client did not understand, an exclusion that bit at claim time. Many of these are preventable at the placement stage, by advising the client accurately on what each insurer's wording actually grants, what it excludes, and what its sub-limits and triggers are, and by documenting that advice. Sarvada gives commercial insurance brokers structured, searchable access to insurer policy wordings, so the broker can compare triggers, grants, sub-limits and exclusions across insurers, set client expectations accurately at placement, and reduce the grievances that arise when cover behaves differently from what the client assumed. Request Access to evaluate how structured wording access supports both better advice and fewer grievances downstream.
