Old timey data entry GUI problem

[Mike Bonner]

I have a couple thoughts on this.

First, thinking of the people doing the data entry as "typists" may not be
the best viewpoint. You should look for people skilled at 10 key operation
and gear the application towards 10 key methods.

Approximately 800 numbers total every 30 minutes should be easily doable by
a good 10 key person. (yes just 1) As you surmise the main drawback is the
flow of the application itself, doesn't matter how good the data entry
person is if there are lag times in the app itself.

So, I assume that when the id is entered for each partner (do partners
change every round?) a database query is done populating the right side of
your app.  Can this be done async so that data can be typed while the
population is done?  And if the partner is the same each time, of course
the partner entry should be queried at the same time and not require the
data entry as someone else stated. Since you mention tables i'm thinking
its a card tourney of some type so changing partners is likely (hence your
chosen method)

A method that might work is to use + to switch between fields (like adding
numbers on a calc) then enable the "add" button when all fields are full,
activated by the enter key.

An additional thought I had was to have a 2nd person for proof check.
(maybe hire the first from a temp agency with the required skills because 1
person who is really good will likely do a better job than 3 or 4 who don't
have the practice)  If you can get your hands on a dymo label printer that
spits out a label containing the just entered data as a type of "receipt"
that is tacked to the original note, the 2nd person can verify and fix an
error if one does occur.