Self-Funded Employer PBM RFP Data: What to Organize Before Vendor Selection Begins

For a self-funded employer, selecting a Pharmacy Benefit Manager (PBM) is not just a vendor search. It is a financial, operational, and member experience decision.

A Request for Proposal (RFP) can help compare PBM options, but only if the employer has the right data organized before the process begins. Too often, self-funded employers start a PBM RFP before they have gathered the information needed to evaluate vendors clearly. The result is a slower process, less comparable responses, more consultant follow-up, and a greater chance that important differences are discovered late.

For self-funded employers, benefits consultants, brokers, coalitions, and procurement teams, the lesson is straightforward: better upfront data makes PBM vendor selection faster, clearer, and more comparable.

Self-funded employer PBM RFP data should not be treated as an administrative afterthought. It is the foundation for understanding current performance, identifying procurement goals, and comparing future PBM arrangements. When self-funded employer PBM RFP data is organized early, the rest of the vendor selection process becomes easier to manage, easier to compare, and easier to defend.

Why Self-Funded Employers Need Better PBM RFP Data

Self-funded employers carry direct financial responsibility for pharmacy benefit costs. That makes PBM evaluation different from a simple vendor comparison. Self-funded employer PBM RFP data gives the employer, consultant, broker, or procurement team a clearer picture of the current pharmacy benefit before vendors begin shaping the conversation.

The employer needs to understand what it currently spends, which drugs drive cost, how members use the benefit, how rebates are handled, what pharmacy networks are used, and whether guarantees or audit rights are meaningful.

Without that information, an RFP can become vague. PBMs may respond with polished but difficult-to-compare proposals because the requestor has not provided enough context. Consultants and brokers may need to fill gaps manually. Procurement teams may receive answers that look complete but rely on assumptions that do not match the employer’s actual pharmacy benefit experience.

This is where many PBM RFPs become harder than they need to be.

The issue is not that PBMs cannot be compared. The issue is that the comparison often begins before the data is ready.

1. Current Pharmacy Claims Data

Claims data is one of the most important parts of self-funded employer PBM RFP data because it shows how the pharmacy benefit is actually being used.

At a minimum, self-funded employers should understand recent prescription drug utilization, total drug spend, member cost share, plan-paid amounts, pharmacy channel use, and high-cost claims activity. Depending on the organization, this may include retail claims, mail service claims, specialty pharmacy claims, and rejected or reversed claim patterns.

Claims data helps PBMs and advisors evaluate the actual population, not just a theoretical plan design.

It can answer questions such as:

• Which drugs are driving cost?
• How much spending is tied to specialty pharmacy?
• Which therapeutic categories are growing?
• How much utilization flows through retail, mail, or specialty?
• What portion of spend is concentrated among a small number of members?
• Where might plan design or clinical management need closer review?

Clean claims data helps vendors price more accurately and helps requestors compare responses more fairly. Weak or incomplete claims data can lead to assumptions, caveats, and less reliable comparisons.

2. Rebate History and Rebate Definitions

Rebates are a major part of PBM economics, but they are often difficult to compare without clear definitions. For self-funded employer PBM RFP data to be useful, rebate history should include more than payment totals. It should also explain definitions, timing, exclusions, and verification rights.

Before starting a PBM RFP, a self-funded employer should gather available information about historical rebate payments, guarantees, reconciliation timing, exclusions, retained amounts, and reporting practices.

The key question is not simply, “How much did we receive?”

The better questions are:

• How were rebates defined?
• Were rebates passed through?
• Were any amounts retained?
• How often were rebates reconciled?
• Were specialty drugs treated differently?
• Were certain drugs, claims, or channels excluded?
• What reporting was provided to verify the arrangement?

A new PBM proposal may promise a different rebate model, but the employer needs a baseline for comparison. Without knowing the current rebate structure, it is hard to determine whether a new offer is truly better or just different.

3. Specialty Pharmacy Data

Specialty pharmacy can represent a large share of pharmacy benefit spend, even if relatively few members use specialty medications.

That makes specialty data essential.

Self-funded employers should understand specialty spend, top specialty drugs, utilization trends, current specialty pharmacy requirements, member support programs, prior authorization patterns, and any existing specialty pharmacy carve-out or limited-distribution considerations.

Specialty pharmacy data can affect several parts of PBM vendor selection, including:

• Pricing terms
• Network requirements
• Clinical program evaluation
• Member support needs
• Prior authorization workflows
• Reporting expectations
• Implementation planning

If specialty pharmacy is a major cost driver, it should not be handled as a minor section of the RFP. It should be one of the areas where the employer organizes data carefully before vendors respond.

4. Current Formulary and Plan Design Information

A formulary is more than a list of covered drugs. It can affect access, cost sharing, rebates, utilization management, member disruption, and clinical strategy.

Before launching a PBM RFP, a self-funded employer should organize current formulary information, tier structure, exclusions, covered drug rules, prior authorization requirements, step therapy requirements, and exception processes.

The employer should also identify how much flexibility it wants in the future.

Some requestors may want a more aggressive formulary strategy to control cost. Others may prioritize member disruption avoidance. Others may need a balanced approach that considers clinical appropriateness, employee expectations, and financial performance.

PBM proposals can look very different depending on formulary assumptions. That is why current formulary and plan design data should be available before comparison begins.

5. Pharmacy Network and Access Data

Pharmacy network decisions affect both cost and member experience.

A self-funded employer should understand its current network arrangement, member geography, pharmacy utilization patterns, retail pharmacy access, mail service use, preferred pharmacy participation, and any known access concerns.

For employers with distributed workforces, geographic access may matter more. For employers with concentrated locations, local pharmacy relationships or disruption risk may be more important. For employers with specific workforce needs, network design may affect both satisfaction and adherence.

Network data helps evaluate whether a new PBM’s proposed network is realistic for the covered population.

A strong PBM RFP should not only ask, “What network do you offer?” It should help determine whether that network fits the employer’s members.

6. Existing Guarantees and Performance Commitments

PBM guarantees can cover claims accuracy, implementation milestones, service levels, reporting, call center performance, rebate guarantees, discount guarantees, mail service turnaround times, or other commitments.

Before starting a new PBM RFP, self-funded employers should gather current guarantees and evaluate how well they have worked.

Important questions include:

• What guarantees are currently in place?
• How are they measured?
• Were they met?
• What remedies apply if they are missed?
• Are reporting and validation rights clear?
• Do the guarantees reflect what actually matters to the employer?

A guarantee is only useful if it is measurable, meaningful, and tied to performance the employer cares about.

If the current guarantees are weak or difficult to enforce, the RFP should address that. If they are strong, they can become a baseline for comparison.

7. Audit Rights and Reporting Access

Audit rights and reporting access are often overlooked until there is a problem.

A self-funded employer should understand what it currently has the right to review, how often audits are permitted, what data is available, what limitations apply, and how reporting is delivered.

This matters because PBM arrangements can include complex pricing, rebate, network, and claims administration terms. Without meaningful reporting and audit rights, it may be difficult for an employer to validate performance.

Before beginning PBM vendor selection, requestors should know which reports they currently receive, which reports they want, and which data gaps create concern.

Reporting should not be treated as an afterthought. It is part of the control system for the pharmacy benefit.

8. Internal Goals and Decision Criteria

Data is not only historical. It is also strategic.

Before issuing a PBM RFP, self-funded employers should define what they are trying to improve.

Common goals may include:

• Reducing net pharmacy spend
• Improving rebate transparency
• Evaluating pass-through pricing
• Reducing specialty pharmacy trend
• Improving member access
• Limiting disruption
• Strengthening reporting
• Improving implementation support
• Expanding audit rights
• Reviewing the incumbent relationship

These goals should be clear before PBMs respond. Otherwise, the RFP may collect information without giving decision makers a clean basis for comparison.

Strong PBM procurement starts by defining what success looks like. This is where self-funded employer PBM RFP data becomes more than a file collection exercise. It becomes the employer’s working definition of what it needs from the next PBM relationship.

How PfRs Improve Early Data Organization

Proposals for Requestors (PfRs) offer a structured alternative for earlier data organization and vendor comparison.

A PfR is a vendor initiated procurement method made available through a controlled online marketplace after access requirements are met. It is structured using standardized templates and represents a vendor’s available offering. It is not public sales collateral. It is not buyer initiated. It is not tailored to one specific requestor.

For self-funded employers and their advisors, PfRs change the starting point.

A legacy PBM RFP often begins when the employer decides it is ready to ask vendors for custom responses. But before that happens, the employer should already understand its own pharmacy benefit needs: claims history, rebate expectations, specialty pharmacy exposure, formulary priorities, network requirements, guarantees, audit needs, reporting gaps, and decision criteria.

That preparation is valuable even if the employer ultimately chooses a legacy RFP.

It helps the organization understand its business better.

Knowing what you need from a PBM forces the requestor to define what matters before vendors begin responding. It clarifies whether the priority is lower net cost, better rebate visibility, specialty pharmacy control, member access, stronger audit rights, implementation support, or improved reporting. Without that self-knowledge, the procurement process can become a document exercise rather than a disciplined vendor selection process.

The same preparation is also important when shopping for PBM services through Rapid Request and PfRs.

Because PfRs are structured marketplace-based offerings, requestors need to understand their own requirements in order to identify the strongest fit. A self-funded employer that has organized its data can search, review, and compare PfRs more effectively. It can recognize which offerings align with its claims profile, specialty pharmacy needs, network expectations, formulary goals, reporting requirements, and contract priorities.

In other words, better data does two things.

It improves legacy PBM RFP readiness.

It also improves PfR marketplace readiness. The same self-funded employer PBM RFP data that supports a legacy RFP also helps requestors evaluate PfRs with more confidence.

For PBMs, structured PfRs can reduce repetitive response work and help present pricing, rebates, network, specialty pharmacy, reporting, guarantees, and audit rights in a more consistent format.

For requestors, PfRs can make vendor comparison more efficient because the offering information is organized before the deepest stage of procurement begins.

PfRs do not eliminate the need for careful review. Complex arrangements may still require negotiation, legal review, consultant involvement, and buyer-specific follow-up.

But they can reduce the amount of disorganized early-stage work that makes PBM procurement slower than it needs to be.

Where AI Can Help, Carefully

Artificial Intelligence (AI) can support PBM procurement when it is used carefully and paired with structured data.

AI should not replace procurement judgment, legal review, consultant expertise, fiduciary responsibility, or executive decision making. But it can help organize information, summarize differences, identify missing fields, and support more efficient comparison once the data is structured.

That distinction matters.

AI is not a shortcut for poor data preparation. If self-funded employer PBM RFP data is incomplete, inconsistent, or poorly defined, AI will not fix the underlying procurement problem.

But when claims data, rebate history, specialty pharmacy information, formulary details, network needs, guarantees, and audit rights are organized clearly, AI-supported tools can help decision makers review information faster and ask better questions.

The foundation is still the data.

Better Data Creates Better PBM Decisions

A PBM RFP should not begin with a blank document and a deadline.

It should begin with organized information.

For self-funded employers, the most important preparation includes claims data, rebate history, specialty pharmacy data, formulary and plan design information, network access needs, guarantees, audit rights, reporting requirements, and internal goals.

That information makes PBM vendor selection more efficient. It helps PBMs respond with more relevant offerings. It helps consultants and brokers compare options more clearly. It helps procurement teams avoid late-stage confusion.

Most importantly, it helps requestors make better decisions for the members who depend on the pharmacy benefit.

Self-funded employer PBM RFP data is not paperwork. It is the foundation for a faster, clearer, and more comparable PBM selection process.

It is the foundation for a faster, clearer, and more comparable PBM selection process.