Team matching reads your CVs against an RFP's requirements and proposes teams to staff the bid. It runs on the Assets & Team step of the proposal wizard, under AI Team Matching. The go/no-go analysis builds its Team Scenarios the same way; see Team coverage.
Run a match
AI Team Matching appears when the assets listed for the RFP include at least one CV.
- Select Run AI Match. The button reads "Analyzing..." while it works.
- Read the summary line: how many CVs were analyzed, how many are recommended, and how many are selected. The "recommended (≥70%)" count is the CVs whose chip shows 70% or more.
- Review the Staffing scenarios. The Recommended Team is applied for you. Applying a scenario replaces the selected CVs with that team's CVs; other selected assets stay selected.
- Select another scenario card if you prefer it. Next stays disabled until a scenario is chosen, with the note "Run team matching and choose a staffing scenario before pricing."
After a run, the button reads Re-analyze. Run it again after you change the business line or add CVs.
The match needs extracted requirements and at least one CV. Without them it stops with "No requirements found in RFP. Cannot match team without requirements." or "No CV assets found in your organization. Upload CVs before matching team."
Which CVs are considered
Propivix uses the CVs assigned to the business line you chose on the Strategy step. When that line has no CVs, it uses all your CVs. CVs whose analysis recorded no person's name are left out, unless none of your CVs has a name recorded.
How a CV is scored
The AI scores each CV against each requirement from 0 to 100, following a fixed scale:
- 80 to 100: shown directly in the CV, with named projects, years of experience and outcomes.
- 60 to 79: related, transferable experience that the CV does not prove directly.
- 40 to 59: general background that is only loosely relevant.
- Below 40: little or no relevant experience.
It also gives each CV an overall score, in which mandatory requirements count double. A CV that clearly fails a mandatory requirement is not meant to score above 60 overall. Each CV card then shows:
- "AI relevance" with the CV's overall score.
- "Recommended:" with the role the AI suggests.
- Up to five matching skills in green, and up to three gaps in red.
When the AI does not answer in time, Propivix scores the CVs by comparing their text with the requirements' wording instead. The step does not say which method was used.
What the scores mean: they are the AI's reading of the CV text against the requirement wording. They do not check that a certification or clearance is current, and they are not a count of requirement evidence. They say nothing about your chance of winning. See Requirement evidence on assets for the evidence figure on the same cards.
The three staffing scenarios
- Lean Team: the best-scoring CVs whose average requirement score is at least 40. Its size limit is one person per four requirements, rounded up, but never below two or above five. When no CV reaches 40, the scenario holds the single best CV and says "No CV in the library clears the fit threshold for this RFP."
- Recommended Team: the Lean Team plus up to three more CVs that cover mandatory requirements the Lean Team covers weakly.
- Low-Risk Team: the Recommended Team plus up to two more of the next best CVs, for redundancy.
What the scenario figures mean
Each scenario card shows:
- "% team coverage": for each requirement, the best score any team member has on it, averaged over all requirements.
- "% mandatory (team coverage)": the same, over mandatory requirements only. With no mandatory requirements, it reads 100%.
- "% certs": the share of certification requirements that a team member's certifications, or a certificate in your library, appear to cover. With no certification requirements, it reads 100%, which does not mean anyone is certified.
- Partner needs: the number of kinds of teaming partner suggested for mandatory requirements that no member scores at least 40 on.
These figures measure whether the chosen CVs can staff the requirements. They are not library evidence, not a price and not a win probability.
Getting better matches
- Upload one CV per person and check that its analysis recorded the person's name. See The CV library.
- Assign CVs to the right business lines. See Organizing by Business Line.
- Make sure the RFP's requirements were extracted. See Re-analyzing an RFP.