Data entry looks simple from the outside, which is why it is easy to test badly. A five-minute typing drill is quick to send, but it measures how fast someone copies prose. The job is reading a source document, putting the right value in the right field, and noticing when something does not add up.
This guide is for recruiters, TA leads and hiring managers who want a data entry assessment test that predicts who will do the work well. It covers what to measure, sample tasks you can copy, how to score fairly, and what to tell candidates so they can prepare. If you are a candidate, our data entry typing test guide is written for you.
What is a data entry assessment test?
A data entry assessment test is a short, timed task in which a candidate enters, checks or corrects data from source material, scored on accuracy and speed. The best ones copy the real job closely, so the score reflects how the person will perform on day one.
The O*NET profile (sponsored by the US Department of Labor) for data entry keyers describes the work in terms worth testing directly. Keyers read source documents such as cancelled cheques, sales reports or bills and enter the data. They compare data with source documents, or re-enter it in a verification format, to detect errors. And they find and correct errors or report them to a supervisor. A test that only measures keystrokes leaves out two of those three.
What should a data entry skills test measure?
A data entry skills test should measure accuracy, speed on accurate work, the ability to spot errors, and comfort with the software the role uses. Weight them in that order for most roles.
| Skill | What it looks like on the job | How to test it |
|---|---|---|
| Accuracy | The right value in the right field, every time | Count errors per field against an answer key |
| Speed | Clearing the day's queue without a backlog | Records completed in a fixed time, counting only correct ones |
| Verification and attention to detail | Catching a transposed digit or a mismatched name before it is saved | A checking task with planted errors |
| Following rules | Applying date formats, codes and naming conventions consistently | A short style guide the candidate must apply |
| Software comfort | Moving between fields, tabs and screens without losing their place | A task in a spreadsheet or a form that behaves like your system |
| Judgement | Flagging an unreadable or contradictory record instead of guessing | Include one or two records the candidate should query before entering |
O*NET lists the abilities behind this work as including near vision, perceptual speed, selective attention, finger dexterity and information ordering. Most of those show up in a well-designed entry and checking task without a separate test for each. For a deeper look at the checking skill, see how to assess attention to detail.
Cohesyve
Test candidates on the work itself
Cohesyve builds an AI job simulation of the role from your job description, finds and contacts candidates for it and returns a ranked shortlist. Ten candidates free, no card.
Is a typing test enough for a data entry test for employment?
No. A typing test is a reasonable first filter, but on its own it misses verification, rule-following and judgement, which are core parts of the job.
Typing tests usually present continuous text. Data entry is mostly short, structured values: account numbers, dates, postcodes, amounts, product codes. Someone who copies prose quickly can still mistype a reference number, and someone of average speed can be very reliable on structured fields. If you keep a typing element, treat it as one part of the score and pair it with a structured task.
What sample tasks work well in a data entry assessment?
The strongest tasks use your own documents with the real data swapped for dummy data. Pick two or three of the formats below to match the role, and keep the whole assessment short.
| Task | What the candidate does | What it reveals |
|---|---|---|
| Form entry from a source document | Reads a scanned invoice, order or application and fills in a web form or spreadsheet row | Core accuracy and speed on realistic input |
| Spot the difference | Compares a source list with an entered list and marks every mismatch | Verification and attention to detail |
| Data cleaning | Fixes a short spreadsheet with duplicates, inconsistent dates and stray spaces | Rule-following and spreadsheet comfort |
| Alphanumeric copying | Enters codes, serial numbers or reference IDs that mix letters and digits | Precision on values where one slip breaks a record |
| Rules application | Applies a one-page style guide (date format, capitalisation, category codes) to raw entries | Whether the candidate reads and follows instructions |
| Query handling | Meets a record that is illegible or contradicts itself | Judgement: flagging instead of guessing |
Match the software to the job. O*NET's list of tools for data entry keyers includes Excel, Access, QuickBooks, Salesforce, SAP and electronic medical record software. If the role lives in a spreadsheet, test in one, and our Excel assessment guide shows what to include. If it lives in a CRM or ERP form, a simple web form with the same fields and tab order is closer than a blank text box.
A task built from your real work is a form of work sample test, which makes it easier to show the test is job-related and easier for candidates to see the point of.
How do you score a data entry assessment fairly?
Score accuracy per field against a fixed answer key, credit only correct records towards speed, and decide the pass mark before you look at any results. Then apply the same rules to every candidate.
A simple scoring model that works for most roles:
- Build the answer key first. Write down the correct value for every field, and decide in advance how you will treat near misses such as a missing capital letter or an extra space.
- Classify errors by cost. A wrong amount, account number or date of birth matters more than a lowercase street name. Give critical fields a heavier penalty.
- Measure net speed. Count records completed correctly in the time allowed. Raw speed rewards rushing.
- Score verification separately. For the spot-the-difference task, count errors found and false alarms. Both matter.
- Set a threshold from the job. Ask the hiring manager what error level the team tolerates today, and set the pass mark from that. Avoid setting it by how the candidate pool happens to score.
- Calibrate on current staff. Have two or three people already doing the job take the test. If good performers fail it, the test or the pass mark is wrong.
Record the results on a shared sheet or an interview scorecard so everyone uses the same criteria at the interview stage too.
How do you keep a data entry test legally defensible?
Keep the test job-related, give the same test under the same conditions to everyone, offer accommodations, and watch pass rates by group. This section is a plain-English summary, not legal advice.
In the US, the EEOC's guidance on employment tests says a test must be job-related and its results appropriate for the employer's purpose. The employer stays responsible for that even when a vendor supplies the validity evidence. If a test screens out a protected group, the EEOC says employers should look for an equally effective alternative with less adverse impact.
The federal Uniform Guidelines use the four-fifths rule as a rule of thumb: if the selection rate for a race, sex or ethnic group is less than four-fifths (80%) of the rate for the group with the highest rate, that is generally treated as evidence of adverse impact (29 CFR 1607.4(D)).
Speed tests deserve particular care around disability. Under the ADA regulations (29 CFR 1630.11), an employer must select and administer tests so that, for an applicant with a sensory, manual or speaking impairment, the results reflect the skill being measured rather than the impairment, unless that impaired skill is what the test measures. In practice, publish how candidates can ask for an accommodation, such as extra time or screen-reader compatible materials, and decide whether raw keying speed is truly essential to the job before you make it a hard cut-off.
If an automated tool scores or ranks candidates, other rules may apply depending on where you hire. Our AI hiring laws guide covers the main ones as of 2026.
How long should a data entry assessment test be?
As short as it can be while still covering the work. Two or three focused tasks usually tell you more than one long drill, and candidates are more likely to finish.
Take the test yourself before sending it, and ask one current team member to do the same. If either finds a task confusing or padded, cut it. Tell candidates the expected time up front, and say what the test is for.
Where does a data entry assessment fit in the hiring process?
Use it early, straight after application or a short screening call, so you interview only candidates who can already do the core work. Then use the interview for what the test cannot show: reliability, how they handle a long queue, and how they raise problems.
| Stage | Purpose | Data entry focus |
|---|---|---|
| Application | Basic eligibility | Availability, location, any required certification |
| Data entry assessment | Can they do the work accurately? | Entry, checking and rules tasks, scored per field |
| Structured interview | How do they work? | Handling repetitive work, catching and reporting errors, asking for clarification |
| Reference check | Confirm patterns | Reliability and accuracy in past roles |
Some teams also add a short attention to detail assessment when the role involves reviewing other people's entries as well as making their own.
How can candidates prepare for a data entry test?
Candidates prepare best by practising structured entry as well as typing, and by reading instructions carefully before starting. Sharing this list with applicants gives everyone the same information about what to expect.
- Practise entering numbers, dates and codes from a printed or scanned document into a spreadsheet, then check every row against the source.
- Use the numeric keypad and the Tab key to move between fields if the job involves heavy number entry.
- Read the whole instruction sheet, including any style rules, before starting.
- Prioritise accuracy. If the test penalises errors, a few seconds saved will not make up for a mistake.
- Flag a record you cannot read instead of guessing, if the test allows it.
- Ask for an accommodation in advance if you need one.
Where does Cohesyve fit?
Cohesyve takes a job description, sources candidates, handles outreach, puts candidates through AI job simulations of the real work and returns a ranked shortlist. For data entry and admin roles, that means candidates work through realistic tasks based on the role instead of a generic typing drill. Plans are a subscription from $199/month billed annually, and a new account includes 10 free candidates. Disclosure: Cohesyve publishes this guide.
FAQ
What is a good score on a data entry test? There is no universal pass mark. Set yours from the error rate your team accepts today and from how current staff score on the same test.
Should I use words per minute or keystrokes per hour? Either works as long as you use one consistently and count only correct work. For structured, numeric entry, records completed correctly in a fixed time is easier to explain than either.
Can I use a generic test from an assessment library? Yes as a starting point, but add at least one task built from your own documents. A generic test cannot show whether someone will cope with your forms, codes and edge cases.
Is it fair to time a data entry test? Timing is fair when speed is a real part of the job. Offer extra time as an accommodation on request, and make sure accuracy carries more weight than speed.
Should the test be proctored? A supervised or proctored setting can make scores more trustworthy for remote hiring. Tell candidates in advance if it is, and what that involves.
What other skills should I check for an admin-heavy data entry role? Spreadsheet skills, written communication and organisation. Our guide on assessing administration skills covers the wider role.