What to capture before consolidation
A benefits vendor inventory connects each vendor to its capability, cost, contract terms, data dependencies, and service responsibilities. It gives the decision group a basis for assessing duplication, exit options, and transition risk. A list of vendor names and fees cannot establish those conditions, even when it appears to account for the full benefits portfolio.
“A list of vendor names and fees cannot establish those conditions, even when it appears to account for the full benefits portfolio.”
The practical test is whether the team can answer, for each vendor, when notice is due, what the current agreement requires, which interfaces depend on the service, and what reported utilization means. Missing answers can delay a consolidation or distort its savings case. Build the inventory to resolve those questions, with links to the records that support each entry.
Treat the inventory as a maintained operating record. Contract documents may be held by procurement, Legal, a consultant, or the vendor; technical and service information may be held elsewhere. Assign an owner to bring the records together and a named contributor for each area. The following four sections organize the information needed for a consolidation decision.
Capture term dates, renewal provisions, the non-renewal notice period, and the method and recipient required for notice. Record per-employee-per-month fees, implementation charges, utilization-based fees, minimum commitments, and performance guarantees, including how each is measured and claimed.
Include transition assistance, data return or destruction terms, and relevant subcontractor obligations. Record available security assessments, their scope, dates, and unresolved findings; a certification label alone is not a complete security assessment. Where the relationship requires a business associate agreement under HIPAA, record the agreement and its status. HHS guidance makes that determination depend on the parties' roles and activities, not simply the movement of health information.
Calculate notice dates from the executed contract and confirm how days, delivery, and receipt are defined. A January 1 renewal with a 120-day notice period creates a decision deadline around early September, potentially well before the team expects to complete its review. Minimum commitments or termination charges can change the economics of an exit, but they do not always require a buyout. Record the actual terms and the owner responsible for interpreting unresolved provisions.
Collect the current executed agreement, amendments, renewals, and relevant schedules. Confirm which documents govern if terms differ. Store a consistent summary with a link to the underlying clause so the decision group can compare vendors without losing the qualifications that matter. Mark missing or disputed information as unresolved rather than filling it from a sales presentation.
For each vendor, document relevant connections: single sign-on, eligibility files, payroll deductions, carrier or administrator feeds, and claims or encounter data. Record the format, frequency, source, destination, owner, and last validation. Include manual steps and locally maintained scripts where they exist. The aim is to identify who can explain and maintain each dependency before a transition changes it.
Map dependencies between vendors as well as direct connections to the employer. A navigation service may need a carrier's claims feed; an advocacy service may depend on an eligibility file for new hires. A vendor or format change can interrupt those functions unless the receiving service is updated and tested. For each proposed removal, specify the replacement connection, acceptance criteria, transition owner, and fallback arrangement.
Record each vendor's utilization definition, reporting period, and denominator before using the figure in a business case. Registrations, encounters, and engaged members describe different activities; eligible employees, covered lives, and registered users describe different populations. Create common definitions for comparable services, but retain differences that reflect how a benefit is intended to work. Cost per active user may be useful within a comparable service category; it cannot by itself make unlike benefits comparable.
“Cost per active user may be useful within a comparable service category; it cannot by itself make unlike benefits comparable.”
Low use calls for interpretation. A service aimed at a small population may be meeting its purpose at a low overall participation rate. A broadly available navigation service may have limited awareness, an eligibility problem, or limited perceived value. Distinguish those explanations before recommending a cut. Where appropriate, compare eligible, aware, registered, active, and repeat users, while recognizing that repeat use is not a suitable objective for every benefit.
For each benefit, identify the first contact for help, the next step when that contact cannot resolve the issue, and the owner responsible for the case. Record contractual service levels and whether performance is measured. Request relevant data, such as speed to answer, abandonment, first-contact resolution, and cases escalated to HR, using consistent periods and definitions. Missing information is a reporting gap to investigate, not proof of poor service.
Test the documented path with representative employee situations. Can the initial contact identify the responsible team, transfer the information, and confirm resolution? Note where HR is expected to intervene and whether it has the authority and information to do so. A replacement vendor will need to address those gaps explicitly; changing the contract holder alone does not resolve them.
Benefits operations can own the inventory, with designated contributors in IT, procurement, Legal, and other relevant teams. Set a review cycle, such as a quarterly update and a fuller review ahead of renewal planning, and require updates when contracts, feeds, or vendors change. Estimate the first build from the number and complexity of agreements and interfaces. A fixed staffing estimate based only on vendor count would overlook missing records and technical complexity.
Use the inventory to connect a recommendation to its supporting conditions. Capability, utilization, and service information inform which options to examine; contracts constrain timing and cost; integrations define transition work. Review the information together before booking savings. Keep unresolved dependencies visible in the decision record so an approval includes the conditions that must be met before implementation.
Start with vendors whose notice or renewal decisions fall within the next 12 months, including agreements that need an earlier decision to allow transition time. Add integration and service dependencies before recommending a consolidation. Normalize comparable measures, retain meaningful differences between benefits, and assign the ongoing owner. The inventory is useful when the decision group can trace each recommendation to current records and a feasible implementation plan.
Connex convenes total rewards and benefits leaders in closed-door peer settings to compare inventory practices, reporting definitions, and contract provisions. Those discussions can help identify questions the local record has missed, while the employer's own agreements and operating evidence remain the basis for its decision.