Entity and staff guide

For who organizes the match for the club/organization: what to configure, what to publish, and what to follow on the day.

Entity checklist

1. Register the entity and invite the staff team.
2. Create the match and set divisions, stages, squads, and ROs.
3. Open registration (public link and/or deadline) and share it with athletes.
4. On the day: make sure ROs can sign in, run check, and enter scores.
5. Publish hub and results; follow the championship if there is one.

1. Access and team

• Staff login (SSO or email/password, depending on the environment).
• Main area: Entity dashboard → Matches.
• Invite users (owner/manager) under Users — the guest gets a link and signs in with SSO.
• In Profile, adjust details and UI language.
• Define which fields the athlete must provide — see "Required fields and customization" just below.

1.0. When the club runs more than one sport

If your club runs practical shooting and clay shooting, the system works on one product at a time: the menu, the matches and the results always belong to the sport you are in. Switching sports is one click at the top of the screen, and nothing you left open is lost.

• You switch each sport on for the club yourself, under Club details: tick "Use clay shooting at this club" and save. Switching it off later erases nothing — the clay matches stay stored and come back when you switch it on again; what disappears is the menu. If that option is not on your screen, the modality is not available in this installation of the system: talk to support before anything else.
• Who sees each sport inside the club is up to the owner or the manager, under Users: you can take clay shooting out of the menu of someone who only handles practical shooting, and the other way around. Nobody loses what they have already scored — the menu just gets shorter.
• Where you land is your call, under Profile → Default module. Leaving it on “Ask on sign-in”, the system shows the choice screen after login, as it always has.
• The whole club can also have a default sport, under Club details. Your own choice in the profile always outranks the club’s.

1.1. Required fields and customization

You decide which data is required in athlete registration and match sign-up — the system does not impose a fixed list. The standard fields (documents, phone, birth date, address and email) live in Club data; the entity's own custom fields, in Entity athletes → Configure fields. The configuration applies to the whole entity (UI, public registration and API).

• Document fields (CPF, RG, CR and CR expiry): for each one you choose whether it shows, is required and is unique (two active athletes cannot repeat the same value).
• Phone and birth date: same show/required table (no "unique"). By default they appear in the form but are optional — they only become required if the club checks the flag.
• Athlete address: off by default. Turning on "show" adds the address block (street, number, district, city, state, postal code) to entity sign-up and the athlete portal; "required" demands street, city, state and postal code. The address lives in the athlete's global profile.
• Email required: on by default. Turn it off for quick registration without email (the system uses the document or the name as a provisional identity); the email can be added later.
• Additional fields: create your own entity fields (text, number, select, checkbox…), each one optionally required and/or unique — e.g. membership number, registration id.
• Registration tags, IPSC Classes and Management categories: catalogs you maintain that become available during registration.

2. Set up the match

1. Create the match — name, dates, public code (used in links), status and registration deadline, if you want it to close automatically.
2. Registration — one or more divisions per session; whether the athlete stays in the same squad across divisions or chooses per match. Mark if the match requires complete profile/club data before the wizard.
3. Public registration — the match is born with the registration link closed. Turn on "Allow public registration" (Registration tab, wizard or the publishing card in the match details) when you want to open it; set the deadline alongside. While closed, the staff can still register athletes internally. Closing does not affect those already registered: athletes without a PIN set it in the field — at the equipment check (if the match uses check) or, in matches without check, on their first score entry.
4. Equipment check — no check, on the squad’s first stage, or before the match by an authorized RO.
5. Modalities and divisions — Open, Production, etc., with Major/Minor power factor when applicable.
6. Areas, stages and Main Matches — range and schedule structure.
7. Squads — slot limits; link to area/Main Match as designed.
8. Schedule — time × stages grid (internal live for the team).
9. ROs — link to the match, set the match password and stages covered. Mark who may run check if the policy is “before the match”.
10. Officials (optional) — Range Master, Stats, Area Chief for progress, DQ and score correction approval.
11. Teams (optional) — if the match has team competition, set size and link registered athletes.

3. Registrations

Ways that can coexist:

• Public link — /i/CODIGO — the athlete signs into the portal, chooses divisions, reserves a squad, and, if the match asks for it, creates the PIN.
• Staff wizard — from the match registration management (for people who did not self-register).
• CSV import — bring entrants in bulk (updates or creates per the system template).
• Export — spreadsheets/lists for checking and organization.

Registration deadline: required while the public link is active. Cannot be after the match end date — the system validates on save and already warns on screen before you confirm.

Require profile and additional club details to register: turns on an extra check, only for this match. Before entering the registration wizard (public link), the athlete must have first name, last name and phone complete in their profile (phone only if the club has not marked it as optional — see 1.1) and, if the entity uses membership linkage, the documentary fields the club requires. If anything is missing, the athlete is redirected to complete it before choosing division and squad. Useful for matches that need a ready-made registration (federated events, document verification) before allowing sign-up.

What the registration list shows

Under each entrant's name you see badges for what has already been done — category and class and, when the Match uses those features, Check done / Check open and Chrono done / Chrono open. It is the quick read of who is ready to shoot, without opening any other screen.

Reset an athlete's PIN

An athlete who forgot the 4-digit PIN mid-Match is sorted out in the registration list itself: Reset PIN (manager, RM or Stats). The button only shows for whoever already has a PIN — the first PIN is still born at registration, at the equipment check or at the first result.

Match name

The name shown in the lists, in the ranking and in the public results is the name in the Match — editable in the registration, both by the athlete (in the portal wizard) and by management. Changing it does not rename the athlete's account or their club membership, and it applies to every division of that athlete in the same Match.

4. Useful extras

• Fast Pass — virtual squad for shooters who go straight to a stage; enable it on the match if you will use it.
• Email — configure the entity’s SMTP for confirmations; staff invites may use the system global email.
• ROs report — check RO × stage assignments.
• Athlete notes — internal notes visible to the match staff.

5. Publish for the public

Turn the options on in match edit or details. Without publishing enabled, the link is not public.

6. Championships (season)

Use when the organization runs several stages in the year and wants one ranking.

1. Under Club, allow championships and save — the menu then appears.
2. Create the championship (name, year, modality) and set planned stages, minimum, and discards.
3. Define the modalities/divisions pattern before linking matches.
4. Link the Matches compatible with that standard. In the link itself you can mark the round as weight 2 (it counts double) — and change that later, from the round list.
5. Generate the public hub and mark each championship as published.
6. Share /c/CODIGO for the list, stages, and ranking.

Weight 2 round: use it for the season final or the main event of the year. The ranking marks the column with ×2 and the displayed value stays the athlete's raw result — what doubles is the round, not what they did. The weight also counts in the drop: dropping a round worth 2 costs twice as much, so it only falls if it really is the worst contribution. Unlinking the Match clears the weight.

7. On the day and after

• Confirm that ROs sign in with username + club code + password (the match is chosen after login).
• Track progress, attendance, DQ and the appeals queue through the officials (RM/Stats).
• DNF: shooting order or registration; restoring is RM/manager only (removes the zero DNF scores).
• If appeals are published on the hub, the public only sees upheld/dismissed requests and the answer.
• Deadline to open appeals: set it on the match (entity's timezone); after the deadline, only what was already open gets decided.
• After the match, review incomplete scores and keep public results up to date.
• If there is a championship, publish each stage so the season ranking can follow.

Finalizing the Match

Once every active athlete has a result in every active Stage, the Match overview invites you to finalize it. Finalizing freezes the Match: it becomes read-only, and nobody edits the setup, moves an athlete between Squads or reopens an already published Score by accident.

Reopening requires a reason (the field is mandatory) and is written to the audit log with who reopened it and why — reopening touches results that have already been published. The notice at the top of the Match shows the reason for the last reopening and links straight to the audit log.

In the same finalize modal, Send results to scoring.services is already checked: classification by division and each athlete’s detail go to the scoring.services portal with source Orbit. You can update or remove later from the match overview. IPSC only.

External export (federation)

In the internal ranking (officials), the External export button generates the CSV in the layout that external federation systems import (CSV Model 1): one row per athlete, with rank, CPF, name, class, division, category, the athlete’s percentage within their division and the match points. DQ is left out and the rank restarts per division — the actual ranking position the athlete competes in.

8. Bluetooth timer: getting the tablets ready

If the match will use the Bluetooth timer on the scoring screen, get the tablets ready before match day — the setup is done once per device and lasts forever.

1. Use an up-to-date Chrome (Android or computer). iPhone/iPad do not work with the timer — it is a limitation of Apple's browsers.
2. On each tablet, open the scoring screen, tap Add Timer and follow the window's instruction: tap Copy next to the setup address, paste it into Chrome's address bar, set it to Enabled and tap Relaunch.
3. Pair the timer once (tap Add Timer → pick the device, a name like SP M1A2). Done: from then on the tablet reconnects on its own, even after the page reloads.

The step-by-step with screens is in the RO guide. Timers supported today: Special Pie (SP M1A2 and M1A2-F) and Shooters Global (SG Timer, SG Timer 2 and SG Timer GO), identified automatically on connection — to integrate another model, talk to us.

← All guides Athlete guide → RO guide →