Mandatory criteria

Nothing excludes a supplier until you say so

A requirement becomes an exclusion rule only after a human confirms it, and missing information surfaces as a gap rather than a silent rejection.

Overview

Human-confirmed mandatories

An automated exclusion is invisible when it is wrong — the supplier who should have been invited simply never appears, and nobody knows to look. SpiderNet requires a person to confirm which requirements are genuinely mandatory before any of them can exclude anyone, and treats unknown information as a gap to investigate rather than grounds for rejection.

What it does

Exclusions you chose deliberately

A requirement excludes only after human confirmation.

Unknown information surfaces as a gap, never a silent exclusion.

Mandatory criteria sit outside the weighted score.

Qualification status is separate from relevance.

No supplier disappears without a recorded reason.

How it works

How confirmation works

1Extraction proposes which requirements look mandatory
2A reviewer confirms, adjusts or rejects each one
3Confirmed criteria become exclusion rules
4Unconfirmed or unknown items are shown as gaps
FAQ

Common questions

Can the system exclude a supplier on its own?

No. Autonomous exclusion without human-confirmed mandatory criteria is explicitly out of scope.

What happens when data is missing?

It surfaces as a gap for someone to check, rather than counting against the supplier silently.

Do mandatory criteria affect the score?

No — they sit outside the weighted score and determine qualification status only.

Explore more

More of what SpiderNet does

Get started

See one of your own SOWs shortlisted

Request a demo to turn a real statement of work into an evidence-backed supplier shortlist.