G2 SEC examination performance does not end when the learner reaches the right idea. The idea must survive the final interface: question number, response location, unit, label, source, option, accuracy and visible final answer. A correct solution transferred incorrectly is still a damaged output.
This ninety-sixth Learner’s Guide develops response-interface integrity across K200 English, K210 Mathematics and K223–K225 Science. It complements Vol 0092 Instruction Hierarchy and Vol 0084 Minimum-Sufficient Answers.
The interface audit
- Is the answer attached to the correct question and subpart?
- Is the final response unambiguous?
- Are units, labels, accuracy and source ownership correct?
- Did the verified working transfer correctly to the final answer?
- Can the response be read exactly as intended without guessing?
1. Question number
Failure surface: Correct content is written beside the wrong number.
Interface repair: Treat numbering as part of answer correctness; relabel before conceptual rechecking.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
2. Subpart label
Failure surface: Part (b) answer is placed under (a).
Interface repair: Map every response to its live subpart before moving on.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
3. Chosen option
Failure surface: The learner answers an optional question but does not identify the choice clearly.
Interface repair: Make the permitted option unmistakable and stop carrying the unchosen option.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
4. Answer line
Failure surface: A correct response is written outside the intended response area.
Interface repair: Check the live paper’s response convention and keep the final answer where markers expect it.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
5. Final-answer transfer
Failure surface: Scratch working is correct but the copied final number is wrong.
Interface repair: Compare final transfer with the last verified working line.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
6. Copied digit
Failure surface: A 6 becomes 8 during transfer.
Interface repair: Use direct visual comparison rather than re-solving.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
7. Decimal point
Failure surface: A decimal shifts during copying.
Interface repair: Check order of magnitude and the exact transfer string.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
8. Negative sign
Failure surface: A sign is lost in the final line.
Interface repair: Inspect sign-sensitive transitions and final transfer separately.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
9. Unit
Failure surface: The number is correct but the unit is absent or wrong.
Interface repair: Treat unit as part of the output interface whenever the quantity requires it.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
10. Degree symbol
Failure surface: An angle answer lacks the required degree notation.
Interface repair: Add the notation locally without reopening the geometry.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
11. Percentage sign
Failure surface: A decimal proportion is written as a percentage without conversion, or vice versa.
Interface repair: Match numerical form and symbol.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
12. Currency label
Failure surface: A monetary value is left unitless.
Interface repair: Use the appropriate currency representation if required by context.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
13. Accuracy
Failure surface: Working is correct but final rounding ignores the instruction.
Interface repair: Repair final presentation from the unrounded value.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
14. Exact form
Failure surface: An exact answer is converted unnecessarily to a decimal.
Interface repair: Restore the requested exact representation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
15. Simplest form
Failure surface: A fraction or algebraic result is left in a non-final form when simplification is requested.
Interface repair: Simplify only the final representation; preserve correct upstream work.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
16. Inequality symbol
Failure surface: The boundary value is correct but < becomes ≤ or vice versa.
Interface repair: Treat the relation symbol as data, not decoration.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
17. Interval endpoint
Failure surface: A bound is copied correctly but inclusion is wrong.
Interface repair: Check whether equality is allowed by the original condition.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
18. Graph axis label
Failure surface: The graph is correct but an axis lacks quantity or unit.
Interface repair: Complete the interface so the representation is interpretable.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
19. Graph scale
Failure surface: Points are plotted correctly relative to an unstated or inconsistent scale.
Interface repair: Verify scale labels before interpreting the graph.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
20. Table heading
Failure surface: Values are correct but column ownership is unclear.
Interface repair: Restore heading, condition or unit rather than rewriting values.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
21. Table row
Failure surface: A value is entered in the wrong condition row.
Interface repair: Repair data ownership locally.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
22. Diagram label
Failure surface: A correct term is attached to the wrong structure.
Interface repair: Position is part of the answer.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
23. Arrow label
Failure surface: A process label points to the wrong direction.
Interface repair: Check arrow ownership and direction separately from terminology.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
24. Source label
Failure surface: An English claim is attributed to Text 1 instead of Text 2.
Interface repair: Repair source ownership without changing a valid interpretation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
25. Speaker label
Failure surface: Dialogue evidence is assigned to the wrong speaker.
Interface repair: Restore speaker before inferring attitude or motive.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
26. Pronoun ownership
Failure surface: The final answer uses they after two groups.
Interface repair: Replace with the precise group noun to remove interface ambiguity.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
27. Quotation boundary
Failure surface: The copied quotation includes irrelevant wording that changes ownership or tone.
Interface repair: Trim to the decisive span while preserving context.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
28. Summary numbering
Failure surface: Points are listed in a way that makes one idea look like two.
Interface repair: Count unique information, not visual bullets.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
29. Requested count
Failure surface: The question asks for two reasons but the answer visibly presents one.
Interface repair: Audit distinct elements before adding length.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
30. Comparison sides
Failure surface: Both facts are present but the relation between A and B is not explicit.
Interface repair: Use comparison wording so the interface performs the command.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
31. Cause arrow
Failure surface: Science cause and effect are both present but order is unclear.
Interface repair: Make causal direction explicit.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
32. Observation/explanation boundary
Failure surface: A Science observation answer includes theory that obscures the measured fact.
Interface repair: Separate evidence from explanation where the command requires it.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
33. Variable role label
Failure surface: The right variable is named under the wrong role.
Interface repair: Attach changed, measured or controlled labels correctly.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
34. Control/treatment label
Failure surface: Data are correct but groups are swapped in the response.
Interface repair: Fix condition ownership before conclusion.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
35. Graph interval
Failure surface: The answer describes the right trend over the wrong time range.
Interface repair: Write the requested interval into the evidence statement.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
36. Population scope
Failure surface: A result for one subgroup is labelled as the whole population.
Interface repair: Restore the correct universe.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
37. Probability event label
Failure surface: The numerical probability is correct for a different event.
Interface repair: Name the event before accepting the number.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
38. Rate denominator
Failure surface: The calculation is correct for items/hour but the question asks hours/item.
Interface repair: The interface unit reveals the reciprocal mismatch.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
39. Percentage base
Failure surface: The percentage is calculated from the wrong reference quantity.
Interface repair: Write the base noun beside the percentage.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
40. Mean label
Failure surface: A computed mean is presented as a total.
Interface repair: Name the statistic.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
41. Median label
Failure surface: The middle value is correct but called mean.
Interface repair: Terminology must match operation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
42. Range label
Failure surface: Difference is correct but assigned to another statistic.
Interface repair: Keep quantity identity explicit.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
43. Coordinate order
Failure surface: Correct x and y values are reversed in an ordered pair.
Interface repair: Use (x,y) ownership check.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
44. Point name
Failure surface: Coordinates are attached to the wrong labelled point.
Interface repair: Match label to graph location.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
45. Transformation notation
Failure surface: The transformed object is correct but vector/order notation is wrong.
Interface repair: Repair representation without redoing the geometry.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
46. Formula variable
Failure surface: A correct number is substituted under the wrong symbol in final explanation.
Interface repair: Restore symbol meaning.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
47. Calculator answer transfer
Failure surface: Calculator shows correct result but paper contains a mistyped digit.
Interface repair: Use display-to-paper comparison.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
48. Scratch-to-booklet transfer
Failure surface: Working on rough space is not transferred fully.
Interface repair: Reserve a transfer checkpoint before leaving the question.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
49. Skipped marker
Failure surface: A question is intentionally parked but looks accidentally blank.
Interface repair: Use a consistent private marker that does not interfere with final submission.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
50. Return closure
Failure surface: A repaired answer still carries an uncertainty mark.
Interface repair: Clear the marker after verification so it is not reopened.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
51. Crossed-out answer
Failure surface: Old and new answers both remain visually plausible.
Interface repair: Make the intended final response unambiguous using permitted correction method.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
52. Multiple MCQ marks
Failure surface: Two options remain marked.
Interface repair: Ensure one final selection where the format requires one.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
53. Faint selection
Failure surface: The intended option is not visually clear.
Interface repair: Make the response legible and unambiguous.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
54. Handwriting ambiguity
Failure surface: A symbol or digit can be read two ways.
Interface repair: Rewrite the local character rather than the whole solution.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
55. Minus versus dash
Failure surface: A negative sign looks like punctuation.
Interface repair: Clarify mathematical notation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
56. One versus seven
Failure surface: Digit shape is ambiguous.
Interface repair: Rewrite the ambiguous digit in final answer.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
57. Zero versus six
Failure surface: A copied digit is unclear.
Interface repair: Use context and rewrite only the character.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
58. Variable l versus number 1
Failure surface: Algebraic symbol is ambiguous.
Interface repair: Use consistent notation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
59. Multiplication sign versus x
Failure surface: Variable x and multiplication symbol collide.
Interface repair: Use spacing or alternative multiplication notation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
60. Decimal comma confusion
Failure surface: Number formatting could be misread.
Interface repair: Follow the paper’s standard numeric convention.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
61. Thousands separator
Failure surface: Grouping punctuation creates ambiguity.
Interface repair: Use conventional notation consistently.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
62. Scientific notation
Failure surface: Coefficient/exponent is correct but notation is malformed.
Interface repair: Repair final representation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
63. Fraction bar
Failure surface: Numerator and denominator ownership are visually unclear.
Interface repair: Rewrite the fraction cleanly.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
64. Bracket ownership
Failure surface: An expression’s scope is ambiguous.
Interface repair: Restore brackets where mathematical meaning depends on them.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
65. Power
Failure surface: Exponent is placed ambiguously.
Interface repair: Rewrite the local term.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
66. Square root bar
Failure surface: Radical scope does not cover intended expression.
Interface repair: Clarify the exact operand.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
67. English paragraph break
Failure surface: Two ideas that need separation are fused.
Interface repair: Use paragraphing only when it improves task structure, not decoration.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
68. English sentence boundary
Failure surface: A run-on makes source or cause ownership unclear.
Interface repair: Repair punctuation to preserve meaning.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
69. Capitalisation of proper source
Failure surface: A named text/person is unclear through careless notation.
Interface repair: Use clear identification where ownership matters.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
70. Science symbol
Failure surface: Chemical/physical symbol is written ambiguously.
Interface repair: Preserve correct scientific identity.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
71. Unit prefix
Failure surface: m, cm, mm or kg/g is copied incorrectly.
Interface repair: Prefix is part of magnitude.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
72. Time unit
Failure surface: seconds and minutes are mixed in final statement.
Interface repair: Align unit with calculation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
73. Compound unit
Failure surface: km/h becomes km or h/km.
Interface repair: Use dimensional check at final interface.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
74. Squared unit
Failure surface: Area answer is written in linear units.
Interface repair: Repair dimensional notation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
75. Cubed unit
Failure surface: Volume answer lacks cubic power.
Interface repair: Repair dimensional notation.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
76. Final sentence scope
Failure surface: Evidence is correct but conclusion drops ‘under these conditions’.
Interface repair: Restore the boundary in the final output.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
77. Final sentence certainty
Failure surface: Source says may but answer says will.
Interface repair: Repair modality without changing the core claim.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
78. Final sentence quantifier
Failure surface: Source says most but answer says all.
Interface repair: Restore exact scope.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
79. Final sentence chronology
Failure surface: Events are correct but causal wording reverses time.
Interface repair: Repair direction.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
80. Submission sweep
Failure surface: The paper is nearly complete.
Interface repair: Audit interfaces first: numbering, blanks, labels, units, selections and transferred answers.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
81. Interface-first review
Failure surface: A question’s reasoning is secure.
Interface repair: Check presentation before reopening concepts.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
82. Content-first review
Failure surface: The interface is correct but answer is substantively uncertain.
Interface repair: Only then spend deeper review time.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
83. Final rule
Failure surface: Correct thinking must survive contact with the answer surface.
Interface repair: A mark can be lost between mind, working and final response; verify the interface explicitly.
For practice, plant this presentation error into an otherwise correct answer. Require the learner to repair it without re-solving the content. This separates reasoning errors from output-transfer errors and makes final review cheaper.
Why interface checks come early in final review
Interface errors are often fast to detect and cheap to repair. Numbering, units, blank responses, ambiguous selections, copied digits and missing labels can be checked before spending several minutes re-solving a difficult question. This does not make them more important than conceptual errors; it makes them high-recoverability review targets.
Links
Use the Examination Craft hub, Vol 0080 Dependency-Aware Repair, the relevant English, Mathematics and Science hubs, and the PSLE Learner’s Guide.
Official-source discipline
For the 2027 SEC G2 school-candidate framework, use the current SEAB G2 syllabus directory and the linked subject syllabuses. SEAB currently lists K200 English Language, K210 Mathematics and K223–K225 Science combinations. Response-interface integrity is an eduKateSengkang training framework, not an SEAB marking rule.
Final rule
Do not stop at “I knew it.” Make sure the paper says what you know, in the right place, with the right label, unit, source and final form. The last centimetre from reasoning to response is part of examination performance.
