Ask useful transparency questions during AI procurement

When to use this guide

A procurement team receives a compliance brochure but no explanation of how the purchased API's outputs are marked.

This is a fictional implementation scenario. The procedure below is Article 50 Hub's suggested working method, not a prescribed legal form, a customer result or a claim that every step is an additional statutory requirement.

Review procedure

1. Describe the intended deployment and output paths to the vendor using non-sensitive facts.

2. Ask which controls are implemented and where customer integration work is required.

3. Request versioned documentation and representative verification evidence.

4. Record unsupported claims and unresolved responsibilities before making the internal decision.

What the example review finds

• The brochure does not cover the API endpoint being purchased.

• The vendor's example requires a UI component absent from the planned integration.

Keep these example observations separate from your own results. An unknown or untested state should stay open until the relevant evidence has been inspected.

Fields for your working record

• Intended use

• Vendor control

• Customer dependency

• Evidence reference

• Unresolved claim

Use the downloadable blank worksheet linked on this page to connect the observed behavior with the deployed system. Add a reviewer, date, evidence reference, unresolved questions and a next action. The worksheet is editable locally and does not upload your records to Article 50 Hub.

Completion and handoff

Close the task only for the scope actually reviewed. Preserve the result that another authorized reviewer can reproduce, identify the owner of remaining work, and record a retest when the implementation changes. A completed worksheet is not a substitute for the underlying evidence.

Decision boundary

A questionnaire does not validate a vendor, determine applicability or authorize a purchase or contract.

The official references below provide legal or technical context. Resolve applicability and exception questions with the responsible qualified reviewer; use the product's tools to organize implementation work within that assessment.