Start an objection (Einspruch) workflow
This article explains how to open an Einspruch (objection) against a Strafmandat (penalty notice) and submit it to the authority. Starting the workflow creates a draft objection and runs an automated viability assessment; submitting it moves the objection into the authority's hands.
Start the objection
Use the start-objection action on the mandate. You can include an optional comment that becomes the objection's reason. This requires the strafmandate:view permission.
The mandate must have enough information for the assessment to run. Specifically it needs a violation time, a location, and a penalty amount greater than zero. If any of these is missing, the start is blocked with VIABILITY_INSUFFICIENT_DATA and the message "Viability assessment could not be completed with available data". In that case the response signals that a manual decision is allowed, so a FleetManager can still proceed on judgement after filling in the details.
When the input is complete, the system:
- Creates a new objection in Draft status, storing your comment as its reason.
- Records the opening transition (from none to draft).
- Returns a viability rating and reasoning for the objection (see Assess objection viability).
Note: Objection actions always operate on the most recent objection for the mandate, so starting again creates a fresh draft.
Submit the objection
Once you are ready, use the submit-objection action. You can attach an optional submission note, which replaces the objection's reason. Submitting also requires the strafmandate:view permission.
Two checks apply before submission succeeds:
- Status — the objection must be in draft. Submitting from any other status is rejected with OBJECTION_SUBMIT_STATUS_INVALID.
- Deadline — if the latest deadline snapshot shows the objection deadline (respond-by) has already passed, submission is blocked with OBJECTION_DEADLINE_PASSED.
On success, the objection advances to authority response pending. The system records the intermediate transitions (draft to submitted, then submitted to authority response pending) and captures the submission time. From here you wait for the authority's decision.
Tip: Calculate the mandate's deadlines before submitting so the respond-by date is current. If the objection deadline is close, the urgency label on the deadline helps you prioritise.
Objection status flow
| Status | Meaning |
|---|---|
| draft | Created but not yet sent to the authority. |
| authority response pending | Submitted; awaiting the authority's decision. |
| accepted / rejected | Final outcome recorded from the authority. |
What happens next
When the authority responds, record the result with the record-objection-outcome action. Until then, the objection and every status change are visible on the mandate timeline.
Related
- Assess objection viability
- Record an objection outcome
- Calculating and tracking deadlines (Fristen)
- The mandate timeline
