Data Quality Audit Summary

Summarises a data quality scan for the data owner.

ConfidentialGenAIData governance · by Nurul Aisyah Rahman · v1.8

★ 4.6 640 runsUpdated 2026-07-18

Prompt template

3 variables

You are helping a data steward review the Dataplex data quality results for a lakehouse table. Summarise what failed, what it affects downstream, and what the steward should do.

Table: {table_name}
Data quality scan results:
{dq_results}
Downstream consumers: {consumers}

Return:
1. Overall verdict (Pass / Pass with issues / Fail)
2. Failed rules, with the share of rows affected
3. Likely root cause for each, labelled as a hypothesis
4. Downstream impact on the listed consumers
5. Recommended actions, and whether the table should be held from publishing

{table_name}{dq_results}{consumers}

Playground

Simulated sandbox

{table_name}{dq_results}{consumers}

Ownership and sensitivity

Owned by

Group Finance Financial Reporting

Accountable owner: Nurul Aisyah Rahman

Who approves access

Owner, Financial Reporting, Nurul Aisyah Rahman

Confidential

Business-sensitive. Models and data products scoped to named business units.

Entitlement per business unit, approved by the owner; conditions attach.

GenAI: Generates text; prompt screening for customer data and output review apply.

Example input & output

Example input

{table_name}: abmb-lakehouse.gold.deposit_balances_daily
{dq_results}: completeness(balance_myr) 99.98% PASS; uniqueness(account_token, as_of_date) 100% PASS; range(balance_myr >= -5000) 99.2% FAIL; freshness 26h FAIL (threshold 24h); referential(branch_code in branch_atm_network) 98.7% FAIL
{consumers}: deposit-flow-forecaster, ALCO liquidity dashboard, regulatory-returns-agent

Example output

1. Verdict: Fail. 2. Failed rules: range check on balance_myr (0.8% of rows below -5,000); freshness at 26 hours against a 24-hour threshold; referential check on branch_code (1.3% of rows not in branch-atm-network). 3. Likely causes (hypotheses): overdraft-linked current accounts were added to the feed without updating the range rule; the core banking extract ran late after the weekend batch; branch codes for the three branches merged in July have not been retired in the reference table. 4. Impact: deposit-flow-forecaster would train on a stale day; the ALCO dashboard shows balances one day old; regulatory-returns-agent must not use this snapshot for the monthly return. 5. Actions: hold publishing of today's partition; confirm the overdraft product scope with Finance and update the range rule; raise a ticket with Group IT on the extract delay; ask Operations to update the branch reference table.

Details

Author: Nurul Aisyah Rahman
Version: v1.8
Rating: ★ 4.6
Runs: 640
Licence: BU Restricted
Updated: 2026-07-18

Powered by

policy-rag-copilot →

This template is tuned for the target model above. Forked copies keep the same target model binding until republished.

Community · 0 threads

Questions, findings and requests from the business units that use this asset. Owners reply here; threads with upvotes surface to the owning team's inbox.

No threads yet. Be the first to ask, or to share what you found.