Differentiate structural null values from missing data
Identify whether null values represent expected business logic or export dropouts. Use it when auditing schema quality or preparing datasets for modeling.
You getNull Audit Table, root-Cause Diagnosis and dbt or SQL Assertion Rules
Prompt
Act as an analytics engineer. Review the table schema, null distribution stats, and sample records below to distinguish structural nulls from true missing data.
- Classify every null occurrence as either Structural (expected non-applicability based on entity type or status) or Data Defect (pipeline dropout, network drop, unmapped field).
- Define dependent conditions that explain why the field is legitimately blank (such as null cancellation dates for active subscriptions).
- Specify data quality validation tests to catch future unintended nulls without alerting on expected ones.
Output format:
1. Null Audit Table: Column Name, Observed Null %, Classification, Business Condition
2. Root-Cause Diagnosis: Explanation for fields identified as defects
3. dbt or SQL Assertion Rules: Specific conditional tests to monitor incoming pipelines
The table schema and null summaries are below:Example output
Paste your table schema, column descriptions, and null counts into Gemini, Claude or ChatGPT. As a next step, ask the model to produce generic dbt tests or Great Expectations expectations based on the output.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Create an anomaly investigation checklist for analytics teams
Run a disciplined diagnostic process before investigating metric shifts. Use this checklist whenever unexpected data spikes or drops appear in reports.
Separate true anomalies from pipeline data errors
Classify extreme values as either legitimate business events or pipeline errors. Use it when high or low metrics distort downstream reporting.
Triage sudden metric spikes for event tracking bugs
Diagnose whether an unexpected surge in product analytics is real user activity or broken telemetry. Use this before sharing anomalous growth numbers.
Clean inconsistent date formats and text categories
Turn chaotic timestamp formats and varied categorical spellings into unified standards. Use it when mismatched export values break dashboards.
Screen survey data for duplicate and low-effort responses
Audit raw survey records for gibberish, straightlining, rapid completion times, and duplicate entries to clean your dataset.
Build standardized KPI definition templates for teams
Standardize team metrics and eliminate conflicting calculations for critical business KPIs. Use this before building dashboards or quarterly reports.
- Compare cumulative customer lifetime value across monthly cohorts
- Estimate potential revenue recovery across funnel drop-off points
- Evaluate past forecast variances to set accurate targets
- Map inconsistent export columns to target schemas
- Translate statistical model outputs into plain business decisions
- Compare planned versus actual project hours