Education and educational support · suite apt-263-teaching-assistant · generated 2026-09-15T15:25:00.380Z
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.
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.
Selecting methods, combining information, troubleshooting, and reaching practical solutions.
Problem solving is the construct that asks you to choose a method, not just execute one: to combine a table with a rule, decide whether an estimate settles the question or an exact calculation is needed, narrow a fault by halving the search space, and check the answer against the constraint that actually binds. It shows up across operations, logistics, manufacturing, technician and analyst selection, and in the situational sections of public-safety batteries. It is also the construct where the marking rewards a defensible route as much as a number. Everything you practise stays on this device unless you export it.
What you should be able to do after this lesson:
Two price structures and the distance where they cross: A delivery of 55 km. Courier A charges 8.00 base plus 0.45 per km. Courier B charges 20.00 flat for the first 40 km, then 0.90 per km beyond that. Which is cheaper? Courier A costs 8 plus 0.45 times 55, which is 8 plus 24.75, giving 32.75. Courier B costs 20 plus 0.90 times 15, which is 20 plus 13.50, giving 33.50. Courier A wins by 0.75. Now the question the item is really testing: is A always cheaper? At 45 km, A costs 8 plus 20.25 which is 28.25, while B costs 20 plus 4.50 which is 24.50. B wins comfortably. So the answer flips somewhere between, and finding where is one line of algebra. Above 40 km, B costs 20 plus 0.9 times distance minus 40, which simplifies to 0.9d minus 16. Set that equal to A's 8 plus 0.45d: 8 plus 0.45d equals 0.9d minus 16, so 24 equals 0.45d, so d is about 53.3 km. Below 53.3 km B is cheaper; above it A is. Check at the crossover: A is 8 plus 24 which is 32.00, and B is 48 minus 16 which is also 32.00. The general lesson is that whichever option has the lower per-unit rate always wins eventually, regardless of the base charges, and the base charges only decide where eventually starts. A single quoted distance never answers a which-is-cheaper question for a fleet.
Halving the search space beats walking the chain: Forty sensors sit on a single daisy-chained cable and exactly one connection is broken, cutting off everything downstream. How many tests do you need in the worst case? Walking the chain from one end and testing each sensor in turn takes up to 40 tests and 20 on average. Test the midpoint instead. If sensor 20 responds, the break is in the upper half and you have eliminated 20 candidates in one measurement; if it does not, the break is below and you have eliminated the other 20. Repeat on the surviving half: 40 becomes 20, then 10, then 5, then 3, then 2, then 1. Six tests, worst case, because each test halves what is left and two to the power six is 64, comfortably more than 40. The saving grows as the problem grows: 1,000 candidates need only ten tests. Two conditions have to hold for bisection to be valid, and stating them is part of the answer. The fault must be monotone, meaning everything on one side of the break behaves differently from everything on the other; and a single test at any point must tell you which side you are on. When there are two independent breaks, or when a test is only meaningful at the ends, bisection does not apply and a different strategy is needed. Candidates who reach for bisection reflexively on a problem that fails those conditions lose more than they save.
Working backwards from the number you were given: A team started a quarter with an unknown budget. In week one it spent half of it. In week two it spent 400 of what remained. In week three it spent a third of what remained after that. It finished with 1,200. How much did it start with? Attempting this forwards means carrying an unknown through three operations. Backwards it is arithmetic. After week three, 1,200 is what is left having spent a third, so 1,200 represents two thirds of the week-three opening balance, which was therefore 1,800. Before week two's spend of 400, the balance was 1,800 plus 400, which is 2,200. That 2,200 is what remained after spending half, so the starting budget was 4,400. Verify forwards, always: 4,400 less half is 2,200; less 400 is 1,800; less a third of 1,800, which is 600, leaves 1,200. Correct. The mechanical rule is to invert each operation and apply the inversions in reverse order. The inverse of spending a third is dividing by two thirds, not multiplying by three, and that specific slip is the most common wrong answer in this family. Working backwards is the right tool whenever the end state is known exactly and the operations are individually invertible, which covers most budget, mixture and journey problems phrased as how much did it start with.
When an estimate is enough, and when it is not: A maintenance window is three hours. Two technicians must service 1,850 units, each taking about 4.5 minutes, plus a shared 20-minute setup and 15-minute teardown. Feasible? Estimate first: 1,850 units at 4.5 minutes is 8,325 technician-minutes; split between two people that is about 4,163 minutes, which is roughly 69 hours. The window is 3 hours. The answer is no by a factor of more than twenty, and no refinement of the setup and teardown figures could change it. Precision here would be wasted effort. Now the same problem with 90 units. Ninety at 4.5 minutes is 405 technician-minutes, halved to 202.5 minutes, plus 35 minutes of setup and teardown, giving 237.5 minutes. That is 3 hours and 57 and a half minutes against a 3-hour window. Still no, but only just, and now every assumption matters: whether the technicians can genuinely work in parallel, whether setup is shared or duplicated, whether 4.5 minutes is a mean or a best case. The judgement being assessed is knowing which regime you are in. If your rough figure misses the target by an order of magnitude, stop and answer. If it lands within a factor of two, the estimate has not settled anything and you must do the exact arithmetic and name your assumptions.
The binding constraint decides, and it is rarely the obvious one: A van carries at most 900 kg and at most 6 cubic metres. Pallet type X weighs 150 kg, occupies 0.8 cubic metres and is worth 200. Pallet type Y weighs 90 kg, occupies 1.4 cubic metres and is worth 260. What mix maximises value? The instinctive heuristic is value per kilogram: X gives 200 over 150, about 1.33, while Y gives 260 over 90, about 2.89, so load Y. That is wrong, and the reason is that weight is not what runs out. Value per cubic metre tells the opposite story: X gives 250 and Y gives about 186. Enumerate the feasible whole-pallet mixes. Six X uses 900 kg and 4.8 cubic metres, worth 1,200. Five X and one Y uses 840 kg and 5.4 cubic metres, worth 1,260. Four X and two Y uses 780 kg and exactly 6.0 cubic metres, worth 1,320. Three X and three Y needs 6.6 cubic metres and does not fit. Two X and three Y uses 570 kg and 5.8 cubic metres, worth 1,180. Four Y alone uses 5.6 cubic metres and is worth 1,040. The best mix is four X and two Y at 1,320. Look at what binds it: volume is used to the last cubic metre while 120 kg of payload goes unused. Once volume is identified as the binding constraint, X's superior value per cubic metre explains the X-heavy answer, and the spare weight explains why two Y still get on board. The transferable move is to compute the usage of every constraint at your proposed answer and see which one is exhausted; a per-unit ratio computed against a non-binding resource is worse than no heuristic at all.
Cause, symptom, and the test that tells them apart: A pump trips out twice a shift. The obvious fix is to reset it, which works for about four hours. Ask why once and you find the thermal overload relay is tripping. Ask again and the motor is running hot. Again and the bearing is running hot. Again and the grease has dried out. Again and the lubrication interval was set for a duty cycle far lighter than the pump has actually been running since the line was rebalanced last year. Each level supports a different fix: resetting the trip costs nothing and lasts four hours; replacing the relay costs a part and lasts until the bearing seizes; regreasing lasts weeks; changing the lubrication schedule to match the real duty cycle is the one that stops the fault recurring. Stop asking why when the next answer stops being something you can act on, or when it leaves the boundary of the system you can change. There is one discipline that separates this from storytelling. A correlation is a lead, not a cause: the fact that the trips started after the line was rebalanced is suggestive, not proof. The confirming test is to intervene and observe: restore the original duty cycle, or apply the corrected greasing interval to this pump and not to the identical one on the parallel line, and see which one trips. If a proposed cause cannot be tested by changing it, treat it as a hypothesis and say so rather than closing the investigation.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
Understanding passages, instructions, policies, technical material, and workplace documents.
Reading comprehension is the ability to take a passage, a policy clause, a procedure or a technical note and answer accurately about what it says, what it means, and how it applies to a case in front of you. It is assessed directly in casework, policy analysis, immigration and language-focused batteries, and it sits underneath almost every other written test as the thing that has to work before anything else can. On the job it is the difference between applying an eligibility rule correctly the first time and generating an appeal. Everything you practise here is stored on this device; there is no account and no upload.
What you should be able to do after this lesson:
Main idea: scope, not truth: Passage: 'When the Kirkwall depot adopted route-optimisation software in 2021, its drivers covered 9 percent fewer kilometres in the first quarter, and fuel spending fell by a similar margin. Delivery times improved on urban routes only; rural routes were unchanged, and two drivers reported longer split shifts. The depot manager has kept the software but now overrides its rural schedules by hand.' Which option states the main idea? (a) 'Route-optimisation software reduces fuel costs.' True, and it is exactly one third of the passage - it drops the mixed results and the override, so it is too narrow. (b) 'The software failed at Kirkwall.' Contradicted: mileage and fuel both improved, and the depot kept it. (c) 'Rural deliveries are harder to optimise than urban ones.' A generalisation the passage never makes; it reports one depot, one year, without explaining why rural routes were unchanged. Too broad. (d) 'At one depot the software produced clear mileage and fuel savings but uneven results elsewhere, so it is now used with manual override.' Correct - it covers all three sentences and no more. The lesson generalises: main-idea distractors are usually wrong for scope, and the two commonest failures are a true detail promoted to the main point, and a reasonable-sounding claim the passage never actually makes.
Reading a clause exactly: and, at least, more than, unless: Rule: 'An employee may claim the remote-working allowance if they work from home on at least three scheduled days per week AND their home is more than 40 km from their assigned office, unless they already receive the travel-card subsidy.' Four cases. Priya works from home four days, lives 52 km away, and receives the travel-card subsidy: not eligible - she satisfies both qualifying conditions, and the 'unless' clause overrides both. Tom works from home three days, lives 38 km away, no subsidy: not eligible, because the connective is AND and 38 is not more than 40. Dan works from home two days, lives 60 km away, no subsidy: not eligible, failing the days condition for the same structural reason. Mira works three days, lives 41 km away, no subsidy: eligible - 'at least three' includes exactly three, and 41 is more than 40. Three separate traps live in one sentence: reading AND as OR under time pressure, treating 'more than 40' as including 40, and forgetting that an exception clause outranks the conditions it follows. The reliable method is to rewrite the rule as a checklist - condition 1, connective, condition 2, then exception - before you look at any case.
Vocabulary in context: the evidence is in the next clause: Sentence: 'The auditor's remarks were characteristically dry, and the board took a full minute to realise she had been criticising them.' Which meaning does 'dry' carry here? (a) arid or lacking moisture, (b) dull and lacking interest, (c) understated and quietly ironic, (d) free of alcohol. Option (b) is the distractor that catches most people, because it is the commonest figurative sense and it half-fits an auditor. But the clause after 'and' is doing the work: a remark that takes a minute to land as criticism is understated, not boring - dullness would not delay recognition, it would only reduce attention. The answer is (c). The general method for vocabulary-in-context items is to ignore the word for a moment, read the rest of the sentence as evidence, and ask what property the sentence requires the word to have. Test items are built so that the most frequent sense of the word is available as an option and is wrong; if the most obvious meaning were correct, the item would measure nothing.
Referents: the former, the latter, and the noun three sentences back: Passage: 'Two remedies were proposed: a fixed surcharge on late filings, and a sliding penalty tied to the amount owed. The committee rejected the former on fairness grounds, noting that it would fall hardest on the smallest filers.' Which remedy was rejected? 'The former' is the first item mentioned, so the fixed surcharge. Candidates who skim choose the sliding penalty because it sits nearer to the pronoun, which is exactly why the item is written this way. Notice also the free consistency check built into the sentence: a fixed amount is the one that lands hardest on small filers, because the same sum is a larger share of a smaller liability, while a penalty tied to the amount owed scales with size by construction. When a passage gives you the reason alongside the reference, use it to confirm the reference. The harder version of this item type replaces 'the former' with a bare 'it' after a sentence containing three noun phrases, and the technique is the same: write the candidate referents in the margin and substitute each one into the sentence to see which produces a sentence the passage could have meant.
Whose view is this? Stance versus report: Passage: 'Supporters of the levy argue that it will fund three new depots within a decade. That projection rests on traffic volumes holding at 2019 levels, which no forecast in the sector now expects.' Question: what is the author's position? (a) The author supports the levy. (b) The author opposes the levy. (c) The author doubts the depot projection. (d) The author has no view. The correct answer is (c). The stance markers are 'rests on', which frames the projection as dependent on a condition, and 'which no forecast now expects', which tells you the condition is not met. Option (b) is the trap, and it is a scope error dressed as a tone question: undermining one argument made by supporters is not opposition to the policy, and the passage says nothing about the levy's other merits or costs. Reading for stance means reading the author's verbs and qualifiers rather than the content of the views being described - a passage can spend four sentences laying out a position it goes on to dismantle in the fifth.
Procedures: when two steps both fire: Instructions: '1. Record the meter reading. 2. If the reading is lower than last month's, do not submit; raise a query instead. 3. Otherwise, submit the reading and file the photo. 4. If the reading is more than double last month's, submit the reading and flag it for review.' Case A: last month 4,180, this month 9,020. Step 2 does not apply, since 9,020 is higher. Step 3 applies: submit and file the photo. Does step 4 also apply? Double 4,180 is 8,360, and 9,020 is more than that, so yes - submit, file the photo, and flag for review. Steps 3 and 4 are not alternatives; nothing in the list makes them exclusive, and both instruct you to submit, which is consistent. Case B: last month 4,180, this month 4,090. Step 2 fires: do not submit, raise a query. Steps 3 and 4 never come into play, because step 3 begins 'otherwise' and step 4's condition is not met either. The trap in case A is treating a numbered list as a decision tree where exactly one branch executes. Read each step's condition independently unless the procedure explicitly says to stop.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
Service recovery, communication, escalation, and policy application.
Learn to recover service without making promises outside your authority: acknowledge the impact, clarify the desired outcome, explain constraints plainly, take an authorized next step, and close the loop.
What you should be able to do after this lesson:
Worked scenario: a refund outside your authority: A customer asks for an immediate refund larger than your approval limit. Acknowledge the delay and confirm what outcome they need, explain the approval boundary without hiding behind jargon, collect the facts the approver needs, and give a realistic update time. Promising the refund may create a second failure; refusing without a route forward leaves the first failure unresolved.
Service-recovery sequence: Use five moves: listen, summarize, acknowledge impact, act within policy, and confirm follow-up. An apology alone is incomplete, while compensation without understanding the issue can be inconsistent or unauthorized.
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.