A high annual wRVU target isn’t automatically a bad offer, and a low dollars-per-wRVU rate isn’t automatically a good one — the red flag only shows up when you separate the production assumption (the wRVU target) from the compensation term (base salary, threshold, $/wRVU rate, and guarantee period) and model them together. Most contract disputes in physician employment trace back to one of those variables being reviewed in isolation.
The Variables That Actually Drive the Offer
Before judging any wRVU-based offer, six inputs need to sit on the same page. Changing any one of them changes the effective value of the contract, even if the headline number stays the same.
| Input | What It Controls |
|---|---|
| Annual wRVU target | The production level the employer expects, usually tied to a specialty percentile |
| Base salary | Fixed pay, often guaranteed for a defined ramp-up period |
| Dollars per wRVU ($/wRVU) | The conversion rate the employer pays for production above threshold |
| Threshold | The wRVU level at which incentive pay begins accruing |
| Guarantee period | How long base salary is protected regardless of production |
| RVU source year | The wRVU dataset and specialty benchmark year the target is compared against |
If a contract omits any of these, or defines them loosely (“competitive market rate,” “to be determined annually”), that ambiguity is itself a red flag, independent of the numbers.
Red Flag 1: Annual wRVU Target Set Above Specialty Benchmarks
Work RVU (wRVU) measures the physician-work component of a CPT-coded service and is the productivity unit most employment contracts use for incentive compensation. It is not the same figure CMS uses to pay a Medicare claim — more on that distinction below.
Specialty compensation surveys (MGMA, AMGA, and Sullivan Cotter are the most commonly cited) publish annual wRVU percentiles by specialty. A target set near or above the 75th percentile for the specialty, without a corresponding base salary or $/wRVU rate that reflects that percentile, means the physician is being asked to produce at a top-quartile level for median-level pay. That mismatch is the red flag — not the raw target number by itself.
To evaluate this correctly:
- Identify the specialty and the survey year the target is being compared against.
- Compare the target to the 25th, median, and 75th percentile wRVU for that specialty and survey year.
- Check whether base salary and $/wRVU scale with the percentile the target sits at.
A pediatric cardiologist offered a target near the 90th percentile of national wRVU benchmarks, paired with a base salary set at the median for the specialty, is being underpaid relative to the production being asked of them — even if the base salary number looks reasonable in isolation.
Red Flag 2: Dollars-per-wRVU Rate Below Market
The $/wRVU rate determines how much incremental pay a physician earns for production above threshold. This rate is set by the employer or group and is negotiated separately from Medicare’s own payment rates — a distinction that matters because these two numbers are frequently, and incorrectly, treated as if they’re linked.
wRVU Compensation vs. Medicare RVU-Based Payment
| wRVU Compensation | Medicare RVU-Based Payment | |
|---|---|---|
| Who sets the rate | Employer, group, or health system | CMS, via the Medicare Physician Fee Schedule (MPFS) |
| Formula | wRVU × negotiated $/wRVU rate | (Work RVU + Practice Expense RVU + Malpractice RVU), each geographically adjusted (GPCI), × Conversion Factor (CF) |
| What it reflects | Internal compensation policy, market benchmarks, group finances | CMS payment policy for a specific CPT/HCPCS code, locality, and year |
| Where it appears | Employment or partnership agreements | Medicare claims and remittance data |
A physician earning $45 per wRVU under an employment contract is not receiving $45 because Medicare “pays” $45 per work RVU. Medicare’s actual reimbursement for a given CPT code depends on all three RVU components — work, practice expense, and malpractice — each adjusted by the Geographic Practice Cost Index (GPCI) for the service locality, then multiplied by the applicable conversion factor for that calendar year. For CY 2026, CMS finalized two separate conversion factors under statute: $33.57 for qualifying Alternative Payment Model (APM) participants and $33.40 for non-qualifying physicians and practitioners, both up from the CY 2025 conversion factor of $32.35. Neither of those figures has any direct relationship to the $/wRVU rate an employer sets in a compensation plan — the two systems are calculated independently and serve different purposes.
When reviewing a contract, check the $/wRVU rate against specialty-specific compensation survey data for the same year, not against Medicare conversion factor movement. A rate that hasn’t been adjusted in several contract cycles, while specialty benchmarks have moved, is the actual red flag — not the raw dollar figure alone.
Red Flag 3: Guarantee Language That Isn’t a True Guarantee
A “guaranteed” base salary is only a guarantee if the contract says the amount is non-recoverable. Many offers instead describe a draw against future production, meaning any base salary paid above what the physician’s wRVU production and $/wRVU rate would have earned is owed back to the employer — either immediately or at contract termination.
Questions the contract should answer explicitly:
- Is the base salary a true guarantee (non-repayable) or a recoverable draw?
- How long does the ramp-up or guarantee period last, and what production level is expected by the end of it?
- What happens to any accrued deficit if the physician resigns, is terminated without cause, or the contract isn’t renewed?
- Is there a repayment schedule, and does it apply pro-rata or as a lump sum?
Missing or vague language on any of these points shifts financial risk onto the physician without them realizing it until the guarantee period ends.
Building the Comparison: A Worked Example
Assume a hypothetical offer with the following illustrative terms (not official CMS or survey data):
- Annual wRVU target: 6,500
- Base salary: $260,000
- Threshold: 5,800 wRVU
- $/wRVU rate above threshold: $40
If the physician produces exactly at target:
\(\text{Incentive wRVUs} = 6{,}500 – 5{,}800 = 700\)
\(\text{Incentive Pay} = 700 \times $40 = $28{,}000\)
\(\text{Total Compensation} = $260{,}000 + $28{,}000 = $288{,}000\)
Now model the same contract at 90% and 110% of target to see how sensitive total compensation is to production shortfalls or overages — this is the step most physicians skip, and it’s where the real red flag often becomes visible: a target set high enough that missing it by even 10% triggers a shortfall against an implied “expected” income the base salary doesn’t actually cover.
| Production Level | wRVU Produced | Incentive wRVU | Incentive Pay | Total Compensation |
|---|---|---|---|---|
| 90% of target | 5,850 | 50 | $2,000 | $262,000 |
| 100% of target | 6,500 | 700 | $28,000 | $288,000 |
| 110% of target | 7,150 | 1,350 | $54,000 | $314,000 |
Running this comparison at multiple production levels, rather than accepting the employer’s single projected figure, is the core function of a contract analyzer workflow — RVUinUSA’s contract analyzer is built for exactly this step, letting you hold the base salary, threshold, and $/wRVU rate constant while varying production to see the real range of outcomes.
Other Contract Terms That Compound These Red Flags
Numeric red flags rarely exist alone. The written agreement should be reviewed for terms that affect the value of the compensation model regardless of production:
- Repayment clauses tied to signing bonuses, relocation assistance, or loan forgiveness, including vesting schedules.
- Termination language specifying notice periods and whether unearned guarantee amounts are forgiven or clawed back.
- Restrictive covenants (non-competes, non-solicits) that could limit the physician’s options if the compensation model underperforms.
- Benefit terms, including retirement contributions and CME allowances, which are sometimes reduced to offset a higher-looking base salary.
None of these are RVU calculations — they’re legal and contractual terms that determine whether a favorable-looking compensation model is actually enforceable in the physician’s favor.
Putting the Workflow Together
The practical sequence for reviewing an offer is to first confirm the specialty, wRVU target, and survey year being cited, then check that target against current specialty benchmark percentiles, then model total compensation across a range of production scenarios using the base salary, threshold, and $/wRVU rate, and only then read the written agreement for guarantee, repayment, and termination language. A resident or fellow comparing two offers should run this same set of assumptions for each offer separately rather than comparing headline numbers side by side, since a higher base salary with a higher threshold and lower $/wRVU rate can produce less total compensation than a lower base salary with a more favorable rate structure.
For a deeper walkthrough of how to structure this review end to end, see RVUinUSA’s contract red flags guide, which pairs directly with the contract analyzer for scenario modeling.
What This Analysis Cannot Determine
A numeric compensation model tells you how a contract’s production and pay terms interact — it does not tell you whether the contract is legally sound, whether the non-compete is enforceable in your state, or whether the guarantee language will hold up in a dispute. It also does not estimate what Medicare or any commercial payer will actually reimburse for the underlying CPT codes; that calculation depends on the specific codes billed, the site of service, the GPCI locality, and the calendar year’s conversion factor, which is a separate question from what the employer pays per wRVU. Treat the numeric red-flag review as the first pass that tells you which clauses in the written agreement need a qualified employment attorney’s review, not as a substitute for that review.