Saarland Abitur Technology (Saarland Abitur) common mistakes
Saarland Abitur Technology · Understand the traps and how to avoid them.
Presenting a technical system's function only in prose and omitting the labelled system diagram (Blockschaltbild/Schaltplan) that the task explicitly requires, so the described signal flow cannot be checked.
Candidates from a strong language or social-science background default to essay-style answers and underestimate how much of the Technik score depends on a correct, normed drawing with named components, terminals and signal direction.
What to do instead
Before writing, list every required representation from the task (Blockbild, Schaltplan, Freikörperbild, Kennlinie). Produce the drawing first, label every block and arrow with the exact technical term, then write prose only to explain it. Practise redrawing standard circuits (Spannungsteiler, Reihen-/Parallelschaltung, Transistor als Schalter) from memory until labelling is automatic.
Confusing the technical quantities and units used in the task (e.g. mixing Leistung P in W with Arbeit W in J or kWh, or treating Stromstärke and Ladung as interchangeable), so numeric results are dimensionally wrong.
Everyday German uses 'Leistung' and 'Energie' loosely, and candidates carry that looseness into calculations; under time pressure they copy numbers without tracking which quantity each symbol denotes.
What to do instead
At the start of every calculation write the formula with symbols, substitute with units included, and carry units through to the result. Check the final unit against what the task asks for. Keep a one-page formula sheet with symbol, quantity, unit and typical context (P=U·I, W=P·t, Q=I·t) and rehearse unit conversions (1 kWh = 3,6 MJ) until they are reflexive.
Describing a control system (Regelkreis) without distinguishing the controlled system (Regelstrecke), controller, sensor/feedback path and disturbance variable, and omitting the reference-variable versus disturbance-variable response.
The Regelkreis is taught as a block diagram with arrows, but candidates memorise the words without mapping them onto the concrete example in the task; the feedback loop is often drawn as a one-way chain.
What to do instead
For any given example, first draw the closed loop with all five elements named, then mark where the disturbance enters and where the sensor measures. Explicitly state how the controller reacts (Stellgröße increases/decreases) and what happens with and without feedback. Practise with two contrasting examples (Heizungsregelung, Tempomat).
Skipping or fudging the dimensioning/verification step: proposing a component (resistor, motor, fuse) without checking it against the calculated load, tolerance or safety margin.
Tasks often ask for a design decision, and candidates stop once they have a plausible number, treating the check as optional rather than as the part that earns the higher-order marks.
What to do instead
Adopt a fixed three-step pattern for every design task: (1) calculate required value, (2) select next standard value/component, (3) verify with a short sentence giving the margin and why it is acceptable (e.g. 'nächsthöhere Normreihe E12, 20 % Reserve für Lastspitzen'). Write step 3 explicitly even when not prompted.
Treating a technical drawing or circuit as a picture to be described aesthetically instead of reading it functionally, e.g. not tracing which contacts are open or closed in a given switching state.
Candidates who are strong verbally describe what they see rather than simulating the circuit's state; they also forget that a relay or switch has a rest position that defines the starting condition.
What to do instead
Before answering, annotate the drawing with the assumed state ('Ruhezustand: Kontakt K1 offen'), then trace the current path step by step and write the resulting state of each actuator. Build a habit of drawing the truth table (Eingänge → Ausgänge) for every logic or switching task.
Giving a purely qualitative evaluation of a technology (e.g. 'ist umweltfreundlich und effizient') without quantifying it against the data in the task or naming the criterion used.
Bewertungsaufgaben feel like opinion questions, so candidates switch to general statements and drop the numbers; they also fail to state the criterion before judging.
What to do instead
Use a fixed evaluation structure: name the criterion (Wirkungsgrad, CO2-Ausstoß pro kWh, Kosten pro Betriebsstunde), compute the indicator from the given data for each option, compare, then conclude. Never write an adjective without a number or a named criterion next to it.
Mixing up the energy-conversion chain in mechatronic or energy systems (e.g. claiming a generator converts current into mechanical energy, or omitting the losses at each stage).
The chain has several stages and the direction of conversion is easy to invert under exam pressure; losses are invisible in the diagram and get forgotten.
What to do instead
Draw the conversion chain as arrows with the physical form at each node (chemisch → elektrisch → mechanisch) and mark where losses appear as heat. State the overall efficiency as the product of stage efficiencies. Rehearse this for three systems: Verbrennungsmotor, Elektromotor mit Batterie, Photovoltaikanlage mit Wechselrichter.
Ignoring the given operating point or boundary conditions (temperature, load, tolerance, norm) and applying a formula outside its validity range.
Formulas are learned in isolation, and candidates do not check whether the task's conditions match the assumptions behind them (e.g. linear approximation, ideal components).
What to do instead
Before calculating, underline every given condition in the task and write one sentence stating which assumptions you make and whether they hold. If the task supplies a characteristic curve, read the value from the curve instead of using a linear formula. Explicitly note where an idealisation is not justified.
Producing an unstructured answer that buries the result: no stated approach, no intermediate steps, the final value appearing mid-paragraph without unit.
Technik tasks carry method marks, but candidates write as if only the final answer counts, and they run out of time because they do not plan the answer before writing.
What to do instead
Use the visible structure Gegeben – Gesucht – Ansatz – Rechnung – Ergebnis – Bewertung for calculation tasks, and a labelled sketch plus numbered steps for explanations. Put the final result on its own line with unit and a one-sentence plausibility check. Allocate the last five minutes to checking that every sub-task has an explicit result.
Answering only the first part of a multi-part task (Teilaufgaben a–d) and leaving later, higher-value parts untouched because time ran out on the first calculation.
Candidates over-invest in the first sub-task, polishing prose and rechecking arithmetic, and misjudge how the points are distributed across the parts.
What to do instead
Read all sub-tasks first and budget time proportional to the marks shown. If a calculation stalls, write the approach and formula, mark it, and move to the next part; partial method marks are awarded. Reserve the final minutes to return to skipped parts and at minimum state the approach.