Competition records, not meet management
Reef keeps each athlete’s competition records, event scores, totals, history, and upcoming events. It does not run a meet, manage sessions, or score one.
Every capability below is built and live in Reef right now.
Payment path availability depends on how an organization is set up. Reef flags likely duplicate athletes for a person to resolve; it does not claim perfect identity matching.
Visibility of sensitive profile information depends on permission. Not every profile note is private - internal notes are the ones held back from families.
Full guardian access remains permissioned, and Reef does not verify custody arrangements or model every jurisdiction’s family law.
Reef shows the conflicts it checks for. It does not auto-schedule or optimize your timetable, and it does not claim to catch every possible conflict type.
Review happens on a review screen. Reef does not model multi-step approval chains, does not calculate payroll, and does not sync with external calendars.
Attendance reporting describes what happened. Reef does not present it as predictive analytics.
Whether a credit is created, and whether a booking needs approval, follows your organization’s policy. Credits cannot be used at another organization, and fill-rate insight is an operational view rather than revenue forecasting.
You build the skill library; Reef does not ship a standardized curriculum, and it does not judge or score a skill for you.
Reef keeps the athlete’s competition record. It is not meet management or scoring software.
Payments are processed by Stripe. Reef is not a bank, a merchant of record, or a payment processor; it does not produce accounting statements or revenue forecasts; and it does not give tax or legal advice. Payment options for a family depend on how the organization is configured, and not every failed payment recovers on its own.
The time clock is a record of work, not a surveillance tool. Export is not a payroll filing, and device and browser support is confirmed by testing rather than promised in advance.
The QuickBooks connection covers approved hours as TimeActivity records only - not invoices or accounting. A verified domain lets mail come from your address; no one can promise inbox placement.
Reef suggests fields; a person reviews and confirms them. Sensitive documents respect access rules, and Reef makes no claim about the legal validity or enforceability of a completed form.
Incident records are an internal documentation workflow. Reef is not an emergency-response system and does not file reports with outside agencies.
Announcement audiences depend on permission, delivery can depend on external providers and device settings, and Reef makes no end-to-end encryption or universal deduplication claim.
This is the same application, shaped by role - not a separate product for families. Switching only reaches organizations and children where a valid seat or grant exists.
Any figure in our illustrations is an example. Reef does not present sample metrics as customer results.
Access architecture is one part of security, not a guarantee on its own.
Your branding applies inside Reef. There are no separately branded app-store builds.
The assistant’s scope is the listed lookups, actions, and domains a user already has permission to reach. It is not general automation, it cannot bypass a permission, and like any assistant it can be wrong - so its work is visible and reviewable.
Reef detects a dropped connection; it is not fully offline-capable. Downloadable availability is advertised only for the platforms where a build is actually distributed.
The list above is the whole of it. Bangai Labs does not market capabilities it has not shipped, so here is the other half of the truth.
Reef keeps each athlete’s competition records, event scores, totals, history, and upcoming events. It does not run a meet, manage sessions, or score one.
Reef records approved hours, creates payroll-period entries, and exports CSV. It does not process payroll, calculate pay, or file anything. Its QuickBooks connection carries TimeActivity records - not invoices or accounting.
There is no lead pipeline, no marketing automation, and no recruiting module. Reef does not build your public website, and it does not sell merchandise or track inventory. There is no public API and no single sign-on, and Reef does not sync to external calendars - its own calendar and notifications carry the schedule instead.
Reef does not advertise a data migration, and there is no self-serve free trial. If you want to see how it fits your organization, we walk you through it.
Reef makes no compliance-certification claims on this website. Instead, the security page describes the concrete access approach: organization scope on every record, location assignment, roster access tiers, about 30 individual permissions, and enforcement in the database behind all of it.
See how Reef can fit your programs, locations, staff, and families.