An alphanumeric data entry test gives you a set of records, such as names, street addresses and account codes, and asks you to key them into matching form fields as fast as you can without mistakes. It is scored in keystrokes per hour (KPH) with an accuracy figure beside it, and the accuracy usually decides whether you pass. Expect the number to be lower than your prose WPM would suggest, because every record is a stream of capitals, digits and field jumps. You can rehearse the whole thing for free with invented records, and the worked example below shows exactly how a score gets calculated.

Practice on your own records: paste sample records into the free custom test and time yourself against the clock.

What is an alphanumeric data entry test?

It is a typing test that looks like a job task. Instead of copying a paragraph, you see a record or a small stack of records, and you enter each piece of it into its own field: a person's name, a street address, a ZIP code, a customer ID, a plate number. The data is "alphanumeric" because the fields mix letters and digits, often in the same string, like KB-2291-7.

Two layouts show up most often. In the first, a source document or PDF sits on one side of the screen and a simulated database form sits on the other, and you copy across record by record. In the second, a prompt shows one record at a time and a blank form waits underneath. Either way you move between fields with the Tab or Enter key, and the test records how long you took and which fields came out right.

The job behind it is plain. The federal O*NET occupational database describes data entry keyers as people who compile, sort and verify the accuracy of data before it is entered. Employers use the alphanumeric test to find out whether you can do that verifying with your fingers instead of your eyes. If you are applying for a role that lists data entry, order entry, claims processing, dispatch or records work, this is one of the screens you are likely to meet. For the broader family of these assessments, see our guide to the ProveIt typing test and the typing test for data entry.

How are alphanumeric tests scored?

Three numbers matter, and they come from different parts of the run.

Keystrokes per hour (KPH). Your keystrokes divided by your elapsed time, scaled to an hour. Letters, digits, spaces and punctuation all count, and on many tests the Tab or Enter you press to leave a field counts too.
Field accuracy. The share of fields you got exactly right. A field with one wrong character is usually a wrong field, which is harsher than the character-level accuracy you see on a prose test.
Adjusted KPH. Raw speed corrected for mistakes. One published prep guide to the Kenexa ProveIT alphanumeric test says the KPH score is adjusted at the end to account for errors, but it does not publish the formula. That is typical. Scoring conventions differ between vendors and between employers, so treat any specific penalty rule, including the one in the example below, as an illustration and not as a universal standard.

The practical consequence is the same everywhere. Speed alone cannot rescue a sloppy run, because a wrong field costs you the keystrokes you spent on it and often more. The conversion between KPH and WPM is simple (KPH is WPM times 300, derived in our WPM to KPH chart), but the two measure different work, which is why the next section matters.

What does a scored run look like? A worked example

Here is a run you can follow with a calculator. Every record below is invented. Each has four fields: name, street address, account code, ZIP. The "keystrokes" column counts every character in the record, spaces included, plus one for the Tab or Enter that ends each of the four fields.

#	Name	Street	Account code	ZIP	Keystrokes
1	Dana Whitfield	4127 Alder Ct	TX-80419	76208	44
2	Omar Reyes	88 Birch Hollow Rd	KB-2291-7	30316	46
3	Lin Park	1500 Harbor Ave Apt 6	MR-55120	98107	46
4	Tessa Moore	912 N Fifth St	QC-7034-A	60614	43
5	Ibrahim Sy	27 Cedar Lane	LD-90172	11215	40
6	Priya Nair	6350 Mill Run	HB-3318-2	43017	41
7	Gus Ferreira	301 W Elm Ave	ZT-41806	85004	42
8	Hana Okoye	74 Quarry Pl	NV-6620-K	02134	40
9	Carl Duvall	2208 Pine Ridge Dr	FP-18453	37203	46
10	Mina Sato	19 Lakeview Ter	JW-5097-3	55408	42

Step 1: total the work. Add the last column and you get 430 keystrokes across 40 fields.

Step 2: apply the clock. Say you finish in 3 minutes flat, which is 180 seconds. Raw KPH is 430 divided by 180 seconds, times 3,600 seconds per hour, which is 8,600 KPH. In WPM terms that is 8,600 divided by 300, about 28.7 WPM. That sounds slow next to a 70 WPM prose typist, and it is the whole point of this article: the same fingers on the same day produce a far smaller number on this kind of work.

Step 3: mark the fields. You check your result and find three wrong fields: the address in record 3 (22 keystrokes with its Tab), the account code in record 6 (10 keystrokes) and the account code in record 9 (9 keystrokes). Field accuracy is 37 correct out of 40, or 92.5 percent.

Step 4: adjust. Under a simple credit-only-correct-fields rule, you lose the 41 keystrokes that landed in wrong fields. That leaves 389 credited keystrokes, and 389 divided by 180, times 3,600, gives 7,780 adjusted KPH.

So one run produces three honest numbers: 8,600 raw, 7,780 adjusted, 92.5 percent field accuracy. Read your own agency report against those three. If the adjusted number is far below the raw one, your problem is accuracy, and no amount of speed drilling will fix it. If the raw number itself is low, work on rhythm and the number row. Our KPH benchmarks guide covers what the bars tend to be.

Why is alphanumeric KPH lower than numeric KPH?

A pure numeric test lets your right hand sit on the keypad and repeat a tiny set of motions. Alphanumeric work takes that away in four ways.

You leave the home row. Digits on a standard keyboard live on the number row, a long reach from the letters, so accuracy there depends on touch typing technique you may not have drilled.
Capitals and symbols need Shift. Names, state codes and plate numbers lean on capital letters, and hyphens and slashes appear inside codes. Each Shift is a coordination step that prose rarely demands this often.
Nothing is predictable. In English prose your brain predicts the next letter. In HB-3318-2 it cannot, so you are reading character by character instead of chunking words.
Fields break your rhythm. Every Tab or Enter is a micro-pause plus a decision about where your eyes go next.

TypeQuicker's page on this format makes the same basic point: digits carry no linguistic pattern, so mixed strings are harder than ordinary words. The practical takeaway is that comparing an alphanumeric score to a 10 key typing test is comparing different motor skills. Someone fast on the numeric keypad can still be slow here, and the reverse is just as common.

What scores do employers expect?

There is no single national bar, and anyone quoting one is guessing. What can be said with a source behind it: the same Kenexa-focused prep guide reports a pass mark of 8,000 KPH for the ProveIT alphanumeric test and 10,000 KPH for its 10 key test, and notes that pass scores vary by job and that CritiCall pass marks vary by state. That ordering, alphanumeric below numeric, matches the mechanics above.

Treat those figures as a reference point and not a promise. Your real target is whatever the job posting or the recruiter tells you, and accuracy usually arrives as a separate requirement. Our wider guides on data entry typing speed requirements and what counts as a good KPH go through how postings phrase these bars.

There is also a reason accuracy tends to outrank speed. Wikipedia's entry on data entry clerks puts it this way: accuracy is usually more important than speed, because detecting and correcting errors can be very time-consuming. A wrong ZIP in a claims system or a transposed digit in an account code does not stay in the test. It becomes someone else's cleanup job.

How do you practice alphanumeric entry for free?

You do not need a prep pack. You need realistic records, a clock and an honest scorecard.

Invent your own records. Write ten fake people with a name, an address, a code like KB-2291-7 and a ZIP. Use the same shape as the table above. Never use real customer data.
Paste them into the custom test. Open the free custom typing test, paste the records as plain text and run it. It times you with a stopwatch and reports accuracy alongside speed, and nothing you paste is uploaded.
Add digits to ordinary practice. On the standard test, switch on the numbers option so digits are mixed into the words. It is a lighter way to get number-row reps in daily.
Score yourself the way the table does. Count keystrokes, count wrong fields, compute raw and adjusted KPH. The arithmetic is the skill, and doing it once removes the mystery from an agency report.
Run it in the right order. Do one slow, clean pass first. Only push speed after two clean runs in a row. Then repeat for 10 minutes a day.
Measure KPH directly when you want the number. The KPH typing test reports keystrokes per hour from a five minute run, and the data entry test page collects the rest of the practice options.

Finally, find out the field-jump rule before test day. If the test expects Tab between fields, practice with Tab. Reaching for the mouse costs more time than any other habit on this list.

Frequently asked questions

What is a good score on an alphanumeric data entry test?

It depends on the employer, so ask. One prep guide reports 8,000 KPH as the ProveIT alphanumeric pass mark, which gives a rough reference point. Whatever speed is asked for, expect an accuracy requirement on top of it, and expect your adjusted KPH, not your raw KPH, to be the number that gets judged.

Is the alphanumeric test harder than 10-key?

For most people it feels harder, because it uses the number row, Shift and unpredictable character strings instead of one hand on a keypad. They are different skills, though, so being strong at one does not predict the other. If you only practice one, practice the one named in the job posting.

Do errors cost more than speed on data entry tests?

Usually, yes. A wrong field typically wastes the keystrokes spent on it, and many employers also set a separate accuracy floor. In the example above, three wrong fields turned 8,600 raw KPH into 7,780 adjusted KPH and a 92.5 percent field score. Slowing slightly to avoid those three errors would have made a better result.

Can I use the Tab key on an alphanumeric data entry test?

On most form-style tests, Tab or Enter is how you move between fields, and some counts include those presses as keystrokes. The rules vary by test, so read the instructions on the first screen. Practice with whichever key the test expects, and never switch to the mouse mid-record.

Alphanumeric Data Entry Test: Format, Scoring, Practice