GUIDES, read 13 Nov 2026
12 guides to checking readiness, written for the lead who must say which data is ready
AI-ready for a table is not AI-ready for a metricGlossary
- AI-ready for a table is not AI-ready for a metricA table is AI-ready on five conditions: owner, description, passing tests, freshness and use.
- Certified is not the same as AI-readyA certificate records a sign-off on one date, while AI-ready data must pass its owner, quality, freshness and access checks today.
- How a readiness label reaches an agent over MCPA readiness label helps an agent only if it comes back in the tool response, can be filtered on and follows the person asking.
- Readiness decays, so a label needs a re-check and a withdrawal ruleA readiness label is true on the day it is set and drifts afterward.
- Who owns the readiness labelA readiness label has three jobs that teams blur: who sets it, who can withdraw it, and who is told when it changes.
- Checking AI readiness on Snowflake with its own featuresOf the ten AI-readiness conditions, Snowflake's own documentation covers nine: comments, tags, data metric functions, classification, ACCESS_HISTORY (365 days), semantic views and masking policies.
- Checking AI readiness on Databricks with its own featuresDatabricks' own documentation covers all ten AI-readiness conditions in Unity Catalog: seven by rule (certification automations, anomaly detection, Data Classification, query and lineage tables, ABAC policies), three by a person (owner, description, metric views).
- Checking AI readiness on BigQuery with its own featuresGoogle's BigQuery and Knowledge Catalog (formerly Dataplex Universal Catalog) documentation covers eight of the ten AI-readiness conditions: data quality scans with a freshness dimension, profile scans, contacts aspects, policy tags, row-level security and INFORMATION_SCHEMA.JOBS.
- Checking AI readiness in dbt with its own featuresdbt's own docs cover five of the ten AI-readiness conditions in project files: documented, tested, fresh, traceable and metric-defined.
- Checking AI readiness in Power BI with its own featuresMicrosoft's Power BI documentation covers seven of the ten AI-readiness conditions natively: documented, certified, fresh, sensitivity, lineage, usage and metric definition.
- Checking AI readiness in Tableau with its own featuresTableau's help pages cover six of the ten AI-readiness conditions natively: owner, documented, certified, quality, sensitivity and lineage.
- Checking AI readiness in Looker with its own featuresGoogle's Looker documentation covers six of the ten AI-readiness conditions natively: documented, certified, quality, usage, metric definition and access.
Last reviewed 13 Nov 2026.