GUIDE, STACK, read 13 Nov 2026
BigQuery can check eight of the ten AI readiness conditions natively, and leaves certification and metric definitions to you
BigQuery covers eight of the ten conditions through Knowledge Catalog and its own views
This guide reads Google's documentation on 13 Nov 2026. The checks come from two places: BigQuery itself (descriptions, labels, policy tags, row-level security, INFORMATION_SCHEMA) and the catalog service that Google's pages now call Knowledge Catalog. Per Google, "As of April 10, 2026, Dataplex Universal Catalog is now called Knowledge Catalog." API and IAM names are unchanged, so older runbooks still apply.
The count: five conditions can be checked by a rule Google runs (quality, fresh, lineage, usage, access), three depend on a person (owner, documented, sensitivity), and two returned none found on 13 Nov 2026 in the pages read (certified, metric definition).
Data quality scans check quality and freshness by rule
Google's data quality documentation says you can "automate scans, measure quality scores, and log alerts when records don't meet your requirements." Rules are grouped into dimensions, and freshness is one of them: "Freshness Measures when the data was last updated or whether it's recent enough to be useful." You can write a custom SQL rule or use the freshness_expectation template.
Profile scans help you start. The data profiling page says scans "report key metrics, such as common values, data distributions, and null percentages," and that results can "generate auto data quality rule recommendations." The readiness check is to list the tables an agent reads and confirm each has a scan that ran recently and a score above the threshold you chose. A table with no scan is unchecked.
Descriptions, contacts and labels hold what a person writes
Documentation sits in table and column descriptions, visible in INFORMATION_SCHEMA.TABLES output as OPTIONS(description="..."). Google also offers generated text: the data insights page says the feature "automatically generates descriptions, relationship graphs, and SQL queries from your table and dataset metadata." Treat generated text as a draft until a person approves it.
Ownership has a home. The metadata documentation lists system aspect types including contacts, usage and data-quality-scorecard, and the catalog overview says aspect types "define schemas for aspects, which attach structured metadata to entries, columns, or relationships." The contacts aspect is where a person records who answers for an asset.
Labels are lighter. Per Google, "Labels are key-value pairs that you can attach to a resource," and they apply to datasets, tables and views. You can search by label, but no label has a reserved meaning like certified.
Policy tags, job history and row-level security cover three more checks
Sensitivity: Google's policy tag page says policy tags "let you enforce column-level access control and dynamic data masking on sensitive table data." A person builds the taxonomy and attaches the tags. Automatic discovery of sensitive columns returned none found on 13 Nov 2026 in the BigQuery and Knowledge Catalog pages read.
Usage: INFORMATION_SCHEMA.JOBS is clustered by project_id and user_email, so you can count which users and which tables ran in a period. Access: row-level security "lets you filter data and enables access to specific rows in a table based on qualifying user conditions."
Lineage is available in Knowledge Catalog; another site covers it.
The ten conditions, checked with BigQuery alone
The table maps each condition to Google's documentation.
| Condition | What the platform gives you | Gap |
|---|---|---|
| Named owner | Contacts aspect type in Knowledge Catalog. | Set by a person; no enforcement. |
| Documented | Table and column descriptions; generated descriptions from data insights. | Generated text needs review. |
| Certified | None found on 13 Nov 2026. A custom aspect type could hold a value. | You design and fill it. |
| Quality | Data quality scans with rules and scores. | Scan per table to set up. |
| Fresh | Freshness dimension in data quality rules. | Rule written per table. |
| Sensitivity | Policy tags in a taxonomy. | Manual; auto-discovery none found on 13 Nov 2026. |
| Lineage | Data lineage in Knowledge Catalog (covered elsewhere). | Outside Google Cloud needs events. |
| Usage | INFORMATION_SCHEMA.JOBS and the usage aspect type. | Jobs, not named report viewers. |
| Metric definition | None found on 13 Nov 2026 in the pages read. | Held in another tool. |
| Access | Row-level security and policy tag access. | Edition limits can apply. |
BigQuery leaves certification, metrics and cross-platform labels to another tool
Certification is the largest gap. No reserved certified status appears in the documentation read, so teams build an aspect type and keep it current themselves. Metric definitions are the second gap, because the pages read describe tables, scans and policies, not governed metrics.
Labels also stay inside Google Cloud. A team with Snowflake or Databricks beside BigQuery has three label systems to reconcile. The ranking below lists the tools whose evidence names BigQuery.
15 of 17 ranked tools name BigQuery in their evidence
This table is built from the systems each tool names, read 13 Nov 2026. A tool that names BigQuery can label its assets only as far as its own documentation shows; the marks come from the Readiness Coverage Matrix.
| Rank | Tool | Named as | Reach | Conditions by rule |
|---|---|---|---|---|
| 1 | OvalEdge | Google BigQuery | 5 | 6 of 10 |
| 2 | Euno | BigQuery | 6 | 8 of 10 |
| 3 | DataHub | BigQuery | 5 | 6 of 10 |
| 4 | OpenMetadata | BigQuery | 6 | 7 of 10 |
| 5 | Atlan | Google BigQuery | 6 | 8 of 10 |
| 6 | Secoda | BigQuery | 5 | 8 of 10 |
| 7 | Databricks Unity Catalog | BigQuery | 5 | 7 of 10 |
| 8 | dbt | BigQuery | 5 | 6 of 10 |
| 9 | Alation | Google BigQuery | 5 | 7 of 10 |
| 10 | Ataccama | BigQuery | 4 | 5 of 10 |
| 12 | Monte Carlo | BigQuery | 4 | 5 of 10 |
| 13 | Snowflake Horizon | BigQuery | 3 | 6 of 10 |
| 14 | Precisely | Google BigQuery | 3 | 5 of 10 |
| 15 | Actian | Google BigQuery | 2 | 6 of 10 |
| 17 | Collibra | Google BigQuery | 3 | 5 of 10 |
Sources
- Google Cloud: Auto data quality overview, read 13 Nov 2026
- Google Cloud: Data profiling overview, read 13 Nov 2026
- Google Cloud: About Knowledge Catalog metadata model, read 13 Nov 2026
- Google Cloud: About metadata in Knowledge Catalog, read 13 Nov 2026
- Google Cloud: Data insights for structured data, read 13 Nov 2026
- Google Cloud: Introduction to labels, read 13 Nov 2026
- Google Cloud: Best practices for policy tags, read 13 Nov 2026
- Google Cloud: INFORMATION_SCHEMA.JOBS view, read 13 Nov 2026
- Google Cloud: Row-level security, read 13 Nov 2026
- Google Cloud: INFORMATION_SCHEMA.TABLES view, read 13 Nov 2026
Last reviewed 13 Nov 2026.