A physician productivity tracker turns a contract offer’s production language — annual work RVU (wRVU) target, base salary, dollars per wRVU, and threshold timing — into a set of numbers you can actually model and compare against specialty benchmarks. This is a compensation modeling exercise, not a Medicare payment calculation, and treating the two as interchangeable is the single most common mistake in reviewing a productivity-based offer.
wRVU Is a Compensation Metric, Not a Payment Amount
Work RVU is one of three components CMS uses inside the Medicare Physician Fee Schedule (MPFS) to calculate reimbursement for a CPT or HCPCS code. The other two are Practice Expense (PE) RVU and Malpractice (MP) RVU. Medicare payment for a specific code is calculated roughly as:
Medicare Payment ≈ [(Work RVU × Work GPCI) + (PE RVU × PE GPCI) + (MP RVU × MP GPCI)] × Conversion Factor
For CY 2026, CMS finalized two separate conversion factors under statutory requirements: $33.57 for physicians and practitioners who qualify as participants in an Advanced Alternative Payment Model (APM), and $33.40 for non-qualifying participants — both up from the CY 2025 conversion factor of $32.35. That figure applies only to Medicare fee-for-service claims, and it says nothing about what an employer pays a physician per wRVU produced.
wRVU-based physician compensation is a separate, employer-defined arrangement. A hospital or group sets its own “dollars per wRVU” conversion rate — often benchmarked to survey data such as MGMA — and pays physicians against that rate once production crosses a threshold. Two employers can offer identical annual wRVU targets with very different compensation outcomes because the dollar-per-wRVU rate, threshold, and guarantee structure are negotiated terms, not CMS-set values. If you want to see how a specific CPT code’s work RVU translates into Medicare payment, use a CPT RVU calculator rather than a compensation model.
Core Inputs for a Productivity Tracker
Before judging whether a wRVU target is reasonable, isolate these inputs and keep them visible together rather than folded into a single “salary” number:
| Input | What It Represents |
|---|---|
| Annual wRVU target | Production goal the physician is expected to reach |
| Base salary | Guaranteed pay independent of production, if any |
| Dollars per wRVU | Employer-set conversion rate for incentive compensation |
| Threshold | wRVU level where incentive pay begins accruing |
| Guarantee period | Time window where salary is protected regardless of production |
| Repayment terms | Whether shortfalls during the guarantee must be paid back |
| RVU source year | The year of the wRVU data or benchmark used for the target |
| Specialty benchmark | Percentile data (25th, 50th, 75th, 90th) for comparable physicians |
Recording the RVU source year matters because CMS updates the work RVU values for many CPT codes annually through the MPFS rulemaking cycle, and specialty benchmark surveys (such as MGMA) are also published on an annual cadence. A wRVU target that looked aggressive against 2023 benchmark data may look average against more recent survey data, or vice versa.
Modeling the Compensation, Step by Step
A basic wRVU compensation model — separate from any Medicare RVU formula — works like this:
Estimated incentive compensation = (Actual wRVU − Threshold) × Dollars per wRVU
Illustrative example (not an official rate): suppose a physician has a base salary of $220,000, a threshold of 4,800 wRVU, and a compensation rate of $45 per wRVU above threshold. If the physician produces 6,000 wRVU in the year:
- wRVU above threshold = 6,000 − 4,800 = 1,200
- Incentive pay = 1,200 × $45 = $54,000
- Total modeled compensation = $220,000 base + $54,000 incentive = $274,000
This is purely a contract math exercise. It does not tell you what Medicare paid for the underlying claims, and it doesn’t account for non-wRVU revenue components some plans include (quality bonuses, call pay, or administrative stipends). A wRVU calculator can run this math across multiple production scenarios so you can see compensation at, for example, the 25th, 50th, and 75th percentile of production rather than a single point estimate.
Comparing the Target Against Specialty Benchmarks
An annual wRVU target only means something in context. A 7,000 wRVU target is unremarkable for some surgical specialties and aggressive for many primary care roles. Specialty compensation surveys report wRVU production by percentile, and the productivity tracker workflow should place the offered target on that distribution before calling it reasonable:
| Benchmark Percentile | What It Signals |
|---|---|
| 25th percentile | Below-median production; may reflect part-time, ramp-up, or lower-volume practice |
| 50th percentile (median) | Typical production for the specialty and setting |
| 75th percentile | High production; often used as an aspirational contract target |
| 90th percentile | Top-tier production; targets set here can be difficult to sustain long-term |
If an offer sets the annual wRVU target at or above the 75th percentile for the specialty, that alone doesn’t make the offer bad — but it does mean the threshold, ramp-up protection, and repayment terms deserve closer scrutiny, since reaching a high percentile target consistently is harder than reaching a median one. Compare the offered target against a specialty benchmark tool using the same source year as the compensation numbers in the contract.
Threshold Timing and Ramp-Up Protection
Threshold timing determines when incentive compensation actually starts accruing, and it’s frequently where offers diverge even when the headline wRVU target and dollar-per-wRVU rate look similar. Key questions to resolve before modeling compensation:
- Does the threshold apply monthly, quarterly, or annually? A monthly threshold can penalize normal month-to-month variation in patient volume.
- Is there a ramp-up period where the threshold is lowered or waived while the physician builds a patient panel?
- Is the base salary during the guarantee period a true guarantee, or a recoverable draw that must be repaid from future incentive earnings if production falls short?
- What happens at the end of the guarantee period — does the physician convert to pure productivity pay, or does a new base apply?
A recoverable draw changes the risk profile of an offer substantially compared to a non-recoverable guarantee, even if both are described in a term sheet as a “$220,000 base salary.”
Where This Differs From a Medicare Payment Estimate
It’s worth restating the boundary explicitly, because productivity tracker content is often confused with Medicare reimbursement estimation:
| Question | Tool/Concept to Use |
|---|---|
| What did Medicare pay for a specific CPT code in a given locality? | Medicare reimbursement calculator using CPT RVU components, GPCI, and the applicable conversion factor |
| How much does a physician get paid per wRVU produced under an employment contract? | Productivity tracker / wRVU compensation model using employer-set dollars-per-wRVU rate |
| How does a physician’s total RVU compare to specialty peers? | Specialty benchmark comparison by percentile |
| How does GPCI change payment for the same CPT code in different cities? | GPCI calculator |
Confusing these four questions is how RVU content ends up telling a physician they’ll “earn $33.40 per wRVU” — that figure is a 2026 non-qualifying APM Medicare conversion factor applied to total RVU for fee-for-service billing, not an employer compensation rate, and the two numbers have no fixed relationship to each other.
Applying This to a Contract Review
A structured review of a productivity-based offer follows a consistent sequence: pull the annual wRVU target, base salary, threshold, dollars-per-wRVU rate, and guarantee terms directly from the written offer; run those numbers through a productivity tracker at two or three production scenarios (threshold, median, and 75th percentile production); compare the target itself against specialty benchmark data from the same or adjacent survey year; and only then read the guarantee, repayment, termination, and restrictive covenant language as a separate legal review step.
Numeric modeling can surface red flags — an unusually high target relative to specialty benchmarks, a threshold set close to the target itself, or a base salary structured as a recoverable draw — but it cannot substitute for legal review of the signed agreement. The productivity tracker output tells you what the numbers mean under stated assumptions; whether those contractual terms are enforceable, negotiable, or standard for the specialty and region requires review by someone qualified to assess the written contract itself.