How to Improve Your SHL Percentile Score: A 4-Week Study Plan
Stuck on the same practice score? This week-by-week plan shows you how to find your weak spots, fix them with an error log, train your pacing and walk into test day with a routine.
Start With an Honest Baseline
You cannot raise a percentile you have not measured, so week one begins with a diagnostic under real conditions. Sit one full-length numerical, one verbal and one inductive practice test, timed, in a quiet room, with only the tools the real test allows. Do not pause the clock, do not look anything up, and do not retake the same test later and call it progress. The goal is a baseline you trust.
Record three numbers for each test: questions attempted, questions correct, and questions you skipped or guessed. These three figures tell you very different stories. A candidate who attempts 14 of 20 questions and gets 13 right has a speed problem. A candidate who attempts all 20 and gets 11 right has an accuracy problem. Fixing speed and fixing accuracy call for opposite training, and most people waste weeks drilling the wrong one.
| Pattern in your diagnostic | What it usually means | Where to focus |
|---|---|---|
| Few attempted, high accuracy | Careful but slow | Pacing rules, shortcuts, skipping discipline |
| Most attempted, low accuracy | Rushing or weak fundamentals | Error log, slower first-pass reading, core skills |
| Strong on one test, weak on another | Uneven skills | Shift practice hours toward the weaker test |
| Scores drop sharply in the last third | Fatigue or panic | Stamina sets and a calm routine for hard questions |
Practice tests are not scored against SHL’s own norm groups, so a practice percentile is only a rough guide. Use your own measures (accuracy, attempt rate, time per question) to judge progress, and treat the percentile figure as a trend line. Our guide to SHL scores explains how raw scores, percentiles and sten scores relate.
Also note which employer you are preparing for. Different employers commission different combinations of tests, and each sets its own cut-offs, which they rarely publish. Look up the format your target employer uses before you decide how to split your time; our TalentCentral assessment guide shows how candidates usually access the tests.
Build an Error Log That Drives Your Practice
An error log turns every wrong answer into a specific, fixable skill gap, and it is the single most effective habit in this plan. After each practice set, write down every question you got wrong or guessed correctly, and label the cause. Over a week, patterns appear that no amount of general practice would reveal.
Use a simple spreadsheet or notebook with four columns: question type, what went wrong, the correct method, and a one-line rule for next time. Be specific. “Misread the chart” is not useful. “Used the 2024 column instead of the 2025 column when the question said ‘following year’” is useful, because you can build a habit around it: underline the time reference before touching the data.
| Error category | Typical example | Fix |
|---|---|---|
| Misreading | Wrong unit, year or currency in a table | Underline units and dates before calculating |
| Calculation slip | Dropped a decimal when finding a percent change | Estimate the answer first, then check the result against it |
| Method gap | Forgot how to reverse a percentage | Rework five similar questions the same day |
| Logic trap | Assuming a statement true because it sounds plausible | Ask: is it stated, implied, or neither? |
| Pattern miss | Tracked shape but ignored rotation in inductive questions | Check one attribute at a time: shape, color, position, count |
Spend the first five minutes of each study session rereading your last three days of log entries. Spaced repetition of your own mistakes is more efficient than doing fresh questions you may already handle well.
Do not log only wrong answers. Questions you got right but took more than twice the average time on are also worth recording, because on a real timed test they cost you the questions at the end. If a type of question regularly eats your time, that is a pacing problem to solve in week three.
Weeks 1 and 2: Fix the Fundamentals
The first two weeks should rebuild the skills that every question depends on, not chase speed. Speed built on shaky fundamentals collapses under pressure. For about 45 to 60 minutes a day, work on the core skill for each test type and keep your scratch paper tidy so you can check your own work.
| Test | Core skills to rebuild | Daily drill idea |
|---|---|---|
| Numerical reasoning | Percentages and percent change, ratios, averages, currency conversion, reading tables and charts | 10 data-interpretation questions, untimed, then re-solve any miss |
| Verbal reasoning | Reading for the stated claim, true / false / cannot say logic, ignoring outside knowledge | 2 passages with 3 statements each, justifying each answer with a quoted line |
| Inductive reasoning | Spotting one rule at a time: rotation, shading, count, position, sequence | 8 pattern questions, naming the rule aloud before choosing |
For numerical work, practice the calculations by hand first, then check them with the calculator if one is allowed on your test. Rules on calculators and rough paper vary by employer, so check your invitation instructions rather than assuming. Being able to estimate quickly (is the answer roughly 20 percent of 3,400, so near 700?) lets you eliminate wrong options even before exact calculation.
For verbal work, the biggest score gain usually comes from one habit: answer only from the passage. Candidates with industry knowledge often lose marks by answering from what they know is true in the real world. Our guide to true, false and cannot say questions walks through this in detail, and for the pattern-based test see the inductive reasoning tips.
It is tempting to keep practicing the test you already score well on because it feels good. Many employers set separate cut-offs per test, so a strong result on one cannot rescue a weak result on another. Weight your hours toward the weakest area, roughly 50 percent of your time in these two weeks.
Week 3: Train Speed and Pacing
Week three is where you convert accurate skills into points by controlling the clock. On a timed SHL-style test, the time per question is short, and the test is designed so that many candidates do not finish. Pacing is therefore a skill you can practice, not just a personality trait.
Start by calculating your target pace. Divide the total time by the number of questions, then set a checkpoint every five questions. If a numerical test gives you roughly a minute and a bit per question, a question that has taken you two minutes is no longer a good investment. Make a firm rule: if you have no clear route to the answer after about 20 to 30 seconds of working, mark your best guess, flag it if the platform allows it, and move on.
| Pacing rule | How to apply it | Why it works |
|---|---|---|
| Checkpoint every 5 questions | Glance at the clock; compare with your target | Catches slow drift early, when it is cheap to fix |
| Two-pass approach | Answer all easy questions first, return to flagged ones if time remains (only if navigation is allowed) | Banks the easy marks before time runs out |
| Never leave blanks | Guess in the last 30 seconds if no penalty is stated | An unanswered question scores nothing |
| Cap time on hard items | Move on after roughly 1.5x the average pace | One difficult item should not cost two easy ones |
Some assessments deduct nothing for wrong answers, but you should read the instructions on your own test before relying on that. Where no penalty is stated, a quick informed guess beats a blank. Where one is stated, only guess when you can eliminate options.
Run at least three fully timed sets this week, and use sectional drills too: 10 questions in 10 minutes, repeated daily. The sectional work builds the pace; the full tests build stamina. After each, update your error log, noting whether any errors came from rushing. If accuracy falls when speed rises, step the pace back slightly: your percentile depends on correct answers, not on attempts.
Week 4: Simulate the Real Thing
The final week is about rehearsal, so every session should look like the real test. Take two or three full-length mock tests at the time of day you are likely to sit the real one, on the device and in the room you will use, with notifications off. This removes surprises and shows whether your pacing rules hold up when the stakes feel real.
Between mocks, do light review rather than heavy new learning. Reread your error log, redo the questions you missed in weeks one to three, and stop new practice 24 hours before the test. Cramming the night before rarely adds points and often adds anxiety.
| Day | Activity | Time |
|---|---|---|
| Days 22–23 | Full mock test 1, then full error review | 2–3 hours |
| Days 24–25 | Targeted drills on the two weakest question types | 45 minutes each |
| Day 26 | Full mock test 2 under strict conditions | 1.5–2 hours |
| Day 27 | Error log review only; tech and logistics check | 30 minutes |
| Day 28 | Rest, light walk, early night | No practice |
Test your internet connection and browser, charge your laptop, and make sure you have rough paper, pens and (where permitted) a calculator within reach. Read the invitation email again for any rules about the environment. Technical stress is avoidable and can eat the first minutes of your test.
If nerves are a factor for you, practice a short reset routine in the mocks: one slow breath, shoulders down, then back to the question. Our article on managing SHL test anxiety covers techniques that you can rehearse before test day.
Test-Day Habits That Protect Your Score
On the day, your job is to execute your pacing and avoid unforced errors, not to learn anything new. The habits below are small, but each one prevents a common way of losing points.
- Read the instructions fully: The examples at the start are not scored in many formats, but they show how questions are laid out. Use the time to settle in.
- Underline the question, not just the data: Many wrong answers come from solving a different question than the one asked. Re-read the final sentence before selecting.
- Write down intermediate steps: On numerical questions, a quick written line saves you from redoing the calculation if you doubt it.
- Use elimination: On multiple-choice items, remove options that are clearly the wrong size, unit or direction before calculating.
- Keep moving after a mistake: Dwelling on a question you think you got wrong costs the next one. Treat each question as independent.
- Do not decode the scoring mid-test: Some formats adapt as you answer, so you cannot reliably tell how you are doing. Focus on the question in front of you.
| Before the test | During the test | After the test |
|---|---|---|
| Sleep, eat, hydrate; read the invitation again | Follow pacing checkpoints; flag and move on | Note which question types appeared |
| Test tech; clear the desk | Guess instead of leaving blanks where allowed | Update your notes if you apply to other employers |
| Do a 10-minute warm-up of easy questions | Reset with one breath after a hard item | Do not replay questions; wait for the result |
Employers and test publishers prohibit sharing real questions, and using leaked content can get your application rejected. Prepare with practice questions that mimic the format. Our practice tests are written for that purpose.
What to Do If Your Scores Plateau
A plateau usually means you are practicing what you already do well, so change the type of practice, not just the amount. Most candidates see steady gains in the first two weeks, then a flat patch. That is normal and fixable.
First, return to the error log and look for the most frequent category. If most mistakes are misreading, doing more questions will not help; slowing your first read will. If mistakes are method gaps, go back to teaching yourself the method from scratch, then do ten questions on that single skill. If mistakes are mostly late in the test, build stamina with back-to-back sets.
| Symptom | Likely cause | Change to try |
|---|---|---|
| Same score across three mocks | Practicing comfort zone | Spend 70 percent of time on weakest question type |
| Score swings widely | Inconsistent pacing or concentration | Use the same checkpoint rules every time |
| Good in practice, poor on real test | Anxiety or environment | Run mocks at the real test’s time of day and device |
| Accuracy good but few attempted | Over-checking | Set a hard 30-second cap per question |
A higher personal score helps, but the cut-off for a given role is the employer’s choice and is usually not published. Your aim is simply to perform as well as you reasonably can, then keep the rest of your application strong: a clear CV, good interview answers and relevant experience all matter alongside test results.
If you want a broader approach to the whole process, from the first online test to the interview, our structured SHL preparation plan shows how to organize your time, and the numerical reasoning guide goes deep on the test most candidates find hardest.
Frequently Asked Questions
Put This Plan Into Practice
Take timed numerical, verbal and inductive practice tests, then use the structured preparation guide to organize your four weeks.
Keep reading
- Guide · Graduate & SchemesASVAB Test Guide: Subtests, AFQT Score & Study Plan
- Guide · Strategy & ScoringWhat is a Good SHL Score? Percentiles, Pass Marks & Cut Scores Explained
- Guide · Strategy & ScoringCase Study Interview: Complete Guide with Frameworks & Worked Examples
- Guide · Strategy & ScoringWhat Would You Do in Your First 90 Days? 30-60-90 Day Plan Answers
- Article · Strategy & ScoringTell Me About a Time You Worked With Limited Resources: How to Answer
- Article · Strategy & ScoringTell Me About a Time You Balanced Speed and Quality: How to Answer