Intellify IQ / Locum Tenens
The Locums Blind Spot
Physician and APP spend is the largest, fastest-growing line in contingent labor, and the least visible. Here is why that is a CFO problem, a CMO problem, and a competitive advantage hiding in plain sight.
By Julie Dey ·
If you ask a healthcare CFO what their largest controllable labor expense is, most will answer quickly: travel nursing. It is visible, it is tracked, and after the pandemic-era surge, it sits at the top of every cost reduction conversation.
The correct answer, increasingly, is locum tenens physicians and advanced practice providers. And most CFOs cannot tell you precisely what they are spending, at what rates, through how many agencies, against what market benchmarks, because the systems they use to manage locums were not built to surface that information.
This is the locums blind spot. It is not a data problem. The data exists, distributed across staffing agency invoices, credentialing files, scheduling systems, and contract records. It is a platform problem: no single system has been built to connect those sources, benchmark the spend, and return an answer a CFO can act on.
Why locums is different from every other labor category
Locums spend behaves differently from travel nursing or per diem spend in ways that have direct financial consequences. The daily rates are significantly higher, a locum physician in a specialty with strong demand can carry an all-in cost that exceeds a permanent FTE on a per-day basis by a factor of three or more. The contracts are more complex, often including travel, housing, malpractice tail, and licensing reimbursements in addition to the daily rate. The billing cycles are irregular. And the number of agencies involved in a single health system's locums program can range from two to fifteen, each billing on its own schedule and format.
The result is a spend category that is structurally resistant to the consolidation and benchmarking CFOs have applied successfully to other labor categories. You cannot benchmark a locum rate you cannot see. You cannot model the cost of a coverage gap if your data on current coverage is distributed across agency spreadsheets. And you cannot make a financially sound decision about whether to convert a locums position to permanent if you do not have a clear picture of the locums cost on a per-shift, per-month, and per-year basis.
The conversion decision is the highest-stakes question in physician workforce
Every health system using locums faces a recurring question: at what point does it make financial sense to convert a locums-covered position to a permanent hire? It sounds straightforward. In practice, it is one of the most analytically demanding decisions in physician workforce management, and most health systems are making it without the data to support it.
The full cost comparison requires modeling the all-in locums cost, daily rate, agency margin, travel, housing, malpractice, licensing, against the total cost of a permanent hire including base compensation, benefits, signing bonus, relocation, onboarding, and the productivity ramp period. It requires projecting coverage continuity assumptions in both scenarios. And it requires accounting for the cost of the coverage gap that exists while a permanent search is underway, which can extend six to twelve months in competitive specialties.
Intellify Locums was built specifically to support this analysis. The platform maintains a complete financial record for every locums engagement, every rate, every agency, every reimbursement, and models it against market benchmarks and permanent hire equivalents on demand. The conversion decision does not require a consultant or a three-week analysis. It requires a question and a platform capable of answering it.
What rate benchmarking actually requires
Most CFOs are familiar with rate benchmarking for travel nursing. Staffing platforms have made market rate data accessible and reasonably transparent for that category. Locums rate benchmarking is fundamentally harder, and the reasons matter.
Physician specialty rates vary significantly by geography, by subspecialty, by call requirements, by the complexity of privileging at a given facility, and by the current supply of available providers in a market. A single benchmark number for hospitalists or emergency physicians is nearly meaningless, what matters is the benchmark for a specific specialty in a specific geography at a specific time. That level of granularity requires data infrastructure that generic workforce platforms were not built to provide.
When Intellify surfaces a rate that exceeds market by 18 percent for a specific specialty in a specific region, that is not a statistical average. It is an observation drawn from actual market transactions in comparable contexts. For a CFO trying to reduce locums spend, that specificity is the difference between a benchmark that drives a real renegotiation and one that merely provides cover for the status quo.
Physician coverage is not a staffing problem
The language health systems use to describe their locums programs, "gap coverage," "temporary fill," "bridge staffing", reveals an underlying assumption that physician coverage is a staffing problem. Find a qualified physician. Get them credentialed. Put them on the schedule. Repeat.
Any Chief Medical Officer or Medical Staff Director who has managed a complex locums program knows how wrong that framing is. Physician coverage is a clinical continuity problem, a credentialing and privileging problem, a quality and safety assurance problem, and a patient experience problem, all of which happen to require a staffing solution. The difference in framing matters because the tools that solve a staffing problem are categorically different from the tools that solve a clinical continuity problem.
Most locums management technology was built to solve the staffing problem. Intellify Locums was built to solve the clinical one.
The privileging problem is unique to physician workforce
No other contingent labor category carries the credentialing and privileging complexity of physician and APP workforce. A travel nurse requires license verification, credential review, and facility orientation. A locum physician requires all of that, plus medical staff privileging that is specific to the facility, governed by medical staff bylaws, subject to Joint Commission standards, and often requiring peer review documentation, malpractice history review, DEA registration, and CME verification on a specialty-specific basis.
The privileging process for a new locums physician at a facility where they have not previously practiced typically takes four to eight weeks under optimal conditions. Under non-optimal conditions, which describes most health systems' current processes, it takes longer. Every day beyond the planned start is a day the position is unfilled. Every day the position is unfilled is a day the medical staff absorbs the coverage load.
Intellify Locums manages the privileging workflow as an integrated part of the platform, not as a parallel manual process. Every requirement, facility-specific privileging criteria, state licensing, DEA, malpractice, peer references, CME, is tracked against the assignment start date with proactive milestone alerts. Credentialing staff see every at-risk file before it becomes a delay. Medical Staff Directors have a real-time view of privileging status across every active and incoming locums provider.
Why locums breaks every standard workforce platform
Every workforce VP responsible for locums management has a version of the same story. The platform works reasonably well for travel nursing. It manages requisitions, tracks vendors, runs invoices. Then you add locums to the scope, and everything that was manageable becomes complicated.
The requisition workflow does not map cleanly to locums engagement structures. The credential tracking module was not built for medical staff privileging. The scheduling integration does not account for call rotations or subspecialty coverage requirements. The billing module cannot handle agency-specific reimbursement structures for travel, housing, and malpractice. And the reporting that works for travel nursing produces outputs that are not meaningful for a physician coverage program.
This is not a configuration problem. It is an architecture problem. The platforms that manage travel nursing and per diem labor were built for a labor category with standardized workflows, standardized credentials, and standardized billing. Locums is none of those things. Extending a travel nursing platform to cover locums produces a system that handles neither well.
The persistent record advantage
One of the most significant operational advantages of a purpose-built locums platform is the persistence of physician records across engagements. In most current systems, a physician who completes an engagement and then returns to the same facility, or moves to a different facility within the same system, starts the credentialing process largely from scratch.
In Intellify Locums, the credential file, verification record, and privilege history persist across engagements and across facilities within the system. When a physician returns, the re-credentialing process starts from a complete existing file, not from a blank intake form. The steps that need to be updated, license renewals, CME verification, updated peer references, are identified automatically. The steps that are already complete are carried forward. The result is a significantly shorter re-credentialing cycle for returning physicians, the category most likely to be immediately available and immediately trusted by the medical staff.
Locums intelligence is the new competitive advantage
There is a moment in every market's evolution when a category that was managed with general-purpose tools becomes complex enough to demand a dedicated platform. It happened in healthcare revenue cycle with the rise of purpose-built RCM software. It happened in supply chain with healthcare-specific procurement platforms. It is happening right now in locums management, and the organizations that recognize it early will have an advantage that compounds over years, not quarters.
Locum tenens has moved from a niche solution for rural coverage gaps to a structural feature of the physician workforce in nearly every health system. The forces driving this shift, physician shortages, subspecialty maldistribution, the geographic concentration of certain training programs, aging medical staff demographics, are not cyclical. They are secular. Locums is not a gap-fill strategy. It is a permanent component of the physician workforce mix, and it deserves the management infrastructure of a permanent component.
The health systems winning the physician workforce competition are not the ones that are spending less on locums. They are the ones that know exactly what they are spending, and use that intelligence to spend it better.
The competitive advantage in healthcare workforce management is increasingly informational. The question is not whether your organization will invest in locums intelligence. It is whether you will do it before or after the health system across town does.