DemeritCheck

Hypothetical. Educational only. Demerit enforcement not proclaimed as of August 2026.

Premise

A driver collects three infringement notices over a quarter: seatbelt (2850), handheld phone (5085), and keep-left / encroachment (5000). For months each matter sits in an open process. Then, in one week, the driver treats all three as concluded for modelling (for example after payment or other finalisation — we are not prescribing which).

Reading A — all pending

CodePointsStatusCounts toward total?
28501PendingNo
50853PendingNo
50005PendingNo

Running final total: 0. The codes still matter — you can see the exposure — but DemeritCheck does not add pending rows to the threshold maths. Open pending stack →

Reading B — all final

CodePointsStatusRunning finalTo 15
28501Final114
50853Final411
50005Final96

Maths: 1 + 3 + 5 = 9 final points (6 below 15). No suspension estimate applies under 15; if this were over 15, the calculator would show an illustrative months figure only, with the ss 24–28 caveat.

Open final stack →

What this teaches

  • Pending vs final is the difference between “codes on a list” and “threshold maths.”
  • Small seatbelt points still stack with larger moving violations.
  • The calculator cannot tell you when RTIA considers a matter final — only you can mark status honestly.