Data Entry, Documentation and Record Keeping
Domain 5: Data Entry, Documentation and Record Keeping
This domain tests accuracy and discipline in capturing data and maintaining records. Expect questions on source documents, fields, validation, verification, filing methods, backup, retention, and confidentiality. The examiner looks for correct procedure and awareness of error prevention.
Core rules and concepts
- Data entry converts source documents (forms, invoices, registers) into digital records. Enter alphanumeric data exactly; preserve leading zeros in codes by formatting cells as text.
- Validation checks whether data is acceptable: range, format, length, consistency, and presence checks. Verification checks whether the entered data matches the source-often by double entry or proofreading.
- Documentation explains a process or system: user manual, SOP, data dictionary. Good documentation has version, date, author, and change log.
- Record keeping follows a lifecycle: create, classify, store, retrieve, retain, and dispose. Use logical file names, folders, indexes, and access permissions. Back up regularly and test restoration.
- Confidential records need controlled access, encryption where appropriate, and secure disposal (shredding or wiping).
Worked example
Question: A date-of-birth field rejects 31/02/2010 but accepts 15/08/2010. Which validation is working? Reasoning: 31 February does not exist, so the field is applying a range/format or date-validity check. It is not checking whether the date matches the source document-that would be verification. The correct answer is validation, specifically a date validity check.
Traps that cost marks
Do not confuse validation with verification. Do not overwrite the only copy of a source record. Do not use spaces or vague names such as “final2” in file names. Do not assume a backup exists-test it. Do not leave confidential printouts on a shared desk.