Specialty RVU benchmarks help translate an annual wRVU target into workload and compensation context. They should not be treated as universal standards. A benchmark is meaningful only when specialty, practice type, ramp-up period, code mix, schedule, support staffing, dollars-per-wRVU rate, and contract terms are visible. RVUinUSA uses specialty benchmark pages as decision support alongside CPT-level RVU data and contract modeling tools.
Benchmarks must be specialty-specific
A raw annual wRVU number has limited meaning without specialty context. A family medicine target and a cardiology target can both be reasonable while sitting at very different numeric levels. Procedure mix, visit mix, call burden, referral access, payer mix, staffing, and patient complexity all affect production. The benchmark should answer whether a target is ordinary, aggressive, or unrealistic for that specialty and practice model.
- Compare targets within the same or closely related specialty.
- Review code mix before judging a productivity number.
- Avoid using one all-physician average for specialty contract review.
Translate the article into a contract model
For compensation review, keep annual wRVU target, threshold, rate, and guarantee language separate before deciding whether the offer is competitive.
- Benchmark
- Specialty percentile
- Risk point
- Threshold
- Review item
- Written terms
Percentiles describe distribution, not fairness by themselves
A median target may be a reasonable starting point for a mature practice, while a 75th or 90th percentile target can require strong volume, efficient workflows, referral access, and support staffing. A high percentile is not automatically unfair, but it needs operational evidence. A low percentile is not automatically favorable if the compensation rate, guarantee, or schedule terms are weak.
- Use the median as context, not as a guarantee.
- Treat 75th percentile targets as aggressive unless support is clear.
- Evaluate compensation rate and threshold together with the percentile.
Connect benchmarks to CPT-level RVU drivers
Specialty production is generated by CPT-level activity. Office visits, procedures, imaging interpretation, hospital services, and ancillary work can all carry different work RVU values. A benchmark page is more useful when it connects annual productivity to the services that generate it. Without code-mix context, a target can look reasonable on paper while being operationally difficult in a specific practice.
- Identify the high-volume CPT codes that drive the specialty.
- Use CPT pages to understand the wRVU contribution of common services.
- Model code mix when comparing service lines or practice settings.
Use benchmarks with compensation terms
Benchmarks do not determine compensation by themselves. The same annual wRVU target can produce different economics depending on base salary, threshold, dollars per wRVU, guarantee duration, collections treatment, draw structure, and termination language. A professional review should model downside, expected, and upside scenarios instead of relying on a single percentile label.
- Compare guaranteed salary against the implied production requirement.
- Review whether productivity pay begins at zero or above a threshold.
- Model compensation at median, 75th percentile, and downside production levels.
New physicians need ramp-up analysis
Residents, fellows, and physicians entering a new market should be especially cautious with annual targets. A mature physician with an established referral base may produce at a level that is not realistic in year one of a new practice. Ramp-up provisions, prorated thresholds, protected base salary, staffing commitments, and referral development should be reviewed before accepting a high target.
- Ask whether the threshold is prorated during ramp-up.
- Ask what volume assumptions support the target.
- Review whether guarantee language protects against early production shortfalls.
Turn benchmark context into a contract model
Start with the specialty page to understand median and percentile context. Then inspect common CPT drivers and use the salary estimator or contract analyzer to model the actual offer. If the question involves Medicare revenue rather than employment compensation, return to CPT and GPCI tools because payment estimates require total RVU, locality, setting, and conversion factor assumptions. A benchmark is strongest when it becomes a transparent model of volume, rate, threshold, and operational support.
- Use specialty pages for annual productivity context.
- Use CPT pages for code-level RVU drivers.
- Use contract tools for thresholds, rates, guarantees, and downside scenarios.