The Internal Float Pool: Why the Math Rarely Works Out the Way You Think

The internal physician float pool looks like a cost-saving solution on a whiteboard. In practice, the math rarely holds. Understanding why requires looking at what the model actually costs versus what it appears to cost.

The Whiteboard Case

The pitch for an internal physician float pool is straightforward, and it is genuinely appealing to any CFO who has spent time staring at a locum tenens invoice.

The argument goes like this: we are spending $8M–$15M per year on locum tenens, paying agency margins of 25–40% on top of the physician's actual compensation. If we build our own internal pool of flexible physicians, employed directly, available on short notice, credentialed across our facilities, we eliminate the agency margin, gain direct control over quality and coverage, and reduce our total flexible workforce spend by 30–40% within two years.

On a whiteboard, this math works. The agency margin alone, on a $10M locum spend, represents $2.5M–$4M in annual savings. Even accounting for the cost of building and running the float pool, the net savings appear compelling.

The problem is that the whiteboard version of this analysis almost always omits the most important cost category: the infrastructure required to make a physician float pool actually function. And that infrastructure is far more expensive, far more complex, and far more operationally demanding than most health systems anticipate when they make the decision to build.

What a Float Pool Actually Requires

A physician float pool is not a staffing strategy. It is an operating business, a business that happens to sit inside a health system rather than on the open market. And like any operating business, it requires a full stack of infrastructure to function.

Credentialing and privileging infrastructure. A float pool physician covering multiple facilities needs to be credentialed and privileged at each one. In a health system with five hospitals, that means five separate credentialing files, five sets of privileging applications, five sets of ongoing maintenance requirements, reappointments, CME tracking, license renewals, DEA registrations, malpractice certificates. Each credentialing file requires staff time to initiate, maintain, and renew. The credentialing coordinator capacity required to support a float pool of 10–15 physicians across five facilities is typically 1.5–2.0 FTEs, a cost that is rarely included in the initial float pool business case.

Scheduling and dispatch infrastructure. The operational value of a float pool depends entirely on the ability to deploy physicians quickly and efficiently to wherever coverage is needed. This requires a scheduling system that has real-time visibility into coverage gaps across all facilities, a dispatch process that can match available float pool physicians to open shifts within hours, and a communication infrastructure that keeps float pool physicians informed of their schedules with enough lead time to plan their lives. In practice, this requires dedicated scheduling coordinator capacity (typically 0.5–1.0 FTE per 10 float pool physicians) plus either a purpose-built scheduling platform or a significant customization of an existing one.

Compensation and benefits administration. Many float pool physicians are employees, which means they require the full employee infrastructure: benefits enrollment, payroll processing, W-2 management, workers' compensation coverage, malpractice insurance, CME allowances, and all the administrative overhead associated with employment. For a pool of 10–15 physicians, this administrative burden is not trivial, and it falls on HR and finance functions that are already stretched.

Compliance and quality oversight. A float pool physician covering multiple service lines and facilities needs ongoing quality oversight, peer review, performance monitoring, credentialing maintenance, and compliance with the specific privileging requirements of each facility. This oversight function requires physician leadership time and administrative support that is rarely budgeted in the initial float pool analysis.

Technology infrastructure. Effective float pool management requires technology that most health systems do not currently have: a centralized credentialing database that spans facilities, a scheduling platform with real-time gap visibility, a communication system for rapid deployment, and analytics that track float pool utilization, cost, and quality metrics. Building or buying this technology stack is a capital investment that typically runs $200,000–$500,000 in implementation costs, plus ongoing licensing and maintenance.

Recruitment and retention. Float pool physicians are a specialized workforce segment with specific preferences and requirements. They value flexibility, variety, and competitive compensation, and they have options. Recruiting and retaining high-quality physicians who are willing to work in a float pool model requires a dedicated recruitment effort, a competitive compensation structure, and an employment experience that is meaningfully better than what they could get from a locum agency. This is not a passive recruitment challenge. It is an active one, requiring dedicated recruiter time and a compelling employer value proposition.

When all of these infrastructure costs are fully loaded into the float pool business case, the picture changes substantially. A float pool of 10–15 physicians, properly staffed and supported, typically requires $800,000–$1.5M in annual infrastructure cost, credentialing coordinators, scheduling coordinators, technology, HR overhead, compliance oversight, and recruitment, before a single physician shift is covered.

The Hidden Costs That Sink the Business Case

Beyond the direct infrastructure costs, float pool programs carry a set of hidden costs that further erode the financial case.

Ramp time. Building a float pool from scratch takes 12–18 months before it is generating meaningful coverage. During that period, the health system is paying the infrastructure costs of the float pool while still relying on locum agencies for the majority of its flexible coverage needs. The ramp period is a period of double cost, and it is rarely modeled honestly in the initial business case.

Utilization risk. A float pool is a fixed cost that generates value only when its physicians are deployed. If the float pool is underutilized, because coverage needs are lower than projected, because scheduling coordination fails, or because float pool physicians are not available when and where they are needed, the fixed infrastructure cost remains while the coverage value does not materialize. Health systems consistently underestimate the utilization management challenge of a float pool: keeping physicians engaged and available without over-scheduling them, while ensuring that coverage gaps are filled efficiently.

Scope creep. Float pool programs have a consistent tendency to expand beyond their original scope. A pool designed to cover internal medicine and hospitalist gaps gets pressure to cover emergency medicine. A pool designed for one region gets asked to cover a newly acquired facility two hours away. Each expansion requires additional credentialing, additional scheduling complexity, and additional infrastructure, but the business case for the expansion is rarely as rigorous as the original analysis, and the cumulative cost of scope creep can significantly exceed the original infrastructure budget.

Opportunity cost. Every dollar and every hour of management attention invested in building and running a float pool is a dollar and an hour not invested in something else. The operational leaders who are managing credentialing coordinators, resolving scheduling disputes, and troubleshooting float pool technology are not working on the strategic priorities that drive the organization forward. This opportunity cost is real, even if it is difficult to quantify precisely.

The Build vs. Buy Calculus

The fundamental question in the float pool decision is not "can we build this?" Health systems can build almost anything. The question is "should we build this, given what is available in the marketplace?"

And the honest answer, for most health systems, is no, because the marketplace has already built it.

The infrastructure that makes a physician float pool work, the credentialing database, the scheduling platform, the dispatch capability, the compliance oversight, the physician network, is not unique to any single health system. It is the same infrastructure that every health system needs. And building it independently, inside each health system, is a massive duplication of effort and investment that serves no one's interests except the vendors who sell the component pieces.

Purpose-built physician workforce marketplace platforms (companies like Syncx) exist precisely to solve this problem. They have already built the infrastructure: the credentialing systems that maintain physician files across hundreds of facilities, the scheduling technology that matches available physicians to open shifts in real time, the compliance frameworks that ensure privileging requirements are met, the physician networks that provide the supply of flexible, high-quality physicians that a float pool requires. They have built this infrastructure at scale, amortized across hundreds of health system clients, and made it available as a service at a fraction of the cost of building it independently.

The economic logic is straightforward. A health system that builds its own float pool infrastructure is investing $800,000–$1.5M per year to replicate capabilities that a marketplace platform provides for a fraction of that cost, and provides better, because the platform's entire business model depends on those capabilities being excellent.

What the Marketplace Model Actually Delivers

The objection to marketplace platforms that health system leaders most commonly raise is control. "We want to own our physician relationships. We want to control quality. We want to know who is covering our patients."

These are legitimate concerns. And the best marketplace platforms are designed to address them directly.

A well-designed physician workforce marketplace does not replace the health system's relationship with its physicians, it enables it. The health system still defines the coverage requirements, the quality standards, and the privileging criteria. The platform handles the administrative infrastructure that makes those standards enforceable at scale: the credentialing verification, the scheduling coordination, the compliance tracking, the performance data. The health system gets the control it wants without the operational burden of building and maintaining the infrastructure that control requires.

The quality argument, that internal float pool physicians are higher quality than marketplace physicians, is also worth examining critically. The quality of a float pool physician depends on the recruitment and vetting process, not on whether the physician is employed directly or engaged through a platform. A marketplace platform with rigorous credentialing standards and a curated physician network can deliver physician quality that is equal to or better than what a health system can recruit independently, particularly for specialties where the health system does not have deep recruitment expertise or an established employer brand.

What the marketplace model delivers, beyond cost efficiency, is scalability and resilience. A health system with an internal float pool of 12 physicians has 12 physicians. When three of them are unavailable simultaneously (vacation, illness, a competing opportunity) the coverage gap falls back to the locum agency anyway. A marketplace platform with a network of hundreds of physicians in the relevant specialties and geographies does not have this single-point-of-failure problem. The supply is elastic in a way that an internal pool, by definition, cannot be.

The Right Framework for the Decision

None of this means that internal float pools are never the right answer. For very large health systems, those with 20 or more hospitals in a concentrated geography, with consistent high-volume coverage needs across multiple specialties, the scale economics of an internal pool can work. The infrastructure cost is amortized across a large enough coverage volume that the per-shift cost advantage over marketplace platforms becomes real.

But for the majority of health systems, the build vs. buy calculus consistently favors the marketplace. The infrastructure cost is too high, the ramp time is too long, the utilization risk is too significant, and the opportunity cost of management attention is too real.

The framework for making this decision honestly requires four inputs:

Your true locum spend, fully loaded, not just the agency invoices, but the administrative cost of managing those relationships, the credentialing cost, and the scheduling overhead.

The full infrastructure cost of an internal float pool, including all the categories described above, not just the physician compensation, but the coordinators, the technology, the compliance overhead, and the recruitment investment.

The realistic utilization rate you can achieve with an internal pool, based on your actual coverage patterns, your geographic footprint, and your ability to manage scheduling complexity.

The total cost of a marketplace solution that delivers equivalent coverage quality and reliability, including platform fees, physician compensation, and the reduced internal administrative overhead that comes with outsourcing the infrastructure. A company like Syncx doesn't charge anything up front, they simply charge a 5% fee on top of the physician pay. This model works because there is no cost to the health system unless there is physician deployment. And every shift with a 5% fee to Syncx is a shift without a 25-40% 3rd party agency markup.

When health systems do this analysis honestly (with all four inputs fully loaded) the marketplace solution wins in the majority of cases. Not because internal float pools are a bad idea in principle, but because the infrastructure required to make them work is a core competency of workforce marketplace platforms, not of health systems. And there is no competitive advantage in building infrastructure that someone else has already built better.

The deeper issue with the internal float pool debate is that it frames the question too narrowly. The real question is not "should we build a float pool or use an agency?" It is "what is the optimal model for managing our flexible physician workforce, and what infrastructure do we need to support it?"

The answer to that question, for most health systems, is a hybrid model: a marketplace platform that provides the infrastructure, the physician network, and the scheduling technology, combined with a small internal team that manages the strategic relationships, sets the quality standards, and ensures that the platform is being used to its full potential.

This model captures the cost advantages of the marketplace (no agency margin, efficient matching, elastic supply) while preserving the organizational control and quality oversight that health system leaders rightly value. It requires a fraction of the infrastructure investment of a fully internal float pool, generates results faster, and scales more efficiently as coverage needs change.

The health systems that are winning the flexible workforce challenge are not the ones that have built the biggest internal float pools. They are the ones that have been most strategic about where to invest their infrastructure dollars, building internal capability where it creates genuine competitive advantage, and leveraging marketplace infrastructure where the platform has already solved the problem better than they could on their own.

The float pool is a good idea. Building all the infrastructure yourself is not.