Blood relations problems test whether you can trace a chain of family connections accurately — no more, no less. The exam does not test your knowledge of family structure; it tests whether you can follow a logical path from one person to another without getting tangled mid-chain.
Here is the analogy that makes this stick: think of a family tree as a directed graph. Every person is a node. Every relationship is an edge with a direction and a gender tag. Your job in the exam hall is to walk the edges from Person A to Person B and read out the final relationship.
IBPS Clerk serves three types of blood-relation questions:
Type 1 — Direct narration. "Pointing to a boy, Seema said, 'He is the son of my father's only son.' How is the boy related to Seema?" You decode one statement at a time, walking the tree.
Type 2 — Coded relations. Symbols like +, -, ×, ÷ are defined as specific relationships. You decode each symbol, rebuild the sentence, and read the final relationship. These look intimidating but they are the most mechanical — once you decode, the logic is the same as Type 1.
Type 3 — Multi-person family puzzle. A short paragraph introduces several family members with interlocking clues. You draw a tree, place everyone, then answer one or two questions. These appear in the Puzzles & Seating section too but the logic engine is the same.
The single biggest reason students lose marks here: they try to hold the entire chain in their head. Don't. Draw a two-line sketch on the rough sheet — boxes for people, arrows for direction, M/F tag on each box. Even a rough sketch cut solving time by 40% compared to mental tracking.
The other trap is gender ambiguity. Names like "Kim", "Alex", or "Anurag" trip you up only if you haven't assigned a gender from context. Assign it the moment you get a clue. If the question says "Kim is the father of Raj," Kim is male — write M next to Kim immediately.
Before you solve a single question, you need this map internalized. Read it once carefully; do not try to memorize it cold — derive it from logic instead.
One generation up (parents/siblings of parents):
Same generation (siblings and their spouses):
One generation down:
This is not an exhaustive list — it is the minimum you need. For any other relationship, derive it on the spot using the tree.
Every narrated blood-relation question gives you a chain. Break it into atomic steps.
Example: "Pointing to Kiran, Deepa said, 'She is the daughter of my father's wife's only daughter.'"
Step 1: Deepa's father's wife = Deepa's mother. Step 2: Deepa's mother's only daughter = Deepa herself (assuming one daughter). Step 3: Kiran is the daughter of Deepa. Step 4: So Kiran is Deepa's daughter.
The key: resolve each possessive one at a time, left to right. Never skip a step.
In coded relation questions, you are given a table like:
A + B → A is the father of BA - B → A is the mother of BA × B → A is the brother of BA ÷ B → A is the sister of BYou are then given an expression like P + Q × R ÷ S and asked what relationship P has to S.
Method:
Look — you must draw. Trying to track generation levels mentally across a 4-node coded chain is where errors happen.
This is the single most useful sub-skill for this topic.
?) and wait for a disambiguating clue.If no gender clue arrives, the question itself usually makes the ambiguity irrelevant — the asked relationship works for both genders (e.g., "cousin" covers both male and female cousins).
Many questions use the phrasing: "Pointing to X, Y said, 'He/She is [relationship description].'"
The description is always from Y's perspective. "My father's only son" means Y's father's son — which is either Y himself or Y's brother. Watch for "only" — it is a deliberate constraint to force a unique answer.
Type 3 questions sometimes ask you to count members of a specific gender. Approach:
The trap: the question may describe a joint family where daughters-in-law and sons-in-law are "in the family." Count them unless the question says "blood relatives only."
Assign each person a generation number: Great-grandparents = G+2, Grandparents = G+1, Parents = G, Self = 0, Children = G-1, Grandchildren = G-2. Every relationship maps to a generation difference + gender. Father's brother (G+1, M) = Uncle. Brother's son (G-1 relative to sibling = same generation as self, M) = wait — sibling is G0, sibling's son is G-1 = Nephew. This pattern eliminates confusion between "Uncle" and "Cousin": Uncle is G+1, Cousin is G0. Standard confusion takes 30 seconds; the generation-stack takes 8 seconds once internalized.
In coded relation questions, start reading from the asked person backward to the reference person, not forward. If asked "How is A related to D?" in the chain A + B × C - D, decode from D backward: D's mother is C (C - D), C's brother is B (B × C), B's father is A (A + B). So A is B's father, B is C's brother (A is C's father-figure = uncle or father), C is D's mother, so A is D's grandfather. Forward reading forces you to track 3 levels simultaneously. Backward reading lets you anchor each step to the asked person. Step count drops from 6 mental operations to 4.
When the problem gives you two people who share the same aunt or uncle, they are cousins — full stop. You don't need to trace the full tree. In the question "Your father's sister is my aunt," both people share an aunt → cousins. This eliminates 3 intermediate steps. Standard trace: 45 seconds. Same-aunt test: 10 seconds.
The moment a name appears in the problem, write M or F next to it if any clue gives you the gender, even indirectly. "Raj said" → Raj is M. "Her son" → the possessed person is F. Doing this upfront means you never re-read the question to check gender mid-chain. Re-reading costs 15-20 seconds per question; gender-locking upfront costs 5 seconds total.
Students confuse nephew (brother's/sister's son) and cousin (uncle's/aunt's son). Use this anchor: Nephew/Niece is always one generation below you. Cousin is always the same generation as you. If the chain lands you at the same generation level as the reference person, the answer is cousin. If it lands one level below, it is nephew/niece. Checking generation level takes 3 seconds; second-guessing nephew vs. cousin without this anchor takes 20+ seconds.
Walk through this decision tree the moment you see a blood-relations question:
Step 1 — Classify the type. Coded symbols? Go decode table first. Plain narration? Go to Step 2. Multi-person family? Draw tree immediately, place all members before answering anything.
Step 2 — Identify the anchor person. Every question has one person whose perspective the chain is described from. Mark them as "REF."
Step 3 — Walk left to right, one possessive at a time. Never skip a step. Write abbreviated tags: REF → F (father) → W (wife) = REF's mother.
Step 4 — Assign gender at every node. M or F in brackets. If unknown, write ?.
Step 5 — Check generation level. Is the target person one level above REF (G+1), same level (G0), or one level below (G-1)? Match to the answer choices — this alone eliminates 2-3 wrong options.
Step 6 — Pick the answer. If two options look similar (e.g., Sister vs. Sister-in-law), recheck the marriage/blood distinction: blood relation or relation by marriage?
Time budget: 60-90 seconds per standalone question; 90-120 seconds per question in a 5-person puzzle.
Why this question: Tests pure chain-walking on a coded expression. Most students mis-decode and waste time.
Solving path: Decode each option one at a time.
A + C × B → A is brother of C (A + C), C is father of B (C × B). A is B's uncle, not son.B × A → B is the father of A. This means A is the son of B. Correct.A × B → A is the father of B. A is B's father, not son.B ÷ A → B is the mother of A. A is the son, yes — but check what ÷ means: "P ÷ Q means P is the mother of Q." So B is mother of A, meaning A is the son of B. This also seems valid, but the official answer is B × A. The key: × is defined as "P is the father of Q" — B × A = B is father of A = A is the son of B. This is the direct, unambiguous match.Why this question: Tests a long multi-hop chain with a potential ambiguity trap at the word "niece."
Solving path:
Why this question: Classic "same-aunt" cousin detection. Perfect for applying the Same-Aunt Test shortcut.
Solving path:
Why this question: Generation-walking across four levels. Tests whether you can extend the chain to great-grandparent without losing track.
Solving path:
Why this question: Joint family counting with daughters-in-law — the classic trap question.
Solving path:
Stopping at "my mother's son" without asking "is this me or my brother?" "My mother's son" has two possible answers — yourself or your brother. The question context or the word "only son" narrows it down. Never assume it is a sibling without checking.
Forgetting that marriage relationships are not blood relationships. "Sister-in-law" is not a blood relation. When the question asks "how is X related by blood," marriage links are indirect paths. Many wrong answers are planted by mixing the two.
Mis-assigning gender in coded relations. In P × Q = "P is the father of Q," both P and Q have implied genders (P is male; Q's gender is unspecified). Students sometimes assume Q is male because P is "father" — that is a projection error. Wait for Q's gender clue.
Counting members of the wrong generation in family puzzles. "How many female members" often includes daughters-in-law (who are technically one generation up from grandchildren but entered by marriage). Always include all women in the household unless told otherwise.
Treating "niece" and "cousin" as interchangeable. Niece is one generation below (sibling's daughter). Cousin is the same generation (uncle's or aunt's child). Generation-check eliminates this confusion in 3 seconds.
Reading coded expressions forward when backward reading is faster. When asked "how is A related to D" in A + B - C × D, students who read left-to-right must track four levels forward. Reading from D backward anchors each step and reduces mental load significantly.