The go/no-go analysis helps you decide whether to bid on an RFP. It checks the RFP's requirements against your asset library and your CVs, builds team and pricing scenarios, and gives a recommendation that you accept or override.
What the go/no-go does
- Open the RFP and select the Go / No-Go tab.
- In Opportunity Facts, add what you know: Known incumbent, Likely wired, Client Relationship, evaluator notes with Add Evaluator, and any Named Personnel Required.
- Select Run Analysis.
- Work through Requirements, Team Scenarios, Pricing and Recommendation. Each step opens once the step before it has what it needs.
After a run, the RFP header shows the composite score as "N/100 Go/No-Go Score".
The analysis produces three numbers that sound alike but measure different things, explained below.
Requirement coverage
Requirement coverage asks: does your library contain evidence for each requirement? Propivix compares each requirement's wording with your CVs, project sheets, past proposals, certificates and boilerplate. This is a fixed matching rule, not a model's opinion, so the same library and requirements always give the same result.
Each requirement gets one status on the Requirements step:
- Met: at least one asset covers enough of the requirement's most distinctive terms. A requirement that asks for a certification or clearance also needs an asset that shows it.
- Gap: assets match some of the terms, but not enough.
- Unmet: no asset matches.
The Mandatory Coverage tile scores the mandatory requirements, counting Met as 1, Gap as 0.5 and Unmet as 0, and shows the average as a percentage. With no mandatory requirements, the tile says "No mandatory requirements". On the Recommendation step, "Requirement coverage (library evidence)" applies the same rule to all requirements.
What it does not mean: as the page notes, matches are keyword overlap with your library, not verified evidence. Coverage does not tell you whether your proposal answers a requirement; the compliance matrix shows that.
Team coverage
Team coverage asks: can the people in your CVs staff the requirements? The Team Scenarios step offers up to three teams built from your CVs. Each card shows Team CV coverage, Mandatory, Certifications and Availability. Availability reads "Not applicable" when a scenario has no team members, rather than a percentage.
- Select Use Scenario on the team you want. Pricing and readiness are recalculated.
- If a member shows no rate, enter it and select Save. The rate is saved as that consultant's default.
On the Recommendation step, "Team coverage (CV matching)" is the selected team's Mandatory score. It measures how much of the mandatory requirements the selected CVs can staff. It is not library evidence and can differ from requirement coverage. If no scenarios appear, add CVs to your library and run the analysis again.
Readiness
The Decision Readiness card shows a Readiness percentage. It measures how complete the inputs behind the decision are. It is not requirement coverage and not team coverage.
It combines team coverage (35%), named personnel (20%), hourly rates (20%) and pricing confidence (25%). It is capped at 65% while team coverage is below 90%, 75% while required named personnel are missing or busy, 70% while any rate is missing, and 60% while pricing is incomplete. Caps that apply are listed under "Score Capped Due To:".
The Recommendation step also shows a win probability, a composite score and a confidence figure. The win probability is an estimate. It blends your tracked win rate with the analysis scores, and is reduced for a known incumbent, a likely wired opportunity, no-go triggers and an overloaded team. Treat it as a planning aid, not a prediction.
Recording the decision
The Decision Panel on the Recommendation step starts on the analysis's recommendation, which you can change.
- Choose Go, Conditional Go, Review or No-Go.
- Write a Decision Rationale. It is required.
- For Conditional Go, list at least one condition with Add Condition, and give each a due date and an owner if you know them.
- Select Save Decision.
Saving Go sets the RFP's status to Go, and No-Go sets it to No Go. Conditional Go and Review leave the status unchanged. Each saved decision is added to the Audit Trail.
After a Go or Conditional Go, Promote to Proposal creates a proposal from the selected team and opens it. Export Brief downloads a Word briefing, and Export Presentation downloads a PowerPoint deck. Escalate flags the pursuit for leadership approval and sends an escalation notification.
When a decision needs review
A saved decision is tied to the analysis figures it was made on. If you run the analysis again, pick another team or change a rate, and those figures change, the decision is kept but marked for review:
- Decision out of date: the figures changed. The notice lists what changed, such as the score, win probability or requirement coverage.
- Decision predates analysis: the analysis is newer than the decision, but the earlier figures were not saved, so no comparison is possible.
For either one, the RFP page shows a Review recorded decision notice without being asked. Select the chip in the header to dismiss the notice for your visit. A third chip, Decision currency unknown, means the analysis behind the decision is not available; select it to show the notice.
To clear the review, check the new analysis and save a decision again on the Recommendation step.