Administration, clerical, records, and office support · suite apt-304-administrative-assistant · generated 2026-09-15T15:10:10.469Z
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.
Resources, dependencies, deadlines, constraints, and contingency planning.
Learn to build a feasible schedule from dependencies, resource limits, deadlines, and uncertainty. A strong plan makes the critical sequence visible and includes triggers for replanning.
What you should be able to do after this lesson:
Worked scenario: a four-hour shutdown: Inspection takes 30 minutes before either repair can start. Two repairs take 90 and 120 minutes, but both need the same technician; testing takes 45 minutes after both finish. The minimum sequence is 30 + 90 + 120 + 45 = 285 minutes, longer than the shutdown. The correct response is to surface the conflict and change scope, staffing, or window, not to place overlapping bars on a chart and call the plan feasible.
Dependency and contingency check: Draw arrows between tasks, then mark scarce resources and approval gates. For the highest-risk dependency, define an early warning and a response: for example, if a permit is not approved by noon, defer nonessential work and notify the owner rather than discovering the conflict at start time.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
Grammar, vocabulary, sentence correction, clarity, tone, proofreading, and workplace writing.
Written communication is assessed in two quite different ways: multiple-choice sentence-correction and proofreading items that test whether you can name and fix a specific grammatical fault, and free-text exercises - an email, an incident note, a briefing - marked on structure, accuracy and tone. It appears in clerical and administrative entry tests, legal support and paralegal batteries, teacher selection, public relations sifts, and any role where a badly worded sentence becomes somebody else's problem. The two formats reward the same underlying skill: knowing what a sentence claims and making it claim exactly that. Practice is device-local, with no account and nothing uploaded unless you export it.
What you should be able to do after this lesson:
Agreement: find the head noun, then decide: 'The set of quarterly returns filed by the three regional offices (was / were) incomplete.' The subject is 'the set', which is singular, so 'was' is correct; 'offices' is merely the nearest noun, sitting inside a prepositional phrase that cannot supply the subject. Strike out everything between the head noun and the verb and the choice becomes obvious - 'the set was incomplete'. Next: 'Neither the manager nor the two supervisors (was / were) informed.' With neither/nor the verb agrees with the nearer of the two subjects, and the nearer one here is 'the two supervisors', so 'were' is correct. Reverse the order - 'Neither the two supervisors nor the manager was informed' - and the correct verb flips to singular, which is a useful check that you are applying the rule rather than guessing. Finally, a pair that trips experienced writers: 'A number of applications are missing' is correct, because 'a number of' functions as a plural quantifier, while 'The number of applications is rising' is also correct, because there 'the number' is a single quantity. Same three words, opposite verbs.
Dangling modifiers and the wandering 'only': 'Having reviewed the tender documents, the deadline was extended by two weeks.' An opening participial phrase attaches to the subject of the main clause, and the subject here is 'the deadline', so the sentence says the deadline reviewed the documents. It reads acceptably aloud because a listener silently supplies the missing actor, which is precisely why this error survives proofreading. Two clean fixes: name the actor as the subject - 'Having reviewed the tender documents, the panel extended the deadline by two weeks' - or drop the participle entirely - 'The panel reviewed the tender documents and extended the deadline by two weeks.' Now the limiting word. 'We only sent the invoice to three suppliers' literally says that sending was the only thing we did to those three. 'We sent the invoice to only three suppliers' says we sent it to no more than three. 'We sent only the invoice to three suppliers' says we sent nothing else. Three placements, three meanings, one word - put 'only', 'just', 'even' and 'almost' immediately before what they limit, and in a marked item the four options usually differ by nothing else.
Parallelism in a list: 'The role involves drafting reports, client liaison, and to maintain the case register.' Three items in three different grammatical forms: a gerund phrase, a noun phrase, and an infinitive. The repair is to pick one form and hold it: 'The role involves drafting reports, liaising with clients, and maintaining the case register.' Parallelism is worth its own item type because it is the most visible marker of careless list writing, and because real documents fail on it constantly - a bulleted list where two bullets start with a verb and the third starts with a noun, or a set of headings mixing questions and statements. The same rule governs correlative pairs: 'not only ... but also' must join two grammatically matching elements, so 'The report not only covers spending but also staffing' is faulty, and 'The report covers not only spending but also staffing' is correct, because the correlatives now bracket two nouns rather than a verb phrase and a noun.
Comma splice, and why 'however' is not a rescue: 'The system was offline for six hours, no backup was available.' Two independent clauses joined by a comma is a comma splice, and there are four legitimate repairs. Use a full stop: 'The system was offline for six hours. No backup was available.' Use a semicolon, which signals the two facts belong together. Add a coordinating conjunction after the comma: '... six hours, and no backup was available.' Or subordinate one clause: 'Because no backup was available, the six-hour outage could not be mitigated.' The trap is the fifth option that people reach for instinctively: 'The system was offline for six hours, however no backup was available.' However is a conjunctive adverb, not a coordinating conjunction, so it cannot join two independent clauses with a comma - the sentence is still spliced. It needs a semicolon or full stop before 'however' and a comma after it. The same applies to therefore, moreover, nevertheless, and consequently, which is why they appear so often in sentence-correction distractors.
Plain language: 37 words down to 14: Before: 'It is the recommendation of this department that consideration be given to the deferral of the implementation of the new filing procedure until such time as adequate training provision has been made available to all affected staff.' That is thirty-seven words. After: 'We recommend delaying the new filing procedure until all affected staff have been trained.' Fourteen. Look at what the rewrite actually did: it turned three nominalisations back into verbs (recommendation to recommend, deferral to delaying, provision to trained), it named the actor instead of hiding behind 'this department', and it cut 'consideration be given to' and 'until such time as', which carry no content at all. Look just as carefully at what it kept: the recommendation, the thing being delayed, and the condition that ends the delay. Plain-language items are marked on meaning preservation, not on brevity alone, and the standard wrong answer is the over-cut version - 'We recommend delaying the new procedure' - which reads beautifully and silently deletes the condition that is the substance of the recommendation. Trim the packaging, never the payload.
One incident, three readers, and the fact-inference line: Facts: the gate camera timestamps a van leaving at 11:42:00; the weighbridge camera, 300 m along the yard road, timestamps the same van at 11:42:15; the yard limit is 20 km/h. The arithmetic: 300 m in 15 s is 20 m/s, and 20 x 3.6 = 72 km/h. Now write it three ways. In the incident record: 'Vehicle VT-118 passed the gate camera at 11:42:00 and the weighbridge camera at 11:42:15. The cameras are 300 m apart, giving an average speed of 72 km/h over that section. The posted yard limit is 20 km/h.' Note what is absent: 'the driver was speeding', which is a conclusion, and 'was travelling at 72 km/h', which overstates the evidence - the figure is an average over the section, not an instantaneous speed. To the yard supervisor: lead with the decision needed and the deadline. 'Two camera timestamps put VT-118 at an average 72 km/h in a 20 km/h yard yesterday morning. I have attached the record. Can you confirm by Friday whether this goes to the safety review?' To the driver's employer: lead with the specific, verifiable reference - vehicle, date, time, the two camera points - and the single action requested. Same facts every time; what changes is which fact leads, and in a written-communication assessment the most apologetic option is rarely the best one, while any option that names blame in a record that has not been reviewed is usually the worst.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
Prioritizing messages, deadlines, stakeholders, and competing tasks.
Learn to triage a busy inbox by impact, deadline, authority, and dependency, then turn that ranking into a realistic action plan with clear owners and follow-up.
What you should be able to do after this lesson:
Worked scenario: three messages at 09:05: Your inbox contains an active-work safety alert, a two-line briefing due at 10:00, and a newsletter marked FYI. First contain or route the safety issue, because delay may expose people. Acknowledge the briefing and reserve a short work block, or delegate a fact check with a precise return time, then defer the newsletter. The order follows impact and deadline, not who wrote the longest email.
Triage grid: impact × time × ownership: For each item, note the consequence of delay, the true deadline, whether another task depends on it, and whether you can decide it. High-impact urgent work comes forward; important non-urgent work gets scheduled; suitable work can be delegated with a checkpoint; low-value information can be filed or declined.
Educational preparation only. Novus Learn does not administer official exams and does not guarantee scores or hiring outcomes.
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.
Matching, filing, coding, record checking, and identifying discrepancies.
Clerical accuracy is the ability to handle a large volume of records correctly and consistently: filing them in the right order, coding them against a key, spotting duplicates that do not look like duplicates, and holding that standard on the two-hundredth record as well as the second. Where error detection asks whether two things match, clerical accuracy asks whether you can apply a rule reliably at volume. It is assessed in administrative, records, clinical admin, school office, evidence-handling and insurance operations selection, and it is exactly the skill an employer is buying when they hire for a data-heavy back-office role. Practice stays on this device; there is no account and nothing is uploaded unless you export it.
What you should be able to do after this lesson:
Word-by-word or letter-by-letter: two correct answers, one rule: File these four names: Van Dyke, Vandenberg, Van Horn, Vance. Under word-by-word filing, each space-separated unit is compared in turn and 'nothing files before something', so the first unit 'Van' sorts ahead of both 'Vance' and 'Vandenberg'. The order is Van Dyke, Van Horn, Vance, Vandenberg. Under letter-by-letter filing, spaces are ignored entirely, so the keys are VANCE, VANDENBERG, VANDYKE, VANHORN, and the order is Vance, Vandenberg, Van Dyke, Van Horn. Both orders are correct filing; only one is correct for the system you are working in. Test items state the convention in the instructions, and the candidates who lose marks are almost always the ones applying whichever convention their previous employer used. The same fork appears with prefixes and punctuation: whether Mc and Mac interfile, whether St is treated as Saint, whether a hyphen counts as a space. Read the rule, restate it to yourself in one sentence, then apply it mechanically and do not let a name that 'obviously' belongs somewhere override it.
Alphanumeric codes: A-102 at the front or the back of the drawer: Sort the references A-7, A-12, A-70, A-102, B-3. Under natural numeric ordering, the way a person reads them, the answer is A-7, A-12, A-70, A-102, B-3. Under plain string ordering, the way most software sorts by default, each character is compared in turn, so '1' comes before '7' and the answer is A-102, A-12, A-7, A-70, B-3, with A-102 first rather than last. Both are defensible; a filing item is testing which one the stated system uses. This is also why serious record systems zero-pad their references: rewrite the set as A-007, A-012, A-070, A-102 and the string sort and the numeric sort agree, permanently. If you are ever asked to design or clean a reference scheme, pad to a fixed width and the whole class of problem disappears. In a test, the giveaway is a set that deliberately mixes one-, two- and three-digit suffixes; that mixture exists only to separate candidates who apply the stated rule from candidates who apply the intuitive one.
Coding to a key: every mark is at a boundary: A claims routing key: under 500 pounds with no injury reported goes to CS1; under 500 with injury goes to CI2; 500 to 4,999 with no injury goes to CS3; 500 to 4,999 with injury goes to CI4; 5,000 and over goes to CE5 regardless of injury. Now code five records. R-118 at 499.99, no injury: CS1, since 499.99 is under 500. R-119 at exactly 500.00, no injury: CS3, because 'under 500' excludes 500 itself and the second band starts there. R-120 at 4,999.00 with injury: CI4, since the band is inclusive at its top. R-121 at exactly 5,000.00 with no injury: CE5, because the top band is 'and over' and its 'regardless of injury' clause overrides the injury split that governs the lower bands. R-122 at 86.40 with injury: CI2. Four of those five decisions turn on a boundary, and that is not an accident, coding items are written so that the interior cases are trivial and every discriminating mark sits on an edge. Before coding anything, underline the boundary words: under, up to, and over, between, inclusive. Then decide, once, what each one does to the endpoint, and apply that decision to every record in the batch.
Duplicates that are not textually identical: Three rows arrive in a merge. Row 1: SMITH, JANE | 07/04/1988 | AB123456C. Row 2: Smith, Jane | 1988-04-07 | AB 123456 C. Row 3: SMITH, JANE | 04/07/1988 | AB123456C. Rows 1 and 2 are the same person: normalise case, strip the spaces from the reference, and convert the ISO date and they match exactly. Row 3 is the genuinely hard one. If the file is in day/month order it is a different date of birth and possibly a different person; if that row came from a system using month/day order it is the same record again. You cannot tell from the row itself, so the correct action is to send it to the exception queue with the ambiguity noted, not to merge it and not to discard it. This is the judgement that separates competent records work from the appearance of it: the goal is not to make every row disappear, it is to make every decision defensible. In test form the item usually asks 'how many distinct individuals are represented', and the answer is often given as a range or accompanied by a 'cannot determine' option for exactly this reason.
Where accuracy actually decays on a long batch: Run a self-measurement rather than trusting a number from anyone: take 200 record pairs, split them into four blocks of 50, and log errors per block. Most people find block 1 slightly worse than block 2, a warm-up cost, and then a rise across blocks 3 and 4 as vigilance falls. The reason to measure it is that the arithmetic of small percentages is brutal at volume. Checking 200 pairs at 98 percent accuracy passes 4 bad records; at 99.5 percent it passes 1. Scale that to a realistic month of 20,000 records and the same two accuracy rates mean 400 defects against 100: a four-fold difference in downstream rework from a 1.5 point difference that would look like noise on a single test. Once you know where your own curve turns, the intervention is cheap: a deliberate twenty-second break at that point, or splitting the batch so the hardest records fall in your strongest block. Practice sessions on this site are recorded on your own device, so building a block-by-block picture across several sessions costs nothing but the logging.
Setting an attempt rate from the scoring rule: A 120-item checking test with a 10-minute limit, scored as correct minus incorrect. Suppose practice has told you that you hold 92 percent at ten items a minute and 96 percent at seven and a half. Fast: 10 x 10 = 100 attempted, 92 correct and 8 wrong, score 84. Careful: 10 x 7.5 = 75 attempted, 72 correct and 3 wrong, score 69. Fast wins by 15. Now change the rule to correct minus three times incorrect: fast scores 92 - 24 = 68, careful scores 72 - 9 = 63, and the 15-point gap has shrunk to 5. Now suppose your real accuracy at ten a minute is 80 percent rather than 92. A gap most people do not discover until they measure it. Fast now gets 80 right and 20 wrong: under simple correct-minus-incorrect that is 60, already behind the careful strategy's 69, and under the triple penalty it is 80 - 60 = 20 against 63. Same test, same person, opposite advice, and the two deciding variables are the penalty multiplier, which the instructions hand you, and your own accuracy-at-speed, which only measurement gives you. Do not pick a pace from temperament. Measure two rates in practice, write both accuracy figures down, and do this arithmetic before the test rather than during it.
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.