Coding by Analogy and Substitution

Coding by analogy and word substitution is the easiest coding family in SBI Clerk and the fastest to clear, yet careless reading loses marks here more than anywhere else. Substitution replaces everyday words with other words and then asks a question in the coded language; analogy coding asks you to extend a given relationship to a new pair. Both are comprehension exercises dressed as reasoning, so the winning skill is reading the substitution list exactly and holding it steady while you answer.

Word Substitution Basics

A substitution question sets up a dictionary — 'call sky as sea, sea as river, river as road' — then asks something like 'where do fish live?' You must answer in the substituted word, not the real one. Fish live in the sea, but sea has been renamed river, so the answer is river. The whole difficulty is remembering to give the code word rather than the real one, which is why underlining or listing the swaps vertically before answering keeps you from slipping back into ordinary language.

The Two-Step Substitution Method

Solve every substitution question in two clean steps. First, answer the question in plain real-world terms and ignore the code entirely — fish live in water, the sky is blue, and so on. Second, translate that real answer into its substituted word using the list. Splitting the reasoning from the translation stops the confusion of trying to think in the coded language directly. The real answer is common sense; the translation is a look-up. Keep them separate and the trickiest-looking substitution becomes routine.

Step 1: answer in real words Step 2: replace that answer with its substitute

Meaningful and Analogy Coding

Analogy coding gives a relationship and asks you to complete a parallel one: if 'teacher' relates to 'school' as 'doctor' relates to a blank, the link is workplace, so the answer is hospital. Meaningful coding works the same way — identify the exact relationship in the given pair, name it in a word, and apply that same relationship to the new term. The error is spotting a loose or wrong link; always pin the relationship down to one precise word before extending it, so the parallel is genuinely the same kind.

Solved Example

Example: If 'green' means 'sour', 'sour' means 'sweet', and 'sweet' means 'bitter', what is the taste of sugar? Real answer: sugar is sweet. Now translate — 'sweet' has been renamed 'bitter', so the coded answer is bitter. The real taste never changes; only its label does.

✗ Answering 'sea' when the question is in coded language  |  ✓ Answering in real words, then swapping to the code word

Avoiding the Reverse-Substitution Trap

Setters like to add a reverse twist: the question is asked using a code word and expects the real-world answer, or asks for the substitute of a word that is itself already a substitute for something else. Read the exact wording of the question stem — is it asking in real words or coded words, and about the real thing or its label? Match your final answer to what the stem asks, not to what feels natural. This one check, done deliberately before you commit, catches nearly every trap in the substitution family and turns these into the most reliable easy marks in the coding block.