Hard Constraints in B2B Matching: When a Strong Score Should Still Fail
A hard constraint represents an unacceptable condition, so it belongs outside weighted trade-offs.
A hard constraint is a condition that must be satisfied for a candidate to remain eligible. It should not contribute points or be averaged against strengths. If required certification is absent, prohibited geography applies or capacity falls below an approved minimum, the match should fail even with strong product and timing fit. Exceptions require an authorised policy change, not an algorithmic compromise.
The gate-before-score rule
Evaluate mandatory gates first, calculate weighted fit only for eligible candidates and record why a gate passed or failed.
| Dimension | What to examine | Decision rule |
|---|---|---|
| Clarity | Write the constraint as a testable pass-fail statement. | Reject vague mandatory language. |
| Authority | Identify who can define or change the rule. | Do not let missing data silently weaken a hard gate. |
| Evidence | Specify what proves compliance and how currency is checked. | Fail when required support is absent or expired. |
| Audit | Record the evaluated value, policy version and outcome. | Make exceptions visible and attributable. |
Example: high score, insufficient capacity
A supplier scores strongly on domain, geography, timing and evidence but covers only 30 percent of a requirement whose policy minimum is 50 percent.
The capacity gate fails. The score explains strengths but cannot make the candidate eligible.
Illustrative scenario, not a customer claim or guaranteed outcome.Hard failures in FoundBefore
The deterministic policy separates weighted factors from hard failures such as materially insufficient capacity or absent evidence for a hard requirement.
Policy changes remain governed and should be tested before publication.
Limits and responsibilities
- Not every preference should become a blocker.
- Badly written gates can eliminate valid candidates.
- Exceptions must remain human-controlled.
FoundBefore does not guarantee a match, buyer, supplier, partnership or completed deal. Identity disclosure requires mutual consent, and the controlled pilot does not replace procurement, contracting or human review.
A hard constraint defines eligibility; a score ranks fit only after eligibility is established.