Result flows and integrity

This page explains, end to end, how a result is created, signed, protected, corrected and — when needed — zeroed or restored. It is the reference for the athlete, the RO and the staff to be sure of the integrity of what is in the system.

1. How a match is set up (onboarding and dependencies)

Before the first shot, the club sets up the structure in this order — each piece depends on the previous one:

• Match: the event itself. It can belong to a championship and have Main Matches (days/shifts) to organize the schedule.
• Area: groups nearby stages; it is the territory of the CRO (Area Chief).
• Stage: where the shooting happens. Besides shooting stages, the match may have special chronograph and equipment check stages.
• Squad: the group that rotates through the stages together, with a fixed shooting order that rotates on each stage (whoever opened stage 1 does not open stage 2).
• Athlete: the registration is per match — division, power factor (Major/Minor), category and squad. No PIN yet? In matches with equipment check, the PIN is created at the check; without check, on the first score entry.
• Public registration: the match is born with the /i/ link closed — it only accepts registrations with “Allow public registration” on, Open status and within the deadline. While closed, the staff registers athletes internally.
• RO: gets a login from the club and is assigned per stage — they can only enter scores on their assigned stages.

1.1 The RO's day, in one line

2. Who signs what (integrity)

Every result has two signatures: the RO’s (who entered it) and the athlete’s confirmation (the 4-digit PIN typed on screen). Over that data the system computes a cryptographic hash (HMAC) that binds the target grid, time, points, Hit Factor and version to the record.

• On every read the hash is recomputed and compared. If someone changes the data outside the normal flow (directly in the database, for example), the score summary shows the “Tampered” alert — and the slot history shows what changed.
• When staff approves without the PIN (athlete absent), the confirmation is signed by the identity of the approver (manager / RM / Stats / CRO) and that is recorded on the result — the “Approved without PIN” badge shows on the summary.
• No edit erases anything: every change writes a line into the append-only history (who, when, what, why).

2.1 Where the PIN comes from

The PIN is created once per Match and covers every registration of that athlete in that Match (multi-division shares the same PIN). It can be born in three places:

• On the first entry without a PIN (match without check), the RO's screen discreetly warns that it will be necessary to create the PIN and approve with it right after.
• In a Match with check, the Score entry screen offers PIN creation again once the check for that registration is done — that is the way back for anyone whose PIN was reset after the check. With the check pending, the PIN still comes from the check.
• Resetting the PIN is a manager / RM / Stats action, is recorded in the Match audit log and only shows for whoever already has a PIN — the first PIN still comes from registration, from the check or from the first result.
• With public registration closed, or without the “Allow PIN through the athlete portal” option, the portal does not change the PIN — the path is the field (check or first score entry).
• Consecutive wrong attempts temporarily lock that athlete's PIN.

3. Entering a score

• While the RO fills it in, the system saves a draft (status Open) — no PIN, no ranking value. Only the confirmed score (Locked) counts.
• Two people cannot edit the same athlete+stage at the same time (short-lived edit lock) — and a second entry for the same slot is rejected.
• Wrong PIN too many times? The system temporarily blocks new attempts.

3.1 Equipment check (when the match uses it)

The match picks the mode: no check, check at the squad's first stage, or check before the match (by an authorized RO). With check enabled, no score goes out before that division's equipment is verified.

• The check is per equipment + division: an athlete in two divisions has one check for each declared equipment.
• The check has the same signing mechanics as the score: without the athlete's PIN it does not complete — which is why, in these matches, the PIN is born here.
• A pending check blocks scoring: the RO's screen warns and points to the check shortcut.

4. Corrections, reshoots and approvals

A locked score cannot be edited on one’s own. There are two paths, always with a recorded reason and authorization by RM / Stats / CRO (or a direct edit by the manager, also with a reason):

• Correction: the same score is edited a single time (e.g. a typing mistake). For overlay disputes the match may require a second check by another official first.
• Reshoot: the old score leaves the ranking (it stays in the history) and the athlete reshoots the stage — the RO enters a new record.
• Every authorization shows who authorized it, the official reason, and when it was used or revoked.

5. DQ (disqualification)

DQ follows IPSC rules 10.4–10.7 and is treated like a result: it has an official reason, a signature and its own history.

• When the RM / Stats / CRO / manager requests the DQ themselves, it is confirmed immediately (approving one’s own request makes no sense).
• On confirmation, all of the athlete’s stages become Zeroed (DQ): results already shot are zeroed while preserving the original in the history; stages not yet shot get a DQ zero.
• The athlete appears at the bottom of the division as DQ, with no competitive position.
• Chronograph (Power Factor): at the chrono stage, the measurement is signed with the athlete's PIN. PF below the minimum for the registered factor → automatic DQ (CRONO.PF) and the scores leave the ranking; a new valid measurement reverts only that DQ — other official DQs remain.

5.1 Reverting a DQ

The RM or the manager can revert a confirmed DQ — in the officials’ DQ panel or directly on the registrations list (red row, Revert DQ button). The dialog shows exactly what will happen before confirming:

• Results zeroed by the DQ → come back exactly as they were (points, HF, time, procedurals), re-signed.
• The stage where the DQ happened → returns as an Open score for the RO/RM to revalidate (the run was interrupted); what had been entered remains in the history.
• Stages that only had the DQ zero → the zero is removed and the stage is released for scoring normally, no authorization needed.

6. DNF and Zero Stage

• Stage DNF (Did Not Finish): the RO marks DNF with a mandatory note — that stage records a zero score (HF 0) and the athlete continues normally on the others.
• Match DNF (management): the athlete leaves the shooting lists and every stage without a result gets a zero; real results already entered keep counting.
• Zero Stage is how those zeros show up on the monitoring panels — an operational zero, different from a DQ.
• Reactivate (RM / manager): removes only the DNF zeros; the stages accept normal scoring again, no extra authorization. Real scores are untouched.
• Difference from DQ: a DNF athlete stays in the ranking (with the zeros); a DQ removes them from the ranking and zeroes everything. One does not overwrite the other — to DQ a DNF athlete (or vice versa) the current status must be resolved first.

7. Attendance and absence (Absent / No-show)

• Attendance (Present / No-show) is an operational check-in — it tells the squad who is on the range. No-show is not DNF and zeroes nothing.
• When the equipment check is completed or the first result is entered, the system marks the athlete as Present automatically.
• In the rankings, a stage without a result shows as absent (—) until the score is entered; it is worth no points and counts as pending in the match progress.

8. Athlete appeals (protests)

If the match allows it, the athlete can contest a result (score, DQ, stage…) from their own portal — and the decision is recorded like everything else.

• The match controls whether it accepts appeals (“Allow athlete appeals”) and until when (its own deadline). After the deadline no new requests come in, but open ones still get decided.
• The athlete follows the status and the reply on the portal; while open, they can withdraw the request.
• If the match publishes appeals on the hub, the public sees only the decided ones (upheld/denied) with the decision text — open requests never appear.

9. How to verify the integrity of a result

1. Open the score summary (via the hub, verify, or the results list).
2. Check the hash badges: OK = data identical to what was signed; Tampered = something changed outside the flow — investigate through the history.
3. Imported = historical batch whose signature cannot be verified. It does not point to tampering, but it is not proof of integrity either.
4. See the slot history: each version shows the full grid at that time, who changed it, the reason and the authorization used.
5. The same goes for DQ: request, confirmation, zeroing and reversal are on the DQ timeline, with the signatures of every step.