Browse the docs

Outcome

Record what happened, why, and how you know, so the next bid decision is smarter than this one.

2 min read · Updated

The last stage asks: what was the result? Recording it closes the loop that makes Paavya's recommendations better over time.

The Outcome stage of a submitted pursuit, awaiting the result, with Record won, Record lost and Record no decision
Outcome. It asks for the result first, and nothing else until you pick one.

Recording the result

Press the result that happened: Record won, Record lost or Record no decision. Only then does the page ask for what that result needs:

  • How you know: the award notice, the debrief, a call with the contracting officer.
  • The reason, for a loss: price, past performance, technical score and so on. "Unknown" is an honest answer; it is recorded and kept out of patterns.
  • The winner, if you know it.

While the buyer is still deciding, the pursuit simply waits. Paavya also watches the public award record each night. When an award matches your solicitation number exactly, it proposes the result to the pursuit's manager. It never records the result on its own.

What Paavya learns

  • The call compared with the result. If you bid against the recommendation, or a recommended bid lost, Outcome lists what the record holds that might explain it, each with its evidence and how it is known. It never concludes for you.
  • Library answers that went into the bid. Each one now carries its record: used in so many bids, won so many, lost so many. Answers Scribble wrote in are marked as such.
  • A rewrite worth keeping. When your team rewrote an approved answer for this bid, Outcome can propose the new wording back to the Library. A person approves it before anything changes.

Patterns across many bids show up in Insights › What we've learned. See Insights.

Pictures are from Paavya's demo workspace, so names, bids and figures are illustrative. Something here does not match what you see? Tell us, or ask Scribble in the app.