Matches and scoring
Matches lists open solicitations scored against your company profile, strongest first. Every score comes with its reasons — which of your codes, capabilities, keywords, agencies, states, certifications, contract sizes and past performance it rests on, and how much each one counted. The score is arithmetic over your own profile; it never depends on AI.
TL;DR — Open Find work → Matches. Read the Strong band first. Choose Why? on any row to see what went into its score. Dismiss what you will never bid, Save or Start pursuit on what you might. Scores refresh daily; choose Refresh scores after you change the profile.
Before you start
- The profile comes first. Matching compares solicitations with your Company Essentials. Until a profile exists, Matches says Describe your company first.
- Target codes decide what is scored. Matching looks at open solicitations whose NAICS or PSC code is one of your target codes — up to 500 per scoring, soonest deadline first. No target codes, no matches.
- Who can do what. Everyone can read Matches. Refreshing scores and dismissing a match need the Business Development User role or above.
The score and its bands
Each solicitation gets a score out of 100 and a band:
| Field | What it does | Accepted values / default |
|---|---|---|
| Strong | Lines up well with your profile on most of what counts. | The band the Dashboard counts as Strong matches, and the one new-match alerts are sent for. |
| Possible | Worth a look, with clear gaps. | Read the reasons before dismissing. |
| Weak | Little in your profile supports it. | Usually a code match with nothing else behind it. |
Each score is stored with the version of the shared data it was computed against (Scored against corpus generation), so a number can always be explained later even after the solicitation changes.
What goes into a score
| Field | What it does | Accepted values / default |
|---|---|---|
| Codes | Whether the solicitation's NAICS or PSC code is one you target, one of your primary codes, or closely related to one. | From Target codes on the profile. |
| Capabilities | Whether the requirement describes a capability you listed — a core capability counts for more. | Read from the solicitation's description, not just its title. |
| Keywords | Whether your keywords appear in the title. | From Keywords on the profile. |
| Agency | Whether the issuing agency is one you target, or part of one. | From Target agencies. |
| Geography | Whether the place of performance is one of your target states, or a state you sell into. | From Target states on the profile and the states under State & local → Where we sell. The reason says when you sell into a state but are not registered to bid there yet. |
| Set-aside | Whether the work is open to any bidder, or reserved for a status you hold. | Compared with your Certifications. |
| Contract value | Whether the estimated value fits your preferred contract size. | From Preferred contract size. |
| Deadline | How much time is left to respond. | Tight or passed deadlines count against a match. |
| Competition | Early-stage notices (the requirement can still be shaped), incumbents, and set-asides that narrow the field. | Unknown competition is said as such. |
| Past performance | Work you have done for this customer or under this code, or a related one. | From Past performance on the profile and pursuits your team has moved to Won. |
Where your profile has nothing to compare — no keywords, no target agencies, no preferred contract size — the reason says so ("You have not recorded any keywords") rather than quietly scoring it as a miss. If there is not enough in the profile to score a solicitation at all, the reason is Not enough in your profile to score this yet.
Why did this score what it did?
Choose Why? on a row. Why this scored lists What went into it: every factor above, its reason in plain words, and its share of the score — or Not counted where it did not apply.
On the Advanced plan, with the workspace's AI switch on, a short written summary sits above the reasons. The summary is only a retelling; the reasons below it are the full breakdown, and the score itself never depends on AI. On other plans, or with AI off, the panel says so and shows the reasons alone. See AI features.
Working the list
| Field | What it does | Accepted values / default |
|---|---|---|
| Band filter | Show one band, or All bands. | |
| Open opportunity | Opens the full solicitation. | Opening it adds it to your You looked at recently list. |
| Save / Start pursuit | Save to My opportunities, or put it straight on the pipeline. | Rows already saved or on the board say so instead. |
| Dismiss | Removes the match from the list for the whole workspace. | Re-scoring never brings a dismissed match back. Show dismissed and Bring back undo it. |
| Refresh scores | Re-scores now, against the current profile and data. | Says how many opportunities it scored. Business Development User and above. |
When scores change
- Every day, automatically, against the current profile and the latest shared data.
- On demand, with Refresh scores — do this after changing the profile, or the Dashboard will suggest it.
- New strong matches found by the daily scoring are announced once, in a single message, to the people who use Axis Capture in your workspace: those who own a live pursuit or have recently opened an opportunity. Each person chooses the channel in Account → Notifications. See Notifications and alerts.
Common gotchas
- "No matches yet." Nobody has scored the workspace yet, the profile has no target codes, or no open solicitation is in your codes today. Choose Refresh scores, then check the codes.
- "An obvious opportunity isn't listed." Its NAICS or PSC code is not one of your target codes, or it is not open. Find it in Discovery, and consider adding the code.
- "A colleague's dismissal hid something I wanted." Dismissals are workspace-wide. Use Show dismissed and Bring back.
- "The written summary says it is not part of our plan." The written summary is an Advanced-plan feature. The reasons are always shown.
Related