CRM Data Hygiene: A Routine for Insurance Agency VAs

Why CRM records drift

An agency CRM collects data from many hands and many sources. Quotes get created quickly, carriers return data in different shapes, and a policy that started as an opportunity becomes a client without anyone updating the stage. Over time the record stops describing the book and starts describing the last person who happened to type in it. A VA who owns a short weekly hygiene pass keeps the CRM usable for everyone.

This guide is administrative. It is not coverage, legal, or tax advice, and it does not replace your agency's written procedures or the judgment of licensed staff.

What clean actually means

Clean does not mean perfect. It means a record another person can trust at a glance. For an insurance agency this usually comes down to four things: one record per real person or business, the correct pipeline stage, the required fields filled, and a next action with a date. Everything else is a nice-to-have.

Define the minimum standard with the owner before you start, because clean is a decision, not a guess. Write the standard down so the same rules apply to every review.

One practical rule is to agree on a definition for each required field before the first pass. If two people disagree about what counts as a complete address or a valid stage, the same record will pass one week and fail the next. Keep the definition in the same place as the field list so it stays in view.

The weekly review

Set a recurring block, for example one hour each week, and run the same pass every time. Consistency keeps the backlog from growing.

1. Search the CRM for records created or edited in the past week.
2. Run the duplicate report and review each suggested pair.
3. Filter opportunities with no activity in the number of days the agency defines.
4. Check each record against the required-field list.
5. Flag records with no follow-up date or a date in the past.
6. Log the issues you cannot fix and send them to the owner.

A week is short enough that the changes are still fresh in memory. It is also long enough that a meaningful amount of new data has arrived. Keep a short log of what changed in each pass, so the owner can see the trend and a replacement VA can pick up the routine without starting from memory.

Merging duplicates

Duplicates usually share a last name, a phone number, or an email address. Open both records side by side and decide which one is the survivor before merging. Keep the record with the most complete history, the correct policy links, and the earliest activity date.

Never merge on name alone. Two clients can share a name, and a merge is hard to undo. When a pair is not a true duplicate, link the records as related instead. If the matching rule itself keeps producing false pairs, that is a settings issue for the owner, not a job for the VA to fix by hand each week.

Stale stages and missing fields

A stale opportunity is one that has not moved in the number of days the agency defines. The VA does not decide that a deal is lost or won. Instead, the VA checks the file for the missing piece, such as a decision date, and asks the owner or producer for the true status.

Required fields are the same on every record. Look for missing policy numbers, addresses, phone numbers, and line-of-business tags. Fill in what you can verify from documents already on file, and mark the rest for follow-up rather than inventing a value. An empty field is honest; a guessed field is worse than no field.

Work the oldest and most active records first, since a stale stage on an open opportunity costs more than a stale stage on a closed one. Correcting a focused set of records is more useful than skimming hundreds and changing nothing.

Follow-up dates and next actions

A record with no next action quietly disappears. Every open opportunity and service item should have one owner, one next step, and one date.

• Missing date. Add the date only when the file supports it.
• Past date. Move it forward or ask the owner what happened.
• No owner. Route it to the person who handles that account.
• No next action written. Add a short, specific step.

A date without a specific action is not much better than no date at all. The point of the field is to make the next move obvious to whoever opens the record.

Reporting issues and review cadence

Hygiene work finds broken handoffs, not bad people. Report issues in a fixed format: the record, the problem, the count, and the suggested fix. Track the same issues month to month so the owner can see whether the process is improving.

A weekly pass suits most agencies because it matches the sales and service cycle. Add a monthly summary that counts duplicates merged, fields corrected, and stale records addressed. Once a quarter, review the required-field list itself, since the agency's needs change over time. The goal is a record the whole team can rely on, not a one-time cleanup.

Keep the weekly log and the monthly summary in one shared place. A short history of fixed issues is the clearest evidence that the routine is working, and it turns the quarterly review into a five-minute conversation instead of a research task.

If duplicate records make it hard to see the book, tell us how your agency organizes its CRM and we will map a weekly routine. InsuranceYo's services page describes the administrative work VAs commonly support.

Scope and limitations

• This article is a general administrative guide. It does not prescribe a specific CRM configuration or vendor.
• The cadences and field lists are examples. An agency should set its own standard with management and licensed input.
• Research limitation: no regulator prescribes a CRM hygiene cadence. The routine here is common office practice, not a compliance requirement, and it is not legal advice.

Sources

1. Federal Trade Commission. https://www.ftc.gov/
2. Insurance Information Institute. https://www.iii.org/
3. National Association of Insurance Commissioners. https://content.naic.org/