Most problems with a background screening RFP trace back to a handful of drafting mistakes made before the solicitation was ever published, not to anything a vendor did wrong in its response. A vague scope of work, unweighted evaluation criteria, blended pricing requests, and stale boilerplate each produce a specific, predictable failure once bids come in: an unusable Q&A cycle, incomparable proposals, or a contract that has to be renegotiated within a year of signing. The seven mistakes below recur across public-sector and enterprise screening solicitations alike, and each has a specific, low-effort fix.
Key Takeaways
- A vague scope of work doesn’t get discovered until the Q&A period, when vendors ask the questions the RFP should have already answered.
- Evaluation criteria that aren’t weighted before proposals open produce a selection that’s hard to defend if a losing bidder challenges the outcome.
- Requesting a single blended price instead of itemized pricing makes bids look comparable when they aren’t.
- Requesting a single blanket turnaround figure instead of per-search-type turnaround hides which searches will actually cause hiring delays.
- Asking for base-term pricing only, with no required option-year quote, leaves renewal-year cost to be negotiated after the buyer has already lost most of its leverage.
- Recycling an old RFP without updating stale references (outdated accreditation names, no acknowledgment of modern delivery methods) signals to vendors that the buyer hasn’t looked closely at its own requirements, and invites generic, low-effort responses in return.
Mistake 1: Leaving the scope of work too vague to bid against
The single most common failure in a background screening RFP is a scope of work that describes services in general terms, “criminal background checks,” “employment verification”, without specifying the parameters that actually determine cost and turnaround. At minimum, a scope of work should state:
- Which jurisdictions are in scope for each search type
- What lookback period applies (and to which search types specifically)
- How many employers or references are verified per candidate before additional ones are billed separately
- Whether continuous monitoring is in scope now, or a future add-on
The real cost of leaving these unspecified shows up during the Q&A period. A hospital system’s RFP addendum, issued after vendors asked for clarification because the original scope didn’t specify these parameters, illustrates exactly this failure: the buyer had to backfill, mid-process, questions like how many years back employment verification should reach, how many employers to verify per candidate before additional employers are billed separately, and whether the request covered pre-hire screening only or also ongoing monitoring. Every one of those clarifying questions is evidence of a drafting gap, not a vendor being difficult. A scope of work that specifies these parameters up front eliminates an entire round of Q&A traffic and produces bids that are actually responsive to what the buyer needs, rather than bids built on each vendor’s own guess about what was meant.
Mistake 2: Publishing evaluation criteria with no weights, or no evaluation criteria at all
An RFP that says proposals will be evaluated on “qualifications, cost, and experience” without stating how much each factor counts is not really publishing evaluation criteria, it’s publishing a list of things the committee might think about. Unweighted criteria let an evaluation committee justify almost any outcome after the fact, which is exactly the vulnerability a losing bidder will target if it challenges the award.
The fix is straightforward and already well established in public procurement: assign a percentage weight to each evaluation dimension before proposals are opened, and publish that weighting inside the RFP itself so every bidder is scored against a standard it could see in advance. A committee that decides its weightings after reading the proposals is, in effect, choosing the weightings that produce the outcome it already prefers, which is a defensibility problem regardless of whether the underlying decision was reasonable.
Mistake 3: Asking for a single blended price instead of itemized pricing
An RFP that asks bidders for one flat number, “total cost per background check“, cannot tell the difference between a vendor whose service is genuinely cheaper and a vendor who has simply structured its quote to look cheaper on a summary line. Background screening pricing has at least two components that behave very differently: the vendor’s own service fee, and pass-through costs like court access and database fees that vary by jurisdiction and that the vendor does not control.
A price schedule that doesn’t separate these components rewards whichever bidder is best at making a blended number look small, not whichever bidder actually costs less for the buyer’s real volume and jurisdiction mix. The fix is to require itemized pricing with three distinct components:
- A base service fee, broken out by search type
- Pass-through fees, listed separately, with a stated method for handling costs above whatever baseline the bidder assumed
- A total calculated against a volume the buyer specifies, not one each bidder is left to guess at
Mistake 4: Requesting a single turnaround figure instead of turnaround by search type
“What is your average turnaround time” is a common RFP question, and it is close to useless as a basis for comparison. A county criminal record search and an international education verification do not take comparable amounts of time, and a single averaged figure obscures which specific searches will actually create a hiring delay. Two vendors can report an identical average turnaround while having very different turnaround profiles once broken out by search type, one fast on the searches the buyer runs constantly and slow on an occasional but important one, the other the reverse.
A useful turnaround requirement asks for:
- Standard turnaround per search type, not a single blended average
- A stated remedy if a committed turnaround is missed
- A disclosed list of search types where third-party response times commonly exceed the buyer’s target window
Requesting turnaround this way produces a comparison that actually predicts what will happen once the contract is running. An averaged figure predicts almost nothing.
Mistake 5: Leaving vendor-type expectations unstated
Background screening providers aren’t structurally identical to one another, and an RFP that doesn’t specify what kind of provider it’s soliciting can end up comparing responses that aren’t actually comparable in the way the buyer assumes. Leaving this unstated doesn’t avoid the question, it just means the buyer discovers the answer after the contract is signed rather than during evaluation, which is a worse time to find out. At minimum, an RFP should ask every bidder:
- Whether it operates as a consumer reporting agency conducting its own compliance program directly, or through another structural arrangement
- Who bears direct FCRA compliance responsibility for the reports it delivers
- To describe its structure plainly, rather than the buyer assuming every bidder responding to the solicitation is organized the same way
Mistake 6: Recycling an old RFP without updating it
Reusing a previous solicitation as a starting template is a reasonable way to save drafting time, but an RFP that’s been recycled across several procurement cycles without a real review accumulates a specific set of tells that experienced vendors notice immediately, and that signal the buyer hasn’t looked closely at its own current requirements. The two most common:
- Referencing an industry accreditation body by a name it stopped using years ago, which reads to any current vendor as a sign the RFP hasn’t been touched since that name changed
- Asking questions that assume manual, paper-based reporting processes with no acknowledgment that most modern screening platforms operate through cloud-based portals and API integrations
A related version of this mistake is asking for company detail disproportionate to what the RFP process actually needs, years of full financial statements, granular technical or source-code detail, from every bidder at the proposal stage, when that level of disclosure is only relevant for the finalist the buyer is actually likely to select. Vendors notice quickly when an RFP asks for confidential details with no realistic chance of advancing to that stage, and the practical effect is that serious respondents either push back with clarifying questions or decline to bid rather than volunteering sensitive information into a process where three or four other companies are asking the identical question.
Before and after: rewriting three of these mistakes
Seeing the actual language side by side makes the fix concrete in a way the general description doesn’t.
| Mistake | Before | After |
| Vague scope of work | “Vendor shall provide employment verification services for candidates as needed.” | “Vendor shall verify employment history for the seven years preceding the application date, covering up to five employers per candidate. Employers beyond the fifth shall be verified at the per-verification rate specified in the price schedule. Vendor shall document all verification attempts, including cases where an employer does not respond within the vendor’s stated turnaround window.” |
| Blended pricing | “Vendor shall provide a total cost per background check, inclusive of all fees.” | “Vendor shall submit pricing in three parts: (a) a base service fee for each search type listed in Section [X]; (b) pass-through court and database fees, itemized separately and billed at actual cost, with a disclosed method for handling any search where actual fees exceed the vendor’s stated baseline estimate; (c) any volume-based pricing tiers, calculated against the annual volume stated in Section [X].” |
| Blanket turnaround | “Vendor shall report average turnaround time for background checks.” | “Vendor shall report standard turnaround time for each search type listed in Section [X], measured in business days from receipt of consent. Vendor shall separately identify any search type where turnaround commonly exceeds the stated standard due to third-party response times outside the vendor’s control, and shall propose a remedy for instances where a committed turnaround is missed for reasons within the vendor’s control.” |
Each “after” version answers, in advance, the exact questions a vendor would otherwise have to ask during the Q&A period, or exploit during evaluation. The scope rewrite closes off guesswork about lookback period and employer count. The pricing rewrite can’t be gamed by a bidder who structures its number to look smaller on a summary line, since every component has to be shown separately. The turnaround rewrite produces a number the buyer can actually act on, since it shows exactly which searches are fast, which are slow, and why, rather than a single figure that could describe almost any underlying mix of search types.
Mistake 7: Asking for base-term pricing only, with no option-year commitment
Most public-sector screening contracts run a base term followed by optional renewal years, and an RFP that asks bidders to price only the base term leaves the cost of every renewal year to be negotiated later, at exactly the point in the relationship where the buyer has already absorbed the cost of implementation and has the least leverage to resist an increase. This mistake is easy to miss because the base-term number still looks complete on its own, the gap only becomes visible at renewal, by which point the RFP that could have prevented it is long closed.
| Before | After | |
| Option-year pricing | “Vendor shall provide pricing for the initial contract term.” | “Vendor shall provide pricing for the initial contract term and for each of the [number] optional renewal years, including the specific escalation mechanism (a stated percentage cap, or an index such as the Consumer Price Index applied to the base service fee only) that will govern any increase in each option year.” |
Requiring full-term pricing at the proposal stage doesn’t commit the buyer to exercising every option year. It does mean the buyer knows, before signing anything, what the full relationship could cost if it does.
What these mistakes have in common
Every mistake above is, at root, a failure to say clearly what the RFP means, not a failure of the underlying requirement. The scope wasn’t wrong to ask for employment verification, it just didn’t say how many employers or how many years back. The evaluation criteria weren’t wrong to weigh cost and compliance, they just never said how much each should count. None of these are complicated fixes. They are, collectively, what it looks like to hold a solicitation to the same standard of clarity a buyer would expect from a vendor’s own proposal.
There’s a second thread running through all seven mistakes, beyond clarity alone: each one, left uncorrected, ends up treating bidders inconsistently even when that isn’t the intent.
- A vague scope lets one bidder guess correctly and another guess wrong, through no fault of either
- Unweighted criteria let a committee’s unstated preferences decide an outcome that a published rubric should have decided instead
- Blended pricing rewards whichever bidder is best at making a number look small rather than whichever bidder actually costs less
- A single averaged turnaround figure rewards whichever bidder picks the most favorable search types to emphasize, rather than the bidder that’s actually fastest where it matters
In every case, the fix that resolves the clarity problem is the same fix that makes the process fair to every bidder measured against it.
GCheck calls this operating standard Compliance for Good®, and applied to an RFP specifically, it is both Transparent Compliance and Fair Compliance at once: a solicitation that tells every bidder exactly what is being asked, so that what comes back can actually be compared, evaluated, and defended on the same terms for everyone who responds.
Frequently asked questions
What is the most common mistake in a background screening RFP?
Leaving the scope of work too vague to bid against precisely, most often by not specifying parameters like lookback periods, the number of employers verified per candidate, or whether continuous monitoring is in scope. This mistake surfaces during the Q&A period as a wave of clarifying questions the original RFP should have already answered, and it’s avoidable simply by naming those parameters explicitly before the solicitation is published.
Why is it a mistake to ask for a single blended price in an RFP?
A single blended number can’t distinguish a vendor that’s genuinely less expensive from a vendor that’s simply structured its quote to look cheaper on a summary line. Background screening pricing includes pass-through costs (court and database fees) that vary by jurisdiction and that the vendor doesn’t control, and a blended rate hides how much of the quote is vendor margin versus a real third-party cost passed through unchanged.
Should an RFP ask for a single average turnaround time?
No. A single averaged turnaround figure obscures which specific search types will actually cause a hiring delay, since different search types take very different amounts of time. Turnaround should be requested per search type, with a stated remedy if a committed time is missed.
What does it mean for an RFP to be “over-recycled”?
An over-recycled RFP is one reused across multiple procurement cycles without real review, and it typically shows tells like referencing an outdated accreditation name or assuming manual, paper-based processes with no acknowledgment of modern cloud-based screening platforms. It signals to vendors that the buyer hasn’t reviewed its own current requirements, which tends to produce generic, low-effort responses in return.
Why should evaluation criteria include stated weights?
Unweighted criteria let an evaluation committee justify nearly any outcome after proposals are read, which is precisely what a losing bidder will target if it challenges the award. Publishing a percentage weight for each criterion before proposals open, and holding every bidder to that published standard, is what makes the resulting selection defensible.
Should an RFP require pricing for renewal option years, or just the initial term?
Bidders should be required to price the full potential term, the initial period plus every optional renewal year, at the proposal stage. Requesting only base-term pricing leaves renewal-year cost to be negotiated after the buyer has already absorbed implementation costs and has far less leverage to resist an increase than it had during the competitive solicitation.
What should an RFP ask about a vendor’s organizational structure?
It should ask each bidder to describe plainly how it is structured and who bears direct compliance responsibility for the reports it delivers, rather than assuming every bidder responding to a screening solicitation is organized the same way. Leaving this unasked doesn’t avoid the question, it just delays discovering the answer until after the contract is already signed.
ABOUT THE CREATOR
Charm Paz, CHRP
Recruiter & Editor
Charm Paz is an HR professional at GCheck, specializing in background screening, fair hiring, and regulatory compliance. She holds from the Professional Background Screening Association (PBSA) and helps organizations navigate employment regulations with clarity and confidence.
With a background in Industrial and Organizational Psychology, she translates policy into practice to build ethical, compliant, human-centered hiring systems that strengthen decision-making over time.
