wRVU Productivity Tracker

A physician’s productivity contract almost never states pay in dollars alone — it states pay in work RVUs (wRVUs), the physician-effort component of the Medicare Resource-Based Relative Value Scale (RBRVS). Tracking wRVU output against an annual target, a monthly pace, and a compensation threshold is the core job of a wRVU Productivity Tracker, and getting the numbers right requires understanding where wRVUs come from and how CMS turns them into payment.

What a wRVU Actually Represents

Every CPT/HCPCS code on the Medicare Physician Fee Schedule (MPFS) carries three separate relative value components: physician work RVU, practice expense (PE) RVU, and malpractice (MP) RVU. Only the work RVU measures the physician’s own time, technical skill, mental effort, and judgment — it is the figure most employment and productivity-bonus contracts use because it strips out overhead and liability costs that vary by setting and specialty. Work RVU is identical whether the service is performed in a facility or non-facility setting, which is why it is the standard currency for internal productivity tracking even though PE RVU can swing 50–70% lower in facility settings for the same code.

For context, a routine established-patient visit, CPT 99213, carries roughly 1.30 wRVUs; a moderate-complexity 99214 carries 1.92 wRVUs; and a high-complexity 99215 carries about 2.80 wRVUs. This is why the tracker’s “average wRVU per visit” input (1.5 in the example above) is a blended assumption across a typical E/M mix rather than a single code value — most primary care and specialty clinics run a case mix weighted toward 99213–99214 level visits.

From wRVU to Actual Medicare Payment

wRVU only becomes a dollar amount once it is combined with the other two RVU components, adjusted for local cost of living, and multiplied by the annual conversion factor (CF):

\(\text{Payment} = (\text{wRVU} \times \text{GPCI}_{work} + \text{PE RVU} \times \text{GPCI}_{pe} + \text{MP RVU} \times \text{GPCI}_{mp}) \times \text{CF}\)

The Geographic Practice Cost Index (GPCI) adjusts each of the three RVU components separately for local wage, rent, and malpractice-cost differences; a locality with a work GPCI of 1.000 (the statutory floor) pays the code at its full national work value, while high-cost metro localities can carry work GPCIs above 1.10. For CY 2026, CMS finalized two separate conversion factors for the first time under MACRA: $33.5675 for clinicians in a Qualifying Alternative Payment Model (QP) and $33.4009 for non-QP clinicians, up 3.77% and 3.26% respectively from the CY 2025 CF of $32.3465. That increase reflects a statutory 2.5% update from the 2025 reconciliation legislation plus roughly a 0.49% budget-neutrality adjustment for redistributed work RVU changes.

This matters for a productivity tracker even though the tool itself only tracks wRVU counts, not dollars: because wRVU is the metric independent of the CF and GPCI, it is the fair, portable unit for comparing productivity across locations and time periods — the compensation conversation ($/wRVU rate) is a separate negotiation layered on top of the raw wRVU count.

Reading the Tracker’s Core Inputs

• Annual target wRVU — the yearly production goal set in the employment or partnership agreement, often benchmarked against MGMA percentile data for the specialty.
• Monthly production — actual wRVUs logged each month; entering fewer than 12 values (zeros for future months) lets the tracker calculate pace-to-date rather than assuming a flat year.
• Daily clinic volume / working days per month / average wRVU per visit — these three assumptions reconstruct a theoretical monthly capacity (visits × wRVU-per-visit × working days) that the tracker can compare against actual reported production.
• Contract threshold — a separate, usually lower, wRVU floor tied to a specific compensation trigger: many employment models pay a base salary guarantee up to a threshold, then a per-wRVU incentive bonus above it, or conversely require a minimum wRVU floor to retain full base pay. MGMA’s compensation surveys are the standard reference for setting this figure, since national data show primary care median wRVUs clustering around 4,500–6,000 annually, while surgical and procedural specialties often reach 7,000–10,000+ per year.

Calculation Logic Walked Through

Using the inputs given — annual target 7,200 wRVU, monthly entries of 520, 540, 590, 610, 585, 620 (six completed months, six months still at zero), a 6,500 wRVU contract threshold, 18 visits/day, 18 working days/month, and 1.5 wRVU/visit — the tracker runs through the following sequence:

1. Completed wRVU = sum of all non-zero monthly entries = 520+540+590+610+585+620 = 3,465 wRVU, across 6 reporting months.
2. Monthly target = annual target ÷ 12 = 7,200 ÷ 12 = 600 wRVU/month.
3. Expected through current month = monthly target × months elapsed = 600 × 6 = 3,600 wRVU.
4. Variance = completed − expected = 3,465 − 3,600 = −135 wRVU, meaning production is running slightly behind the flat-line pace.
5. Forecast monthly wRVU = completed ÷ months reported = 3,465 ÷ 6 = 577.5 wRVU.
6. Annualized pace / forecast annual wRVU = forecast monthly × 12 = 577.5 × 12 = 6,930 wRVU.
7. Target progress % = completed ÷ annual target = 3,465 ÷ 7,200 ≈ 48.1%.
8. Year-end gap = forecast annual − annual target = 6,930 − 7,200 = −270 wRVU, a shortfall if the current run-rate holds.
9. Threshold gap = forecast annual − contract threshold = 6,930 − 6,500 = +430 wRVU, meaning the physician is still on pace to clear the contract’s minimum threshold even while falling short of the stretch target.
10. Remaining target = annual target − completed = 7,200 − 3,465 = 3,735 wRVU, over 6 remaining months.
11. Required monthly wRVU to hit the annual target = 3,735 ÷ 6 = 622.5 wRVU/month.
12. Required daily wRVU = required monthly ÷ working days = 622.5 ÷ 18 ≈ 34.6 wRVU/day.
13. Required visits/day = required daily wRVU ÷ average wRVU per visit = 34.6 ÷ 1.5 ≈ 23.1 visits/day, versus the 18 visits/day currently assumed — a roughly 28% volume increase needed to close the gap.

This sequence is why the “quota status” flag reads as behind: the physician clears the compensation-safety threshold comfortably but needs a meaningful volume increase — either more visits per day or a higher-acuity case mix pushing average wRVU per visit above 1.5 — to reach the full annual target.

Applying This to Contract and Coding Decisions

For a practice manager, the threshold gap is the number that drives payroll risk: a physician tracking above the contract threshold but below the stretch target usually still earns base pay plus partial incentive, while falling below the threshold itself can trigger a compensation review clause. For a coder or biller, the monthly wRVU trend is a useful cross-check against claims data — if reported wRVU consistently lags what the E/M code mix should produce (for example, a practice coding mostly 99214s at 1.92 wRVU each should generate more monthly wRVU than one under-coding at the 99213 level), it often signals documentation or coding-level issues rather than a genuine productivity shortfall. Comparing the required-visits-per-day figure against actual scheduling capacity is also the fastest sanity check on whether a stated annual target was realistic in the first place, given the practice’s real average wRVU per visit and working-day calendar.