This page lists three turns, the messages you send to the AI one after another in the same chat, and then a check of the answer. Keep it open next to your chat. Each turn shows the next thing to paste, with the values you entered already filled in. Nothing is sent from this page, and your conversation stays in the AI tool you are using.
Agency, solicitation number, vehicle and contract type, dollar value, evaluation scheme, and who won.
Every date that matters, including when you learned the basis of each ground.
Each suspected error, with the source: debriefing, notice, solicitation, or inference.
Where you are thinking of filing, or say undecided and let the outline compare.
Incumbency, follow-on work, other pending awards with this agency, and the client's appetite.
Watch for these throughout
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.