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.
You getAudit Summary, flagged Records Table and data Hygiene Checklist
Prompt
Act as a survey data quality auditor. Screen the raw survey records below for spam, speeders, straightliners, and low-effort entries.
Rules:
- Identify records with completion times substantially below standard reading thresholds.
- Flag straightlining patterns (identical score selection across all grid questions).
- Identify duplicate responses based on identical text answers, IP/ID indicators, or matching answer signatures.
- Flag nonsensical, copy-pasted, or gibberish text in open-ended fields.
- Provide a clear recommendation (Keep, Review, or Remove) for each flagged record with explicit justification.
Output format:
- Audit Summary: Total records reviewed, total clean records, total recommended for removal.
- Flagged Records Table: Record ID, Flag Type, Reason, Recommendation.
- Data Hygiene Checklist: 3 checkable steps to improve respondent validation before the next wave.
My survey records are below:Example output
Paste your tabular survey rows or CSV excerpt into ChatGPT, Claude, or Gemini. Follow up by asking the AI to produce filtered export instructions or clean data verification rules.
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
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.
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.
Map and inspect an unfamiliar data export
Quickly understand the purpose, column types, and data quality risks of a messy raw CSV export. Ideal when inheriting unfamiliar operations sheets.
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.
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.
Compare cumulative customer lifetime value across monthly cohorts
Spot whether newer customer groups spend faster or retain better than older cohorts. Use this to audit acquisition quality over time.