Why Your Current RFP Is Not Actually Screening for the Right Things
Most medical coding vendor RFPs look thorough. They ask about years in business, client count, coder certifications, and whether the vendor carries liability insurance. The vendor fills out the form, returns a polished PDF, and the practice administrator reads through it feeling like due diligence has been done.
Three months into the contract, the cracks appear. Denial rates creep up on a handful of specialty-specific codes. Turnaround times stretch during the vendor's internal staff changes. A payer audit surfaces documentation gaps nobody flagged at onboarding. The relationship that looked solid on paper turns out to have had real weaknesses the RFP never surfaced.
This pattern repeats because generic medical coding vendor RFP questions are easy to answer well without saying anything meaningful. The fix is not a longer questionnaire. It is a more specific one, built around the mechanisms that actually predict vendor performance.
Why Generic Questions Give You Generic Answers
Take two of the most common RFP questions: "What is your coding accuracy rate?" and "Are your coders certified?"
Both sound reasonable. Neither tells you much.
A vendor can truthfully claim a high accuracy rate without specifying whether that figure was measured on a random sample or cherry-picked charts, whether it covers your specialty, how recently it was calculated, and whether "accuracy" means CPT code selection, modifier application, diagnosis sequencing, or all three. Accuracy methodology varies so widely across vendors that two claims of the same percentage can represent completely different realities.
Certification is the same problem. "Our coders are certified" could mean CPC-credentialed generalists coding cardiology procedures they encounter once a month, or it could mean a team with specialty-specific credentials like the CPC-A reviewed by a CCS-P with ten years in the same specialty. The statement is technically true in both cases.
When you evaluate vendors on questions that can be answered confidently without specificity, you end up selecting based on presentation quality and sales skill rather than operational fit. The vendor that sends the most polished proposal wins, even if a less polished competitor would have outperformed them in practice.
Specificity is the antidote.
The Specific RFP Questions That Actually Differentiate Vendors
Accuracy and Quality Assurance
Do not ask whether the vendor has a quality assurance process. Every vendor will say yes. Ask exactly how second-level review works on a typical account.
You want to know: What percentage of charts receive a second-level review, and how is that sample selected? Is it random, risk-stratified by CPT complexity, or triggered by a specific error type? Who performs the review, a senior coder or a supervisor, and how are discrepancies documented and fed back to the original coder? What happens when the reviewer and the original coder disagree?
Ask them to describe what would happen if a coder consistently undercodes E/M visits in the 99213 to 99215 range. A vendor with a real QA process can walk you through a specific remediation workflow. A vendor without one will describe something vague.
Also ask how accuracy is measured for your specific account after go-live, not just company-wide. A meaningful vendor will offer a post-implementation audit at 30 and 60 days. Consider pairing this with an independent coding quality audit so you have a baseline that does not rely solely on the vendor's self-reporting.
Security and Data Handling
Asking whether a vendor will sign a BAA is a floor, not a filter. Every compliant vendor will sign one. The questions that actually differentiate are about operational data handling.
Ask specifically: Where is coding work performed? If the vendor uses offshore coders or a distributed workforce, which jurisdictions are involved? What access controls govern who can view PHI at the chart level, and how are those controls audited? What is the breach notification timeline in their incident response plan, and can they share a redacted version of that plan?
Ask what happens to your data after contract termination. Some vendors retain chart-level data in their systems longer than practices realize, and that is a risk that surfaces well after the relationship ends.
A vendor that handles these questions with specificity has thought through their security posture. A vendor that redirects every security question back to "we are HIPAA compliant" has not.
Specialty Fit
This is the category where the most useful question is also the simplest: ask the vendor to describe a specific coding rule or common edge case in your specialty without prompting from you.
If you run a multi-specialty group that includes gastroenterology, ask the vendor what the distinction is between 43239 and 43249 and under what documentation circumstances you would report 43249 with modifier 52. If you are evaluating a vendor for physician coding (ProFee), ask them how they handle split-shared visits under the 2023 and 2024 guidelines and what documentation they need from the physician to support the billing provider's time claim.
A vendor with genuine specialty depth will answer without hesitation and will likely add a nuance you did not ask about. A generalist vendor will give a correct but surface-level answer, or will ask if they can follow up after consulting their team. Both responses are informative.
Do this for each major specialty in your practice. It takes fifteen minutes per vendor and predicts more about real-world performance than any certifications list.
Transition and Onboarding
Ask for the vendor's actual onboarding timeline, in writing, with specific milestones.
Not "we make transitions easy" or "most clients are fully onboarded within a few weeks." Ask for the week-by-week plan: when does the practice upload its superbill or charge capture workflow for review, when does the vendor complete a payer-mix analysis, when do coders shadow existing charts for calibration, when does live coding begin, and how is a backlog handled if the transition takes longer than planned?
A backlog plan is something many RFPs skip entirely, and it is one of the most predictive questions in the set. Practices that switch vendors almost always accumulate a charge backlog during the transition window. Ask the vendor how they handle a 15-day backlog of charts on day one of go-live. Ask whether they will dedicate additional coder capacity, and whether that capacity is included in the contract or billed separately.
For practices using outpatient coding workflows, ask how the vendor integrates with your EHR for outpatient encounter routing and what happens when a chart is flagged for physician clarification mid-workflow.
Written Answers Beat Verbal Confidence
Sales calls are not a reliable evaluation tool.
A confident presenter can make an unprepared vendor sound strong, and an operationally excellent vendor can come across as understated in a sales conversation. The only way to evaluate consistently is to require written answers to every specific question you care about.
Written specificity matters for a second reason: a vendor that cannot answer a specific operational question in writing is telling you something important. If they respond to "describe your second-level review process for your top three coders on this account" with "we are happy to discuss this on a call," that hesitation is data. Vendors who have built the process describe it easily. Vendors who have not built it prefer to redirect.
Require written responses to all technical questions before any finalist call. Use the call to probe and clarify, not to gather initial information.
Structuring the Evaluation So You Are Comparing the Same Thing Across Vendors
One of the most common ways RFP processes fail is that each vendor ends up being evaluated differently. One vendor gets a detailed follow-up call where the administrator probes their QA process; another submits a strong written response and never gets the same follow-up. At the end of the process, the team is comparing impressions rather than answers.
Standardize the question set. Every vendor gets the same written questions in the same order. Every vendor is scored on the same criteria. If you allow follow-up calls, all finalists get the same questions on that call.
A structured scorecard approach, where each category (QA methodology, specialty fit, security posture, transition planning, references) carries a defined point weight, produces a far more reliable comparison than an unstructured RFP document evaluated by gut feel. Download the free Medical Coding Vendor Evaluation Scorecard to start with a ready-built framework rather than building your own from scratch.
Also weight categories according to your actual risk profile. A practice that recently survived a payer audit should weight security and QA more heavily. A practice that had a traumatic transition from its last vendor should weight onboarding planning at the top.
Reference Checks Are Not a Formality
Most practices check references because it feels like due diligence. The references vendors provide are not random. They are clients who have agreed in advance to speak positively.
Make reference checks specific. Ask the reference contact what the denial rate looked like in the first 90 days. Ask whether the onboarding timeline the vendor quoted matched what actually happened. Ask what the vendor did when something went wrong. Ask whether they would use the same vendor again for a different specialty and why.
If a reference contact cannot answer those questions or deflects to general positives, that is a data point too. For more on the warning signs that appear before and after signing, the post on medical coding company red flags covers the operational signals worth watching.
Knowing What a Vendor Is Worth Before You Start Negotiating
Before you finalize your shortlist, it is worth calculating what improved coding accuracy and denial reduction would actually mean for your revenue cycle. Use the free Coding Outsourcing ROI Calculator to run those numbers against your current volume so you know what performance threshold a new vendor needs to meet to justify the switch.
The RFP process is also a good time to review how to evaluate a coding outsourcing partner from a structural standpoint, including contract terms, SLAs, and exit provisions. The post on how to evaluate a coding outsourcing partner covers those dimensions in detail.
The Bottom Line
Generic medical coding vendor RFP questions produce generic answers that tell you almost nothing about how a vendor will actually perform on your account, in your specialty, after the sales process ends. Replacing vague questions with specific, process-level ones, and requiring written answers before any finalist call, filters out vendors who present well but cannot back it up operationally.
If you want a team that can answer every one of these questions in writing before the first contract conversation, connect with MedCodex to see how our specialty-specific coding approach holds up to your toughest RFP questions.