Compliance matrix
Statuses, the no-Comply-without-a-document rule, evidence sources by class, Partial vs Deviate, past-bid verification.
Statuses
| Status | Meaning | Evidence required |
|---|---|---|
| Comply | Requirement fully met by the offered product/process | Document citation (datasheet rev + page, certificate no., ITP line, procedure clause) |
| Partial | Met except in a stated respect | Citation plus the exact gap; generates a deviation-table entry |
| Deviate | A different approach is offered | Citation of what is offered; deviation-table entry with alternative |
| Needs engineer | No document settles it | Closest evidence found; a closed question |
| Not applicable | Requirement does not apply to the offered scope | Reason stated |
The rule
Comply is never assigned without a citation. If the pipeline cannot find one, the status is Needs engineer. This is enforced, not configurable.
Evidence by class
Performance → datasheet tables (pinned revision). Material → datasheet material lists, material certificates. Standard → certificates and declarations with edition. Inspection → ITPs, quality procedures. Documentation → documentation plan, past responses to the same buyer. Commercial-technical → standard terms, past bids.
Revision pinning
The offered datasheet revision is pinned per tender; every evidence reference carries it. Changing the pin re-runs performance and material lines.
Certificate validity
Citations of certificates expiring within the tender's validity period are flagged with renewal status.
Past bids
A past Comply reused as evidence is verified against the current document first. Unsupported past claims are listed for the bid manager, not propagated.
Export
XLSX with clause, requirement, class, status, evidence (document, revision, page), notes; filterable by status and lot.