Delhi Police Head Constable Ministerial common mistakes
Delhi Police Head Constable Ministerial · Understand the traps and how to avoid them.
Spending the final weeks only on General Awareness and Reasoning while almost never practising timed Hindi/English comprehension passages and grammar sets, so the language sections (which carry heavy weight) are attempted last and rushed.
General Awareness feels productive because facts can be memorised quickly, and Reasoning puzzles are enjoyable, whereas language practice produces slower visible gains. Candidates therefore default to the comfortable sections and neglect the ones where accuracy is built only through repeated timed practice.
What to do instead
Build a fixed weekly timetable that allocates at least as many hours to Hindi and English as to GA and Reasoning, and practise each language section under a strict per-question time cap (roughly 45-60 seconds) with a written error log of every grammar rule you got wrong. Review the log weekly so recurring rule errors are eliminated rather than repeated.
Attempting every question in sequence in the objective paper, including long calculation-based Numerical Ability items, instead of making two passes and skipping time sinks.
Candidates treat the paper as a school test where leaving questions blank feels like failure, and they lack a pre-decided cutoff for abandoning a question. One stubborn simplification or percentage problem can consume four to five minutes and destroy the timing of the whole paper.
What to do instead
Adopt a two-pass strategy in every mock: first pass solves only questions you can finish within about 60 seconds, second pass returns to the rest. Set a hard rule to abandon any question after 90 seconds. Practise this in at least ten full-length mocks so the habit is automatic on exam day.
Preparing for the typing skill test only in the last week and practising on a keyboard or layout different from the one used in the test, without measuring gross speed, net speed and error count separately.
Typing feels like a formality compared with the written paper, so it is deferred. Candidates also practise casually without a timer or accuracy tracking, and many have never used a standard QWERTY desktop keyboard under test conditions, so backspace corrections and unfamiliar key spacing wreck their net speed.
What to do instead
Start typing practice at least two months before the test, 20-30 minutes daily on a standard desktop QWERTY keyboard. Track gross words per minute, accuracy percentage and net speed after deducting errors. Target a comfortable margin above the qualifying speed (commonly around 30 words per minute for English or 25 for Hindi, subject to the official notification) so exam-day nerves do not push you below the cutoff.
Memorising current affairs as isolated headlines without linking them to static topics, and not revising the list, so facts from three to six months before the exam are forgotten.
Candidates consume daily news in bulk but never consolidate it. Without spaced revision, retention of unlinked facts drops sharply within weeks, and questions on schemes, appointments, sports and awards are answered from vague impressions rather than recall.
What to do instead
Maintain a single monthly current-affairs sheet organised by category (national, international, sports, awards, appointments, schemes, defence, science). Revise each month's sheet three times at increasing intervals and connect each item to its static background, such as the constitutional article, state capital or organisation headquarters. Do a monthly 25-question self-test from your own sheet.
Solving reasoning questions by intuition on the first attempt and never writing down the arrangement, grid or symbol mapping, leading to repeated errors in seating arrangement, blood relations and coded inequality questions.
Under time pressure, candidates try to hold multi-condition puzzles in their head. Working memory overloads, one condition is dropped, and the answer chosen is consistent with an incorrect arrangement. Because the method is never recorded, the same error is not identified in review.
What to do instead
For every multi-condition reasoning question, draw the arrangement, family tree or symbol table before evaluating options. In practice, keep a notebook of the exact diagram you drew and compare it with the correct solution. Do sets of 10 questions of one type at a time until the diagramming method becomes fast and reliable.
Treating Hindi grammar as general reading and skipping the rule-based topics such as संधि, समास, उपसर्ग-प्रत्यय, मुहावरे and अशुद्धि शोधन, so vocabulary and grammar questions are answered by ear rather than by rule.
Fluent Hindi speakers assume the section needs no preparation because they understand the language. Spoken fluency, however, does not supply the formal classifications and standard forms that objective questions test, so plausible-sounding but non-standard options are selected.
What to do instead
Work topic by topic through a standard Hindi grammar list, making a one-page rule sheet for each (sandhi types with examples, samas types, common muhavare with meaning and usage, common shuddh-ashuddh pairs). Follow each sheet with 20-30 practice questions and revise the sheets fortnightly.
In English, choosing options that merely sound correct in fill-in-the-blank and error-spotting questions, without identifying the grammatical rule being tested.
Candidates rely on reading flow rather than analysis, so subject-verb agreement, article use, prepositions, tense sequence and parallelism errors pass unnoticed. Options that read smoothly are often the distractors.
What to do instead
For each error-spotting or fill-in question, name the rule before choosing (for example, 'subject-verb agreement with a collective noun' or 'preposition after the verb insist'). In review, write the rule beside every mistake and drill that rule with ten fresh sentences. Maintain a personal list of the twenty rules you get wrong most often.
Ignoring the computer knowledge section and the practical typing interface details, such as not knowing common shortcut keys, file extensions, basic MS Office and internet terminology, or how the typing test window displays errors.
The computer section is short and perceived as easy general knowledge, so it is left to chance. Similarly, candidates never simulate the actual test interface, so they are distracted by unfamiliar display of speed, errors and backspace rules on the day.
What to do instead
Prepare a compact one-page reference of shortcut keys, file extensions, basic hardware and software terms, internet and email terminology, and common MS Word and Excel functions, then test yourself with 15 questions weekly. Before the exam, practise on a typing simulator that reports gross speed, net speed and error count so the interface is familiar.
Relying on memory of the exam pattern and marking scheme without checking the current official notification, including section-wise qualifying rules, negative marking and eligibility documents.
Coaching material and older aspirants circulate outdated patterns, and candidates assume the structure is unchanged. This leads to misallocated practice time and, occasionally, last-minute document or eligibility problems.
What to do instead
Download the current official notification and read the scheme of examination, marking, negative marking and eligibility clauses directly. Write a one-page summary of the pattern and keep it at your desk, and check the official website periodically for corrigenda before the exam.
Taking full-length mocks without a post-mock analysis, so the same question types are missed repeatedly and scores plateau.
Candidates equate more mocks with more preparation and skip the slower, uncomfortable step of reviewing every wrong and guessed answer. Without analysis, practice reinforces existing habits, including bad ones, rather than correcting them.
What to do instead
After each mock, spend at least as long analysing as taking it: classify every error as concept gap, calculation slip, misread question or time pressure, and record the correct approach. Re-attempt the same paper after a week and track whether those specific errors recur. Reduce mock frequency if analysis time is unavailable.