Here's the myth: if you're productive, RVU pay will automatically beat per diem. Sounds clean. Sounds merit-based. It's also wrong often enough to cost physicians real money.
RVU-based locums are usually sold as "fair." You eat what you kill. More work, more pay. Per diem, by contrast, gets dismissed as blunt and old-school: show up, work the shift, collect the rate. But the business logic of these models is completely different, and that difference matters more than most clinicians realize. RVUs don't just change compensation. They change who carries the risk when volume drops, documentation gets challenged, payer mix turns ugly, or the schedule falls apart.
Plain English version: per diem pays you for your time and coverage. RVU pay tries to pay you for output. The trap is assuming output is simple to count and impossible to manipulate. It isn't. Specialty mix, coding intensity, payer behavior, site efficiency, no-shows, chart completion rules, and contract language all get a vote.
This article is for educational purposes only, not financial, legal, or tax advice. Contract terms, compensation formulas, coding rules, and actual outcomes vary widely by specialty, state, and site, so run any deal past qualified legal and financial professionals before you sign.
Will RVU Locums Beat Per Diem? The Myth: "More productivity = always more money."
The sales pitch for RVU locums is seductive because it flatters you. You're efficient. You work hard. Why shouldn't you get paid for that? Fair question. Bad assumption.
I've seen physicians take an RVU contract expecting upside, only to discover they'd basically accepted a variable-pay job with hidden penalties and no protection against low-volume days. Meanwhile the "boring" per diem doc in the next room made the same money whether the schedule was full, half-empty, or a dumpster fire.
The best model isn't universal. It depends on what you actually do all day. Procedures versus cognitive work. Stable clinic flow versus chaos. High-acuity patients versus quick follow-ups. Clean documentation systems versus EHR sludge. If your specialty has predictable throughput, standardized coding, and a site that actually knows how to support billing, RVUs can work beautifully. If not, they can backfire fast.
That's the point most people miss: RVU pay is not just compensation. It is risk transfer. Sometimes you're being paid for productivity. Sometimes you're being handed the downside of operational dysfunction and being told it's "performance-based."
The Pay Mechanics: How RVUs Actually Translate Into Net Pay (and Where the Gotchas Hide)
An RVU contract sounds simple until you read the actual terms. Then the weeds show up.
First, ask what kind of RVU you're being paid on. Usually it's work RVUs, not total RVUs. That matters. Work RVUs reflect physician effort. Total RVUs may include practice expense and malpractice components. If a recruiter says "RVU-based" and can't immediately tell you whether it's wRVU or tRVU, that's not a harmless detail. That's a warning sign.
Next comes the conversion factor. That's the multiplier applied to your RVUs to determine compensation. Fine. But then the fine print starts doing its thing. Are modifiers applied before or after reconciliation? Is there a threshold before RVUs start counting? Is there a floor? A cap? A quality withhold? Is compensation based on submitted charges, coded charges, or adjudicated claims? Those are not accounting trivia questions. They decide whether your "high productivity" turns into actual money.
Then there's professional versus technical component confusion. Most locums physicians are being paid on the professional side only, but some organizations speak loosely enough to make comparisons misleading. You can't compare one RVU offer to another unless the definitions match.
And now the really common gotchas. Who is responsible for coding? You? Central billing? A stressed clinic manager who also handles prior auths and printer toner? If the site undercodes, delays charge entry, or rejects incomplete documentation, your pay can fall for reasons that have nothing to do with your clinical output. Some contracts also allow post hoc reconciliation after audits. Translation: you got paid, then they decide later that your documentation didn't support all the billed work, and suddenly your paycheck gets "adjusted." Funny how the risk of that adjustment rarely flows the other direction.
Per diem isn't perfect. Plenty of per diem deals bury productivity expectations unofficially. You may be expected to move a certain number of patients, cover call, finish inbox work, or absorb canceled slots without extra pay. But at least the math is usually legible. Show up, work the agreed shift, get the agreed rate. Predictability has value. A lot of value.
What the Data Actually Says About "Earning More with RVUs": Volume, Risk, and Incentives
The lazy story is that RVUs reward hard workers. The data-driven story is uglier: RVUs reward billable output under a specific documentation, coding, and payer environment. That's not the same thing.
If volume is high and stable, RVU pay can beat per diem. Obvious. But that upside is often overstated because real contracts rarely function as clean linear equations. Caps flatten earnings. Documentation defects down-rate claims. Delayed coding delays pay. Site inefficiency destroys throughput. And if your patient mix shifts toward visits that are time-consuming but RVU-light, your hourly effective rate drops while your day gets worse. Brutal combination.
Case mix matters too. A physician can work extremely hard and generate fewer RVUs simply because the schedule is full of lower-complexity follow-ups, no-shows, counseling-heavy visits, or services that are clinically demanding but not especially lucrative in RVU terms. The spreadsheet doesn't care how exhausting the day felt.
Then come the incentive distortions. This is where people get weirdly sentimental about productivity pay, as if incentives never shape behavior. They do. RVU-heavy systems can push faster throughput, shorter visits, preference for better-coded encounters, and subtle cherry-picking of schedules. Not because physicians are villains. Because contracts work exactly as designed. If the system rewards velocity and coding intensity, don't act shocked when velocity and coding intensity rise.
That can increase denial risk, audit exposure, and friction with sites that wanted both "high productivity" and immaculate compliance without investing in support. I've watched this movie before: enthusiastic launch, a few great months, then complaints about chart quality, coding variance, missed add-ons, or "unexpected compensation trends." Suddenly the contract that was sold as aligned incentives turns into a dispute over whose spreadsheet is holy.
Specialty Matters: Where RVU Contracts Likely Win (and Where They Commonly Backfire)
Specialty is destiny here. Not completely, but close.
RVU contracts tend to work better in procedural or high-standardization environments. Think settings where visit types are predictable, coding patterns are stable, documentation is straightforward, and the site can reliably feed you volume. In those situations, RVU compensation may genuinely reflect output. You do more. You bill more. You get paid more. Fine.
They get shakier in cognitive-heavy fields, in clinics with inconsistent support, and in any environment where your day depends on messy human reality. Time-based counseling. Complex family meetings. Care coordination. Unreliable rooming. Frequent add-on tasks. EHR friction. These don't always translate cleanly into RVU upside, but they absolutely consume your time.
Emergency medicine, hospital-based coverage, and some inpatient consult work can go either way depending on flow and staffing. A packed board doesn't guarantee efficient RVU generation if nursing is thin, beds are blocked, or documentation requirements balloon. Primary care and pediatrics often look decent on paper until no-shows, portal work, refill burden, and unpaid admin time eat the day alive. Surgery or procedural subspecialties may do better under RVUs if block time, case mix, and coding support are stable. If not, even proceduralists can get trapped in a "high effort, low realized pay" setup.
The myth is that RVU deals favor the industrious. The reality is they favor the industrious physician working in a well-oiled system. Big difference.
The Contract Checklist: 12 Questions to Protect Your Pay Under RVU-Based Locums
Here's the contrarian rule: don't negotiate the upside first. Negotiate the failure modes. Anyone can make an RVU contract look pretty at expected volume. What matters is what happens when reality shows up.
Ask these questions, directly, and don't accept hand-waving.
First, what exact RVU metric is used: wRVU or tRVU? Second, what is the conversion factor, and can it change during the term? Third, are there caps, floors, thresholds, or minimum guarantees? Fourth, how often is pay reconciled, weekly, monthly, quarterly? Long lag times are not neutral; they finance the employer with your labor.
Fifth, what counts as an RVU for payment purposes: billed, coded, submitted, or paid? Sixth, who owns coding responsibility and who eats the loss if charts are down-coded or denied? Seventh, what documentation deadlines apply, and what happens if a chart is late because the site's EHR crashed or the shift ran over? Eighth, is there an audit process, and can prior compensation be clawed back after review?
Ninth, how are no-shows, cancellations, template gaps, and low census handled? If the site controls the schedule and you bear the volume risk, that's a bad deal. Tenth, is call coverage included, and is admin time paid separately or silently absorbed? Eleventh, are quality withholds, denials, or payer adjustments used to reduce compensation? If yes, define every trigger. Twelfth, what are the exit terms? Termination for convenience, dispute timelines, and treatment of unresolved coding issues matter more than people think.
You also need the operational truth, not the brochure version. Ask how many patients the last three locums actually saw. Ask how long charts remain open. Ask who enters charges. Ask what percentage of work gets re-coded. Ask whether APP supervision, inbox cleanup, or hospital committee nonsense lands on your plate without compensation. I've seen physicians agree to "productivity pay" and then spend unpaid hours fixing templates, answering messages, and cleaning up charting backlog. That's not productivity pay. That's unpaid labor with a motivational slogan taped on top.
Decision Framework: A Practical Rule to Choose RVU vs Per Diem Before You Sign
Here's the practical rule I'd use: compare the per diem offer not to your best-case RVU projection, but to your conservative RVU scenario after friction. Real friction. No-shows. Slower onboarding. Incomplete templates. Coding lag. Audit risk. Lower-than-promised volume. If RVUs still win after that haircut, now we're talking.
Estimate your likely RVUs per shift using a realistic range, not recruiter fantasy. Then model three scenarios: expected volume, low-volume month, and ugly month. If the RVU deal loses badly in the ugly month and the contract has no meaningful floor, per diem is often the smarter choice even if the headline ceiling is lower.
The smartest physicians I know don't chase the highest theoretical pay. They chase the best expected value with the least nonsense attached. That's not timid. That's adult math.
Bottom Line Summary: When RVU Locums Deliver, and When They Backfire
RVUs are not a magic money printer. They are a compensation structure that can either reward efficient clinical work or dump operational and documentation risk onto you wearing a "performance-based" badge.
RVU locums usually deliver when volume is stable, workflows are standardized, coding support is competent, contract definitions are explicit, and audit or down-rating risk is tightly controlled. They backfire when caps sit below realistic output, documentation rules are vague, admin work is unpaid, scheduling is volatile, and the employer controls volume while you absorb the downside.
So no, more productivity does not always mean more money. Sometimes it means more work, more charting, more disputes, and less pay than the supposedly boring per diem contract. Fact beats fiction. Read the guardrails, not the headline.
