Learning Center · Proposal Writing

References for RFPs: A How-to Guide

References are how an evaluator tests whether your claims survive contact with someone who worked with you. Here's how to choose them, what each entry needs, why you should call before you submit - and why part of your federal past performance record is held by the government, not by you.

By The Bid Lab Team·Published 2/6/2024·Updated 8/26/2026

Nearly every RFP, RFQ and RFI asks for references, and the section is scored more often than bidders assume - it is how an evaluator tests whether your claims survive contact with someone who has actually worked with you. Choosing well means picking clients whose projects resemble this scope, whose contacts still work there and will answer the phone, and who know the call is coming. For federal work there is a second layer most bidders miss: some of your past performance record is held by the government, not by you.

How Do You Choose Which References to Use?

Match the scope before anything else, then check the reference is reachable. In order of importance:

  1. Similarity of work. A project resembling this scope in what was delivered, at what scale, under what constraints. This outranks how much the client likes you.
  2. Recency. Recent work reflects your current team and methods. Many solicitations set a window - often three to five years - and a reference outside it may not count at all.
  3. Sector fit. A public-sector reference carries more weight for a public buyer, because the constraints they can speak to are the ones this buyer faces.
  4. A contact who is still there. The most common failure in the whole section. People change jobs, and an unreachable reference scores as no reference.
  5. Willingness to be specific. A referee who will say "they recovered a four-week slip without a change order" is worth several who will say the team was a pleasure to work with.

What Should You Do Before Listing Someone?

Call them, and do it before you submit rather than after. Confirm they are willing, confirm they will still be reachable during the evaluation window, and confirm the details you are about to publish about their project - value, dates, your role - match what they remember. Then tell them what this bid is for and which two or three things the evaluator is likely to ask about, so they are not hearing about the scope for the first time from a stranger. This is not coaching; it is the difference between a referee who gives a specific, confident answer and one who is caught off guard and hedges. Give them the solicitation title and a rough window for the call.

Find the bid that fits.Search Bid Banana

What Information Does a Reference Entry Need?

FieldWhat to putWhy evaluators want it
Client organizationLegal name, plus the department or divisionConfirms who the work was actually for
ContactName, current title, direct phone, emailThe section is worthless if they cannot reach them
Project title and datesStart and end, and whether it is ongoingTests recency against any stated window
Contract valueDollar value, or annual value for multi-year workTests whether you have worked at their scale
Your rolePrime, subcontractor, or joint venture partnerA prime and a sub did not do the same job
Scope deliveredTwo or three sentences on what you actually didLets them compare it against this scope
OutcomeA result, with a number where one existsTurns an assertion into evidence

How Many References Should You Give?

Exactly the number requested, no more. If a solicitation asks for three and you supply five because you are proud of all of them, you have created work for the evaluator and risked a compliance flag - and in a scored section, extra entries can dilute rather than strengthen. Where a range is given, the top of the range is usually right, provided every entry genuinely matches the scope. Where no number is stated, three is the convention. Quality matters more than volume here: one closely comparable project with a reachable, articulate contact outperforms five loosely related ones.

What Happens on Federal Work That You Do Not Control?

Your federal past performance is partly a government record. Agencies document contractor performance in the Contractor Performance Assessment Reporting System, and under FAR 42.1503 those evaluations are made available to source selection officials for future awards - within three years of completion of performance, or six years for construction and architect-engineer contracts. Two consequences follow. First, evaluators on federal procurements may be reading an assessment you did not write and did not choose to submit. Second, you get a window to respond: the rule gives contractors up to 14 calendar days from notification to submit comments, rebutting statements or additional information, and your response is retained as part of the evaluation. Letting that window lapse on an unfair rating means living with it on every bid for years.

What Are the Most Common Mistakes?

  • A contact who has left. Verify by phone, not by looking at an old email signature.
  • A reference who was never asked. Being surprised by an evaluator's call produces a lukewarm answer at best.
  • Details that do not match. If your entry says $2.4 million and the client remembers $1.8 million, the discrepancy is what gets remembered.
  • Your best client rather than your most similar project. Warmth does not substitute for relevance.
  • Ignoring a stated format. Many solicitations supply a reference form; using your own instead is a compliance problem regardless of content.
  • Listing work you did as a subcontractor as though you were prime. Evaluators verify this, and it reads as misrepresentation rather than as rounding.

Where Should References Live Between Bids?

In your content library, reviewed on a schedule rather than reconstructed each time. Reference details rot faster than almost anything else in a proposal: contacts move, titles change, outcomes get restated. A short list holding each project's scope, value, dates, your role, the outcome and the current contact - checked every six months - turns the reference section from an afternoon of archaeology into a ten-minute copy job, and eliminates the single most common defect in the section.

Find the Bid Before You Chase the References

Which references you need depends entirely on the scope in front of you, so start from a live solicitation rather than a general list. Search open RFPs on Bid Banana.

Frequently asked questions

How do you choose references for an RFP?

Match the scope first: a project resembling this one in what was delivered, at what scale, under what constraints. Then check recency against any stated window, prefer sector fit, and confirm the contact still works there and will answer. A referee willing to give a specific result outperforms several who will only say the team was pleasant to work with.

Should you contact references before submitting a proposal?

Yes, before rather than after. Confirm they are willing and reachable during the evaluation window, check that the project details you are about to publish match what they remember, and tell them the solicitation title and what the evaluator is likely to ask. That is not coaching - it is the difference between a confident specific answer and a hedged one.

What information should an RFP reference entry include?

The client's legal name and department, a contact with current title, direct phone and email, project title and dates, contract value, whether you were prime or subcontractor, two or three sentences on the scope delivered, and an outcome with a number where one exists. Whether you were prime or a sub matters, and evaluators do verify it.

How many references should an RFP response include?

Exactly the number requested. Supplying extra creates work for the evaluator, risks a compliance flag, and can dilute a scored section rather than strengthen it. Where a range is given, the top of it is usually right if every entry genuinely matches the scope. Where no number is stated, three is the convention.

How does CPARS affect references on federal bids?

Agencies record contractor performance in CPARS, and under FAR 42.1503 those evaluations are available to source selection officials within three years of completion - six for construction and architect-engineer contracts. Evaluators may read an assessment you did not submit. Contractors get up to 14 calendar days from notification to submit comments or rebutting statements, which are retained.

Writing Your Response