Use buyer feedback and your own bid record to make one testable process change, without mistaking a hypothesis for an official finding.
After a public-sector bid, request any feedback available under the buyer's rules, preserve the proposal and solicitation record, separate confirmed findings from your team's hypotheses, and choose one process change to test on the next suitable opportunity. A debrief can explain part of an outcome. It cannot prove that one change will increase your win rate.
Research reviewed October 1, 2026. The federal rules cited below apply to covered federal negotiated procurements. City, county, school, and state buyers can use different feedback processes; check the actual solicitation, award notice, and buyer instructions. The action-log method is GreenLight's analysis, not a government-mandated format.
Save the award or exclusion notice and identify the permitted feedback channel, recipient, and deadline. For covered federal postaward debriefings, FAR 15.506 describes a written request received within three days of award notification and the information a debriefing should contain. FAR 15.505 addresses preaward debriefings after exclusion. Those federal windows are not a default rule for a school district or municipal bid. If a local buyer offers only a score sheet or no formal meeting, record that limit instead of inventing a debrief.
Ask questions tied to the stated requirements and evaluation factors: Which part of our response was unclear? Which evidence did not establish the claimed capability? Was a weakness tied to approach, staffing, price, past performance, or a required attachment? A federal debriefing can address significant weaknesses, deficiencies, ratings where applicable, and the award rationale; it does not provide a point-by-point comparison with another offeror's protected proposal. (FAR 15.506)
Keep the version of the solicitation and amendments used for the bid, the submitted package, the internal go/no-go decision, the requirement trace, and delivery evidence. Record who owned each item and when it was checked. That makes it possible to tell whether a buyer comment concerns an actual gap in the delivered response or a different interpretation of the requirement.
For a subcontractor, keep the exact input sent to the prime and the prime's request or instructions. A prime's feedback may describe the overall offer and may not isolate the subcontractor's contribution. Ask the prime to identify what can be shared, then record uncertainty where attribution is unavailable.
Write each finding as a narrow observation. Use the source of the statement and the relevant solicitation passage. Federal evaluations are made against the factors and subfactors stated in the solicitation; FAR 15.304 requires those factors and their relative importance to be clearly stated, and FAR 15.305 describes evaluation on those factors. Those rules make the factor map a useful federal review anchor. For other buyers, use their own published criteria.
| Record field | Example of a useful entry | What to avoid |
|---|---|---|
| Source and status | Buyer debrief, dated score sheet, or internal package check | Treating team opinion as buyer feedback |
| Requirement or factor | Exact solicitation section and issued version | A generic label such as “technical weakness” |
| Observation | Buyer cited missing staffing detail in a named section | “We lost because our price was too high” without evidence |
| Action and owner | Proposal lead adds a staffing-proof review gate by Friday | “Write better proposals” |
| Test | Check the next eligible bid against that gate before submission | Claiming the action already improved outcomes |
Use three evidence states: buyer-confirmed, internally observed, and hypothesis. A score or comment can be buyer-confirmed; a late internal handoff is internally observed; an assumption that a competitor offered a lower price is a hypothesis unless the buyer disclosed enough to support it. Do not collapse these states into a single “reason we lost.”
Some findings point to a fix in the response process: a missing source citation, unclear staffing proof, stale attachment, or unverified package item. Others show that the opportunity was a poor fit before writing began. Revisit the documented qualification decision only when the evidence supports that conclusion. The evaluation-criteria guide helps distinguish what the buyer scored from what your team assumed mattered.
The federal framework does not support a universal “lowest price always wins” or “technical quality always wins” lesson. FAR 15.304 requires the solicitation to state the relative importance of the factors; FAR 15.305 describes how proposals are assessed against those factors. Read the actual buyer model before changing pricing or technical strategy.
For each recurring or material finding, name a process owner, a change, a due date, and the next bid where it can be tested. If a buyer cited weak past-performance relevance, for example, the action might be to add a review prompt asking writers to map each reference to the solicitation's scope and performance period. FAR 15.305 treats currency, relevance, source, context, and trends as considerations in covered federal past-performance evaluation. The next proposal still must follow its own instructions.
Avoid turning one outcome into an untested house rule. A single loss may reflect the buyer's particular need, competition, or evaluation method. Record the proposed change and look for repeat evidence over later pursuits. Close an action only after the team used the new step and inspected the resulting package; do not close it merely because a playbook was edited.
Before the next delivery, compare its actual response against the current source set and your action log. The final submission review covers the package and delivery checks. Keep the lessons log separate from any protest or legal decision. A debrief may raise questions, but a post-bid process review is not legal advice or a finding that the buyer erred.
GreenLight can preserve a documented, human-reviewed pursuit decision with confirmed disqualifiers and unresolved conditions, and it can organize detected response requirements into a source-linked package inventory. Those records can give a proposal team context for its own post-bid review. People still need to compare the actual submitted files with the buyer's feedback, decide which observations are credible, and own the corrective action.
GreenLight does not conduct official buyer debriefings, infer the award rationale, decide whether to protest, or guarantee a better outcome on the next bid. Automated requirement extraction can miss items, so the current buyer documents remain controlling. If your team wants to review how pursuit and requirement records could support this process, Book a 15-minute call using the button on this page.
Yes. Capture what the buyer actually said and what your team observed about effort, scope, and delivery. Do not infer that every technique in a winning bid caused the award. Keep repeatable strengths distinct from unsupported success stories.
Use the award notice, any permitted score sheet or feedback, and your own submitted record. Label internal observations and hypotheses clearly. Check the buyer's process before requesting additional information; the federal Part 15 request windows do not apply automatically to state and local bids.
Yes, but limit conclusions to the scope and files you supplied. Ask the prime for shareable feedback and preserve its wording. Do not present an overall buyer judgment as a finding about your work unless the source supports it.
Not necessarily. Federal postaward debriefings have defined minimum content and disclosure limits under FAR 15.506. Local processes vary. Record what was disclosed and leave the rest as unknown.
See how GreenLight helps your team qualify the opportunity, organize the buyer's requirements, and check the package before you submit it.