PQC Contract Clause Checklist.

Required input fields.

• Vendor type (required): SaaS, Cloud, PKI/certificate provider, Network/VPN, ...
• Data sensitivity (required): No sensitive data, Business confidential, Regulated or long-lived
• Cryptographic role (required): Unknown, Consumes crypto protocols, Provides cryptographic service
• Contract term (required): Less than 1 year, 1-3 years, More than 3 years

Data handling: this interface uses the L2ET protected same-origin instrument engine. Do not enter confidential, regulated, privileged, incident, medical or sensitive operational data.

Evidence Matrix logic.

Maps vendor type, data sensitivity and cryptographic role to clause themes around inventory, algorithm agility, roadmap, notification, testing and audit evidence.

Source families

Assumptions

• This is a thematic checklist.
• Legal drafting requires counsel.
• Jurisdiction and sector requirements may differ.

PQC contract clause checklist.

The generated artifact includes findings, assumptions, limitations, recommended next actions and exportable structured output.

Export options

Example input and output.

Example input

Critical SaaS supplier with business confidential data and unknown crypto role.

Example output

Outputs clause themes for inventory disclosure, roadmap, weakness notification, migration assistance and audit evidence.