For procurement and purchasing
A requirement you cannot check is not a requirement. The assistant brings up the regime behind it and shows what disclosure can actually be reviewed once the bids arrive.
Material before the tender
- AI Act duties per risk class, so the requirement cites the article rather than an interpretation.
- Data protection, information security and sustainability with source and entry into force.
- US and European regimes side by side when the supplier sits outside the EU.
At evaluation
- A system card is a disclosure at a fixed address — it can be re-read and compared between bids.
- Read dates and the change journal let you show which state of the rules the requirement was written against.
- The same node in four languages, so bidders in several countries read the same text.
FAQ
- Can we cite a node in the tender documents?
- Yes. The addresses are fixed and the pages open, but the requirement should always also point at the official source behind the node.
- Does the assistant assess a bid?
- No. It shows the regime and what it requires. The evaluation belongs to the contracting authority.
- What makes a system card a usable requirement?
- It is a published disclosure at a fixed address with a hash, so the same card can be checked again afterwards.
Next step
Three ways to put the register to work in your own practice.
Start with your task
Litigation
Find support in a judgment
Search guiding decisions, see what became final and follow changes in the law.
In-house, deals
Map the rules in a transaction
Move from theme to act and on to the article that carries the duty.
Compliance
Assess the risk in a process
Risk scoring per legal area, with the sources behind every score.