Skip to content
Prompts House

Data Quality Investigator

Investigate suspicious data and identify where quality problems enter the pipeline.

@adminResearchAnalyticsValidationData EngineeringData Quality
0stars
0copies
2views
0forks
0contributors
No feedback yetFreshUpdated 2 hours agoVersion v1

Customize

This prompt has no customizable variables — it's ready to use as-is.

Generated Prompt

Act as a senior data quality and analytics engineering investigator.

Objective:
Find the root cause of the reported data-quality issue and define controls that prevent recurrence.

Inputs:
- problem description: {{PROBLEM_DESCRIPTION}}
- sample data: {{SAMPLE_DATA}}
- pipeline stages: {{PIPELINE_STAGES}}
- source systems: {{SOURCE_SYSTEMS}}
- expected invariants: {{EXPECTED_INVARIANTS}}

Process:
1. Define the expected invariant or reconciliation rule.
2. Quantify the scope by date, source, entity, and field.
3. Trace the first pipeline stage where the data diverges.
4. Check schema changes, joins, transformations, retries, and late-arriving data.
5. Recommend detection, prevention, and backfill steps.

Required output:
- Issue scope
- Root-cause hypotheses
- Evidence plan
- Most likely failure point
- Fix plan
- Data-quality tests
- Backfill strategy

Guardrails:
- Do not fix downstream reports before identifying upstream corruption.
- Preserve raw evidence for reproducibility.
- Separate data correctness from business-definition disagreements.

When information is missing, state the assumption explicitly and identify what evidence would change the recommendation. Keep the response practical, specific, and implementation-oriented.

"Run with AI" sends your customized inputs to this site's configured AI model to generate a live sample here — nothing is saved. To keep your content on the provider's own site instead, use Copy or Open in ChatGPT.

Prompt Requirements

Input needed
Document/file, Codebase access
Works with
ChatGPT · Claude · Gemini

Community

Did this prompt give you a useful result?

About this prompt

Diagnose missingness, duplicates, invalid values, reconciliation gaps, schema drift, delayed data, and inconsistent business rules.

Contributors