Bid Protest Procedure for Local Governments: Building the Response Record

When a protest letter lands on the issuer's desk

A grants manager at a nonprofit that passes federal funds to a regional transit partner receives an email two days after the notice of intent to award goes out. The second-ranked offeror says its technical score was unfair, that one evaluator seemed to have seen another's scores, and that the winning offeror's price included an option the solicitation never asked for. The manager has a folder of scoresheets, a Word memo, and a shared spreadsheet with several versions. The protest deadline in the local policy is short, and the governing board meets soon.

None of the three grounds can be answered from memory. Each can be answered only from what the file shows about what happened, in what order, and under which rule. Reconstructing the evaluation falls to the issuer, because only the issuer holds the record.

This guide explains how a written protest procedure usually works, which stages it should cover, and how to map each protest ground to a specific document in the evaluation file. After reading it, you will be able to check whether your file could answer a protest and to name what is missing before one arrives.

Why the issuer's own record is the defense

A protest is a challenge to how the issuer ran the solicitation or evaluated proposals. Whatever standard your policy or local law applies to the protest, the issuer's answer depends on what it can show it did. That puts the weight on documentation created during the evaluation, not after it.

For organizations spending federal award money, the Uniform Guidance puts this responsibility in writing. Under 2 CFR 200.318(k), the recipient or subrecipient settles all contractual and administrative issues arising out of its procurement transactions. In the regulation's words: "These issues include, but are not limited to, source evaluation, protests, disputes, and claims." The same paragraph says the federal agency will not substitute its judgment for the recipient's unless the matter is primarily a federal concern. A separate piece on 2 CFR 200.318(k) and protests for grant recipients covers that section in more detail.

Section 200.318(i) sets the standard for what the file must hold. It requires records detailed enough to show the history of each procurement, including four elements:

• the rationale for the procurement method;
• the contract type selection;
• the contractor selection or rejection;
• the basis for the contract price.

A protest tests exactly these elements. The method rationale answers a challenge to how the solicitation was run. The selection and rejection record answers a challenge to the ranking. The price basis answers a challenge to cost evaluation. Confirm the current text of both paragraphs at eCFR, which describes itself as authoritative but unofficial; the official edition is the annual CFR on govinfo.gov.

A caution on scope. Protests also arise outside federal awards, under state law or local ordinance, and those rules may be stricter. Where both apply, your procedure may need to satisfy both. This article does not state any state's rule, and your counsel or procurement office should confirm which governs.

What the federal protest numbers do and do not tell you

Public data on protests at the local and grant-recipient level is thin, and we do not publish a figure for how often they occur. The best-documented numbers come from the federal bid-protest system and describe federal agency procurements only.

In its fiscal year 2025 annual report (GAO-26-900695, December 12, 2025), GAO listed the most common grounds on which it sustained protests: an unreasonable technical evaluation, an unreasonable cost or price evaluation, and an unreasonable rejection of a proposal. The same report shows GAO sustained 14 percent of the protests it resolved on the merits that year, and gives an effectiveness rate of 52 percent. GAO defines the effectiveness rate as the share of protests closed in the year in which the protester obtained some form of relief, either through voluntary agency corrective action or a sustained protest.

These figures do not describe grant recipients or local governments, and a local protest body may work very differently. What they show is where evaluation records tend to be challenged: the technical evaluation, the price evaluation, and the decision to reject. Those are the three areas where a local file should be strongest.

The stages of a written protest procedure

Section 200.318(a) requires documented procurement procedures for work under a federal award, consistent with state, local, and tribal law. A protest procedure belongs in that document. The stages below are common across written procedures, but every period and form is set by your own policy and applicable law, so we do not state a default.

Stage 1: The notice and what it tells offerors

Many procedures begin with a notice of intent to award, sent to all offerors before the contract is executed. The notice often marks the point from which a protest period runs, if your policy provides one. Check what your policy says the notice must contain, who must receive it, and how the date of receipt is recorded. A notice whose date nobody can prove makes the protest deadline itself a dispute.

Stage 2: Receipt and logging

When a protest arrives, record the date and time, the sender, and the method of delivery. Check it against the policy's requirements for a valid protest, such as writing, signature, identification of the solicitation, and a statement of grounds. A bid protest letter typically has to identify the solicitation and the specific grounds, and the policy may set a standard for how specific. We do not provide a template here; your counsel or procurement office should confirm what the policy requires of a protester.

Stage 3: Hold and preserve

Decide, under your policy, whether the award or contract execution is paused while the protest is pending. Then preserve the file as it stands. Do not edit scoresheets, replace memos, or tidy minutes. A file that changes after a protest is received invites a worse question than the original ground.

Stage 4: Review by someone independent of the evaluation

Many policies route the protest to a person who did not serve on the evaluation committee, often the procurement official, a department head, the governing body, or counsel. Record who reviewed, what they read, and when. If a protest names an evaluator, consider whether that person should be involved in the response at all.

Stage 5: Written decision

The decision should state the grounds raised, the facts found, the rule applied, and the outcome. Tie each finding to a document in the file. Keep the decision as plain as the record allows; a decision that cites a scoresheet and a consensus rationale is easier to defend than one that restates conclusions.

Stage 6: Appeal, if your policy provides one

Some policies allow a further review. Others end at the first decision. Record whichever applies, and note what offerors were told about further options. If a dispute moves toward litigation or a funder complaint, involve counsel.

Mapping each protest ground to a file document

The most useful preparation is a table you build before any protest: for each common ground, the document that answers it. If a row of your table is empty, that gap is the finding.

"The evaluation criteria were applied differently from the solicitation"

Section 200.320(b)(2)(i) requires an RFP to identify all evaluation factors and their relative importance. The answer to this ground is a side-by-side record: the factors and weights as published, and the factors and weights as scored. Weights that total 100 and appear identically in both places close the question. Weights that were adjusted mid-evaluation need a recorded reason and, usually, an amendment sent to all offerors. See the piece on RFP evaluation documentation for how to lay this out.

"Scores were not independent"

Anchoring, or an accusation of it, is a common protest theory. The answer is a record showing when each evaluator submitted scores, that no one could see another's scores before submission, and that disagreement was handled at a consensus meeting, not through influence beforehand. In a shared spreadsheet this is hard to show, because nothing in the file records who saw what and when. The article on evaluator scoring independence goes through the mechanics.

"An evaluator had a conflict of interest"

Section 200.318(c) bars an employee, officer, agent, or board member with a real or apparent conflict of interest from participating in the selection, award, or administration of a contract supported by a federal award. The answer is a signed conflict attestation from each evaluator, dated before the first score was recorded. An attestation collected afterward is weaker evidence.

"The rating of my proposal was unreasonable"

This is the technical-evaluation ground, which GAO listed first among its most prevalent reasons for sustaining federal protests in fiscal year 2025. The answer is the rating definitions fixed before scoring, each evaluator's score and comments, and the consensus rationale for each final score. A final score with no written reason is the weakest document in most files. Section 200.320(b)(2)(ii) requires written procedures for technical evaluations and selections, so cite your own procedure as well.

"The price evaluation was unfair"

Here the file needs the price formula as stated in the solicitation, the bids as entered, the treatment of any alternates and options, and the calculation. Above the simplified acquisition threshold, 2 CFR 200.324(a) requires a cost or price analysis, and independent estimates must be made before bids or proposals are received.

A worked example shows why the formula matters. Using a lowest-price method with 30 price points, three offers of $80,000, $100,000, and $125,000 yield 30, 24, and 19.2 points. The calculation is lowest evaluated price divided by this offer's evaluated price, multiplied by 30. If the solicitation said something else, the file must show which formula applied. If one offer included an option that others did not, the protester's complaint about the winner's price may be correct unless the file shows the option was excluded from the evaluated price on a stated basis.

"My proposal was wrongly rejected"

The answer is a per-proposal responsiveness checklist showing which requirement was not met, who determined it, and when. Rejection should rest on a requirement the solicitation actually stated.

"The award did not follow the stated basis"

For proposals, 2 CFR 200.320(b)(2)(iii) says contracts must be awarded to the responsible offeror whose proposal is most advantageous to the recipient or subrecipient considering price and other factors. The answer is the ranking, the responsibility determination, and the award decision recorded by the person with authority to make it. Qualifications-based selection for architectural and engineering services is a separate method in which price is not a selection factor; if you used it, the method rationale must show that.

Assembling a protest file before you need one

Preparing in advance is cheaper than reconstructing under a deadline. A protest file generally collects the following in one place:

• the solicitation and all amendments, with dates sent;
• the method rationale and contract type selection;
• evaluator invitations, conflict attestations, and scoring instructions;
• individual scoresheets and the record of when each was submitted;
• consensus minutes with the rationale for each final score;
• bid tabulation, the price formula, and the cost or price analysis with the independent estimate;
• responsiveness and responsibility determinations;
• the award decision and the notice of intent to award;
• the debrief record, if any, covered in the piece on RFP debriefs for unsuccessful offerors;
• the log of the protest itself and the written decision.

The procurement file documentation checklist walks through the full list. Retention matters too: 2 CFR 200.334 sets a baseline of three years from the final financial report unless an exception applies, and local public-records rules may require longer. Confirm the period with your awarding agency or pass-through entity. An unresolved protest, claim, or audit can extend what you must keep.

Moving rules deserve a note. The 2024 Uniform Guidance revision took effect October 1, 2024, and the FAR thresholds that 2 CFR relies on changed effective October 1, 2025. On May 29, 2026, OMB also published a proposed rule that would revise 2 CFR Part 200 again (91 FR 32198); as of October 2026 the Federal Register shows no final rule. Check your award terms for the version that applies and confirm the current status before relying on either. A file that records which rule applied at the time of the solicitation can show which rule it followed when a protest arrives years later.

Keeping the response record organized

A protest response is a records exercise before it is anything else. Fix your weights and rating definitions before scoring opens, record independence and conflict attestations as they happen, and require a written reason for every consensus score. Then build the protest map above and check it against your last solicitation. Note each empty row and decide how to close it before the next RFP.

RFPManagement is a software publisher's web workspace for the evaluation stage, designed to hold the solicitation record, anchored criteria, hidden-until-lock scoresheets, consensus rationale, bid tabulation, and an append-only audit trail with ZIP export. Scoring stays human-only. A workbook for this stage, the Bid Protest Response Workbook, is designed to record the protest log, the ground-to-document map, and the written decision. Store availability is not yet open. To hear when the evaluation workspace opens, join the waitlist.

RFPManagement records and computes. It does not give legal or procurement advice. The award decision stays with your organization.