Client Records for Insurance Agents: A Checklist That Survives Audits and Renewals

An agent in Kalyan has 640 families on her books, built over eleven years. Motor renewal dates are in a diary, health renewals in her phone calendar, life premiums in an Excel sheet her nephew set up in 2019, and policy PDFs scattered across four insurer portals and a WhatsApp chat called “Docs”. Her sub-agent leaves to join another agency and takes his phone, with 90 of her clients’ numbers on it. A month later, a family floater she sold six years ago lapses into the grace period because nobody called, and the client renews online with someone else.

None of that is a sales problem. It is a records problem. This guide answers one question: what should an insurance agent’s client database contain, and how do you keep it accurate, lawful and in your hands? It covers the manual version you can set up this week in a spreadsheet, the rules that shape it, and where a CRM or custom agency software makes it reliable. It draws on what we see when we move agencies and sales teams off WhatsApp and Excel.

What should an insurance agent’s client database contain?

An insurance agent’s client database should hold one record per household, each family member’s identity and contact details, every policy they hold with any insurer (number, product, sum assured, premium, mode, due dates, nominee), KYC status, consent records and a log of every contact. That is enough to run renewals, spot cover gaps and answer an insurer or regulator query.

Most agents we meet already have most of this information. The problem is that it lives in five places that do not talk to each other. The checklists below are designed so you can build them as columns in a spreadsheet today and move them into software later without redoing the work.

1. Fields to record for every client

Record identity, contact, family role, a few life-stage facts that drive insurance needs, KYC status and consent for each person. Keep it to what you will actually use for advising, servicing and renewals. Every extra field is one more thing to keep accurate and protect.

Source: Infoways practice. Consent and calling requirements are covered in sections 5 and 6, with their sources.

2. Fields to record for every policy

Each policy needs a row that links to the proposer, the insured persons and the nominee, plus everything that drives renewals and commission: insurer, product, policy number, cover amount, premium, mode and the dates. If a field changes at renewal, keep the history instead of overwriting it.

Source: free-look and grace periods as reported by Outlook Money and Moneylife on IRDAI’s 2024 master circulars, linked in sources. Confirm product-specific terms with each insurer.

The habit that saves the most money is simple: a renewal is marked “done” only when the new policy number is entered. In the systems we build, the renewal list cannot be cleared any other way. Agents who mark “client said he will pay” as done are the ones who discover lapses a month later.

3. How to structure households and families for cross-sell

Group people into households, give each household one ID, and link every person and policy to it. You can then see each family as a grid of members against types of cover, and the empty cells are your cross-sell list, built from need rather than from a product push.

A typical household we load has four to six people and policies from three or more insurers. Corporate agents were reported in March 2024 as allowed to tie up with up to nine insurers per line, so a family’s cover can be spread widely. Without a household view, nobody notices that the parents’ health cover is still a small individual policy bought fifteen years ago, or that the newly married son has no term plan.

Illustration only. Suitability of any product depends on the family’s situation and the insurer’s terms.

Two rules keep the household structure clean. First, a person belongs to one household at a time; when a son marries and sets up his own home, move him to a new household and link the two. Second, record life events (marriage, a child, a new car, retirement) as dated notes, because they are the honest reasons to call a client outside renewal season.

See also: Choosing between a ready-made tool and your own system is a broader question. See custom software vs off-the-shelf.

4. How to keep client data accurate

Data stays accurate when every record has one owner, key fields are mandatory, changes are checked against insurer data every month, and old values are kept as history instead of being overwritten. Accuracy decays fast in insurance because numbers, addresses, nominees and policy numbers all change.

1. One ID per person. Before adding anyone, search by phone and date of birth. Duplicate records are the main reason reminders go twice or not at all.
2. Mandatory fields. No policy is saved without insurer, policy number, next due date and agent code. No lead is saved without a next call date.
3. Monthly portal check. Download each insurer’s policy or renewal list from the agent portal and compare due dates and status with your records. Fix differences the same week.
4. Renewal review. At every renewal, confirm phone, address, nominee and sum insured with the client, and log the date you confirmed it.
5. History, not overwrite. Keep the old policy number, old nominee and old premium with a date. Commission disputes and claims often need the earlier value.
6. A yearly clean-up. Mark lapsed clients you have not reached in a year, and decide whether you still have a purpose to keep their data (see section 6).

5. What insurers and IRDAI expect agents to keep, and what not to keep

Insurers and IRDAI expect agents to be able to show records of the business they do: policies sold and renewed, claims they helped with, complaints, staff and receipts. KYC due diligence and its records sit with the insurer. The safest pattern is to keep business records and references in full, and to keep copies of identity and medical documents only as long as you have a clear need.

The specific rules are worth knowing, with a caveat. IRDAI’s Minimum Information Required for Investigation and Inspection Regulations 2020, in force from May 2021, require insurers and intermediaries to keep listed records on paper or electronically for at least ten years from the last transaction, according to a LiveLaw summary. In December 2020, Cafemutual reported IRDAI clarifying that agents should keep records of new policies sold, renewals, claim settlements, grievances and complaints, employees if any, and receipts for payments made and received.

On KYC, IRDAI’s AML/CFT master guidelines put the ultimate responsibility for customer due diligence on the insurer, which uses the Central KYC Registry and keeps identity records for five years, as summarised by Digio. On security, IRDAI’s Information and Cyber Security Guidelines of April 2023 cover brokers, corporate agents and other intermediaries but not individual agents or POSPs; insurers must make sure those individuals follow a minimum security framework set in the insurer’s own policy, per a Conventus Law primer.

Source: Infoways suggestion, based on the regulations and reports linked above. Your insurer’s agency agreement and channel guidelines may set specific retention rules; they take precedence. This is not legal advice.

6. DPDP Act 2023 and Rules 2025: your duties when you hold client data

An agent or agency that decides why and how client data is used is a Data Fiduciary under the DPDP Act 2023. That means giving a plain consent notice, using data only for the stated purpose, protecting it with reasonable security safeguards, telling clients and the Data Protection Board about a breach, answering requests to access, correct or erase data, and deleting it when the purpose ends.

The Rules were notified on 14 November 2025 with an eighteen-month phased compliance period, according to the PIB explainer. The gazette text brings rules 3 and 5 to 16, which include the notice, security, breach and retention rules, into force eighteen months after publication, so around May 2027. Building the habits now is cheaper than retrofitting them across a client book later.

Source: DPDP Rules 2025 (MeitY gazette) and PIB explainer, November 2025. Penalties per PIB: up to ₹250 crore for failing to keep reasonable security safeguards, up to ₹200 crore for not notifying a breach, up to ₹50 crore for other violations.

Health details deserve extra care even though the Act does not create a separate “sensitive” category. A leaked list of who has which illness, with phone numbers, is the worst-case breach for an agent. Our rule when building agency systems is simple: health information stays with the insurer, and the agent’s system only records that a declaration was made and when.

Calling rules sit alongside the data rules. Insurers and intermediaries were directed to make service and transactional calls from 1600-series numbers from 15 February 2026, and promotional calls and SMS follow TRAI’s preference rules. Store consent and DND flags on each person, as listed in section 1.

See also: Reminders over WhatsApp need the same consent discipline. See WhatsApp Business, AI and UPI for Indian businesses.

7. Excel or a CRM for an insurance agent?

Excel or Google Sheets is fine for a solo agent with a few hundred families who checks it daily. Once you have sub-agents or POSPs, more than one insurer’s renewals to chase, or a need to prove who saw which client, a CRM with logins, reminders and audit logs is safer and cheaper than the renewals you lose.

Source: Infoways comparison. Features of named and unnamed CRMs change often; check each vendor directly.

If you stay on a spreadsheet, use a cloud sheet with two-step login rather than a file passed around on WhatsApp, protect the columns that hold formulas, and keep one master copy. If you pick a ready-made CRM, confirm it holds policies from all your insurers, sends reminders from your own WhatsApp Business number and lets you export everything.

8. Access control for team members

Give every team member their own login, let advisors see only their own clients, let back office see policies but not export the whole book, and keep exports for the owner. Remove access the day someone leaves. This protects clients and keeps the book with the agency.

Source: Infoways practice. Adapt to your hierarchy and your insurers’ requirements.

For agency teams, the same database should drive daily reporting. We built a daily sales reporting system for a team of more than a hundred reps that replaced evening WhatsApp reports with entries in an app. The lesson that carries over to insurance agencies is that when advisors enter business in one place, the manager’s report, the leaderboard and the incentive sheet all come from the same records, and nobody argues about whose figures are right.

9. Backups that would survive a lost phone or a crashed laptop

Keep at least two copies of the client database in different places, one of them automatic and off your phone, and test a restore every quarter. DPDP Rule 6 lists backups among reasonable safeguards, and for an agent the business reason is plainer: the client book is the business.

• A cloud sheet or CRM with its own version history is the first copy.
• A weekly export (Excel or CSV) to an encrypted drive or a separate business cloud account is the second.
• Policy PDFs live in one secured business folder, not in WhatsApp media.
• Every quarter, open the export on another device and check that the renewal list for next month matches.

10. Migration plan: from diaries and Excel to one database

Move in this order: collect what you have, build the household and person list, load policies with verified due dates, switch on renewals, then add leads and team reporting. Most agencies we work with take four to eight weeks, and most of that time goes into cleaning duplicates and checking dates.

1. Week 1: gather. Download policy and renewal lists from every insurer portal. Photograph or type up diary entries. Export phone contacts tagged as clients.
2. Week 1-2: people and households. Merge duplicates by phone and date of birth, assign Household IDs and roles.
3. Week 2-3: policies. Load policies from portal exports first, because they are the most accurate. Add diary-only policies after checking them with the client or insurer.
4. Week 3: verify a sample. Check 50 random policies against the portal: due date, status, nominee. Fix the pattern behind any error, not just the row.
5. Week 4: renewals live. Run the morning renewal and grace list from the new database. Keep the diary running in parallel for one cycle.
6. Week 4-6: consent and access. Start giving the consent notice to clients as you contact them, set up logins by role and stop sharing files on chat.
7. Week 6-8: leads and team. Add leads with next call dates, then daily entries and plan vs actual if you run a team.

Where this advice breaks down

This checklist assumes you sell across several insurers and keep your own book. If you work for one insurer and its agent app already holds your clients, renewals and leads, a separate database may duplicate effort; use the insurer’s app and keep only a household view and consent record of your own.

The regulatory points above come from regulations, gazette text and reputable summaries as of October 2026, and several are reported rather than read in the original. Insurer agency agreements often add stricter rules, and the insurance laws were amended in December 2025, with follow-on regulations still arriving. Treat the tables as a starting point to confirm with your insurer’s channel or compliance team, not as legal advice.

Finally, software does not fix a habit of not calling. We have seen agencies buy a CRM and keep losing renewals because nobody opened the morning list. The database earns its keep only when the daily routine is built around it.

Where software helps most is the part people forget: reminders that go on their own, a grace list that cannot be ignored, logins that end when someone leaves and a book that belongs to the agency. Our insurance agent and agency software page shows how we build those modules, from family records to commission checks.

Your client records checklist

The Kalyan agent did not need more clients. She needed the 640 families she already had in one place she controls, and that is a job you can start this week.