Independent insights for benefits professionals

The CFO–HR Renewal Evidence Packet: Seven Numbers and Four Questions

Give finance and HR the same decision record before changing a plan: enrollment, contributions, renewal terms, data quality, service evidence, and unanswered questions.

NB
Nexus Benefit Solutions
October 28, 2026·4 min read
The CFO–HR Renewal Evidence Packet: Seven Numbers and Four Questions

Renewal gets expensive when finance sees only a rate increase and HR sees only employee disruption. For January-plan-year employers reading this in late October, use the packet for the immediate decision meeting: identify what can still be decided, what needs carrier confirmation, and who owns the communication deadline. If the decision is already made, complete it as a record and use it to start the next renewal cycle earlier.

This packet comes after the timeline work in Your 120-Day Health Plan Renewal Checklist. That checklist sequences the season; this is the copyable decision-meeting artifact that lets a CFO, HR lead, and payroll owner decide from the same evidence. It does not forecast costs or promise savings. Sources were checked September 16, 2026.

Bring seven comparable numbers

Use the same census date, plan-year period, coverage tiers, and cost basis for every option. Put the source date beside each item. A blank marked “not available from vendor” is better than a figure inferred from an old proposal.

NumberRecordSource/owner
1Enrolled lives by tierHRIS/enrollment; HR validates date
2Current monthly employer cost, including identified feesInvoice/general ledger; finance
3Current employee deductions by tierPayroll configuration; payroll
4Renewal monthly employer cost on the same basisCarrier/TPA proposal; finance
5Renewal employee deduction illustration by tierContribution model; finance and HR
6Participation and waiver countEnrollment census; HR
7Open billing, eligibility, payroll, or vendor-service exceptionsIssue log; named owner

If aggregate vendor reporting is available, record its period, population, limitations, and interpreter. Do not turn a utilization dashboard into a conclusion about an individual’s health, future claims, or a guaranteed renewal result.

Copy this one-page meeting packet

Fill-in labelMeeting record
Employer / plan year / packet version________________ / ________________ / ________________
Meeting date / facilitator / finance approver / HR owner________________ / ________________ / ________________ / ________________
Comparison basisCensus as of ________; effective date ________; plans compared ________; included funding/fees ________; contribution rule ________.
Decision problemWe need to decide ________________________________________________.
Seven numbers1 ______ 2 ______ 3 ______ 4 ______ 5 ______ 6 ______ 7 ______ (attach source/version)
Option A / Option BEmployer cost ______ / ______; employee deduction change ______ / ______; material employee or implementation change ______ / ______.
Decision requested todayApprove / defer / request vendor evidence / choose communication approach: ____________________.
Open item, owner, due date____________________________ / ____________________ / ____________________
Record of decision and rationale______________________________________________________________________

Reconcile before debating options

Most confusion is a mismatched assumption: an old census, a per-employee contribution model while payroll uses tiers, or a rate sheet that excludes a fee on another invoice. HR confirms eligibility classes, counts, communication needs, and operational constraints. Finance confirms cost basis, budget treatment, contribution assumptions, and approval authority. Payroll confirms that deductions can be configured and tested. Record the version of every proposal you rely on.

Ask four questions and write the answer

  1. What problem are we solving? Write one sentence: budget pressure, network access, administration, comprehension, or a defined combination.
  2. What changes for employees and employer? Compare deductions, core plan features, contribution levels, services/fees, and implementation workload; list questions that only the carrier can answer.
  3. What evidence is missing? Name the document, vendor question, data exception, owner, and due date. Do not hide uncertainty in a footnote.
  4. Who operates the choice on day one? Name the owners for enrollment, eligibility feeds, payroll, employee questions, invoice reconciliation, and escalation.

Use the SBC as a comparison tool

Attach or link the current Summary of Benefits and Coverage for each medical option and label the plan year and option. CMS describes the SBC as a standard comparison form; its coverage examples illustrate general coverage in common situations, not what a particular employee will pay. Keep full plan materials and carrier provider/prescription tools available for follow-up.

Close with a handoff, not a verbal choice

Hypothetical example: A 70-person employer sees a proposed premium increase. Finance models the same enrolled tiers and existing contribution policy. HR adds a network difference and a new enrollment process. The meeting records a vendor network question, payroll test date, contribution decision, and communication owner; it does not call an option “best” from premium alone.

After the meeting, save the completed packet with the rate sheet and plan-material versions cited in it. Send each owner only the action, due date, and decision they need. At the next meeting, update the same packet rather than rebuilding the rationale from memory. This creates a useful record when a carrier answer arrives, payroll identifies a configuration constraint, or leadership asks why an option was selected.

  • Premium-only view: finance adds identified fees and employee deductions.
  • Inconsistent census: HR dates every comparison and explains material changes.
  • Verbal service promise: HR records scope, escalation route, implementation commitment, and exclusions.
  • No post-selection owner: leadership assigns actions through first-invoice reconciliation.

For a renewal review connecting plan design, employee communication, and implementation, explore Nexus group benefits.

Primary sources and scope

CMS: SBC and Uniform Glossary supports the SBC’s standardized comparison purpose. DOL: Working With Service Providers supports obtaining comparable service, experience, and cost information and conducting formal review. Checked September 16, 2026. This is an internal business tool; plan terms, carrier/TPA confirmation, and qualified advice control their respective questions.