Study AUR30820 by pairing every motorcycle concept with the procedure, measurement and documented decision that prove competence. Build symptom-to-test decision chains, rehearse them with written scenarios, and check yourself with a rubric rather than re-reading notes.
What AUR30820 competence actually asks you to demonstrate
AUR30820 is the Australian vocational qualification for motorcycle mechanical technology. Competency means performing service, diagnosis and repair to workplace standard, and showing evidence — so study each concept together with its procedure and the records that support it.
The qualification sits inside the Australian automotive training package, which organises learning into units covering areas such as engines, fuel systems, electrical work, chassis, braking and workplace safety. Because each unit describes performance criteria — the tasks you must carry out and the evidence you must produce — your study map should start from those task descriptions rather than from a list of technical facts.
A practical mapping method: for each broad topic (for example, cooling systems or wheel alignment), write one line describing the job task, one line describing the safe work procedure, and one line describing what you would record on a job card. If you cannot fill all three lines, that topic is not yet studied at the depth the qualification expects. Revisit the issuer's pages on training.gov.au for the current structure and administrative details, since unit arrangements are updated over time.
Two-stroke versus four-stroke: why the same noise leads to different decisions
Two-stroke and four-stroke engines differ in lubrication, valvetrain and sealing, so an identical symptom — a knock, smoke or a loss of power — points to different component lists and different confirming tests before any teardown.
A four-stroke carries oil in a sump and uses camshafts, valves and clearances; a two-stroke mixes oil with fuel or uses oil injection, and seals depend on the piston, rings, crank seals and reed or piston-port induction. That changes your decision chain. Smoke on startup on a four-stroke raises valve guide or ring questions; on an oil-injected two-stroke you first confirm the oil pump delivery and oil quality before blaming the bottom end.
Worked scenario: a two-stroke single develops a metallic knock at speed. The plausible mistake is committing straight to a crankshaft overhaul because two-stroke bottom ends are known wear items. The better decision is to isolate first: run briefly with the clutch disengaged to separate transmission noise, check for crankshaft end float and small-end play by hand, and inspect the exhaust power valve for carbon fouling that mimics mechanical noise. Why it matters: a premature teardown wastes parts and time, while a missed clutch or power-valve cause means the knock returns immediately after rebuild.
Carburettor or EFI? Choosing the right fault-finding path
Carburettor and EFI faults produce overlapping symptoms but demand different tests: carburettors need circuit reasoning and mechanical checks, EFI needs sensor, fuel-pressure and fault-code investigation. Decide the path first, then test.
On a carburettor, think in circuits: the pilot circuit governs idle and low throttle, the vacuum slide and needle govern mid-range, and the main jet governs full throttle. Lean surging at steady cruise suggests a jetting or air-leak question; a four-stroke that only misbehaves when hot points to heat-related jetting change or an air leak at the intake boot. On EFI, the chain runs through fuel pressure, injector condition and sensor inputs such as throttle position and intake temperature, plus stored fault codes.
Use the table below as a decision aid, then verify with the confirming test in the third column before ordering parts. A short practice example: a bike hesitates off idle. Idle is clean, so the pilot circuit is likely fine on a carburettor model — move your attention to the slide or needle area. On an EFI model with the same hesitation, check throttle position sensor output and fuel pressure first, because off-idle dip is a classic mapping or low-pressure symptom rather than a mechanical one.
| Symptom | Carburettor — likely question to test | EFI — likely question to test |
|---|---|---|
| Rough or hunting idle | Pilot jet blockage, mixture screw setting, intake air leak | Idle air control function, fault codes, vacuum leaks |
| Lean surge at steady cruise | Mid-range jetting, needle position, intake boot cracks | Fuel pressure under load, injector flow, sensor input plausibility |
| Rich smell, fouling plugs | Float height or leaking needle valve, choke stuck on | Leaking injector, regulator or sensor reading fault |
| No start, spark confirmed | Fuel delivery to carb, blocked passages, float bowl empty | Pump prime and pressure, injector pulse, crank/cam sensor signal |
A charging-system case: reading tests in the right order
Electrical faults punish out-of-order testing. Work from battery condition, to charging output, to unwanted draw — and take readings under the conditions each test requires rather than from a single snapshot.
A motorcycle charging system is a chain: stator output, rectifier/regulator, battery, and the loads and earth paths in between. Each link has its own test conditions — stator output is assessed across engine speed with the system connected, regulator behaviour is checked for correct rectification and voltage limiting, and battery health needs a loaded test, not just an open-circuit voltage glance.
Worked scenario: a customer reports a flat battery every few mornings. The plausible mistake is measuring charging voltage once at idle, seeing a plausible figure, and replacing the battery anyway. The better decision: first load-test the battery and recharge it fully; then measure charging voltage across a rev range; then, with everything off, connect an ammeter in series and measure parasitic draw, removing fuses one at a time to find the circuit. Why it matters: an accessory with a stuck draw, or a regulator diode leaking with the ignition off, will flatten even a brand-new battery — replacing the battery alone guarantees a repeat complaint.
Torque values, sequences and fastener state: assembly decisions that get checked
Assembly competence is judged on correct torque values and sequences, thread condition and locking method, and whether fastener settings were recorded. Treat every critical fastener as a documented decision, not a feel-based action.
Torque is about clamping force, and clamping force depends on thread size, lubrication and condition. Oiled versus dry threads change the friction split, which is why specifications sometimes state a lubrication condition — applying the wrong one shifts the actual preload even when the wrench clicks at the printed number. Sequence matters for the same reason: cylinder heads and clutch centres are tightened in a staged pattern to seat components evenly and avoid distortion.
Build the habit with a labelled worked example: a service manual lists a 30 Nm fastener to be tightened dry, in a criss-cross sequence, in two stages. Write the chain — confirm thread condition, clean, verify the specification and its lubrication note, stage the tightening in the stated pattern, record the final value. A plausible mistake to rehearse avoiding: adding thread locker or oil 'for safety' on a fastener specified dry, which over-stresses the clamp. Why it matters: distorted heads, pulled threads and repeated gasket failures are assembly-practice faults, not parts faults, and they are exactly what practical assessment checks.
Safety decisions and job-card evidence: what your records must show
Safe workplace practice and documentation are assessed as part of the job, not separately. Your evidence should show hazard controls chosen before work began, and measurements and authorisations recorded as the work progressed.
Under Australian work health and safety practice, the habit assessed is risk identification and control before the task: supporting the motorcycle securely before working underneath, disconnecting the battery before electrical or welding-adjacent work, controlling fuel and solvent vapours, and handling hot components and exhaust gases with the right isolation and ventilation. Write the control next to the task in your practice notes so the pairing becomes automatic.
Documentation is the other half of the chain. A defensible job card records the complaint in the customer's terms, the tests performed with their readings, parts replaced with justification, and the post-repair check that confirms the fault is resolved. Rehearse this by converting your scenario work into one-paragraph job cards. If a reader cannot reconstruct what you did and why from your notes alone, the record is not yet workplace-standard — tighten it until it is.
A written case-study exercise, self-check rubric and preparation sequence
Consolidate with written case studies: three symptoms, three decision chains, marked against a rubric. Then run an adaptable sequence — concepts, procedures, scenarios, job cards — and finish with concrete readiness checks.
The exercise: write three invented case studies across different systems (for example, a two-stroke power loss, an EFI no-start, and a battery-drain complaint). For each, produce four lines: symptom in plain language; the first test and why you chose it; the expected measurement or observation that would confirm your hypothesis; and the repair decision plus what you would record. Do this closed-book, then check against the decision table in this article and your notes. Rubric — score one point each, out of four per case: (1) the chosen test matches the symptom's most direct path; (2) the expected reading is specific and realistic for the stated conditions; (3) a plausible alternative cause is acknowledged or excluded; (4) the documentation line names the confirming check. Twelve or more out of twelve is a study milestone showing your chains are complete — it is a learning indicator, not a prediction of any assessment outcome.
A preparation sequence you can adapt: weeks one and two, map topics to task, safety-control and evidence lines as in the first section; week three, drill two-stroke versus four-stroke and carburettor versus EFI decision paths until each table row is explainable without notes; week four, write the three case studies and mark them with the rubric; final week, convert each case into a job card and have a peer or supervisor read it for reconstructability. Readiness checks: you can state a decision chain for any system in under a minute; you can name the safety control before each task; your job cards pass the closed-reader test; and you can explain, for any torque task, the value, sequence and lubrication condition together.
For current qualification structure, units and administrative requirements, refer to the issuer's listing on training.gov.au rather than relying on secondary summaries, since training package details are revised over time.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.