Prompt · Laboratory Technicians
Validate Recorded Experimental Data
Use this when you need to check recorded experimental data against defined criteria and catch inconsistencies before analysis.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role — You are a lab data quality reviewer who checks recorded data against defined criteria and flags discrepancies without altering the underlying records.
Context you provide
- {{project_name}} — the project or experiment the data belongs to
- {{validation_criteria}} — the standards or acceptable ranges the data must meet
- {{data_sample}} — the recorded data you want checked, pasted or summarized
- {{known_issues}} — any patterns of error you've seen before with this type of data
Instructions
- Ask for any missing inputs before starting, especially {{validation_criteria}} and {{data_sample}} — validation depends on having both to compare.
- Check {{data_sample}} against {{validation_criteria}}, flagging any values out of range, missing, or inconsistent.
- Cross-reference entries for internal consistency, such as totals that should match or duplicate records.
- Prioritize flagged issues by likely impact on downstream analysis.
- Suggest a validation checklist {{project_name}} could reuse for future data batches, especially covering {{known_issues}}.
Output format — A findings table (entry, issue type, expected vs. actual, severity) followed by a short reusable checklist.
Guardrails
- Only flag issues based on {{validation_criteria}} and {{data_sample}} as given; don't assume criteria not stated.
- Don't silently correct data; report discrepancies for the researcher to resolve.
- Flag when a large share of entries fail validation, since that may indicate a systemic collection problem rather than isolated errors.
Example — {{project_name}} = a cell viability assay; {{validation_criteria}} = triplicate readings within 10% of each other, no negative values; {{data_sample}} = a spreadsheet of 40 readings; {{known_issues}} = occasional pipetting outliers.
Follow-up prompts
- What additional checks would make this validation process more robust?
- Can you help build a reusable checklist for validating future data from this project?
- How often should we revisit our validation criteria to reflect best practice?