Dental-school admissions preparation: study guide

Worked examples and pitfalls

Rotation preserves handedness; reflection reverses it: A figure carries three distinguishable marks (say a red band, a blue band and a yellow band), which read red, blue, yellow going clockwise around its centre. Rotating that figure in the plane, by any angle, never changes that clockwise order: it still reads red, blue, yellow clockwise from whatever mark you start at. Mirroring it reverses the order, so a reflected copy reads red, yellow, blue clockwise. That single check answers the whole is-this-a-rotation-or-a-reflection family without imagining any motion. It works on letters, which is why no in-plane rotation of the letter R produces a backwards R, and no rotation of a lower-case b produces a d: b and d are mirror images across a vertical line, and turning one will never give you the other. Contrast b and q, which are related by a half turn and therefore genuinely are rotations of each other. The distinction is exactly what the clockwise-order test measures. In three dimensions the equivalent is handedness at a corner: pick three edges meeting at a vertex, and a rotation preserves whether they form a right-handed or left-handed set while a reflection swaps it. This is exactly why most Western dice, viewed at the corner where the 1, 2 and 3 faces meet, show those numbers running anticlockwise, and a die showing them clockwise is a mirror-image die rather than a differently rotated one. The one honest limitation: a figure with its own mirror line looks identical after reflection, so the test decides nothing for symmetric shapes, which is precisely why item writers use asymmetric ones.

Cube nets: two apart in a strip means opposite: A net made of six squares. Four of them, call them A, B, C and D, sit in a horizontal strip left to right. Square E sits directly above B, and square F sits directly below B. Fold it. The strip of four wraps around the cube as a band, so squares two apart in that strip end up on opposite faces: A is opposite C, and B is opposite D. E and F are the remaining pair, and they become the top and bottom, opposite each other. The two rules that solve almost every net item are exactly these. Squares separated by one square in a straight line end up opposite. Squares sharing an edge on the net end up adjacent on the cube, and can never be opposite. Everything else is applying them carefully. A die adds one more constraint worth carrying: opposite faces of a standard die sum to seven, so 1 faces 6, 2 faces 5 and 3 faces 4, and a net showing 1 and 6 two apart in a strip is consistent while a net showing 1 and 2 two apart is not a standard die. The classic error on these items is trying to fold the net in your head all at once. Do not. Pick one square as the base, identify its opposite by the two-apart rule, then repeat for a second pair, and you have determined the cube in two cheap steps rather than one expensive act of visualisation.

Three views, one solid, and the cubes you cannot see: A solid is built from unit cubes on a base one cube deep and three cubes wide. The column heights, left to right, are 3, 1 and 2. The front view is therefore a staircase profile of heights 3, 1, 2. The side view, looking along the row from the right, is a single column three cubes tall, because the tallest column hides the others behind it. The plan view is a three-by-one rectangle. Total cubes: 3 plus 1 plus 2, which is 6, and here the three views pin it down exactly because the plan view tells you the solid is only one cube deep. Now change one thing. Suppose the plan view is three by two, so the solid is two cubes deep. The front view can still read 3, 1, 2 while the count is anything from 6, one row of cubes with a hollow back, up to 12, a solid block matching the front profile in both rows. The views constrain the shape but do not determine it, and a well-written item will either supply the count or ask for the minimum and maximum rather than a single figure. That is the trap in this family: candidates who assume every hidden position is filled will over-count, and candidates who assume nothing is hidden will under-count. Read the plan view first to establish the footprint, then use the elevations to cap each column, then ask explicitly whether the item wants the minimum, the maximum, or a determined value.

Punched and unfolded, with coordinates: Take a square sheet 8 units across, with the origin at its centre so the corners are at plus or minus 4 in each direction. Fold the right half onto the left half across the vertical centre line, then fold the bottom half up onto the top half across the horizontal centre line. What is left visible is one quarter, the region where x runs from minus 4 to 0 and y runs from 0 to 4. Punch a single hole at the point minus 3, 3. Now unfold, one step at a time, and treat every unfold as a reflection. Undoing the horizontal fold reflects across the line y equals 0 and adds a hole at minus 3, minus 3. Undoing the vertical fold reflects both existing holes across x equals 0 and adds holes at 3, 3 and 3, minus 3. The finished sheet has four holes, at all four combinations of plus or minus 3. Two rules generalise from this. The number of holes is one punch multiplied by two for each fold the punch passed through, so two folds give four holes and three folds give eight, provided the punch went through every layer, which it does when the folds are through the middle. And the positions are mirror images across each fold line, never rotations. That second point is where the marks go: candidates who place the fourth hole by rotational symmetry get three holes right and one wrong, which is exactly the answer option the item includes.

Bearings, and the difference between the map and the walker: A walker leaves a gate, goes 300 m due north, then 400 m due east. The straight-line distance back to the gate is the hypotenuse of a 300 by 400 right triangle, which is 500 m: the 3-4-5 triangle, so no calculator is needed. The bearing from the gate to the walker is measured clockwise from north, and it is the angle whose tangent is 400 over 300, which is about 53 degrees, so the bearing is 053. The return bearing is that plus 180, which is 233. Bearings are always three digits and always clockwise from north, so 53 degrees is written 053 and a bearing of 350 is very slightly west of north, not south. Now the other half of this construct, which trips up more people than the trigonometry. You are facing south and you turn left. Which way are you now facing? East. Your left hand points east when you face south, and the standard wrong answer, west, comes from reading left as left-on-the-map while forgetting that the map is drawn north-up and you are not. The general fix is to state your heading before every turn and rotate your frame with the traveller: facing north, left is west; facing south, left is east; facing east, left is north; facing west, left is south. On route items, physically rotate the page so the direction of travel points up before working out a turn, and rotate it back only to read off the final compass direction.

What a cut actually reveals: Cross-section items ask what shape a plane makes as it slices a solid, and the reflex answer of circle is wrong most of the time. A cylinder cut perpendicular to its axis gives a circle. Cut parallel to the axis, it gives a rectangle. Cut obliquely so the plane crosses only the curved surface, it gives an ellipse; cut obliquely so the plane also crosses one flat end, it gives an ellipse with one side sliced flat, a D-shape. A cone is richer, because its sections are the conic sections that give the family its name: perpendicular to the axis gives a circle; an oblique cut that crosses every side of the cone gives an ellipse; a cut parallel to one slanted side gives a parabola; a cut parallel to the axis gives a hyperbola branch; and a cut through the apex gives a triangle. A cube is the one that surprises people. A cut parallel to a face gives a square, obviously. A cut through three vertices that are mutually adjacent to one corner gives an equilateral triangle. And a cut through the midpoints of six edges, perpendicular to a long diagonal of the cube, gives a regular hexagon: a six-sided section from a six-faced solid with no curves anywhere. For a flat-faced solid, work these by counting faces rather than by visualising: the section of a convex polyhedron gains exactly one straight edge for every face the plane passes through, so a cut crossing six faces of a cube must close into a six-sided figure and a cut touching only three cannot have more than three sides. For curved solids the question becomes whether the plane meets the curved surface all the way round, which gives a closed circle or ellipse, or only partway, which leaves an open arc closed off by a straight chord.

How to practise this skill

• Replace visualisation with a rule wherever one exists. Two-apart-means-opposite on nets, and clockwise-order-preserved for rotations, both give a checkable answer in seconds and are reliable when mental imagery gets tired late in a section.
• Physically rotate the paper or the device on route and orientation items so the direction of travel points up, work out the turn, then rotate back to read the compass direction. Fighting the north-up convention in your head is the single largest source of left-right errors.
• On view and cube-count items, read the plan view first to fix the footprint, then use the elevations to cap each column, then decide explicitly whether the question wants a minimum, a maximum, or a determined count.
• Treat every unfold as a reflection across the fold line. Say the word reflection out loud as you draw each new hole; the rotational version of the pattern is a deliberately included wrong answer in almost every folding item.
• Build a physical reference once. Fold a paper cube net, mark the faces, and hold it: ten minutes with a real cube fixes the opposite-face rule more firmly than an hour of diagrams, and the memory transfers to items you have never seen.
• Practise untimed first and check whether your errors cluster in rotation, folding, views or orientation, because the four subskills train differently. Attempts are stored on this device only, so an honest error log costs nothing and is what tells you which drill to repeat.

Glossary

Chirality (handedness)

The property that distinguishes a figure from its mirror image. Rotation preserves it and reflection reverses it, which is what makes the clockwise-order test decisive for asymmetric figures.

Net

A flat arrangement of faces that folds into a solid. On a cube net, squares two apart in a straight strip become opposite faces and squares sharing an edge become adjacent ones.

Plan view

The view looking straight down on an object. It fixes the footprint of a stacked-cube solid, which is why it is the first view to read.

Elevation

A view looking horizontally at an object, usually given as front and side. Each elevation caps the heights it shows but hides anything directly behind.

Orthographic projection

A drawing convention showing an object through separate parallel views with no perspective. Together the views constrain a solid but do not always determine it.

Bearing

A direction measured clockwise from north and written with three digits, so due east is 090 and a heading slightly west of north is 350. The reverse bearing differs by 180 degrees.

Egocentric versus allocentric frame

The difference between directions relative to a traveller who is turning and directions relative to a fixed map. Left means different compass headings in the two frames, which is why headings must be restated before every turn.

Cross-section

The shape revealed where a plane cuts a solid. It gains one straight edge for each flat face the plane crosses and one curve for each curved surface, which turns the question into a count.

Study this next

• Spatial reasoning skill hub
• Spatial reasoning practice bank
• Mechanical comprehension lesson
• Firefighter spatial reasoning suite
• Architecture and design aptitude suite
• Spatial reasoning lesson on Novus Learn

Where this material comes from

• Worked items written for Novus Learn from standard introductory geometry: cube-net opposite-face rules, orthographic view reconstruction, reflection across fold lines, right-triangle distances and bearings, and the conic and polyhedral cross-sections. The 3-4-5 distance, the 053 and 233 bearings, and the four hole coordinates were each computed and checked.
• Terminology checked against the public Wikipedia articles 'Net (polyhedron)', 'Multiview orthographic projection', 'Chirality', 'Bearing (navigation)' and 'Conic section'. Definitions only; every figure described above is original.
• Novus Learn aptitude construct registry (catalog seed) for the construct scope and related suite mapping.
• Public educational framing only: not affiliated with any official exam board, publisher or employer, and no copyrighted test item is reproduced.

Worked examples and pitfalls

A cancellation count you can actually check: Count every 7 in this row: 4 7 1 7 7 3 9 7 2 8 7 5 7 6 0 7. Working left to right and tapping once per hit: hits at the second, fourth, fifth, eighth, eleventh, thirteenth and sixteenth positions. That is seven sevens. Two error modes produce nearly all the wrong answers. The first is the adjacent pair - the 7 7 at positions four and five gets counted once, because the eye takes a repeated character as one perceptual object. The second is losing the place after the 9, where the visually similar 9 and 7 force a moment of re-checking and the scan restarts a character early, producing an over-count of eight. The defence for both is a fixed scan path with a physical anchor: a fingertip or cursor moving one character at a time, never jumping back. Re-scanning to check is the thing that creates the double-count, so if you must verify, verify by counting a second time from the RIGHT-hand end and comparing totals, never by re-reading part of the row.

Hits, misses and false alarms: the eager candidate loses: A checking batch contains 300 records, 40 of which are genuinely faulty. Candidate A flags 46 records and 36 of them are truly faulty. Hits 36, misses 40 minus 36 equals 4, false alarms 46 minus 36 equals 10. Candidate B flags 38 and 34 are truly faulty: hits 34, misses 6, false alarms 4. On hit rate alone A wins, 36 out of 40 which is 90 percent against B's 34 out of 40 which is 85 percent. Now apply the scoring rule that most checking tasks actually use, where a false alarm cancels a hit: A scores 36 minus 10 equals 26, B scores 34 minus 4 equals 30. B wins by four despite catching two fewer faults. This is why 'flag anything that looks odd' is bad advice on a scored checking task, and why the first thing to read on a checking item is whether wrong flags are penalised. Your response criterion - how much evidence you demand before flagging - is adjustable, and it should be set from the scoring rule, not from your temperament.

The transposition that passes every gist check: Compare these two lines and decide whether they match. Invoice 4820-7391-06. Invoice 4820-7931-06. They do not: the middle group reads 7391 in the first and 7931 in the second, with the 3 and the 9 swapped. Transpositions are the most-missed error class in record checking for a structural reason - the character SET is identical, the length is identical, the first and last characters of the group are identical, so every fast check the visual system runs comes back clean. Substitutions and omissions change the character inventory and get caught; transpositions do not. Two habits raise the catch rate. Read digits in fixed groups of two rather than as a whole number, so 73-91 against 79-31 becomes a mismatch at the first group instead of a subtle difference somewhere in a four-digit blur. And check groups in a deliberately non-natural order - last group, first group, middle group - because reading left to right lets the confirmation you built at the start carry you through the middle, which is exactly where the swap is usually planted.

Conflict: why reading fights you: The classic demonstration is Stroop's, published in 1935: the word RED printed in blue ink, with the instruction to name the ink colour. Naming takes measurably longer, and errors go up, because reading a familiar word is automatic and cannot be switched off, so the automatic response has to be suppressed before the controlled one can be produced. The same conflict has a numeric version you can test on yourself in a second: how many characters are in the string 4 4 4? The answer is three, and the digit 4 pulls at you the entire way. In an assessment this appears wherever the salient feature and the asked-for feature come apart - a chart where the tallest bar is not the answer to the question, a form where the highlighted field is not the one being verified, a row where the bold total is not what the stem requested. The practical move is to name the target feature out loud before you look - 'ink colour', 'character count', 'the value for March' - because pre-loading the target biases selection before the automatic reading response gets a chance to win.

Where the errors actually appear in a 45-minute block: Errors in a long checking block are not spread evenly. Mackworth's 1948 clock-watching study established the pattern that gives the effect its name: detection declines over a prolonged watch, with the sharpest deterioration early rather than at the very end. Practically, on a 45-minute self-timed checking block, expect your per-minute error rate in minutes 20 to 45 to run visibly above minutes 1 to 20 even though nothing about the material changed, and expect the subjective sense of effort to lag the actual decline, so it will not feel like you are getting worse. Two things work against it. Break the block into three fifteen-minute segments with a ten-second reset between them - look away, unfocus, breathe out - which costs thirty seconds of a 45-minute block, about one percent of the time, and buys back more than that in caught errors. And score your practice by segment rather than as one number, because a single overall accuracy figure hides exactly the information you need: whether your problem is skill, which shows as flat error rate, or endurance, which shows as a rising one.

Two streams: alternate on a cadence, do not try to merge: A dispatch-style monitoring task: keep a running total of the numbers announced on channel one while watching channel two for the code word AMBER. Genuine simultaneity is not available - the two tasks compete for the same control resource - so the choice is not whether to alternate but whether to alternate deliberately or accidentally. Deliberate looks like this: fix the arithmetic to a rhythm, updating the total only at each announcement and holding a single number between updates, which frees the gaps for channel two. If the total is 34 and the next announcement is 7, you spend under a second reaching 41 and then you are free again. Accidental looks like re-deriving the running total from the beginning because you did not trust it, which locks up the whole window and is when AMBER goes past unheard. The measurable failure of divided attention is almost never a failure to hear the target; it is a failure to have any spare capacity at the moment it arrived. The related phenomenon worth knowing is inattentional blindness, illustrated by Simons and Chabris in 1999: an unexpected and perfectly visible event is missed entirely when attention is committed to a counting task.

How to practise this skill

• Fix your scan path before you start, and never re-scan backwards to double-check. Backward re-scanning is what produces both double-counts and lost places; if you need to verify a count, run it again from the other end and compare.
• Read the scoring rule before the first item. Whether false alarms are penalised changes the correct strategy completely, and a criterion set for the wrong rule costs more marks than slow reading does.
• Check numeric strings in fixed groups of two or three and in a deliberately shuffled group order. Transpositions are the errors that survive whole-string comparison, and they are the ones planted on purpose.
• Time your practice in segments and log accuracy per segment, not per session. A flat error rate means you need speed; a rising one means you need endurance and breaks, and the two problems have opposite fixes.
• Name the target feature out loud before each conflict item. Pre-loading the relevant dimension is the cheapest available defence against the salient-but-wrong answer.
• Practise with an actual distractor present rather than in silence. A test hall has movement, coughing and page-turning, and attention practice in perfect quiet trains a condition you will not meet.

Glossary

Selective attention

Prioritising one source or feature while suppressing competing ones. It is what fails when the visually salient element of a display captures the response instead of the requested one.

Sustained attention (vigilance)

Maintaining detection performance over a long, low-event period. It is the capacity that checking, monitoring and inspection tasks are really sampling.

Vigilance decrement

The decline in detection performance over a prolonged watch, typically steepest early in the block. Mackworth's 1948 clock test is the standard public reference.

Divided attention

Handling two streams that compete for control. Performance is best modelled as fast alternation with a switch cost, not as genuine parallelism.

Hit, miss, false alarm, correct rejection

The four outcomes of any detection decision: flagging a real fault, missing one, flagging a clean record, and correctly leaving a clean record alone. Any honest accuracy claim needs at least the first three.

Response criterion

How much evidence you require before flagging. Shifting it trades misses against false alarms without changing your underlying sensitivity, which is why it must be set from the scoring rule.

Stroop interference

The slowing that occurs when an automatic response, such as reading a word, conflicts with the requested response, such as naming its ink colour. Named for Stroop's 1935 experiments.

Inattentional blindness

Failing to notice a fully visible, unexpected event because attention is committed elsewhere - the effect Simons and Chabris demonstrated in 1999 with a counting task.

Study this next

• Attention and concentration skill hub
• Cognitive Skills Lab: attention practice
• Emergency dispatch and 911 communications suite
• Error detection lesson
• Perceptual speed lesson
• Attention and concentration lesson on Novus Learn

Where this material comes from

• Character strings, invoice comparisons, batch counts and monitoring scenarios above are written for Novus Learn. All figures are original and no published test item is reproduced.
• Terminology and directions of effect follow widely published work: Mackworth (1948) on the vigilance decrement, Stroop (1935) on response conflict, Simons and Chabris (1999) on inattentional blindness, and the standard hit/miss/false-alarm framing from signal detection theory. Concepts only; no result figures are attributed to those studies.
• Novus Learn aptitude construct registry (catalog seed) for construct scope and suite mapping.
• Public educational framing only - not affiliated with any official exam board, publisher or employer, and not a clinical, diagnostic or attention-disorder screening measure.

Worked examples and pitfalls

Worked scenario: an unverified safety concern: A colleague reports a possible equipment fault while a deadline is approaching. First distinguish the known fact, the report, from the unverified cause. A strong response protects people and affected work, checks the concern through the right channel, tells the relevant lead, and records what was done. Ignoring the report underreacts; shutting down unrelated work or accusing someone before checking the facts overreacts.

Method: facts, duties, risks, response: Write four short notes before ranking options: what is known, who may be affected, which duty or boundary applies, and what safe next step is available now. Prefer an action that addresses the immediate issue and creates useful follow-through. Do not reward an option merely because it sounds decisive.

How to practise this skill

• Answer the question asked: best first action, worst action, or complete response are different tasks.
• Check whether an option acts within the person's authority and escalates only as far as the risk requires.
• When two options look reasonable, prefer the one that gathers missing facts and communicates ownership.

Glossary

Proportionality

Matching the urgency and scope of a response to the evidence, likely impact, and authority available.

Role boundary

The limit of what a person may decide or do without approval, specialist help, or escalation.

Follow-through

Confirming ownership, recording the decision, and checking that the issue was actually resolved.

Study this next

• Situational judgement test
• Workplace ethics
• Decision-making
• Situational judgment lesson on Novus Learn

Where this material comes from

• Novus Learn original situational-judgment suite scenarios and published construct mapping.
• Novus educational framework: facts, duties, risks, role boundaries, proportional action, and follow-through.

Worked examples and pitfalls

Reverse percentages: the item most candidates get backwards: A subscription price rose by 15 percent and now stands at 57.50 pounds. What was it before? The correct move is to divide, not subtract: the new price is 115 percent of the old, so the old price is 57.50 / 1.15 = 50.00. Check it forwards: 15 percent of 50 is 7.50, and 50 + 7.50 = 57.50. The tempting wrong answer takes 15 percent of the NEW figure, 0.15 x 57.50 = 8.625, and reports 48.88. That distractor is always on the option list because it is what most people do under time pressure, and it is wrong by 2.25 percent, small enough to look plausible. The same asymmetry drives the successive-change item: a price that rises 20 percent and then falls 20 percent does not return to where it started. Multiply the factors: 1.20 x 0.80 = 0.96, a net fall of 4 percent. Starting at 500 pounds you get 600 then 480, not 500. Percentages compose by multiplication; they never add.

Ratio splits: count the parts before you divide: A 4,830 pound budget is split between three teams in the ratio 3:5:6. Add the parts first: 3 + 5 + 6 = 14. One part is 4,830 / 14 = 345. The shares are 3 x 345 = 1,035, 5 x 345 = 1,725 and 6 x 345 = 2,070, and they sum back to 4,830, which is the check you should always run. Two classic failures. The first is dividing by 3 because there are three teams. That gives 1,610 each and ignores the ratio entirely. The second is treating 5 as a fraction and computing five sixths or five fourteenths of something other than the total. The more interesting version of this item gives you a difference instead of the total: 'the second team receives 690 pounds more than the first, what is the whole budget?' The difference between the shares is 5 - 3 = 2 parts, so one part is 690 / 2 = 345, and the budget is 14 x 345 = 4,830. Same number, reached from the other end, and the arithmetic is trivial once you have made the parts explicit.

Rates and units: 2 h 15 min is 2.25, not 2.15: A delivery van covers 174 km in 2 hours 15 minutes. Average speed is distance over time, and the time must be in hours: 15 minutes is 15/60 = 0.25 h, so 174 / 2.25 = 77.3 km/h. Type 2.15 into the calculator instead and you get 80.9 km/h: an error of roughly 4.7 percent that sits comfortably inside the plausible range and will match one of the options. Now extend it. The van consumes 8.6 litres per 100 km, so the trip needs 174 x 8.6 / 100 = 14.964 litres, and at 1.48 pounds per litre that is 14.964 x 1.48 = 22.15 pounds. Notice the units doing the work: (km) x (L / 100 km) leaves litres; (L) x (pounds / L) leaves pounds. If your intermediate line has km still attached at the end, you have divided when you should have multiplied. Write the unit next to every number and the method checks itself.

Unit pricing: normalise before you compare: Three pack sizes of the same fluid. Pack A: 750 ml for 3.60 pounds. Pack B: 2 litres for 9.40. Pack C: 1.5 litres for 7.20. Convert all three to price per litre. A: 3.60 / 0.75 = 4.80 per litre. B: 9.40 / 2 = 4.70. C: 7.20 / 1.5 = 4.80. So B is cheapest by 10p a litre, and A and C are identical despite looking like different deals. The 'bigger pack is cheaper' heuristic happens to hold here but is not a rule, and test writers know it. Half of these items are built specifically so the largest pack loses. Now add the multibuy that these questions love: pack A is on three-for-two. Three packs give 2.25 litres for the price of two, 7.20 pounds, which is 7.20 / 2.25 = 3.20 per litre and beats everything. The trap in the multibuy version is dividing by the number of packs paid for rather than the volume received.

Combined work rates: add rates, never times: Printer A completes a 3,000-page run in 50 minutes; printer B completes the same run in 75 minutes. Running together, how long? Convert to rates: A prints 3,000 / 50 = 60 pages per minute, B prints 3,000 / 75 = 40 pages per minute, and together they print 100 pages per minute, so the job takes 3,000 / 100 = 30 minutes. Verify by counting output: in 30 minutes A produces 1,800 pages and B produces 1,200, which is 3,000 exactly. The two wrong answers you will see on the option list are 62.5 minutes (the average of 50 and 75) and 125 minutes (the sum). Both are impossible on inspection: two machines working together must finish faster than the faster machine alone, so any answer above 50 minutes is wrong before you compute anything. The general form is 1 / (1/50 + 1/75), and it is worth being able to write that line directly, but the sanity bound catches the error faster than the algebra does.

Estimate first, then compute: killing distractors in ten seconds: 'A department spent 847,300 pounds in 2024. In 2025 the budget fell by 12.5 percent. What was the 2025 spend?' Options: 741,387.50 / 953,212.50 / 105,912.50 / 762,570. Estimate before anything else: 12.5 percent is exactly one eighth, one eighth of roughly 850,000 is roughly 106,000, so the answer is roughly 744,000. That single line eliminates three options. 953,212.50 applied the change upwards. 105,912.50 is the size of the reduction, not the resulting spend: the 'answered the wrong question' distractor, and the most commonly selected wrong option on items of this shape. 762,570 is a 10 percent cut, planted for anyone who misread the rate. Exact working: 847,300 x 7/8 = 5,931,100 / 8 = 741,387.50. Doing it as a fraction avoids the decimal multiplication altogether. Learn the fraction equivalents cold (12.5 percent is 1/8, 16.7 percent is 1/6, 37.5 percent is 3/8, 62.5 percent is 5/8) because a fraction turns most percentage items into one division.

How to practise this skill

• Memorise the fraction-to-percentage table up to eighths and twelfths. Almost every 'nasty' percentage on these tests is a clean fraction in disguise, and the fraction route is two or three times faster than decimal multiplication.
• Write the unit beside every intermediate number, including the ones you keep in your head. Most numerical errors on timed sections are unit errors, not arithmetic errors, and units are the only cheap way to catch them.
• Rehearse reverse percentages as their own drill until dividing by 1.15 feels more natural than subtracting 15 percent. It is a single, identifiable technique that accounts for a disproportionate share of lost marks.
• Before selecting, re-read the last clause of the stem out loud. 'By how much did it fall' and 'what was it after the fall' have different answers, and both are always on the option list.
• Keep an error log with four columns (misread the question, wrong operation, unit slip, arithmetic slip), and tally which one you actually commit. Three sessions is usually enough to show that one column dominates, and that is the column to train.
• Work untimed until your method is stable, then add the clock in stages: generous, then realistic, then 20 percent tighter than the real test. Attempts stay on this device, so a slow first pass costs nothing.

Glossary

Percentage point

The arithmetic difference between two percentages. A rate moving from 4 percent to 5 percent rises by one percentage point but by 25 percent in relative terms; questions specify which they want and the two answers are both on the option list.

Reverse percentage

Recovering an original amount from a figure that already includes a percentage change, by dividing by the multiplier (1.15 for a 15 percent rise, 0.88 for a 12 percent fall) rather than subtracting the percentage from the new figure.

Multiplier (decimal factor)

The single number a quantity is multiplied by to apply a percentage change: 1.20 for plus 20 percent, 0.80 for minus 20 percent. Successive changes are handled by multiplying the factors, which is why plus 20 then minus 20 gives 0.96, not 1.

Ratio part

One unit of a ratio split. Dividing the total by the sum of the ratio terms gives the value of one part; every share and every difference between shares is then a whole number of parts.

Unit rate

A quantity expressed per one of something: price per litre, pages per minute, litres per 100 km. Comparisons are only valid once every option has been converted to the same unit rate.

Combined rate

The sum of two or more individual rates working simultaneously. Times cannot be added or averaged; only rates add, and the combined time is the total work divided by the combined rate.

Significant figure estimate

Rounding every input to one meaningful digit to get an approximate answer in a few seconds. Its purpose is not accuracy but elimination: it removes any option that is off by a factor or has the sign of the change wrong.

Distractor

A wrong option written deliberately to match a specific predictable error: subtracting instead of dividing, reporting the change instead of the result, averaging instead of combining rates. Recognising the pattern is often faster than recomputing.

Study this next

• Numerical reasoning skill hub
• Numerical reasoning practice in the Cognitive Skills Lab
• Data interpretation lesson
• Office numeracy suite
• Finance, accounting and insurance careers
• Numerical reasoning lesson on Novus Learn

Where this material comes from

• All worked figures above were written and checked for Novus Learn. Every division, ratio split and rate calculation in this lesson was verified by recomputing it in the reverse direction.
• Conventions only (percentage point, unit rate, significant figures) cross-checked against standard public references such as the Wikipedia articles 'Percentage', 'Ratio' and 'Rate (mathematics)'. No item text is drawn from any published test.
• Novus Learn aptitude construct registry (catalog seed) for construct scope and suite mapping.
• Public educational framing only: not affiliated with any official exam board, publisher or employer, and no copyrighted test item is reproduced.

Worked examples and pitfalls

The negation test finds assumptions; nothing else does: Argument: 'The council should fit bin sensors across the district. In the trial depot they cut collection trips by a fifth.' Candidate assumption A: 'The trial depot's waste pattern is broadly representative of the rest of the district.' Negate it - suppose the trial depot is nothing like the rest of the district - and the argument collapses, because a result that does not transfer supports nothing about the district. So A is a required assumption. Candidate assumption B: 'Bin sensors are the cheapest available technology for this purpose.' Negate it - suppose they are the most expensive - and the argument still stands as given, since it argued from a reduction in trips, not from cost. B is not required; it would strengthen a cost-based argument that was never made. Candidate C: 'Fewer collection trips reduce total operating cost.' Negate it and the recommendation loses its point, so C is required too, even though the argument never mentions cost. That last case is the one candidates miss, because the required assumption is what bridges the evidence to the recommendation, and bridging assumptions are by definition unstated. The failure mode across this whole item type is picking statements that support the conclusion instead of statements the argument cannot survive without.

Base rates: 90 percent accurate, 15 percent right: A production line runs an automated defect test. Defects occur in 1 percent of units. The test flags 90 percent of genuinely defective units, and wrongly flags 5 percent of good units. A unit has just been flagged - how likely is it to be defective? Work in whole units rather than probabilities. Take 10,000 units: 100 are defective and 9,900 are good. Of the 100 defective, the test flags 90. Of the 9,900 good, it wrongly flags 5 percent, which is 495. Total flags: 90 + 495 = 585. Of those, 90 are genuine, so the answer is 90 / 585 = 15.4 percent. Better than the 1 percent base rate, and nowhere near the 90 percent that intuition offers. The error has a name - confusing the probability of a flag given a defect with the probability of a defect given a flag - and it has a practical consequence: the rework queue has to be sized for 585 units a batch, not 100, and 495 of the 585 units sitting in it are perfectly good. Whenever a test, screening rule or model accuracy figure appears in an item, ask how many of the negatives there are, because with a rare condition the false positives from a large clean population swamp the true positives from a small affected one.

Three alternative explanations, and the comparison that settles it: Claim: 'Employees who attended the optional resilience workshop took 30 percent fewer sick days last year, so the workshop works.' Alternative one, selection: attendance was optional, so the people who signed up may have been the healthier and more engaged to begin with, and would have taken fewer sick days regardless. Alternative two, reverse direction: employees who were frequently unwell were the least able to attend a full-day workshop, so illness determined attendance rather than the other way round. Alternative three, a common third factor: the workshop ran on Thursday afternoons at head office, so attendance largely tracks being an office-based rather than shift-based worker, and shift workers take more sick leave for reasons that have nothing to do with resilience training. What would settle it: randomly assigning the offer to half the workforce and comparing the two groups. Failing that, the cheapest useful check already exists in the payroll data - compare attendees' and non-attendees' sick days in the year before the workshop. If attendees were already 30 percent lower, selection is doing the entire job. The habit worth building is to name the comparison group before you accept any before-and-after number.

Deduction: affirming the consequent versus modus tollens: Rule: 'If an invoice is over 10,000 euro, it requires two signatures.' Argument A: 'This invoice has two signatures, therefore it is over 10,000 euro.' Invalid - this is affirming the consequent. The rule makes two signatures necessary for large invoices; it says nothing that prevents a cautious manager from double-signing a 400 euro invoice, so a two-signature invoice of any size is consistent with the rule. Argument B: 'This invoice has only one signature, therefore it is not over 10,000 euro.' Valid - this is modus tollens, denying the consequent to deny the antecedent, and it holds assuming the rule was followed. Argument C: 'This invoice is not over 10,000 euro, therefore it does not have two signatures.' Invalid again, denying the antecedent. Two further points that deduction items test directly. First, validity is about form alone: 'All banks close on Sundays; Riverton Mutual is a bank; therefore Riverton Mutual closes on Sundays' is perfectly valid even if the first premise is false, and a valid argument with a false premise can deliver a false conclusion. Second, in these items you must accept the premises as given even when you know them to be untrue, because the question is whether the conclusion follows, not whether it is true.

Interpretation: what a survey figure does and does not license: Data: all 1,200 employees of a firm were surveyed. 62 percent said they would accept a four-day week at 90 percent pay. Of those who said yes, 71 percent were under 35. Conclusion one: 'A majority of this firm's employees would accept the trade.' This follows - 62 percent of a complete census of the firm is a majority, and the conclusion is properly limited to this firm. Conclusion two: 'A majority of the firm's under-35 employees would accept the trade.' This does not follow, and the arithmetic shows why. Sixty-two percent of 1,200 is 744 accepters, and 71 percent of 744 is about 528 accepters aged under 35. That is the composition of the accepters, not the acceptance rate within the under-35 group, and without knowing how many under-35s the firm employs the rate is undetermined: if there are 900, the rate is 528 / 900 = 59 percent; if there are 600, it is 88 percent; if there were 1,100 the rate would be below half. Conclusion three: 'The firm should move to a four-day week.' This does not follow either - a stated preference about pay says nothing about output, shift cover, customer hours or cost. Notice that conclusion two is the base-rate error from the screening example, wearing survey clothing.

Strong and weak arguments on the same question: Question: should the agency publish raw inspection scores for every site? Strong argument for: 'In the neighbouring authority, publication was followed by a measurable fall in repeat violations, which is the stated aim of the inspection regime.' It is directly about this decision, it addresses the regime's own objective, and it offers evidence - and if true it would change your view. Weak argument for: 'Yes, because transparency is always good.' Sweeping, unsupported, and it would apply identically to publishing anything at all, which is the tell. Strong argument against: 'Raw scores omit the severity weighting, so a site with one critical failure can rank above a site with six minor ones, and a member of the public cannot see the difference.' Specific, mechanistic, directly about the proposal, and it would change your view. Weak argument against: 'No, because businesses will object.' It may be true and it may matter politically, but it does not bear on whether publication achieves the regime's aim, and no evidence is offered. Two tests separate strong from weak: is the argument about the exact question asked, and would accepting it change the decision? Note that you can hold a firm personal view on publication and still be required to mark the argument on the other side as the strong one - that split is what the item type is measuring.

How to practise this skill

• Negate every candidate assumption out loud. If the argument survives the negation, it was never an assumption, however supportive it sounds. This single habit converts the assumption item type from guesswork into a mechanical check.
• Write the conclusion in your own words before reading any option. Half of the wrong answers on inference and evaluation items are responses to a conclusion the argument never reached.
• Ask 'percentage of what?' on every percentage in the stimulus and reconstruct the denominator in whole units. Base-rate and composition errors both dissolve the moment you write out counts instead of rates.
• Deliberately practise marking arguments you disagree with as strong and arguments you agree with as weak. Assessments in this construct are built to catch agreement masquerading as evaluation, and the effect is largest on politically loaded stimuli.
• For any causal claim, write two alternatives - selection and a third factor - and name the comparison group that would rule them out, before you decide whether the evidence supports the claim.
• Log wrong answers by task type rather than by topic: inference, assumption, deduction, interpretation, evaluation. Candidates are rarely weak across all five, and the profile tells you where the next hour of practice belongs.

Glossary

Conclusion

The claim an argument is trying to establish. It is not always last, is often signalled by therefore, so, or should, and locating it correctly determines every subsequent judgement about the argument.

Assumption

An unstated premise the argument requires in order to work. Identified by negation: negate it and a genuine assumption brings the argument down, while a merely helpful statement leaves it standing.

Validity and soundness

An argument is valid when the conclusion cannot be false while the premises are true, which is a property of form alone. It is sound when it is valid and the premises are actually true.

Affirming the consequent

The invalid pattern 'if P then Q; Q; therefore P'. It is the most common deductive distractor because it differs from the valid modus tollens form by only the position of a negation.

Base rate

How common something is in the population before any test or evidence is applied. Ignoring it makes accurate-sounding tests appear far more informative than they are when the condition is rare.

Confounder

A third factor associated with both the supposed cause and the outcome, capable of producing the entire observed relationship on its own. Ruled out by randomisation or by an explicit comparison group.

Selection effect

A difference between groups created by how people entered them rather than by the treatment under study. Optional programmes and voluntary surveys are where it appears most often.

Falsifiability

The property of a claim that some observation could show it to be wrong. A claim compatible with every possible result carries no information, which is why 'what would change your mind?' is a diagnostic question.

Study this next

• Critical thinking skill hub
• Practise the critical thinking bank
• Verbal reasoning lesson
• Government audit suite
• Investigator and detective reasoning suite
• Critical thinking lesson on Novus Learn

Where this material comes from

• Worked items written for Novus Learn. The arguments, survey figures, defect-test numbers and evaluation options above are original and invented for this lesson; no published or copyrighted test item is reproduced.
• The five task types named in the summary - inference, assumption, deduction, interpretation, evaluation of arguments - describe a structure used publicly across several critical-thinking assessments; no affiliation with any publisher is claimed or implied.
• Terminology follows standard, widely published usage in introductory logic and research methods - validity, soundness, affirming the consequent, base rate, confounder, selection effect.
• Novus Learn aptitude construct registry (catalog seed) for the construct scope and the suite mapping shown in the related links.
• Public educational framing only - not affiliated with any official exam board, publisher or employer.