Aptitude skill lesson
Error detection: skill lesson
Error detection is the skill of holding a source and a copy side by side and finding the one character, digit or field that moved, and of knowing which errors a given check will and will not catch. It is assessed directly in clerical checking, banking operations, records, proofreading and dispatch selection, and it underpins quality control anywhere a record is rekeyed or transcribed. The useful part of the skill is not staring harder; it is a repeatable scan procedure plus a set of arithmetic checks that catch what the eye misses. Everything you practise is stored on this device only, with no account and no upload unless you export it.
Published · last reviewed
Applies to Novus Learn 0.1.0
What changed, and when
- , Replaced the body of all 27 non-judgement lessons with construct-specific material: six worked examples each, carrying the actual arithmetic, the actual inference or the actual procedure, plus expanded objectives, practice tips and glossary. Every 'Related Learn topics' link now points at a real page on this site rather than a generic search. The eight workplace-judgement lessons are unchanged.
- , Rebuilt the lesson page around a sticky contents rail, per-section links, previous/next lesson navigation, and two graded checkpoints drawn from the open practice bank.
- , Repaired the aptitude integrations behind the lessons so each one links to skill-specific practice instead of the unscoped fixture engine.
- , Published one lesson for each of the 35 aptitude skill constructs: objectives, worked examples, practice tips, glossary, Learn topic links, and sources.
These 35 skill lessons are authored and revised as one set, so they share one revision history rather than 35 identical dates.
Objectives
Copy link- Name the four transcription error families (substitution, transposition, omission, duplication), and state which of them a plain digit-sum check will fail to detect.
- Run a fixed field-order comparison between a source record and a copy, reporting the specific field and character position that differs rather than a general impression.
- Compute a modulus 11 check digit (ISBN-10 style) by hand and use it to decide whether a single record is internally consistent.
- Apply the Luhn algorithm to a candidate account number, and state the one transposition case Luhn provably cannot catch.
- Work out, from a stated scoring rule, whether guessing on an uncertain item has positive, zero or negative expected value.
- Reconcile a document at batch level (line totals, subtotal, tax, grand total) and explain why an internally consistent document can still be wrong.
Checkpoint: does the idea land?
Copy linkBefore the worked examples, check that the objectives above actually landed.
Two questions from the open practice bank, answered here and scored on this device. Untimed, ungraded, and not added to your practice history, the full bank is where attempts are recorded.
Examples
Copy linkThe four transcription error families
Source reference: INV-2024-08871. Four corrupted copies, one of each family. INV-2024-08571 is a substitution: a single character changed, 8 to 5. INV-2024-0871 is an omission: one character dropped, and the string is now a character short. INV-2024-088711 is a duplication: a character repeated, one character long. INV-2024-08817 is a transposition: the final 7 and 1 have swapped places, and crucially the string is the same length and contains exactly the same characters. That last property is why transposition is the hardest of the four to see and the most dangerous in practice. Anything that checks length catches omission and duplication. Anything that compares character sets or sums the digits catches substitution but not transposition, because 0+8+8+7+1 and 0+8+8+1+7 both come to 24. Reading the reference aloud catches substitution reliably and transposition poorly, because the ear is comparing sounds and both versions sound similar at speed. The only defences against transposition are a positional comparison and a weighted check digit.
A fixed scan order finds the one field that moved
Source record: Name Priyanka Ramaswamy / Account 4471-9026-3358 / Date of birth 14/03/1991 / Postcode SW1A 2AA / Phone 0161 496 0872. Copy: Name Priyanka Ramaswamy / Account 4471-9026-3358 / Date of birth 14/03/1991 / Postcode SW1A 2AA / Phone 0161 469 0872. The difference is in the phone field, where 496 has become 469: a transposition inside the middle block. Most candidates find it eventually; the ones who find it in eight seconds are the ones running a procedure. Always compare in the same field order, top to bottom, never skipping a field because it 'looks fine'. Compare long strings in the printed blocks rather than as a single run (4471, then 9026, then 3358) because short-term memory holds about four items and a twelve-digit run does not fit. Say the block silently, look, compare, move on. On a same-or-different item you may stop at the first mismatch; on a 'how many fields differ' item you must complete every field, and the instruction wording is what tells you which regime you are in. Getting this wrong in either direction costs marks: stopping early on a count item, or exhaustively checking a same-or-different item you had already resolved.
Modulus 11: why a weighted check digit catches a transposition
The ISBN-10 scheme multiplies the ten digits by descending weights 10, 9, 8 down to 1 and requires the total to be divisible by 11. Take 0-306-40615-2. Working left to right: 10x0 = 0, 9x3 = 27, 8x0 = 0, 7x6 = 42, 6x4 = 24, 5x0 = 0, 4x6 = 24, 3x1 = 3, 2x5 = 10, and the check digit 1x2 = 2. The sum is 0 + 27 + 0 + 42 + 24 + 0 + 24 + 3 + 10 + 2 = 132, and 132 = 12 x 11 exactly, so the number is valid. Now transpose the 1 and the 5 to give 0-306-40651-2. The digits are identical, so a plain digit sum is unchanged at 27 either way and would report no problem. The weighted sum, however, becomes 0 + 27 + 0 + 42 + 24 + 0 + 24 + 15 + 2 + 2 = 136, and 136 - 132 = 4, so it is not a multiple of 11 and the record is rejected. That is the entire reason check digits are weighted rather than plain: position has to matter, or the commonest human error passes straight through.
Luhn: the number that fails, and the one case it misses
The Luhn check, used on payment and many membership numbers, doubles every second digit counting from the right, subtracts 9 from any doubled result above 9, sums everything, and requires a total ending in zero. Take 4539 1488 0343 6467. The doubled positions contribute 3, 3, 8, 0, 7, 2, 6 and 8, totalling 37; the undoubled positions contribute 7, 4, 3, 3, 8, 4, 9 and 5, totalling 43. The grand total is 80, which ends in zero, so the number passes. Now transpose the last two digits to 4539 1488 0343 6476. The doubled contributions become 5, 3, 8, 0, 7, 2, 6, 8 = 39 and the undoubled become 6, 4, 3, 3, 8, 4, 9, 5 = 42, giving 81. Not a multiple of ten, so the mistyped number is rejected at the point of entry. Luhn catches every single-digit substitution and almost every adjacent transposition: with exactly one blind spot. Swapping an adjacent 0 and 9 leaves the total unchanged, because doubling 0 gives 0 and doubling 9 gives 18 which reduces to 9, so both digits contribute the same amount whether doubled or not. A form that validates with Luhn will happily accept 90 where you typed 09. Knowing the blind spot is the point: a check digit narrows the space of undetected errors, it never closes it.
Negative marking: 44 right can beat 46 right
Many clerical checking sections score correct minus incorrect, with omissions neutral. Under that rule, guessing between two remaining options has an expected value of 0.5 x (+1) + 0.5 x (-1) = 0, exactly neutral, and guessing blindly among four options has an expected value of 0.25 - 0.75 = -0.5, clearly negative. Concretely: on a 60-item section you attempt 48, get 44 right and 4 wrong, and score 40. A colleague attempts all 60, gets 46 right and 14 wrong, and scores 32. More correct answers, a lower score. Reverse the scoring rule to plain raw-correct with no penalty and the ordering flips: 46 beats 44 and leaving a blank becomes strictly irrational. Neither strategy is universally right, which is why the instruction screen is not optional reading. Find the sentence that says whether wrong answers are penalised, and if it is absent, assume raw scoring and answer everything.
Reconcile the batch: consistent is not the same as correct
An invoice lists three lines: 12 at 14.25 = 171.00; 7 at 33.60 = 235.20; 3 at 128.00 = 384.00. The stated subtotal is 709.20, VAT at 20 percent is stated as 141.84, and the total is stated as 851.04. Every downstream figure checks out against the one above it: 709.20 x 0.20 = 141.84 and 709.20 + 141.84 = 851.04. Nothing in the tax or total column is inconsistent. But recompute the lines: 171.00 + 235.20 + 384.00 = 790.20, not 709.20. The subtotal is a transposition of the correct figure, and because every later number was calculated from the wrong subtotal, the document is perfectly self-consistent and perfectly wrong. The true VAT should be 158.04 and the true total 948.24, a shortfall of 97.20. This is the single most valuable habit in the construct: never verify a total against the number printed above it, always recompute it from the underlying items. Internal consistency proves that one person did the arithmetic carefully; it proves nothing about whether they started from the right number.
Checkpoint: can you apply it?
Copy linkNow apply it. These come from a later section of the bank, so they are not more of the same.
Two questions from the open practice bank, answered here and scored on this device. Untimed, ungraded, and not added to your practice history, the full bank is where attempts are recorded.
Practice tips
Copy link- Drill transposition specifically. Generate pairs where the only difference is two adjacent characters swapped, because that is the family your eye is worst at and the family a naive check will not catch.
- Fix a scan order and never vary it: field by field, top to bottom, and within a long value block by block. Free-roaming comparison feels faster and reliably misses one field per record.
- Learn one check-digit scheme by hand, modulus 11 is the easiest, until you can run it in about twenty seconds. It converts a whole class of 'does this record look right' items from judgement into arithmetic.
- Read the scoring rule before the first item and decide your guessing policy then, not at minute seven when you are behind. Under penalty scoring, an omission is a legitimate answer; under raw scoring it is a wasted mark.
- When you are checking financial or tabular documents, recompute the lowest-level figures first and work upward. Errors introduced at a subtotal propagate perfectly and are invisible from below.
- Log the errors you miss, not the ones you find. A miss log after four sessions usually shows a personal signature (always the middle of long numeric strings, or always the second occurrence of a repeated field), and that signature is what to drill.
Glossary
Copy link- Transposition error
- Two adjacent characters exchanged, as in 496 typed for 469. Length and character content are unchanged, so length checks and plain digit sums both pass it; only positional comparison or a weighted check digit detects it.
- Substitution error
- One character replaced by another, as in 08571 for 08871. It is the family most reliably caught by reading a value aloud against the source, and by any check digit scheme.
- Check digit
- An extra digit computed from the others so that a corrupted record fails an arithmetic test. It detects errors; it never corrects them and never proves the record refers to the right person or item.
- Modulus 11
- A weighted check scheme in which digits are multiplied by descending position weights and the total must divide by 11. Used in ISBN-10 and several banking and national identifier formats.
- Luhn algorithm
- A modulus 10 check that doubles alternate digits from the right and requires the sum to end in zero. It catches all single-digit errors and most adjacent transpositions except an adjacent 0 and 9.
- Miss and false alarm
- A miss is a genuine discrepancy passed as correct; a false alarm is a difference flagged where none exists, usually a formatting variant such as a trailing space or a differently written date. Misses are the costlier of the two in records work, which is why procedures normalise formatting first and then bias toward escalating doubt.
- Correction for guessing
- A scoring rule that subtracts a fraction or multiple of the wrong answers from the correct ones, making blind guessing negative in expectation and turning omission into a rational choice.
- Reconciliation
- Recomputing an aggregate from its components rather than accepting the printed figure. It is the only check that catches an error introduced at summary level, where everything below and above it still agrees.
Sources
Copy link- The ISBN-10 modulus 11 worked example (0-306-40615-2, weighted sum 132) and the Luhn worked example (4539 1488 0343 6467, sum 80) were computed by hand for this lesson and each was re-verified digit by digit, including the corrupted variants.
- Algorithm definitions cross-checked against the public specifications described in the Wikipedia articles 'International Standard Book Number' and 'Luhn algorithm', including the documented 09/90 transposition blind spot. Records, invoices and reference numbers above are invented.
- Novus Learn aptitude construct registry (catalog seed) for construct scope and suite mapping.
- Public educational framing only: not affiliated with any official exam board, publisher or employer, and no copyrighted test item is reproduced.
Your notebook for this lesson
Saved sections and notes are kept in this browser, on this device. No account is required, and nothing is sent to us unless you create one and switch on backup. They travel with your backup file from My Learning, and they are lost if you clear this site’s data.
Saved sections
None yet. Use Save beside any section heading above to keep it here.
4000 characters left
Your own words, so you can find this again from any other lesson. Up to 12.