IT VENDOR CLAIMS-TO-EVIDENCE WORKSHEET
Yenra | https://yenra.com/vendor-product-information-technology/
Use: complete requirements before demos. Duplicate a REQUIREMENT block for each.
Send the same tasks and constraints to competing vendors. Empty evidence is an
open question, not a pass. Use synthetic or approved test data.

COMPARISON CONTEXT
Business outcome / owner / decision date:
Users / volume / environment / integrations / access constraints:
Vendor / product / edition / version / quote date:
Mandatory requirements and acceptable exceptions:

REQUIREMENT
ID / task / mandatory or preferred / business owner:
Vendor's exact claim and source URL/document/version/date:
Evidence type: documentation / demonstration / trial / contractual commitment:
Supported configuration and dependencies:
Acceptance condition defined before test:
Test inputs, normal case, exception and recovery case:
Expected result / observed result / evidence location / test date:
Status: verified within stated scope / partial / failed / untested / roadmap:
Gap / remedy / responsible party / cost / due date / retest:

FICTIONAL TEST: ORDER INTEGRATION
Create a two-item order, update its address, interrupt and retry a transfer in
an authorized test environment. Compare IDs, quantities, address and status.
Check duplicates, error reporting and reconciliation. Record edition/version.

COMMERCIAL CHECK
Quoted edition matches trial:
Add-ons, usage limits and overages:
Implementation and ongoing integration ownership:
Support hours and version lifecycle:
Export formats, attachments, limits, assistance and exit charges:
Decision, approved exceptions and conditions requiring a future review:
Source context: CISA Secure by Demand covers software security procurement;
this broader worksheet is an original aid for functional and commercial evidence.