The Connected Benefit Proposal Workflow

Move through three connected stages

The old five-step checklist treated setup, upload, plan configuration, modeling, and export as separate handoffs. The current BART workflow keeps the work connected: source data, a working recommendation, and client delivery all stay tied to the same case.

1. Bring in and verify carrier files

Start a case with the material you received: carrier quotes, rate sheets, SBCs, invoices, or spreadsheets. Review the extracted plan data alongside the source documents, correct anything that needs attention, and organize the comparison before recommendation work begins.

• Keep carrier source documents available while you review plan values.
• Confirm the comparison before it becomes the basis of a recommendation.
• Use the approved case as the shared source for the work that follows.

2. Work the recommendation in Scenario Manager

Create a safe working copy when you need to explore contribution or enrollment changes. Scenario Manager lets you compare alternatives without changing the original case, so the baseline remains intact until you deliberately adopt a recommendation.

• Use the baseline as the reference point for every alternative.
• Test the changes that matter to the client conversation.
• Adopt only the scenario you intend to carry forward.

3. Deliver the approved case

Once the recommendation is ready, prepare the right client-facing output from that same approved case: a designed Proposal Book, a Present Proposal deck for the meeting, and an employee-facing Benefit Guide for rollout.

A practical review checklist

• Confirm plan details against their source documents.
• Keep experimental modeling in a named working scenario.
• Check the recommendation and materials before they leave the case.
• Choose the delivery format that fits the client meeting and employee rollout.

Why the separation matters

Keeping source verification, recommendation work, and client delivery connected makes it easier to review changes deliberately. The case stays understandable to the broker and reusable for the next conversation instead of becoming a collection of disconnected spreadsheets and exports.