Consist of tables and label/data fields

Users read form-fills selectively

• Switch at most once between tables and label/data fields.
• If user enters data from a paper document, its layout should be mirrored by the screen layout.
• Left-align labels, data fields, and columns of tables
• Position labels close to the fields
• left-align labels or use visual connectors if distance is too wide

• Allow for a space of at least two characters between columns, and one character between data and surrounding frame.
• Insert a blank line after about every fifth line of data.
• Split long alphanumeric codes in groups of 2-4 characters.
 
• Allow for flexibility in the input format   
• If a specific format of the user input is required, communicate this to the user:
  • Use underscores, periods etc. to indicate the exact or maximum input length.
  • Units (like $, ft., mph) and separators (like "-", "/") should be part of the form
    (i.e., users should not be required to enter them ).
  • Use short ancillary explanations like "dd/mm/yy" or "(example: 12/08/59)".

• If input must meet constraints, point those out
• Mark fields where entry is required (e.g., by *, ?, or color), or group such fields separately.  
• Hitting the tab key should bring the user to the next required entry field (or possibly even jump there automatically when a field has been completed ).

• Fill in data fields with default values or with the most recently entered value.
• Enter field values automatically if they can be inferred from other user inputser:
• e.g., do not force user to enter both DOB and age
• Allow for abreviated entries which can be expanded by hitting a single key
  
• Automatic expansion is also o.k., but more difficult for beginners
• If the result is not unique, show available alternatives.
• Automatically entered values should however never have dangerous effects.

• Alphabetical listings should be arranged vertically, possibly in several parallel columns.

Example