Record Flensburg points for a driver

This article shows you how to record a driver's Flensburg points (Punkte from the German Fahreignungsregister) so their risk score and recommendation stay current. Because this is Halterhaftung-relevant (keeper-liability) data, updating points requires the strafmandate:manage permission — a higher level than the read-only view permission used for most Strafmandate screens.

Who can do this

Recording points is restricted to roles that carry strafmandate:manage (for example a FleetManager granted management rights, or a SystemAdmin). A user with only strafmandate:view can see the driver risk overview but will be blocked from editing points.

Record the points

Open the driver from the driver risk overview and use the update-Flensburg-points action, then complete the fields.

1. Points — the driver's new total Flensburg points, from 0 to 18. Values outside this range are rejected.
2. Reason — required. A short note explaining the change (for example the source document or authority notice). This is stored with the entry.

When you save, the driver's risk score and recommendation are recalculated immediately and returned to you.

Note: The maximum is 18 points, matching the German Fahreignungsregister scale at which a licence is withdrawn. The field enforces the 0–18 range, so you cannot record a higher total.

How the update is stored

Points are kept as an additive ledger rather than a single editable number. When you enter a new total, the system:

• Calculates the difference between the new total and the current summed points, and writes that difference as a new point entry (dated now) with a source reference of manual-update: followed by your reason.
• Recomputes the risk score as (active mandate count × 10) + (new points × 8).
• Writes a new risk snapshot for the driver, tagged with the rule version risk-v1-manual-update.

The result shows the previous points, the new points, the new risk score, the risk level (low, medium, or high), and the recommendation for that level.

Warning: Because entries are cumulative and immutable, entering a lower total than the current one writes a negative correcting entry rather than deleting history. Always enter the driver's correct current total, not the delta, and use the reason field to document why it changed.

Requirements and errors

• The driver must exist and be active, otherwise the update returns a "driver not found" error.
• A reason is mandatory; a blank reason is rejected.
• Points must be a whole number from 0 to 18.

Recording points also generates the driver's first risk snapshot if they did not have one, which clears the "missing data" flag on the risk overview.

Related

• Driver risk overview and how risk is scored
• Dashboard overview and KPI widgets
• Review a penalty notice's financial summary and history