Skip to content

Features

What the precision shooting module does

From the modality to the published standings, with the scoresheet the sport actually uses: one row per target, columns from X to 0, and the total closing itself.

Modalities

The course of fire is a parameter, not code

Each club shoots what its rulebook says, and no fixed list covers that. In Orbit the modality describes the course: how many targets per series, how many shots per target, how many series and how much time.

Building the match

Series, benches and registration by modality

The wizard takes the Match from its name to open registration, asking at each step only what that Match needs.

In the field

Ring by ring, on the official’s phone

The scoring screen is the scoresheet: one row per target, columns X, 10, 9… 0 and the total. The official taps the ring of each shot and the maths closes itself, including the X count that decides the tie-break.

Integrity of the result

Who scored it, when, and what changed afterwards

Every closed Score gets a chained digital signature: tampering with an old result breaks the chain of the ones after it, and that shows. The history is append-only — a correction comes in as a new row, never erasing the previous one.

Results

The rulebook tie-break, worked out on the spot

A tie on the total is the rule, not the exception — and the tie-break criterion is exactly where rulebooks disagree. That is why it is a Match setting, not a constant in the system.

Integration

Its own REST API, the same entity key

The module has its own public API — Matches, modalities, series, relays, registrations and results — under the same entity-key authentication as the other sports. OpenAPI specification and test console included.

Get started

From sign-up to your first match, in minutes

No side spreadsheet, no install, no contract. Three steps and your match is already running on Orbit.

Your club already has the next match scheduled. Put it on Orbit today.