RFP references are contacts at past clients who confirm that a vendor delivered similar work on time, on budget, and to a good standard. Buyers use them to verify the claims in a proposal, usually by calling or emailing each contact, and often score the results as part of the past performance or qualifications section.
How RFP references work in the evaluation
Evaluators treat references as independent proof. Anyone can write that they delivered a similar project; a client who confirms it carries more weight. In U.S. federal buying, the Federal Acquisition Regulation says past performance information is one indicator of an offeror's ability to perform the contract successfully, and agencies may weigh information from sources beyond the ones you submit. Private-sector and state buyers follow the same logic even when the rules are less formal.
That has a practical consequence. A reference is not a formality you fill in at the end. It is a scored or screened input, and a single unreachable contact can cost points or trigger a compliance flag. Treat each entry as a mini-proposal with its own owner, deadline, and review.
RFP references compared with other proof points
Proposal teams often mix up references with letters, case studies, and questionnaires. Each serves a different purpose, and many solicitations ask for more than one. The table below separates them.
| PROOF POINT | WHAT IT IS | WHO PRODUCES IT | HOW BUYERS USE IT |
|---|---|---|---|
| Client reference | Contact details and project summary for a past client | Vendor lists it, client confirms by phone or email | Called or emailed to verify claims and ask about performance |
| Reference letter | Signed written endorsement from a client | Client, often drafted with vendor help | Read as supporting evidence without a call |
| Case study | Narrative of a project and its results | Vendor | Shows approach and outcomes in context |
| Past performance questionnaire | Standard form a client completes about your work | Client, sent by the buyer or the vendor | Scored against the buyer's rating scale |
| CPARS record | Government evaluation of a federal contractor | Federal agency | Reviewed by source selection officials without being submitted |
If a solicitation asks for a questionnaire, see our guide to the past performance questionnaire. This post covers the contact references themselves.
How to choose RFP references
Selection is where most teams go wrong. The instinct is to name the happiest or biggest client. The better test is similarity. The Bid Lab's guide to references for RFPs ranks the criteria in this order: similar work, recency, sector fit, a reachable contact, and a referee who can cite a concrete result.
Match scope, scale, and sector
Pick projects with comparable deliverables, volume, and constraints. A bank evaluating a compliance platform wants to hear from another regulated buyer, not from a startup that loved your onboarding. Public-sector buyers generally weight public-sector references more heavily.
Respect the recency window
Many solicitations limit references to work completed in the last three to five years. Read the window before you shortlist, and never stretch it. A reference outside the window can be disqualified or ignored.
Give exactly the number requested
Submit the number the RFP asks for. Extra entries add evaluator work and can dilute a scored section. If no number is stated, The Bid Lab suggests three as a sensible default.

How to prepare references before you submit
A reference you have not warmed up is a risk. Contacts change jobs, forget details, or miss the call. Run this short sequence for every proposal:
- Ask permission and confirm the contact is still in role and willing to answer calls or email during the evaluation window.
- Share the solicitation title, the likely timing of outreach, and the kind of questions the buyer may ask.
- Confirm the facts you plan to publish, including project dates, contract value, and your role, so they match the client's records.
- Give the contact a short briefing note with your key delivery outcomes, so the call stays accurate and specific.
- Send a thank-you after the evaluation and share the result, which keeps the relationship warm for the next bid.

What each reference entry should include
Use the buyer's reference form if one is provided. If not, a consistent entry makes evaluators' work easy and protects you from missing a required field:
- Client legal name and department
- Contact name, title, phone, and email that are current
- Project dates and contract value, using annual value for multi-year work
- Your role: prime, subcontractor, or joint venture partner
- Two or three sentences on the scope you delivered
- One measurable outcome, such as time saved, error rate reduced, or revenue protected
Federal past performance and CPARS
Federal bids add a layer. Agencies record contractor evaluations in the Contractor Performance Assessment Reporting System, and under FAR 42.1503, contractors get up to 14 calendar days from notification to submit comments or rebuttals on an evaluation. Past performance information is used within three years of completing the work, or six years for construction and architect-engineer contracts.
Evaluators can read CPARS records you never submitted, so check yours before you bid. Also note that under FAR 15.305, an offeror with no record of relevant past performance may not be evaluated favorably or unfavorably on it. If your history is thin, key personnel and major subcontractors with relevant experience can help carry the section.
Keep RFP references current in your content library
Reference details go stale quickly. Titles change, contacts leave, and project values get restated. The fix is to store every approved reference as a managed record with an owner and a review date, instead of re-typing it into each response. A governed content library gives your team one verified version to pull into any proposal. Our guide to RFP content management shows how to set that up, and teams that respond to RFPs at volume can see how it fits into the broader RFP response workflow.
A practical rule: review each reference record every six months, and again right before any bid that requires it.
Common RFP reference mistakes
- Listing a contact who has left the organization.
- Naming references who were never asked.
- Publishing figures that do not match the client's records.
- Choosing your best client instead of your most similar project.
- Ignoring a required reference form or submitting the wrong format.
- Presenting subcontract work as prime work.
Each of these is avoidable with a simple checklist and a reference owner on the proposal team. Fix the process once, and every future response benefits.
Want to stop rebuilding reference sections from scratch? Book a RocketDocs demo to see how a governed content library keeps approved references ready for every proposal.
Looking for the platform behind this? See the RocketDocs platform or book a demo.