A monthly wRVU tracker tells you whether your production pace is ahead of, on track with, or behind your annual work RVU target — before the year-end compensation reconciliation locks in a number you can’t easily dispute. It is a planning tool, not a payment calculation, and treating it as anything more precise than that is where most physicians and administrators go wrong.
Why Monthly Tracking Exists Separately From Compensation Calculation
Work RVU (wRVU) is the productivity component of the Medicare RVU system that most physician compensation plans borrow to measure clinical output. It is important to be precise about what wRVU actually represents in this context, because the term gets used two different ways in physician practice:
- Medicare payment RVU — the wRVU published in the CMS Physician Fee Schedule for a given CPT/HCPCS code, used together with Practice Expense (PE) RVU, Malpractice (MP) RVU, the Geographic Practice Cost Index (GPCI), and the Conversion Factor (CF) to calculate what Medicare actually reimburses for a service.
- Compensation-plan wRVU — the same underlying wRVU values, but used by an employer or group solely as a productivity metric, multiplied by an internal compensation rate (dollars per wRVU) set in the physician’s contract.
Monthly tracking is almost always about the second use case. A physician accumulating wRVUs toward an annual production target is not accumulating Medicare payments — the employer has already collected (or will collect) the actual Medicare reimbursement, PE, and MP components separately, and the compensation formula only borrows the work RVU number as a yardstick. Keeping this distinction explicit in your tracker prevents a common misreading: a high monthly wRVU total does not mean a high monthly Medicare payment total, and the two should never be tracked as if they were interchangeable.
Step 1: Establish the Annual Target Correctly
The annual wRVU target should come directly from the signed compensation agreement, the productivity plan, or a documented internal benchmark — not from an assumption or a prior year’s actual production.
Proration matters. If a physician started mid-year, took extended leave, reduced FTE status, or is in a contractual ramp-up period, the stated annual target is usually not the number to track against on a straight 1/12-per-month basis. Track two figures separately:
| Figure | Purpose |
|---|---|
| Contract annual target | The full-year number written into the agreement |
| Adjusted (prorated) target | The target scaled to actual working months/FTE for pace comparison |
Comparing monthly actuals against the unadjusted contract target when a physician was only active for nine of twelve months will make production look artificially behind, which can create unnecessary tension before a compensation review even begins.
Step 2: Record Completed wRVU on a Consistent Schedule
Monthly wRVU entries are only useful if they come from the same source and the same reporting cutoff every time. Mixing a mid-month EHR productivity dashboard pull one month with an end-of-month billing office report the next month introduces noise that looks like a production swing but is really a reporting-timing artifact.
A few practical realities to build into the tracker:
- Charge lag — services performed late in a month may not be coded, billed, and reflected in wRVU totals until the following reporting cycle.
- Coding review delays — if a coder or auditor adjusts a CPT code after initial charge entry, the wRVU value tied to that encounter can change retroactively.
- Employer report cadence — some organizations post official productivity numbers only monthly or quarterly, meaning your internal tracker will run ahead of the “official” figure for part of the cycle.
Label every entry as either estimated (pulled from an internal or provisional source) or final (from the employer’s official productivity report). Never blend the two without a label — a tracker with unlabeled mixed data is functionally unreliable for pace comparison and unusable as documentation if a compensation dispute arises later.
Step 3: Compare Actual Pace to Expected Pace
Once you have a reliable, labeled monthly wRVU total, calculate the pace gap:
Pace Gap = (Actual cumulative wRVU) − (Expected cumulative wRVU at this point in the year)
Expected cumulative wRVU is normally the adjusted annual target divided proportionally by elapsed working time, not simply divided by 12, if the physician’s clinical schedule varies seasonally (for example, heavier surgical scheduling in spring, lighter clinic volume around major holidays).
Illustrative Example (not official CMS data)
Assume a physician’s adjusted annual target is 6,000 wRVU and six months of the contract year have elapsed with no ramp-up or leave adjustment needed.
| Metric | Value |
|---|---|
| Adjusted annual target | 6,000 wRVU |
| Expected cumulative wRVU at month 6 | 3,000 wRVU |
| Actual cumulative wRVU reported | 2,760 wRVU |
| Pace gap | −240 wRVU (≈4% behind expected pace) |
This example is illustrative only — it does not represent an official CMS figure, a specific CPT code’s wRVU value, or any published compensation benchmark. It exists purely to show how the gap calculation works.
A negative gap at the six-month mark is informational, not conclusive. Before drawing any compensation-related conclusion from it, weigh it against:
- Remaining scheduled clinical time — a physician with more high-volume months still ahead may close the gap without any change in effort.
- Known schedule disruptions — vacation, CME time, credentialing delays, or a temporary reduction in OR block time.
- Seasonality patterns specific to the specialty or practice.
- Contract threshold language — some agreements define a minimum production floor only at year-end, meaning a mid-year gap has no compensation consequence unless it persists.
What a Monthly Tracker Cannot Tell You
A wRVU pace tracker measures clinical production volume against a target. It does not calculate:
- The physician’s actual dollar compensation, which depends on the contract’s dollar-per-wRVU rate, any base salary component, and threshold or tiered-bonus structures.
- Medicare reimbursement for the underlying services, which depends on the full RVU components (Work RVU + PE RVU + MP RVU), the locality-specific GPCI adjustment, and that year’s Medicare Conversion Factor — none of which are part of a compensation-tracking exercise.
- Payer-mix effects, since commercial insurers are not required to use Medicare’s RVU-based fee schedule at all, and many negotiate their own rates independent of the Medicare Physician Fee Schedule.
For the compensation-dollar side of the calculation, use a dedicated salary calculator once the wRVU total for the period is confirmed as final. For benchmarking whether a given wRVU pace is typical for a specialty, cross-reference the physician productivity benchmarks reference rather than relying on the raw pace gap alone.
Building a Practical Monthly Tracker
A functional tracker needs only a few consistent fields, but each one should be treated as mandatory rather than optional:
- Reporting period (calendar month, with cutoff date noted)
- Data source (EHR dashboard, coding department report, employer official statement)
- Status label (estimated or final)
- Monthly wRVU total and cumulative wRVU total
- Expected cumulative wRVU for that point in the year (adjusted for proration/schedule if applicable)
- Pace gap (actual minus expected, shown as both raw number and percentage)
Reviewing this against remaining months well before year-end — rather than waiting for the final reconciliation — gives both the physician and the practice manager time to address a genuine shortfall (or confirm that an apparent shortfall is just a timing artifact) before it becomes a compensation surprise.
For anyone still building intuition around how work RVU fits into the broader Medicare payment structure — including how the same CPT code’s wRVU interacts with PE RVU, MP RVU, GPCI, and the Conversion Factor to produce an actual Medicare payment amount — it’s worth reviewing that calculation separately from any internal compensation tracking, since the two systems share a number (wRVU) but serve entirely different purposes.