Default Sanctions
The ability to specify Default sanctions per event type (and even per competition type) has been available in COMET since the development of the disciplinary module. Following your disciplinary code, you can specify the severity and combination of sanctions for any yellow card, sin bins, or red card issued to players or team officials on the bench. For example, if a player is issued a red card for an act of violence, he is immediately suspended for 3 matches and also fined for 200 $.
This feature gives the Superuser full transparency of the pre-defined default sanctions and allows full editing capability. Note that any changes to this information are applied immediately.
You can access this tool in the COMET Admin App (add /appadmin to your Comet homepage address) → Competition → Default Sanctions menu.
Once you click Default Sanctions on the main menu, you will see a message telling you if this feature is active and used by your organization (your tenant). If so, then any change you make here is immediately active. If this feature is not enabled, you will have some time to work on the definition of default sanctions for various event types (and even competition types).
Let's go through the rules and the logic of this important section:
If Default sanctions are enabled for your tenant, COMET expects to see something configured in this section. If nothing is configured, no disciplinary case and no default sanction will be created for any match event.
System logic looks for competition-specific rules, and if it does not find them, it looks for general rules per event type (i.e., from more specific to more generic). You may have special rules for certain professional-level competitions with stricter sanctions, while all other competitions have a milder generic set of rules.
If your disciplinary code specifies a combination of sanctions per some event type, then each sanction is specified separately (e.g., a monetary fine needs its own definition, and a suspension sanction needs its own row).
If your disciplinary code specifies an ever-increasing set of sanctions based on the order number of the card, then you must enter a new row for each event type + order number + sanction combination (e.g., 1st yellow card = 5 $, 2nd YC = 10 $, 3rd YC = 15 $, 3rd YC = 1 match suspension, etc.).
Each time you want to Add a new item to the list or Edit an existing definition, note that some fields are mandatory (e.g., Match event type, Sanction type) and others are not.
The pop-up entry screen also offers you helpful hints/explanations of what each field represents so that you can choose or type the correct information. To read the explanation, position your mouse over the question mark symbol ❔ next to the field name
Adding a new sanction
In the Default sanctions tab under the Competition, select an event type for which you want to add a new sanction from the tabs above.
To add a new default sanction, click on the Add button and fill out the necessary fields:
ID - automatically generated
Competition type - select a competition type from the drop-down
Event type - this field is prefilled according to the event under which a new default section is being created
Reason - select a Reason from the drop-down. If the reason is selected, the default sanction relates only to the match event with the same reason of event type. Otherwise, the default sanction relates to the match event of the same main match event type.
Order - allows specifying different default sanctions based on the occurrence of the same match event type. For example, the first yellow card in the first match and the second yellow card in the second match cause a fine of some value, but an occurrence of the third yellow card in the third match causes a match ban suspension (with or without a fine as another default sanction with same order number).
Max matches - this field presents a maximum number of matches in competition for which accumulated cards will trigger a sanction → see more in the following paragraph
Sanction type - select one sanction type from the drop-down
Value
Date from offset - Sanction date from will be moved days defined here from the date of the match
Article - used as an article on disciplinary case
Suspension scope - the suspension scope refers to the scope of the match(es) where the player or team official will be suspended. This setting may be overridden with competition setting for Suspension scope
Additionally, you can check the following checkboxes:
Immediate sanction - immediate sanctions get automatically closed. It never becomes active
Second yellow - second yellow is used only in combination with Yellow card 🟨 or Sin bin main match event type for sanctioning a person who received two yellow cards or two sin bins in the same match
You can see all sanctions for some competition types by selecting this competition type from the drop-down under the specified event type.
Max matches
A quite common requirement for accumulated yellow cards is that they be "forgiven" if they were collected over a relatively long period of time. For example, in some competitions, 5 yellow cards lead to a match suspension only if they were collected in the first half-season (e.g., 19 matches). If a player collects 5 yellow cards in 25 matches, this will not lead to a match suspension.
For that purpose, an optional Max Matches field was added to the Default Sanction entity for yellow cards. If that field is set, that Default Sanction will lead to an actual sanction only if the cards were accumulated in the number of matches in that competition lower or equal to Max Matches.
This optional attribute (number) is not visible on the list, just in the Default sanction detail, when adding or editing.