Team Training Release: July 22, 2026 July 2026
Release 7.22.26

Quick CS Wins

Four small changes that clear real friction out of the daily workflow

What Changed?

Four unrelated fixes, bundled together because each one is small and each one came from Customer Success watching people get stuck.

The theme running through them: stop making users do a step before they're ready. Two are about documents no longer blocking progress, two are about the employer dashboard reflecting how people actually work.

1 & 2. Documents No Longer Block the Plan Build

A document is no longer required to move forward

In the plan build, a document was required before a user could proceed. That's now lifted. Users can build the plan and attach documentation when they have it.

This is the right call because the plan and the paperwork don't arrive at the same time. A broker often knows the plan design well before the carrier's document lands in their inbox. Forcing the document first meant either stalling the build or attaching a placeholder just to get past the gate.

Plan option document dropdowns are gone, replaced by the standard tagger

The per-option dropdowns for attaching a document are hidden, and the restriction on moving forward without associating a doc is removed.

In their place: the same tagger already used on the RFP builder and the renewal process. That's the point of this one. Rather than three different ways to attach a document depending on where you happen to be, there's now one pattern people already know.

Screenshot slot — tagger on the plan option, replacing the old dropdown

3. Employer Dashboard Table Order

Plans first, then Presentations, then RFPs

The RFP and Presentation tables swap position, so the dashboard now reads in the order the work actually happens.

Before

  1. Plans
  2. RFPs
  3. Presentations

After

  1. Plans
  2. Presentations
  3. RFPs

4. “RFP” Becomes “Marketing”

Label change on the employer overview

On the employer overview, the RFP tables are renamed:

RFPs Marketing
Start RFP Start Marketing Event

This matches the language brokers use. Sending an RFP is one part of marketing a group to carriers, and “marketing event” is what they call the thing they're starting.

Verify the scope of the rename before training on it

The card specifies this rename on the employer overview. Whether the same relabel carries to every other place “RFP” appears in the UI is not stated, and should be confirmed against the build rather than assumed.

Screenshot slot — employer overview with reordered + renamed tables