Skip to content
InovagioInovagio

Series · Knowledge layer deep dives

AI-ready data checklist for regulated teams

Twenty-eight checks to run against the data an AI process will read, before it goes live and at set intervals after. Grouped by stage, from sources and owners to documents, mapping and run-time checks, each with why it matters to an examiner and how to test it.

· Published · Updated · 8 min read

On this page

An AI-ready data checklist is a set of pass/fail tests you run against the data one AI process will read, before it goes live and at set intervals after. For a regulated team, each test should answer a question an examiner or auditor could reasonably ask, and leave evidence that answers it. This one has 28 checks in seven groups, each with why it matters and how to test it.

We wrote it for the people who get asked those questions: the head of a lending or loan servicing operation, a model risk manager, a data governance lead. It is the short form of two longer guides. Preparing data for a knowledge layer explains the method behind the first six groups, and data quality checks for AI agents explains the run-time group. For the business case, data hygiene for AI shows what a duplicate record does in an agent's hands, and data cleanup before AI sets out what to fix first. The examples come from Pellmoor Savings Bank (Example company), a community bank where an AI agent prepares commercial loan renewal files and the credit team decides every loan.

What regulators already expect from data

#

None of this is new to banking. The Basel Committee's principles for risk data aggregation, known as BCBS 239, were published on January 9, 2013, and four of them set the bar for aggregating risk data: accuracy and integrity, completeness, timeliness and adaptability (Basel Committee). A decade later, the Committee's progress report on 31 global systemically important banks found that additional work was required at all of them, "seven years after the expected date of compliance", and said boards should take full responsibility for their data governance frameworks (BIS, November 28, 2023). The principle most relevant to an AI build is the one people quote least. Under Principle 2, paragraph 33 asks for integrated data taxonomies and "single identifiers and/or unified naming conventions" for everything from legal entities to accounts, and paragraph 34 gives business and IT owners joint responsibility for the quality of risk data. Checks 6 and 12 below ask the same thing.

Two numbers from the Basel Committee's 2023 progress report: 31 banks assessed, all needing more work, seven years after the expected date of compliance
Source: Bank for International Settlements press release, November 28, 2023.

For AI specifically, Article 10 of the EU AI Act sets data governance duties for the data high-risk systems learn from and are tested on: the relevant design choices, how the data was collected and where it came from (and, for personal data, why it was originally collected), preparation steps such as cleaning and labelling, an examination for bias, and identifying data gaps and how to close them. The data sets it is trained and tested on must be "relevant, sufficiently representative, and to the best extent possible, free of errors and complete" (EU AI Act, Article 10). The Digital Omnibus, Regulation (EU) 2026/1744, amended the article in July 2026 and moved the obligations for the high-risk uses in Annex III to December 2, 2027. Article 10 is written for training and test data rather than the records an agent reads at run time, but expect an examiner to hold those records to the same bar.

In the US, the NIST AI Risk Management Framework asks organizations to document how data was collected and selected, including whether it is representative and suitable for the purpose (MAP 2.3), to monitor systems once deployed (MEASURE 2.4), and to have contingency plans for failures in third-party data (GOVERN 6.2) (NIST AI 100-1, January 26, 2023). State bank examiners have their own framework from the Conference of State Bank Supervisors (CSBS), which our CSBS AI framework checklist maps control by control.

The EU AI Act's Article 10 wording on what high-risk data sets must be, set as a large quotation
Source: EU AI Act, Article 10(3), as amended by Regulation (EU) 2026/1744.

The checklist below doesn't claim to satisfy any of these. It gives you evidence you can point to when someone asks.

Not legal advice. The rules above are summarized from the dated sources linked to each one. Check your obligations with counsel and your regulators.

How to use the AI-ready data checklist

#

Scope it to one AI process and the data that process reads, because a checklist run against the whole data estate produces a long list of red that nobody owns and nobody finishes. At Pellmoor that's the renewal queue: four questions, seven sources, a few thousand documents. Grade each check:

  • Pass: the check holds, and the evidence shows who tested it, when, and what they found.
  • Partial: it holds for some of the data, or the evidence is incomplete. Every Partial gets a named owner and a date.
  • Fail: it doesn't hold.

Our bar for go-live is plain: no Fail in sources, ownership or sensitive data, and no Fail anywhere on a check that blocks the agent. Your risk team may set a stricter one.

1. Sources

#
#CheckWhy it mattersHow to test it
1The AI process and the questions it must answer are written downReadiness is defined per use case; without the questions there is no finish lineThe process owner signs a one-page list of questions
2Every source those questions touch is listedAn unlisted source is a hidden dependency nobody checksTrace each question to the systems that hold its answer; compare with a sample run's task records
3The system of record is named for each critical fieldFixes made in a copy are overwritten by the next feedFor each field, name the system that wins when two disagree
4Each feed is reconciled for completenessRecords that never arrive can't fail a checkCompare the count each source says it sent with the count received, for a week

Most teams skip check 4, and it's the costliest one to miss. The data quality checks guide describes a bank that went more than four years without a check that every relevant transaction was reaching its monitoring system, while a feed error kept some of them out.

2. Ownership

#
#CheckWhy it mattersHow to test it
5Each source has a named ownerData nobody owns doesn't get fixedA person's name, not a team mailbox
6Each domain has a named approver for what its terms mean, whoever your organization makes responsibleTwo teams' definitions of the same word produce two answersThe approver is recorded against each approved term
7Owners have agreed how quickly they fix their sourceA fix with no deadline waits behind everything elseThe time is written into the source's data contract
8Third-party data has a contingency planBought feeds fail too, and you answer for themThe plan says what the AI process does when the feed stops or is wrong

At Pellmoor, the shared drive of borrower files failed check 5 on day one. The credit administration manager took it on, and checks 17 and 18 got easier the same week.

3. Quality

#
#CheckWhy it mattersHow to test it
9Critical fields are profiled against named quality dimensions"Good data" means different things to different teamsResults per dimension (the DAMA UK six, or ISO/IEC 25012) are recorded with a date
10Duplicate records are resolved with evidence, and merges can be undoneA false merge puts one person's obligations on anotherPick ten merged records, show the evidence for each, and undo one
11Every source code maps to one approved termUnmapped codes are silently dropped or guessedCount the codes in the source with no approved term; the count is zero
12Identifiers outlive any one system and contain no personal dataRow IDs change on migration and break every link; a tax ID in an identifier is copied into every logShow that an entity keeps its identifier across a system change

4. Sensitive data

#
#CheckWhy it mattersHow to test it
13Every field the AI process reads is classifiedAccess rules can only follow a classification that existsThe classification is set for each field in the data contract
14Fields the process doesn't need are masked before ingestionAnything indexed can be retrieved and repeatedSearch the index for a known Social Security number pattern; there are no hits
15Retrieval respects the permissions of the person the agent acts forAn agent can otherwise show one user another's documentsAsk the same question as two users with different access and compare the citations
16The origin and original purpose of personal data are recordedPurpose limitation under the GDPR (Article 5(1)(b)) depends on it, and Article 10 of the EU AI Act asks for both for training and test dataEach source's record shows where the data came from and why it was collected

5. Documents

#
#CheckWhy it mattersHow to test it
17One current version of each document can be found, with its effective dateAn agent that finds the old policy applies last year's rulesSearch for each policy title; count the versions that come back
18Near-duplicate documents are removed before indexingCopies crowd better passages out of the resultsRun a duplicate scan on the collection; the residue is reviewed
19Optical character recognition (OCR) quality on scans is sampled by a person, and every extracted value keeps its confidencePublished research found the OCR it tested not adequate for retrieval knowledge basesA person reads twenty scanned pages against their extracted text
20Every passage carries its owner, date, classification and sourceThe agent can cite the page, and access can follow the labelInspect ten indexed passages

Check 19 rests on the OHRBench study, which tested 8,561 document images and found answer quality fell as OCR noise rose (Zhang et al., arXiv 2412.02592, ICCV 2025). Pellmoor's scanned tax returns failed it the first time. A fax had turned a 7 into a 1 in a debt service figure.

6. Mapping and lineage

#
#CheckWhy it mattersHow to test it
21The process's questions run as queries and return the answers an expert expectsIt is the acceptance test for the whole knowledge layerRun them; the expert compares the results with the answers they'd give
22Sources are mapped to the ontology and the result validatesA mapping error spreads to every answer that uses itThe SHACL (Shapes Constraint Language) validation report shows no violations, or each one has an owner
23Every derived value can be traced to its sourceAn examiner will ask where a number came fromPick one figure from an output and follow it back to the page or row
24Each source has a versioned data contract signed by its ownerA source can change shape without anyone noticingThe contract exists, its version matches the live schema, and its owner signed it

Three of these checks have open standards behind them. Check 22 maps with R2RML, the W3C language for mapping relational tables to an ontology (W3C, September 27, 2012), and validates with SHACL (W3C, July 20, 2017). Check 23 usually needs two records: W3C PROV-O for where each fact in the graph came from, and OpenLineage for which job runs read and wrote which datasets. And for check 24, the Open Data Contract Standard added a context section for AI agents in its version 3.2.0 on September 8, 2026 (ODCS releases).

7. Run time

#
#CheckWhy it mattersHow to test it
25Checks run before the agent acts, and each one is set to block, warn or sampleAn agent acts on whatever it is givenThe data contract records the response for each check
26Failed records go to a dead-letter queue with an owner, never a silent dropDropped records are invisible; ignored ones are worseSend a known-bad test record and find it in the queue
27Freshness limits and recertification dates are set, and alerts fireStale data looks exactly like current dataLet a test source go stale and confirm the agent holds its work
28Each task's record shows the records and versions it read, the checks that ran and the rule version appliedAn auditor needs to reconstruct a decision without an engineerPick a task at random and reconstruct it from its record

Read a task record shows what the record behind check 28 looks like in our platform.

When to run it again

#

Passing once tells you about one day. Run it again whenever one of four things happens.

A cycle of four moments to rerun the AI-ready data checklist: before go-live, when a source changes, every quarter, and after a bad record gets through
The evidence from each run goes into the record, so the next examiner sees the history, not just the last result.

The four are before go-live, when a source changes, every quarter and after a bad record reaches the agent. Each run's evidence should be kept, with who ran it and when, because the history is what shows control. A single Pass on a single date shows only that someone looked once, while four quarters of runs with the same owners and the fixes they made show an examiner a process that works.

Where Inovagio fits

#

Several checks map directly to what the platform does. Synesis keeps the approved terms with their approvers (checks 6 and 11), resolves entities with explainable, reversible merges, with a person approving any merge of two people and a second approver if you require one (check 10), runs competency questions as executable queries (check 21), and proposes R2RML mappings from your database schemas that the right person approves before SHACL validates the result (check 22). Every approved fact keeps a PROV-O chain back to its table and column or its page (check 23). Perception keeps the source and confidence on every extracted value and masks personal data before storage (checks 14, 19 and 20). MNEMOS trims every result to the documents the person could open (check 15) and runs durable queues with dead-letter handling (check 26). Phylax keeps the hash-chained audit trail behind check 28. The evidence stays yours, too: your rulebook exports free, in open standards, so what backs checks 6 and 11 doesn't depend on us. The checks about owners and their contracts are yours; no software can sign them for you.

A timeline of the standards and rules behind this checklist, from BCBS 239 in 2013 to the EU AI Act's high-risk obligations in December 2027
Sources: Basel Committee, January 9, 2013; NIST, January 26, 2023; Bitol, September 8, 2026; EU AI Act as amended by Regulation (EU) 2026/1744.

Further reading

#
  • Principles for effective risk data aggregation and risk reporting (BCBS 239), Basel Committee, January 9, 2013: bis.org
  • Progress in adopting the Principles for effective risk data aggregation and risk reporting, BIS press release, November 28, 2023: bis.org
  • EU AI Act, Article 10: Data and data governance, as amended by Regulation (EU) 2026/1744: artificialintelligenceact.eu
  • Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, January 26, 2023: nist.gov
  • OCR Hinders RAG, Zhang et al., ICCV 2025: arxiv.org
  • R2RML: RDB to RDF Mapping Language, W3C, September 27, 2012: w3.org
  • Shapes Constraint Language (SHACL), W3C, July 20, 2017: w3.org
  • Open Data Contract Standard, Bitol at LF AI & Data, v3.2.0, September 8, 2026: github.com

Share

Questions

What people ask.

What is AI-ready data?

AI-ready data is data that is fit for one specific AI use: owned by someone, measured against named quality dimensions, identified consistently, traceable to its source, protected where sensitive, and checked again every time the AI reads it. Readiness is proven per use case, not declared once for a whole company.

How many checks does an AI-ready data checklist need?

Enough to cover each stage the data passes through. This checklist has 28 in seven groups: sources, ownership, quality, sensitive data, documents, mapping and lineage, and run time. A team can add checks its own regulators ask about.

Who should run the AI-ready data checklist?

The owner of the AI process runs it, with each source owner and each domain's approver supplying evidence for their checks. A risk or audit function should review the results before go-live and at each rerun.

How often should we rerun it?

Before go-live, whenever a source the process reads changes, at least every quarter and after any bad record reaches the AI. Keep the evidence from every run, because the history is what shows control.

Does passing the checklist mean we meet the EU AI Act or BCBS 239?

No checklist can make that determination. This one gives you evidence for the data questions those rules raise, such as data origin, completeness, accuracy and governance. Whether you meet a specific rule is for your compliance team and your regulators to decide.

How do I know if my data is ready for AI?

Test the data one AI process will read, not the whole estate: its sources, owners, quality, sensitive fields, documents, mappings and run-time checks. The data is ready for that process when no check that blocks the agent fails and every Partial has a named owner and a date.

The products, industries and examples it covers.

See it on your work

See how one of your tasks runs, start to finish.

A 30-minute walkthrough of one of your workflows, the approval step and the audit record, with the people who build the platform.

We use these details to answer your request. See our privacy policy.

What happens next

  1. 1We reply within one business day to find a time.
  2. 2A 30-minute walkthrough of one of your tasks, start to finish.
  3. 3You leave with a short write-up of what we covered.