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.
You getClassification Table, pipeline Bug Root-Cause Checks and modeling Treatment
Prompt
Act as a senior data quality analyst. Review the anomalous records and data summary below to separate true statistical outliers from pipeline or ingestion bugs.
- Group anomalies into two categories: Likely Pipeline Bugs (formatting, duplicate summing, default values, sensor failure) and Genuine Business Outliers.
- State the exact diagnostic signals that support each classification (such as round numbers, repeated timestamps, or mismatched foreign keys).
- Recommend an immediate filtering rule or transformation for the data model.
Output format:
1. Classification Table: Record Identifier, Value, Classification, Primary Reason
2. Pipeline Bug Root-Cause Checks: Bulleted checklist for engineers
3. Modeling Treatment: Specific filtering or imputation recommendation
The sample data and context are below:Example output
Paste your suspect data rows, metric summaries, or column distributions into ChatGPT, Claude or Gemini right after the prompt. As a follow-up, ask the model for a SQL CASE statement to handle the identified cases.
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.
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.
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.
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.
Plan an exploratory data analysis from scratch
Generate a practical exploratory data analysis plan when starting with unfamiliar data. Frame key business questions, data hygiene checks, and visualization priorities.
- Map and inspect an unfamiliar data export
- Audit driver-based models for compounding optimism bias
- Calculate survey demographic weights to fix sample skew
- Clean inconsistent date formats and text categories
- Compare cumulative customer lifetime value across monthly cohorts
- Diagnose circular loops and friction steps in signup funnels