Auto-Populate Renewal Month — Plansight Training

What Changed?

Primary Renewal Month was a fully manual field with no connection to actual plan dates — which led to mismatches like an employer showing “January” while every active plan renews 06/01.

Now the field auto-populates from real plan renewal dates, with manual edits always respected.

How It Works

Priority Order

Plansight fills Primary Renewal Month using this priority:

BenefitPoint import with a medical plan → use the medical plan's renewal date.
Medical plan built manually (and the field is empty) → use that medical plan's renewal date.
No medical plan → use the first plan built, by benefit-type priority (Medical → Dental → Vision → Life → Disability → Other).

Manual Edits Are Never Overwritten

If Primary Renewal Month already has a value, automation will not change it. Anything you set by hand stays put.

One-Time Backfill

A one-time script updates existing employer records using the same logic, so historical employers get accurate renewal months too. Records that already had a value are skipped (and logged).

Walkthrough Video

Drop the training video here once recorded.

Video slot — paste the embed iframe or replace this box