This guide teaches a per-section decision rule system for the Delhi Police Constable (Executive) examination: classify reasoning items into named families, write the setup before any arithmetic, split English into rule lookup and passage evidence, run GK as a weekly consolidation loop anchored to Delhi-specific knowledge from official portals, and treat physical preparation as measured, progressive practice against the standards published for your category. Two worked scenarios, a scored self-check drill, and a four-week adaptable sequence show how to apply it.
One written test, four different decision rules
The computer-based test mixes pattern recognition, calculation, rule application, and recall in a single sitting. Each section rewards a different first move, so the practical goal is one explicit decision rule per section, drilled until it is automatic.
Reasoning items reward a fast elimination move built on named families: series, coding, Venn-based syllogisms, arrangements. Quantitative items reward writing the setup — the unit rate, the ratio line, the equation — before any arithmetic. English grammar items are rule lookup, while passages are evidence discipline. General knowledge is consolidation of facts you have already met, not fresh puzzle solving. Naming these first moves turns revision into checking rules instead of rereading whole topics.
The trap is treating every section as the same activity: more timed practice. A session that drills speed without a per-section rule simply repeats the same wrong first move faster. Compare two equal-length sessions: one where you write the decision rule at the top of each section and apply it item by item, and one where you just answer. The first produces error patterns you can actually fix; the second produces only a score that tells you nothing about why it moved.
The table below is the operating summary for the whole plan. Keep it visible during practice and update it whenever you discover a new item family or a recurring wrong first move in your own error log.
| Section | Typical item shape | First move to train | Trap to watch |
|---|---|---|---|
| General Intelligence and Reasoning | Series, coding-decoding, syllogisms, arrangements | Classify the item into a named family, then apply that family's rule | Solving every item from scratch as a one-off puzzle |
| Quantitative Aptitude | Arithmetic, ratio, time and work, averages, percentages | Write the setup line (unit rate, ratio, equation) before calculating | Starting arithmetic before the setup is fixed |
| English Language and Comprehension | Error spotting, fill-ups, cloze, passages | Match the sentence to a named grammar rule; answer passages from the text alone | Choosing by what sounds right rather than by rule or evidence |
| General Knowledge and Current Affairs | Facts across polity, history, science, geography, Delhi affairs | Weekly consolidation linking current items to static anchors | Chasing a daily news feed without revisiting older facts |
Reasoning: named pattern families and the syllogism conversion rules
Reasoning preparation works when items are classified into families, each with its own rule. For syllogisms, the conversion rules for the four quantified statement types decide conclusions faster and more reliably than intuition.
Learn the conversion rules by name. All A are B converts only to Some B are A. No A is B converts to No B is A. Some A are B converts to Some B are A. Some A are not B converts to nothing. A conclusion follows only if it holds in every valid Venn arrangement, not merely in the one you happened to draw. These two ideas — conversion direction and the all-valid-diagrams test — resolve most syllogism items in seconds.
Worked scenario. Statements: Some pens are pencils. All pencils are erasers. Conclusions to test: (i) Some pens are erasers; (ii) All erasers are pencils. The plausible mistake is accepting (ii) because the sentence chain sounds close, or judging by one mental picture. The better decision: draw the minimal diagram, then deliberately redraw it to break each conclusion. Conclusion (i) survives every redraw — pens overlapping pencils must overlap erasers — so it follows. Conclusion (ii) breaks in a redraw where some erasers sit outside the pencil circle, so it does not follow. This matters because conversion direction is exactly where a fast intuitive read goes wrong, and the redraw check costs almost no time.
Train the other families the same way, one short drill per family with the rule written first. For number series, name the mechanism before computing: constant difference, increasing difference, multiplicative step, two interleaved alternating sequences, or square and cube offsets. For coding, test letter-position offsets, reversal, and positional shifts in that order. When an item resists classification within a few seconds, mark it and return — the classification step, not the solving step, is what you are training.
Quantitative aptitude: the setup-before-calculation habit
Quantitative items reward fixing the setup first. Write the unit rate, ratio line, or equation in one short line before touching numbers, because the classic slip is calculation that begins before the setup is settled.
Worked scenario. A and B together finish a task in 12 days; B alone finishes it in 20 days; find A alone. The plausible mistake: subtracting days to get 20 minus 12 equals 8, or adding the numbers, because the question reads like day arithmetic. The better decision: write the work-rate setup — combined rate one-twelfth of the task per day, B's rate one-twentieth, so A's rate is one-twelfth minus one-twentieth, which is five-sixtieths minus three-sixtieths, or two-sixtieths, giving 30 days. This matters because rates add and subtract while days do not; writing the unit (task per day) before calculating makes the wrong operation visibly wrong.
Extend the same habit to the other staples. Percentages: convert to a fraction first (17.5 percent becomes seven-fortieths) before multiplying. Ratio problems: write the total-parts line and the value of one part. Averages: write sum equals mean times count. Time-speed-distance: check the unit, converting between kilometres per hour and metres per second deliberately. Then drill in two columns — setup line on the left, calculation on the right — and when an error occurs, note which column failed. This separates concept errors, which need rule relearning, from arithmetic slips, which need only careful execution.
English: rule lookup versus passage evidence
The English section splits into two different skills. Grammar items are rule lookup — agreement, tense, prepositions, structure — while passages and cloze tests are evidence discipline. Train them separately because their first moves differ.
For grammar, maintain a named-rule list: subject-verb agreement when a phrase separates subject and verb, tense consistency across a sentence, parallel structure in lists, common preposition pairs, and pronoun case. In error-spotting drills, name the rule being tested before choosing an option; if no rule comes to mind, that sentence becomes a list entry. In fill-ups, find the signal word that triggers the rule — since versus for with time spans, each of with singular verbs, not only paired with but also — and let the signal, not the ear, decide.
For passages and cloze, separate three item intents: stated facts, vocabulary in context, and inference. An inference must be supportable by a specific line; if you cannot point to the sentence that supports it, it is an assumption, not an answer. Read a cloze passage fully before filling any blank, because tense and subject carry across blanks. The characteristic error is choosing a word that fits its blank locally while breaking agreement with the sentence's subject two lines earlier — a mistake that a full first read prevents.
General knowledge: consolidation loops and Delhi-specific grounding
General knowledge rewards a consolidation loop: weekly revision of covered material with current affairs attached to static anchors. For Delhi-specific knowledge, build the base from the official Delhi Police portal and the syllabus of your own application cycle.
Divide static GK into mapped buckets — polity and the Constitution, history, geography, general science, everyday economics — and run a weekly review in which each current-affairs item is written beside its static anchor: a government scheme under its ministry, a summit under the host country's geography, a sports result under its venue. At month end, redraw the map from memory; the gaps show exactly what to relearn. This differs fundamentally from consuming a daily news feed, which adds unconnected facts that decay quickly.
For Delhi-specific knowledge, build a one-page map of the force's organisation, units, and citizen-facing initiatives directly from the Delhi Police recruitment portal rather than from second-hand compilations. Take special care with law-related topics: Indian criminal statutes were replaced by new codes in recent years, so older notes may carry outdated names — match every law topic to the codes and material named in your cycle's syllabus. One administrative note: notifications, eligibility, dates, and fees are published only by the Staff Selection Commission and Delhi Police on the official portals linked at the end of this article; confirm all logistics there.
Physical standards and efficiency: measure, don't guess
The physical stage is assessed against standards published for your category in the official notification, so read those standards yourself first. Preparation then becomes measured, progressive practice — recorded timings and gradual builds — not sudden last-week intensity.
Build an aerobic base with a progressive run-walk plan plus mobility and bodyweight strength work, recording distance, time, and perceived effort each session. Verify the race distance, timing pattern, and any height, weight, or chest standards only from the notification for your category and gender, since these differ by category and stage. Consider the contrast scenario: one candidate trains only at maximum sprint intensity every day in the final week, arrives with tight legs, and posts a slower trial than in practice. The better decision is weeks of base building followed by timed trials at target pace with full recovery between trials, so the test day repeats a familiar, rehearsed effort rather than a new one.
The measurement side of the physical stage cannot be trained — height is fixed — but you can and should confirm in advance exactly which standards apply to your category, so no application effort is wasted on an avoidable ineligibility. Keep the document checklist ready per the notification: identification, category certificate, and any required declarations. Keep all physical preparation safe and sensible — familiar routes, hydration, rest days, no hazardous or unsupervised drills — since the stage requires consistent conditioning, not risky experimentation.
A four-week adaptable sequence with a self-check rubric
Run a four-week cycle: week one, rules and family classification; week two, quant setups and grammar rules; week three, mixed timed sections scored with the rubric; week four, full mixed review plus measured physical trials. Compress or stretch it to fit your timeline.
The core exercise is a 20-minute mixed drill. Take a single practice set and select four reasoning, four quantitative, four English, and four GK items. Before answering each reasoning and quantitative item, write its family or setup line in a few words. Score every item on the rubric: 2 means correct answer with the setup or rule correctly named; 1 means correct answer but missing or wrong setup; 0 means incorrect. Expected observations when you review: quantitative and reasoning errors cluster in the setup column, English errors cluster where no rule was named, and GK errors concentrate in topics missing from your consolidation map. Re-run the drill weekly — the useful signal is where the 1s and 0s sit, not the total.
Treat the rubric scores as learning milestones, never as pass predictions. A rising share of 2s means your first moves are stabilising, which is what makes performance steady under pressure; a high total with many 1s means you are still answering by intuition and the score can swing either way. When your error log shows setups consistently correct, families named within seconds, and GK map gaps shrinking week over week, the written-test side of your preparation is functioning as designed regardless of any single drill's raw score.
- Readiness check 1: you can name the family and first move for any reasoning item within a few seconds of reading it.
- Readiness check 2: your quant error log shows correct setups with calculation slips, or fully correct items — no wrong-setup errors remain.
- Readiness check 3: you can redraw last month's GK consolidation map from memory with only a few gaps.
- Readiness check 4: for every inference answer in a passage, you can point to the supporting line.
- Readiness check 5: your recorded practice timings show a multi-week trend toward the standard published for your category in the notification.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.