Admin

Your screens

Admins have the same bottom bar as the meet director — Competition, Pilots, Status, Retrieve, Feedback — plus a management menu (☰):

• Questions · Events · Staff · Vehicles · Equipment · Competition Settings
• Tracker Management and Pilot Sync, if granted; Live Leaderboard Coming soon; About.

Bringing a brand-new competition into CompBuddy is done by a Master.

Competition tab: days, events and tasks

The Competition tab lists every competition day; today's day is opened automatically. Each day shows its type (Registration, Race Day, Final Day, Off Day, Cancelled, Stopped), its events, and its task.

Events

Add events to a day with +:

• Create New Custom Event — a one-off for this day.
• Add from Events — pick one from the competition's event list.
• Apply Template — load a whole set of events at once, e.g. "Race Day".

Tap an event for its actions:

• Continuous Check-in / Check-out — the same scan loop as Staff.
• Send Notification — notify all pilots and staff about this event now.
• View Attendance — three lists, In, Out and Missing, each with scan times and a search.
• Edit Event — name, extra text, start and end time, place (a label and a pin on the map), check-in / check-out, and reminders (Remind at Start, Remind Before n minutes).

Task

Each day has the same Task Settings as the meet director — publish, final, task board photo, QR import, window and stop — plus Sync Task with Airtribune to pull the task from Airtribune and a link to view it there. Past days are locked; their task map and task board photo can still be viewed.

Pilots tab

The pilot list (total / active) with a search by name or pilot number. Small icons on every row show where each pilot stands:

• Active — checked in at the registration desk; or Invite sent, or inactive.
• WhatsApp verified, data Checked, glider Certificate on file, App linked to an account.
• Tracker — crossed out if none assigned, grey if assigned but no data today, green if reporting.

The top bar has three tools: Register pilots (the registration desk, below), Import tracker CSV (see Trackers) and Broadcast notification to all pilots.

Pilot actions

Tap a pilot for: View Pilot Info · Checkpoint Status · Send WhatsApp · Send Message (opens a CompBuddy chat) · Push Notification · Take Avatar Photo · Send / Resend Invite Email · Connect / Re-connect Account (scan their account QR or paste the ID, then take their photo).

Pilot info

Everything from the pilot's Airtribune registration — contact, licences, insurance, emergency contact, equipment, their Safety Buddy — plus their QR code, their tracker serial (tap to edit), and:

• See us before registering — flag a pilot who has to talk to you first (missing paperwork, a question). The desk scan won't check them in.
• Revoke Registration — reset the pilot's in-app registration; they'll have to go through the registration form again.

The registration desk

The last step of every pilot's registration happens in person. Tap Register pilots in the Pilots tab and scan the QR code on each pilot's "Not yet registered" screen:

• Activated — the pilot is checked in, and CompBuddy offers to take their photo for the pilot list. Their phone switches to the full home screen by itself.
• Already Registered — nothing to do.
• See Staff First — the pilot is flagged "See us before registering". Sort it out, clear the flag in Pilot info, and scan again.

Tap Scan Next after each pilot; the counter in the title shows how many you've registered. The desk needs a connection.

Feedback tab

Pilot feedback per day: how many pilots took part, the average of each rating question and the comments, with a detailed view per question that shows each pilot's CIVL ranking. Export CSV creates a spreadsheet of every answer for the competition, ready to copy.

Questions

Two tabs: this competition's questions, and the default questions new competitions start with. Each question is a 1–10 rating or a text comment and can be switched active or inactive. The first two ratings — satisfaction and safety — are required for pilot feedback and can't be deleted.

Events

Build the schedule once and reuse it: Events is this competition's list of events (e.g. "Registration Desk", "Task Briefing", "Launch Check-in"), Templates groups them into sets like "Race Day" or "Rest Day" to apply to a day in one go, and Defaults is the library new competitions start from.

Staff

Add a staff member by scanning their account QR code (or pasting their account ID) — or, if they're not there in person, enter their email and CompBuddy sends an invite. Then set:

• Name, phone, and Staff Type — Staff, Driver, Retrieve Coordinator, Meet Director or Admin.
• Assigned Vehicle and Map Marker Color — for drivers.
• Tracker Device Serial — if they carry a Flymaster tracker.
• Extra Functions — Tracker Management and Pilot Sync.

From the staff list: Edit, Send Invite, or Remove from Competition.

Vehicles

Retrieve vehicles with a name or number plate, how many pilots they carry, and a photo. Assign drivers to vehicles in the staff editor.

Equipment

The database of glider and harness manufacturers, models and sizes (with weight ranges and certification) that pilots pick from during registration. Shared by all competitions.

Competition Settings

• Private competition — only masters and people connected to the competition see it in the competition list.
• Locations — HQ and transport, pinned on a map. HQ appears on every task map.
• Glider check required — pilots need a glider certificate on file at Airtribune to complete registration.
• Retrieve method — None, CompBuddy, WhatsApp (with the retrieve WhatsApp number) or Flymaster. This decides the retrieve card pilots see, and whether the Retrieve Manager is active.
• Flymaster API — Pilots and — Staff — tracker group IDs and API keys from Flymaster Live, for the tracker features. Needed whatever the retrieve method.
• Radio frequencies — safety and retrieve, shown to pilots.
• Contacts — the safety contact name and WhatsApp number on the pilots' Info tab.
• Pilot invites — Send Invites emails every pilot who has an email address and isn't connected yet.