CIOPages
All RFP questions

RFP Questions · AI Governance

Bias, fairness & content provenance questions to ask a software vendor

105 bias, fairness & content provenance questions for the RFI, the RFP and the finalists, with scoring guidance, in one Excel workbook.

What this module is for

These are the bias, fairness & content provenance questions to put to any software vendor, whatever the product does. Add them to an RFP next to the questions about the product itself.

What it covers. Questions on bias and fairness testing, how results are measured across demographic groups, where training data came from, content provenance, and what the vendor does when you find bias after deployment.

A selection usually runs in three rounds. The module has questions for each:

  • RFI, to the long list. 25 questions screen out vendors that fall short.
  • RFP, to the shortlist. 41 questions ask for detail.
  • Deep dive, to the finalists. 39 questions ask for evidence.

Each question comes with why it matters, what a good answer looks like and the red flags. The workbook scores the answers 0 to 5, weights them and totals them by round and section.

3 questions from the module

From the RFI round. The first shows part of the guide each question carries; the workbook adds follow-ups, a response format, a weight and a score column.

1. Describe your methodology for evaluating bias in the model(s) powering your product. Include the benchmarks and datasets used, the cadence of re-evaluation, and triggers for out-of-cycle reviews.

Why it matters. Bias claims without documented methodology cannot be validated or compared across vendors. Buyers need to know whether the vendor treats bias evaluation as a continuous process tied to model changes, not a one-off exercise.

Good answer
  • Names specific public or internal benchmarks used (e.g. BBQ, BOLD, CrowS-Pairs, WinoBias).
  • Describes statistical tests and significance thresholds used.
  • Defines a regular cadence for re-evaluation (e.g., per model release, quarterly).
Red flags
  • Generic claims of 'rigorous testing' with no named benchmarks or metrics.
  • Treats bias evaluation as a one-time pre-launch activity with no defined re-evaluation cadence.
  • Cadence is described as 'as needed' with no objective triggers.

2. Which fairness metrics (e.g. demographic parity, equalized odds, predictive parity, calibration) do you report for your model(s), and why were those metrics chosen?

Why it matters. Common fairness metrics cannot all be satisfied at once when base rates differ between groups and prediction is imperfect (Kleinberg, Mullainathan and Raghavan, 2016; Chouldechova, 2017). The vendor's choice of metric is a trade-off the buyer should see.

3. Describe the sources and categories of training data used for the model(s) powering your product (e.g. licensed datasets, web crawl, customer data, synthetic data, partner data).

Why it matters. Training data provenance bears on bias, IP, and privacy risk. Without a description of data sources, the buyer cannot assess bias or copyright exposure.

What the module covers

  • Bias evaluation methodology & cadence (22)
  • Fairness metrics reported & demographic slices (24)
  • Training & evaluation data provenance (32)
  • Customer-facing remediation & escalation (27)

This module is one of 7 in AI Governance. All 7 in one workbook: $499

Questions about this module

How many bias, fairness & content provenance questions are there?

105: 25 for the RFI stage, 41 for the RFP and 39 deep-dive questions for the finalists.

What comes with each question?

Why it matters, what a good answer looks like, the red flags, follow-up questions, the response format, whether most buyers treat it as mandatory, and a suggested weight for scoring.

Which license do I need?

The Enterprise License covers any number of evaluations inside one organization. The Consultancy License covers use with any number of clients. Neither allows reselling or republishing the questions.

Included in these RFP packages

Each package carries this module's screening questions next to its questions about the software.

Related

Keep reading

Buyer Guide
AI Governance & Responsible AI
Job 02
Govern the AI already in use

Staff already use AI tools nobody approved, and most SaaS products now ship AI features by default.

Free checklist
AI-Suggested Package Vetting Checklist

A checklist for vetting a package an AI coding assistant suggested, from whether it exists to its license and CVEs.