Commercial assessment-provider familiarization · suite apt-355-aon-style-assessment-familiarization · generated 2026-09-15T21:52:00.267Z
Private practice result. Not an official exam certificate, employer decision, hiring signal, admissions decision, or guaranteed outcome. Scores stay on this device unless you export them.
Answer keys and scoring logic stay server-side and are never included in any download or export.
This file contains the whole study outline for this suite: every skill it draws on, the full lesson for each of those skills, worked examples, practice tips, a glossary, and where each piece of material comes from. Nothing here is a summary of a page you still have to visit.
Practice attempts are stored on the device you used, never on an account. Exporting a result is the only way anything leaves that device.
| Mode | Duration | What it is for |
|---|---|---|
| Guided practice | 15 minutes | Untimed, with feedback after every item. |
| Mini-test | 18 minutes | A short timed set for checking pace. |
| Full simulation | 45 minutes | Full length and full time, in one sitting. |
This suite draws on 5 skill constructs. Each one below carries its complete lesson.
Evaluating workplace responses against role-relevant principles.
Learn a repeatable way to compare workplace responses: establish the facts, identify duties and risks, respect role boundaries, then choose a proportionate first action. This is educational preparation, not an official scoring guide.
What you should be able to do after this lesson:
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.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
Tracking multiple streams, priorities, alerts, and changing conditions.
Practise monitoring several information streams without treating every change as equally urgent. Define normal ranges and action thresholds, keep a reliable scan, and protect handoffs when attention must switch.
What you should be able to do after this lesson:
Worked scenario: alert, call, and routine log: A dashboard crosses a defined critical threshold while a caller asks for a non-urgent update and a routine log is due later. Acknowledge the critical alert, stabilize or escalate it under the procedure, tell the caller when ownership will return, and leave a time-stamped note before resuming. Finishing the easy log first feels productive but ignores consequence; trying to answer everything at once weakens all three tasks.
Scan–detect–decide–record: Set a repeatable scan order, compare each stream with its expected range, act only when a threshold or trend requires it, and record the state before switching. This reduces memory load and makes the next handoff recoverable.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
Completing simple cognitive operations accurately and efficiently.
Processing speed is how fast you can carry out simple cognitive operations that each require a decision (substituting symbols for digits, adding two small numbers, judging which of two words comes later alphabetically) repeated many times under a clock. It differs from perceptual speed in that a rule has to be applied, not just a match made, and that difference is why automating the rule is the whole game. It appears in short commercial cognitive batteries, game-based assessments, data entry screening and several graduate sifts. Practice here is device-local: no account, and results stay on this device unless you export them.
What you should be able to do after this lesson:
Substitution: turning a lookup into a recall: A key maps six letters to digits: Q = 1, W = 2, E = 3, R = 4, T = 5, Y = 6. The sequence W E Y Q R T E W becomes 2 3 6 1 4 5 3 2. Trivial, and that is the point. The item content is not the difficulty. Break the per-item cost into three parts: a glance up to the key and back, the match itself, and writing or keying the digit. Say those cost roughly 0.3, 0.4 and 0.5 seconds while you are still reading the key, giving 1.2 seconds per item and 72 seconds for sixty items. Once the six pairs are held in memory, the glance disappears and each item costs about 0.9 seconds, so sixty items take 54 seconds: a saving of about 25 percent. The investment arithmetic matters: at 0.3 seconds saved per item, ten seconds spent deliberately rehearsing six pairs is repaid after about 34 items and everything after that is profit, whereas thirty seconds of rehearsal would need 100 items to break even. So on a short section, learn the key quickly and imperfectly; on a long one, learn it properly. Use your own measured times rather than the illustrative ones above. The structure of the decision is what transfers, not the numbers.
The optimum error rate is not zero: A 90-second section scored one point per correct answer, nothing deducted for a wrong one. Three paces. Careful at 1.8 seconds an item: 90 / 1.8 = 50 attempted, 96 percent right, 48 correct and 2 wrong. Brisk at 1.2 seconds: 75 attempted, 92 percent right, 69 correct and 6 wrong. Reckless at 0.75 seconds: 120 attempted, 70 percent right, 84 correct and 36 wrong. Under raw scoring the totals are 48, 69 and 84, so faster keeps winning right up to the point where accuracy collapses entirely, and most candidates sit nowhere near that point, which is why 'slow down and be careful' is such common and such bad advice on a no-penalty section. Now change the rule to correct minus incorrect: 48 - 2 = 46, 69 - 6 = 63, 84 - 36 = 48. The brisk pace wins and the reckless pace has fallen back to roughly where the careful one sits. Change it again to correct minus twice incorrect: 44, 57 and 12. Brisk wins by more, and reckless is now catastrophic. Three scoring rules, three different optimal paces, and under none of them is the answer either extreme. The instruction screen gives you the penalty; only your own practice log gives you the accuracy you actually hold at each pace.
Switch cost: the same items, slower, for free: Take forty items, twenty additions and twenty alphabetical comparisons. Present them in two blocks of twenty and people complete them faster than when the same forty items are interleaved one after the other, even though not a single item has changed. The extra time is switch cost: reconfiguring the mental task set on every alternation. If a blocked pace is 1.0 second an item and a mixed pace is 1.25, eighty items cost 80 seconds blocked and 100 seconds mixed, and the 20-second difference bought you nothing. The practical consequences are concrete. On a paper form or a scrollable list where you control the order, do all items of one type first and then the other. On a randomised screen where you cannot, expect the mixed rate and do not interpret it as having got worse. And in real work, batching the same kind of task (all the invoices, then all the emails) is the same effect, which is why an interruption costs far more than the seconds it occupies.
Rate, not raw score: comparing two practice sessions: Session 1: six minutes, 148 correct, 9 wrong. Session 2: four minutes, 112 correct, 4 wrong. On raw correct, session 1 looks better by 36. Convert to rates: 148 / 6 = 24.7 correct per minute against 112 / 4 = 28.0. Convert the errors to rates too: 9 out of 157 attempted is 5.7 percent, against 4 out of 116 which is 3.4 percent. Session 2 is better on both dimensions, faster and more accurate, and the raw comparison had it backwards purely because it ran for two minutes less. This is the most common self-assessment error in speed practice, and it matters because it drives the wrong training decision: the candidate concludes that longer sessions suit them and keeps practising in a way that inflates the number they are watching. Log four figures per session: duration, attempted, correct, wrong. Everything else is derivable, and no comparison should ever be made on a figure that has duration baked into it.
Automating the easy arithmetic: Processing speed sections use arithmetic that is deliberately easy, which means what is being measured is whether it has become automatic. Compensation is the main technique: 38 + 47 becomes 40 + 45 = 85, moving two across so there is no carry to track. Rounding and correcting handles multiplication: 6 x 24 is 6 x 25 - 6 = 150 - 6 = 144, and 49 x 8 is 50 x 8 - 8 = 392. Percentages decompose: 15 percent of 320 is 10 percent, 32, plus half of that, 16, giving 48. Division by four is halving twice, so 96 becomes 48 becomes 24. None of these is clever, and that is exactly why they work under time pressure. Each replaces a multi-step procedure with one you can run without holding intermediate state. Drill them until you stop noticing which method you used. The distinction that matters is between knowing a shortcut and having automated it; on a two-second-per-item section, a shortcut you have to consciously select is barely faster than the long way.
What actually moves a speeded score on the day: Four things reliably cost points and all four are controllable. First, an unfamiliar input device: practising on a laptop and sitting the test with an external mouse, or drilling on a full keyboard with a dedicated numeric pad and meeting a compact one where the digits live on the top row, changes a motor skill you had automated. Second, interruptions: a notification mid-block costs the item you were on plus the next one or two while the task set is rebuilt, which is switch cost arriving uninvited. Third, no warm-up: the first thirty seconds of a cold speeded section are measurably slower, so two minutes of low-stakes practice before a timed attempt is not superstition. Fourth, unrecorded conditions: a bad session with no note of why looks in your log like a decline in ability. Write down the device, the time of day, the sleep and whether you warmed up. A speeded score is sensitive to all of these in a way a reasoning score simply is not, and half of an apparent plateau usually turns out to be uncontrolled conditions rather than a real ceiling.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
Holding, updating, and manipulating short sequences, rules, or instructions.
Working memory is the small, fast, easily disrupted workspace you use to hold a few items while you do something to them: reversing a digit string, keeping a running total, tracking which rule is currently in force. It is not general memory and it is not intelligence; it is capacity plus the ability to update and resist interference. Assessment batteries probe it with backward span, letter-number sequencing, n-back and running-memory tasks, and game-based screens lean on it heavily. At work it shows up whenever you hold a customer's account number while navigating three screens, or carry a partial calculation while someone talks at you. Everything you practise here is device-local: no account, and nothing leaves the device unless you export it.
What you should be able to do after this lesson:
Backward span: chunk first, then reverse the chunks: Read this once and answer without looking back: 7 2 9 4 1 6 3 8, reported backwards. Item-by-item reversal fails around six digits because you are re-reading a decaying trace eight times. Chunk instead. Pair them at input: 72, 94, 16, 38 - four items, comfortably inside span. Now reverse the chunk order and the pair inside each: 38 becomes 83, 16 becomes 61, 94 becomes 49, 72 becomes 27. Output 8 3 6 1 4 9 2 7. Check it against the original read left to right and it matches. The trap is a partial reversal: candidates reverse the chunks but forget to reverse inside them and answer 3 8 1 6 9 4 7 2, which looks right because every digit is present and the first digit is plausibly near the end of the original. That answer is tempting precisely because the gist check - same digits, roughly backwards - passes. Only a position check catches it, so verify the FIRST digit you output equals the LAST digit you heard, then stop worrying and recite.
N-back: the lure sits one position away: A 2-back task on the letter stream T, L, T, K, R, K, R, R, M. You press only when the current letter matches the one two positions earlier. Walk it. Position 3 is T against position 1, T - target. Position 4 is K against position 2, L - no. Position 5 is R against position 3, T - no. Position 6 is K against position 4, K - target. Position 7 is R against position 5, R - target. Position 8 is R against position 6, K - no, and this is the whole point of the item: position 8 matches position 7, an immediate repeat that feels overwhelmingly like a hit. It is a 1-back lure. Position 9 is M against position 7, R - no. Three targets: positions 3, 6 and 7. Familiarity is the wrong signal here, because the recent repeat is the most familiar thing in the stream; the task requires position, not familiarity. The practical defence is to run a strict two-slot window and physically discard the older slot as each new letter arrives, rather than letting a queue of five or six letters build up.
Letter-number sequencing: two sorts, one pass: Presented: R 4 B 9 K 1 M 7. The instruction is to report the numbers in ascending order first, then the letters in alphabetical order. Splitting at input is what makes this tractable: as each character arrives, drop it into one of two mental piles instead of storing the presented order at all. Numbers pile: 4, 9, 1, 7, sorted to 1 4 7 9. Letters pile: R, B, K, M, sorted to B K M R. Answer: 1 4 7 9 B K M R. Candidates who store all eight characters in the order given then try to sort afterwards are holding eight items and running two sorts on a decaying trace, which is roughly double the load for no benefit. The common wrong answer preserves presented order inside each pile - 4 9 1 7 B K M R - because the sort step was dropped under load while the split step survived. If you can only do one thing well under pressure, sort at input and let presentation order go.
Sequential arithmetic: never hold two partial results: Instructions given aloud, one line at a time: start at 17, multiply by 4, subtract 12, divide by 8, add 19. Run it strictly in order. 17 x 4 = 68. 68 - 12 = 56. 56 / 8 = 7. 7 + 19 = 26. The answer is 26. Two traps live here. First, order of operations: this is a sequence of instructions, not an algebraic expression, so nobody does the division before the subtraction, and a candidate who silently applies precedence rules gets a different and confidently wrong number. Second, load: the discipline is that after each line, only ONE number exists. The moment you are carrying both 68 and 12 as separate live values you have doubled the load for no reason. The same discipline turns awkward multiplications into easy ones by rounding to a friendly anchor and correcting once: 68 x 7 becomes 70 x 7 = 490, minus 2 x 7 = 14, giving 476. One anchor, one correction, one live value at a time.
Rule updating: the stale value is what gets marked wrong: The standing rule is to sort a support queue by priority, High before Low. An exception is added: if the queue name begins with a vowel, sort by age instead, oldest first. The queue is Onboarding, holding ticket A (High, 2 days old), ticket B (Low, 9 days) and ticket C (High, 5 days). Onboarding begins with O, so the exception is live and priority is now irrelevant. Sorted by age, oldest first: B, C, A. The tempting answer is A, C, B - the two High tickets first, oldest of them leading - because the priority labels are the most visually salient thing on the screen and the exception was a single clause read several seconds ago. This is what working-memory items actually test: not whether you can sort, but whether the currently active rule successfully overwrote the default. The habit that fixes it is to say the live rule out loud, in one short phrase, immediately before you act - 'vowel, so age, oldest first' - which forces a retrieval of the rule rather than a retrieval of the habit.
Why some lists are heavier than others of the same length: Span is not measured in items alone. Hold B, C, D, G, P, T, V - seven letters that all rhyme in English. Now hold F, K, L, Q, R, Y, W - also seven letters, but acoustically distinct. Almost everyone recalls the second set more accurately, and the errors on the first set are confusions within the rhyming set rather than lost items. That is the phonological similarity effect, reported by Conrad and Hull in 1964, and it tells you the verbal store holds something sound-like. Length matters the same way: five short country names - Chad, Burma, Greece, Cuba, Malta - are easier to hold than five long ones such as Nicaragua, Afghanistan, Venezuela, Madagascar and Yugoslavia, an effect Baddeley, Thomson and Buchanan reported in 1975 and tied to how much can be rehearsed in about two seconds. The practical consequence for a test: when material is confusable, stop rehearsing it as sound and re-encode it visually or spatially - imagine the digits on a keypad, or the letters at clock positions - because that moves the load to a different store instead of stacking it in the one that is already saturated.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
Sustained focus, selective attention, and accuracy under time pressure.
Attention and concentration is the skill of still noticing on minute forty of a checking block as reliably as you did on minute two, and of pointing the noticing at the right thing when two things compete. It has three distinguishable parts - selective attention, sustained attention or vigilance, and divided attention - and assessments load them differently: cancellation and checking tasks load vigilance, conflict tasks load selection, and dispatch-style monitoring loads division. It is the construct that decides whether a records clerk, a dispatcher, an air-side controller or a quality inspector catches the one wrong digit in a shift. Practice here is device-local, with no account and nothing uploaded.
What you should be able to do after this lesson:
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.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
Answer keys and scoring logic stay server-side and are never included in any download or export.
Formal suite answer keys and scoring logic stay on the server and are not part of any download, in any format. Downloadable keys exist only for the open, untimed practice material (the practice packs on the puzzles, cognitive-skills and reasoning practice lab pages), where the answers are already public teaching content.
Novus Learn needs no account. Your practice history lives in this browser's storage on this device, and is sent to a server only if you create an account and switch on backup. This file contains no attempt, session or result link, so it is safe to share.