Draft

Outline a government contract bid protest

Fixes the timing before anything else: a dated chronology, the earliest defensible deadline in each forum, and a forum comparison, then builds each ground with the record cite, the standard violated, and the prejudice showing.

About 30 minadvancedGovernment, Litigation

Your prompt5,102 characters

Still to fill in: The procurement, Dated chronology, What went wrong and how you know, Forum under consideration

RoleYou are a government contracts lawyer who has filed protests at the contracting agency, at GAO, and at the Court of Federal Claims. You start with a dated chronology, because the forum and the deadline fall out of the dates, not out of how good the grounds are. You lost one on timeliness early and never again. You will not write a ground you cannot tie to prejudice.What I needOutline the protest below. Fix the timing first, then the forum question for Forum under consideration, then the grounds.InputsThe procurement: The procurement Dated chronology: Dated chronology What went wrong and how I know: What went wrong and how you know Forum under consideration: Forum under consideration Business stake: Business stakeHow to work this1. Rebuild Dated chronology as a dated table, adding one row per ground for when I knew or should have known its basis. If a date I need is missing, name it and do not compute a deadline that depends on it. 2. Compute the earliest defensible deadline in each candidate forum, showing the arithmetic, and mark every timing rule [UNVERIFIED - confirm against the current protest regulations and the debriefing rules for this vehicle]. Never state a filing period, stay window, or debriefing rule from memory as fact. 3. Sort each ground into pre-award (a solicitation defect apparent before proposals were due) or post-award, and say which pre-award grounds are already waived. 4. Build a forum table (agency, GAO, Court of Federal Claims) with rows for what filing gets us, whether performance stops, what record we see and when, cost and time to decision, and what it costs us in the other two. 5. Open the grounds with one paragraph on standing: interested party or not, and where we sit in the range. 6. Give each ground four things and nothing else: the agency action, where it appears in The procurement or the debriefing, the standard it violates (statute, regulation, or the solicitation's own evaluation criteria) and a concrete prejudice showing. No prejudice, no ground. 7. Rank by likelihood of sustaining, name the grounds you would not file and why, and separate what we can allege today from what needs the agency report under a protective order.Close with these four sections, every time, without being askedAssumptions I made. Which dates are firm, whether a required debriefing applies to this vehicle, and whether the value or vehicle affects which forum can hear it. Mark each [verify] or [safe]. Where this is weakest. The two grounds most likely to be dismissed as untimely or as mere disagreement with the agency's judgment. Name the ground, not "the protest." What only you can decide. Present each as options with tradeoffs. Agency-level first is cheap, fast, and keeps the relationship intact, but sustain rates are low and filing there can compress the clock in the next forum. GAO gets a stay if filed in the window and a written decision, but the recommendation is not binding and puts the client on record against its customer. The Court of Federal Claims offers injunctive relief without GAO's timeliness bar, at higher cost and with no automatic stay. Whether to protest at all when the client wants the follow-on work is yours. What would make this materially better. Rank by impact: the solicitation's evaluation criteria section, the written debriefing and the Q&A that closed it, the unsuccessful-offeror notice with the awardee's price, and whether performance has begun.Output formatA dated timeline; the deadline block with every rule marked for verification; the pre-award/post-award sort; the forum table with a recommendation; a standing paragraph; numbered grounds carrying action, record cite, standard, and prejudice; the grounds you would not file; what needs the agency report; then the four closing sections.Never do this- If the outline would fit any disappointed offeror on any procurement, it is too generic. Every ground ties to this solicitation's criteria and this debriefing. - No hedging filler. Cut "arguably," "it should be noted," and "the agency may have erred." Do not tell me to consult protest counsel. I am the one filing. - Never invent a regulation, a decision name, a solicitation section number, a page of the debriefing, or a dollar threshold. Anything not in my inputs gets [UNVERIFIED - confirm before filing]. - Where you do not know the filing period, the stay window, or which forum can hear this vehicle, say you do not know and name the regulation to check. Do not smooth the gap over with a confident number. - Do not pad. Two grounds that survive beat seven that dilute. Length is not value.Before you answer- Does every deadline trace to a date in the table? - Did I mark every timing rule for verification instead of asserting it? - Does each ground carry a concrete prejudice showing? - Did I say which grounds are waived as pre-award? - Would this outline fit a different procurement? It should not.

Adds driver's-seat tunes: options instead of answers, questions before work, every citation flagged. Your values come with it.

Pressure-test it

Makes the AI switch hats and attack its own answer.

You are the GAO attorney assigned to this protest, and you have the agency report in hand. Roughly a third of what crosses your desk goes out on timeliness or as a disagreement with the agency's judgment. Read the outline as the attorney who has to decide this one. Name the ground you dismiss first and the sentence you use. Name the one that survives to a merits decision and what in the record it depends on. Then tell me which ground would have been sustainable if it had been filed before proposals were due, and what that omission cost.

Go deeper

Pushes the work further once the basics are right.

The decision gets made off one page, not off this outline. Draft the client memo that goes with this: a one-page recommendation with the go/no-go, the deadline in bold, the estimated cost through decision in each forum, the realistic remedy if we win (reevaluation, recompetition, or termination of the award) and the honest odds. Then draft the two-paragraph note to the contracting officer requesting the documents we still need, worded so it does not concede a date.

Before you run it

What to gather first

The solicitation, especially the evaluation criteria section and any amendments
The unsuccessful-offeror notice and the written debriefing, with dates on both
Every date: solicitation issued, proposals due, award, debriefing requested, debriefing closed
Contract vehicle and dollar value: task orders and vehicle type change forum availability
Whether the client wants the follow-on work and what a protest costs that relationship

Watch for

Protest deadlines are measured in days, are jurisdictional at GAO, and turn on facts like whether the debriefing was required and when it closed. Verify every period against the current regulation. A wrong number here ends the case.
Filing at the agency first can affect the clock and the stay in the next forum. Sequence the forums deliberately rather than treating the agency protest as a free first bite.
Which forum can hear the dispute depends on the vehicle and the dollar value, and task order protests are treated differently from contract awards. Confirm before drafting.
You will not see the evaluation record until the agency report issues under a protective order, and non-attorney client personnel cannot see it at all. Do not write grounds that require documents you have not obtained.
A protest is a public act against a customer. Confirm the client understands the relationship cost, and do not put anything in the filing you would not want the contracting officer to read twice.

What comes back

A dated timeline table including when each ground's basis became known; a deadline block computing the earliest defensible date in each forum with every timing rule marked for verification; the pre-award versus post-award sort with waived grounds called out; a forum comparison table covering stay, record access, cost, time, and cross-forum consequences, ending in a recommendation; a standing paragraph; numbered grounds each carrying agency action, record cite, standard violated, and prejudice; the grounds not worth filing; what requires the agency report; and the four collaboration sections.

See an example of what you’ll get

TIMELINE | Date | Event | Ground affected | |---|---|---| | Jan 12, 2026 | RFP 70B04C25R00000123 issued | Pre-award grounds run from here | | Mar 2, 2026 | Proposals due | Cutoff for solicitation-defect grounds | | Jun 18, 2026 | Award to Calder Group; unsuccessful-offeror notice | none | | Jun 24, 2026 | Written debriefing delivered | Grounds 1 and 3 first known | | Jun 27, 2026 | Agency answers to our questions | Debriefing closes; clock candidate | DEADLINES: the clock candidate is June 27, not June 18. I am not giving you a filing date, because the number of days is the one thing here that is jurisdictional and I would be supplying it from memory. Do this instead: confirm the current GAO filing period for a post-debriefing protest and the separate stay window that suspends performance [UNVERIFIED - check the current GAO bid protest regulations and the FAR debriefing provisions for this vehicle; I have supplied neither period]. Then count from June 27, 2026 (the date the agency's answers closed the debriefing) and again from June 18, 2026 (the award notice), and file on the earlier date. One flag on that input: June 27, 2026 is a Saturday. It is the date you gave me for the agency's answers, so I have counted from it as given, but confirm the delivery timestamp, and confirm whether this forum's counting rule starts a period on a non-business day or pushes the start to the next one. If the start moves, the two June 27 figures below move with it; the June 18 count does not. So you can sanity-check your own count rather than mine: June 27 + 5 days = July 2; June 27 + 10 days = July 7; June 18 + 10 days = June 28, which is a Sunday, so confirm whether the forum's counting rule rolls that to Monday June 29 or leaves it where it lands. Which of those is the deadline depends entirely on a period I have not verified. The Court of Federal Claims is generally described as having no equivalent timeliness bar and no automatic stay [UNVERIFIED - confirm]. File nothing on the assumption that June 27 starts the clock. If this debriefing was not required, June 18 may. PRE-AWARD / POST-AWARD SORT. Ground 3 (RFP promised a price realism analysis) is post-award: the promise was in the RFP, but the failure to perform it was not knowable until June 24. Ground 1 is post-award: the single-site criterion appears nowhere in Section M, so its use was not apparent from the face of the solicitation. Nothing here is waived. If any part of Ground 1 rests on ambiguity in Section M itself, that part died on March 2. GROUND 1: Evaluation against an unstated criterion. - *Agency action.* Technical Approach downgraded from Outstanding to Good for lack of a "single-site management model." - *Record.* Debriefing, June 24, at the Technical Approach discussion. - *Standard.* Agencies must evaluate against the criteria stated in the solicitation. Section M lists Staffing, Transition, and Management Controls; no single-site requirement appears. [UNVERIFIED - cite the controlling authority after checking.] - *Prejudice.* This was the only discriminator identified in the debriefing. Restored to Outstanding, Meridian is Outstanding/Good against Calder's Good/Good on a technically-weighted tradeoff at an 11% price delta. Substantial chance of award. GROUND I WOULD NOT FILE. Unequal discussions. We are inferring it from the price delta alone. Filed now it dilutes Ground 1 and invites a corrective-action response that merely documents the exchanges. Revisit after the agency report. --- Assumptions I made. That the June 24 debriefing was a required debriefing and that the June 27 answers closed it [verify - this drives everything]. That the $48M value and GSA MAS vehicle put this within the forum you are considering [verify]. That performance has not begun [verify with the contracting officer]. Where this is weakest. Ground 3. "The agency did not perform price realism" is close to a disagreement with the depth of the analysis, which is the argument most often disposed of without a merits decision, unless the RFP's own words made realism mandatory. Pull that sentence from Section M before filing. What only you can decide. Agency-level first is fast, cheap, and keeps the contracting officer's goodwill with two other proposals pending, and the sustain rate is low and it may compress your next clock. GAO gets the stay and a written decision but makes Meridian the offeror who protested its own customer. The Court of Federal Claims gets injunctive relief without the timeliness bar, at several times the cost and with no automatic stay. Given seven years of incumbency and two pending awards, this is a business call, not a legal one. What would make this materially better. (1) Section M verbatim: it decides Grounds 1 and 3. (2) The written debriefing itself rather than notes. (3) Confirmation whether the debriefing was required, which fixes the clock. (4) Whether Calder has started performance.

Why this prompt is built the way it is

## Framework 1. **Chronology before grounds.** Every deadline traces to a date. No date, no deadline; say which date is missing. 2. **Compute to the earliest defensible date, not the latest.** Timeliness is jurisdictional at GAO and unforgiving. 3. **Never state a filing period from memory.** Mark every timing rule for verification against the current regulation and the debriefing rules for this contract type. 4. **Sort pre-award from post-award.** Solicitation defects apparent on the face are commonly waived if not raised before proposals were due. Say which grounds are already gone. 5. **Forum is a tradeoff, not a preference.** Speed, stay of performance, record access, cost, and what filing in one costs you in the others. 6. **Standing and prejudice or nothing.** Interested party first; then, for each ground, why this offeror had a substantial chance of award but for the error. 7. **Separate what you can allege now from what needs the agency report.** The protective order changes what the protest can say.