How to Use Mock Tests for SSC CGL Preparation: Sectional Pace, Order and Marks per Minute

The short answer: SSC CGL Tier I is a speed exam with a 15-minute timer for each of four sections, so use mocks to measure marks per minute in each section, to test the order in which you take them and to set a per-question time cap. Then review the slowest questions with a faster method. The score improves when the pace in each 15-minute block improves.

Why CGL mocks are about pace

Tier I has 100 questions in one hour, with each section limited to 15 minutes (as published in the SSC scheme). Most questions are not conceptually hard; the exam tests whether you can do them in 36 seconds on average. Study improves what you know, but only timed practice improves how fast you can use it. A mock is therefore less a test of knowledge than a measurement of your pace in each block. The pattern is described in the SSC CGL exam pattern guide.

Measure marks per minute, section by section

For each section in each mock, record the net score (correct × 2 − wrong × 0.50) and the time you actually used. Then compute marks per minute. An illustrative example from one paper:

Reading the table: General Awareness gives 3.8 marks per minute and finished in 9 minutes, so six minutes of the timer were unused (they cannot be carried forward). Quantitative Aptitude gives only 1.6 marks per minute and used the whole 15 minutes, with 7 questions unattempted. The conclusion is not "work on everything": it is that the best return is in Quantitative Aptitude, where the candidate is leaving about 7 questions (14 marks at full accuracy) unattempted, and where unused time elsewhere cannot help. The decision this supports: spend practice time on Quant speed methods and skip rules, and use the spare six minutes in General Awareness to re-check doubtful answers rather than hurrying.

Set a per-question cap and a skip rule

In a 15-minute section, a 90-second question costs you more than two other questions. A cap makes the choice automatic:

These caps are starting points. After a few mocks, adjust them from your own data: if you finish a section early with high accuracy, raise the cap; if you run out of time, lower it. See how to pick which questions to skip.

Test your section order

If the platform lets you choose the order, treat it as an experiment. Take the first two mocks in your natural order. Take the next two with the section you find hardest first, while you are fresh; and the next two with the section you are strongest in first. Compare total net scores and how you felt. Because every section has its own timer, the order does not change the time available to each; it changes your composure and the effect of fatigue. Fix the order a few weeks before the exam and rehearse it.

Review the slowest questions, not only the wrong ones

In a speed exam, a correct answer that took 90 seconds is a problem too, because it costs you the time to answer two others. In your review, sort the questions in each section by the time they took, if the platform shows it, or by your memory. For the five slowest, read the explanation for a faster method and then redo the question with it. Over weeks you build a library of fast methods for the question types that cost you most. Our topic pages, such as percentage, time and work and coding-decoding, include methods you can practise.

Classify errors

• Concept gap: you did not know the method or fact. Study and drill.
• Speed problem: you knew it but ran out of time. Practise timed sets and learn faster methods.
• Calculation error: the method was right and the arithmetic wrong. Use estimation and checks.
• Reading error: you missed "not" or a condition. Underline the key word.
• Selection error: you stayed too long on a hard question. Apply the cap.
• Guess error: you marked without elimination. Track net marks from guesses.

The fix differs by category, which is why the classification matters. See how to review incorrect questions.

A weekly plan for the last two months

Mistakes to avoid

• Practising with one 60-minute clock. The sectional timer is the real constraint.
• Only taking full papers. Sectionals train each 15-minute block.
• Hurrying in General Awareness when spare minutes could improve accuracy.
• Ignoring slow correct answers. They are future lost time.
• Changing section order in the last week.

A checklist for each mock

1. Take the paper on a computer, with sectional timers, in your exam slot.
2. Record net score and minutes used for each section; compute marks per minute.
3. Note the slowest questions and the questions you did not reach.
4. Classify errors by cause and update your error log.
5. Redo the slowest questions with a faster method.
6. Choose one change for the next paper.

To begin, try a free SSC CGL mock test, read the SSC CGL mock test strategy and browse the SSC CGL hub. Please confirm the pattern in the SSC notice for your year; tests on TestMint are independent practice papers.