01 · The Question
Can AI Find Mistakes Made When Research Data Were Entered?
You have transferred 400 paper-based questionnaires into a spreadsheet. During inspection, you notice that one student's age is recorded as 220, another respondent has a score of 8 on a five-point scale, and several dates appear in inconsistent formats.
Could generative AI examine the dataset and identify possible typing mistakes, incorrect codes, or values entered into the wrong columns? Could it also determine what the correct values should be?
The difficulty is that a suspicious value is not necessarily a data entry error. Some mistakes are obvious because they violate established rules, while others remain plausible and may escape detection entirely.
03 · What You Need to Know
How Generative AI Can Help Detect Data Entry Errors
What Is a Data Entry Error?
A data entry error occurs when information is recorded incorrectly during transcription, coding, importation, or transfer from one data source to another.
For example, a participant selects 3 on a questionnaire, but the researcher enters 8 into the spreadsheet. The spreadsheet no longer faithfully represents the source response.
Not every problematic value is a data entry error. A participant may misunderstand a question, provide an inaccurate answer, or select an option inconsistent with another response. These problems originate at different stages of data collection and require different remedies.
Data entry error
The recorded value differs from the information contained in the original source.
Response or measurement error
The original recorded response itself may be inaccurate, misunderstood, or affected by the measurement process.
This distinction matters because correcting a transcription mistake restores source information, while changing an original participant response requires a separate methodological justification.
Which Data Entry Errors Can AI Help Identify?
Generative AI can help researchers develop checks for several common problems. Some are detectable through explicit rules, while others require additional evidence.
| Potential Error |
Example |
How to Investigate |
|
Out-of-range entry
|
A Likert item contains 9 when only 1–5 are permitted. |
Compare the value with the instrument and original response. |
|
Digit transposition
|
Age 24 is entered as 42. |
Check the original source because both values may be plausible. |
|
Incorrect category code
|
A program is coded 4 instead of its documented code 3. |
Compare the recorded category with the codebook and source record. |
|
Wrong-column entry
|
A response appears under an adjacent questionnaire item. |
Inspect source alignment and the data entry procedure. |
|
Formatting or type error
|
A numeric response is stored as text or a date is misinterpreted. |
Verify the original representation and import settings. |
|
Missing-value coding error
|
A documented missing code of 99 is treated as a valid score. |
Check the variable's missing-value conventions. |
The table illustrates why error detection and error confirmation should remain separate. A value of 42 might be correct even when most participants are younger, while a response of 9 on a five-point item is invalid under the specified coding scheme.
How Can AI Apply Range and Type Validation?
Range validation checks whether a value falls within permitted boundaries. Type validation checks whether it has the expected representation, such as an integer, date, or text category.
For example, a researcher can provide the codebook and ask AI to generate Python or R code that flags non-integer values or entries outside the permitted response range.
These checks are usually best executed through deterministic software functions rather than repeated conversational judgments. The AI can help construct and explain the rules, while the script applies them consistently.
OpenRefine's official documentation describes faceting and filtering tools that help researchers inspect unexpected values, inconsistent types, and errors created during transformations. Its numerical facets can expose values outside the expected distribution, while text facets can reveal inconsistent codes.
The related task of identifying missing and impossible values provides the foundation for these checks. However, a value that passes validation may still have been entered incorrectly.
Can AI Detect Errors That Fall Within the Valid Range?
Sometimes, but this is considerably more difficult.
Suppose a participant selects 2 on a five-point questionnaire item, but the data entry operator records 4. Both values are permitted, so a range check will not identify the mistake.
An AI system might flag the response if it differs substantially from related items. However, that inconsistency is not proof of incorrect entry. Participants can legitimately express different opinions across questionnaire statements.
Comparing the entered value with the original questionnaire is much stronger evidence than predicting what the participant probably intended.
For manually transcribed datasets, independent double data entry or source-to-dataset verification may identify errors that statistical screening cannot detect.
Can AI Identify Values Entered Into the Wrong Column?
AI can help investigate column shifts, inconsistent row structures, and values that appear incompatible with their assigned variables.
Suppose a questionnaire contains an age field followed by a five-point satisfaction item. A value of 21 appearing in the satisfaction column may indicate a misplaced age entry.
However, detecting one suspicious value does not establish how the row became misaligned or which other fields may have been affected.
The researcher should inspect the source questionnaire, import procedure, and surrounding records. When a systematic import problem is confirmed, correcting the underlying transformation may be more reliable than editing individual cells.
Can AI Identify Date and Decimal Errors?
Yes. AI can help develop checks for inconsistent date formats, invalid dates, unexpected decimal separators, and unit mismatches.
For example, the date 03/04/2026 could mean March 4 or April 3, depending on the format used. A chatbot should not silently choose one interpretation.
Similarly, a recorded value of 1.500 might represent one and a half or one thousand five hundred under different conventions.
These ambiguities should be resolved through documented collection conventions, original records, and import settings rather than assumptions about the most familiar format.
How Can AI Help Verify Corrections?
One practical approach is to request an error report rather than a corrected dataset.
The report should identify the record, variable, original value, violated rule, possible explanation, and verification status. A proposed replacement should be recorded separately from the verified correction.
For example, the report might identify a response of 8 on a five-point item and suggest checking for a transcription error. If the original questionnaire shows 3, the researcher can authorize changing the entered value to 3.
If the original source cannot be recovered, the researcher should document the unresolved value and follow an appropriate missing-data or analytical procedure.
This approach supports verification of every AI-assisted correction and avoids treating a model's plausible suggestion as evidence.
Why Is Preserving the Original Dataset Important?
Data entry corrections should be traceable to the original information. If AI overwrites source values, researchers may lose the ability to distinguish verified corrections from unsupported changes.
OpenRefine provides a history mechanism for reviewing and undoing data transformations. Such functionality illustrates the value of maintaining a record of what changed, although the research team must still preserve appropriate source files and decision documentation.
For AI-assisted workflows, maintain an audit trail of corrections that records the original value, corrected value, source of verification, and reason for the change.
The objective is not simply to eliminate suspicious values. It is to restore the dataset's correspondence with the information actually collected.
04 · A Practical Example
Detecting Data Entry Errors in a Student Questionnaire
Hypothetical Example
Checking an Academic Self-Efficacy Dataset
A researcher manually enters 250 paper questionnaires into a spreadsheet. The instrument contains demographic questions and 15 academic self-efficacy items scored from 1 to 5.
The researcher uses an AI assistant to generate validation checks and produces a separate report of potentially incorrect entries.
| Record |
Entered Value |
Source Verification |
Decision |
| P018, SE04 |
8 |
Original questionnaire shows 3. |
Correct to 3. |
| P047, Age |
42 |
Original questionnaire shows 24. |
Correct to 24. |
| P093, SE11 |
1 |
Original questionnaire also shows 1. |
Retain. |
| P126, SE07 |
Blank |
Original questionnaire is blank. |
Preserve missingness. |
| P204, Age |
220 |
Original questionnaire is unavailable. |
Flag as unresolved. |
The first two cases are confirmed transcription errors because the original questionnaires establish the correct values. P093 is a valid low response and should not be altered merely because it differs from other scores.
P126 represents a genuinely unanswered item, while P204 remains unresolved because the source cannot be checked.
Interpretation: AI helps identify which entries deserve attention, but only source verification establishes which corrections are justified. A successful procedure distinguishes confirmed mistakes from legitimate responses and unresolved anomalies.
07 · A Quick Checklist
Before Accepting AI-Detected Data Entry Errors
Before correcting flagged entries, check:
Preserve the original dataset and available source records.
Confirm valid codes, ranges, formats, and variable definitions using the codebook.
Use reproducible validation checks rather than unsupported AI judgments.
Investigate potential digit transpositions, column shifts, and import errors.
Compare suspected mistakes with original questionnaires or authorized records.
Distinguish confirmed transcription errors from participant responses and unresolved anomalies.
Document the original value, approved correction, and supporting evidence.
Verify that no unrelated values changed during correction.