Understand Infraction Types and Severity

v3 fixes (2026-05-04, validated vs live UI): Threshold notification = single "Enable threshold notifications" checkbox (not 3 configurable Low/Mid/High levels); Significant Point Threshold default = 5 (not 20).

---

At a glance

Infractions in OneClick are points-weighted records that leaders create on a team member's profile to document policy violations and other concerns. Points accumulate across active infractions, each point total maps to a penalty label in the Accountability table (written warning, meeting with a director, suspension, termination), and threshold notification emails can fire automatically when the total crosses the configured level. The record itself is documentation; the discipline action is the leader's decision informed by the record. This reference covers the data model (types, points, expiration, signatures), the notification system, the permission structure, and retention.

Before you start

This is a reference article. Read it once to understand the model, then return when needed.

Core reference content

What an infraction is

An infraction is a timestamped record tied to a single team member describing a single incident. Each record includes: an issue date, an infraction type (from a configured list), a point value (from the type's default), an expiration date for the points, a notes field, a leadership signature, and optionally an employee signature. Infractions are visible on the Infractions tab of the team member's profile, which shows the Accountability table (the points-to-penalty ladder) and the team member's current total points.

The points and penalty ladder

The core of the Infractions feature is a numeric points system. Each infraction type has a point value. When a team member receives an infraction, that type's points add to their running total. The total sits against a ladder of penalty labels:

The default ladder is:

1. 1 point: Ineligible for promotion.
2. 5 points: Written Warning.
3. 8 points: Meeting with a director.
4. 10 points: 3-Day Suspension without pay.
5. 15 points: 5-Day Suspension without pay.
6. 20 points: Termination.

The ladder is configurable per store under Settings > Infractions > Penalties. Point values on each infraction type are also configurable. The default point structure is a starting template; your store can reconfigure it to match its disciplinary policy.

The penalty label at a given point total is presentational: OneClick highlights the reached level in the Accountability table, but the actual disciplinary action still happens outside the app. The store's policy determines whether leadership acts on the labeled penalty immediately, after review, or on some other cadence.

Expiration and the New Point Duration window

Each infraction has an expiration date, set at issue time, that controls when its points stop counting toward the running total. This lets stores apply rolling-window accountability rather than permanent cumulative scoring.

Two related settings govern how points age:

1. Per-infraction expiration. Set when the infraction is issued. When the expiration date passes, those specific points stop counting.
2. New Point Duration (in Settings > Infractions). A rolling window that determines which infractions count toward the displayed total. The displayed total is calculated as: today's date minus New Point Duration equals the oldest infraction date still counted. Infractions older than that window drop off the total even if their per-infraction expiration has not passed.

Whichever constraint removes the points first wins. Most stores use one approach or the other rather than both; confirm with your Director which model your store uses.

The significant point threshold

The significant point threshold setting (default: 5 points) determines at what total the penalty label turns red in the Accountability table. This is a visual warning for leaders that the team member is at a disciplinary edge and is separate from threshold notification emails (see below).

Signatures and the acknowledgement text

Each infraction captures a leadership signature and, optionally, an employee signature. Defaults: leadership is Required, employee is Optional. Both are configurable per store to Required, Not Required, or Optional.

The signature block is preceded by an Acknowledgement text that the store can configure. The acknowledgement is meant to hold a short statement that the signer is affirming, for example, that the infraction has been discussed with the team member, or that the team member has had the opportunity to add their perspective. The acknowledgement is blank by default and activates only if your store fills it in.

Three global signature settings can override all per-infraction settings (found at the top of the signature section under Settings > Infractions):

1. Allow edits to all infractions. If checked, any infraction can be edited regardless of other settings.
2. All submitted signatures editable. If checked, signatures can be changed after submission.
3. No signatures editable after submission. If checked, signatures lock on submission.

These three checkboxes override all other infraction settings. If your store's paper-trail compliance requires locked signatures, check the third box and confirm it overrides any per-type configuration.

Notifications

Two kinds of notifications fire from Infractions:

Team member email (off by default). Enable Infraction Received email under Settings > Infractions > Email Notifications to have the team member receive an email each time an infraction is issued to them. Set Reply-To Email in the same section to control where replies go; leave it blank to send from a no-reply address.

Threshold notifications (off by default). Enable the Enable threshold notifications checkbox in Settings > Infractions > Email Notifications. When enabled and a team member crosses the configured point threshold, the designated recipients receive an email. Repeat notification behavior (how many days to wait before re-notifying for the same threshold) is also configurable. These notifications are how leadership stays aware of team members trending toward the penalty edge without having to poll profiles manually.

Permissions

Infraction permissions are layered:

1. View history: Shift Leader level and higher.
2. Issue new: follows the view permission (anyone who can view can issue).
3. Edit existing: Manager level and higher.
4. Delete: Director and Operator only.
5. Access settings page: Manager level and higher.

Team members cannot view the Accountability table themselves, but they can receive the Infraction Received email if that setting is enabled.

Retention

Infraction history persists indefinitely until a Director or Operator deletes the record. Points may stop counting (via expiration or New Point Duration), but the record itself stays on the team member's profile as historical documentation. This retention model supports long-term pattern recognition across a team member's tenure without inflating their current-total penalty.

Negative points are not supported

OneClick explicitly does not support using negative-point infractions to recognize positive behavior. The infractions system is designed to count up from zero; negative values are not a valid configuration. The recommended pattern for positive recognition is Moola, which has its own reward mechanics and reporting. Mixing the two in Infractions produces ambiguous data and breaks the signal the Accountability table is meant to provide.

Video

Not planned for this reference article.

Common gotchas

The penalty label showed up automatically but no one got disciplined.

OneClick labels the reached penalty level in the Accountability table, but the discipline action is the leader's responsibility. Use the label as a prompt to take the action your store's policy defines for that threshold. Also consider enabling threshold notifications so leadership receives an email when a team member crosses the level rather than discovering it by chance.

I edited an infraction and the changes did not save.

If the global "No signatures editable after submission" override is checked under Settings > Infractions > Signatures, edits to any submitted infraction are blocked regardless of other settings. Uncheck the override or ask an Operator to do so. If the override is not checked, confirm you have Manager permission or higher; Shift Leaders can view but not edit.

The points on a team member's profile do not match what I expect.

Three things can reduce the displayed total:

1. Per-infraction expirations have passed, dropping those points off the total.
2. The New Point Duration rolling window has aged an infraction out of the counted window.
3. A Director or Operator deleted an infraction.

Check the infraction history on the profile for items that have dropped off. If you need the full history regardless of current-total counting, scroll the history list; historical infractions remain visible even when their points no longer count.

A team member disputes an infraction.

Record their position in the notes field of the infraction and leave the record in place. If the store's acknowledgement text is configured and the Employee signature is Required, the team member has already signed an acknowledgement at issue time. If the dispute is resolved in the team member's favor, a Director or Operator can delete the infraction.

I want to track positive behavior alongside infractions.

Use Moola. OneClick separates positive and negative behavior systems deliberately: Moola counts up from zero for rewards, Infractions count up from zero for policy violations. Keeping the two separate keeps both datasets clean for reporting and for individual performance conversations.

Infraction types differ between our stores in the same organization.

Infraction types are configured per store. If your organization wants consistent types across stores, an Operator needs to coordinate the configuration at each store individually; there is no central template feature. Document the target configuration, then have a Manager at each store apply it under Settings > Infractions.

Related articles

1. Issue an Infraction (How-To Guides)
2. Configure Infraction Settings (How-To Guides)
3. Understand Permission Levels (Reference)
4. Understand Moola (Reference), for the positive-behavior companion system

Still stuck

If infraction behavior does not match this reference or you cannot find the Infractions tab, submit a support ticket with your store number, the team member's name, and a screenshot of what you are seeing.

---

Pre-publish checklist status

33 b76b0b78-57b7-44ef-beec-d402d283bc16 complete All seven sections filled (Reference adaptation).

34 32f54723-a4d3-436c-8486-d03f750732f2 complete At a glance within template spec.

35 19cf9e48-1ee8-4e15-bce2-fa582743f2ad complete No em dashes, no hedge words, permission-based throughout.

36 f974888d-cf68-43d0-9e3e-fbed32f88f96 complete Voice: operator-as-actor violations cleaned.

37 96359b76-b7e0-4221-9bd4-a79f89d95101 complete VERIFY blocks resolved via Infractions PDF (fields, points ladder, expiration vs New Point Duration, significant point threshold, signatures, acknowledgement text, notifications, permissions, retention, negative-point support).

38 d0136e38-af6b-4434-9697-2f8b21359b36 complete v3 (2026-05-04): threshold = single Enable checkbox (not 3 Low/Mid/High levels); default 5 points (not 20). validated vs live UI.

39 4b821b77-a48d-41bf-ac7e-03557ee4e4b4 incomplete UI verified against Production.

40 d44d035c-913d-4969-8bc0-cd8e7915dcda incomplete Reviewed by Jared and Kevin.