The whole season, one system.

Draws, results, and a ladder that keeps itself.

An association runs its competition across every member club: the draw, the rounds, the grades. Referees submit a result, an admin approves it, and the ladder recomputes on the spot, points, bonuses, differential and tiebreakers all by the rules of your code.

Every fixture becomes a match centre: teams and crests, venue and weather, kick-off countdown, ladder impact, team lists, the report and the gallery. Team pages build themselves from the results.

Competition data comes in the honest way: a club-authorised import or a sanctioned integration. MeetPi never scrapes your association's site, and nothing written here writes back to it.

One message, the right channel, every time.

Reach a team or the whole club by text, push and email at once, deduped so a guardian with two kids gets one message. A reply threads itself back to the right game and lands on the board. Anything MeetPi should not guess at goes to one inbox, Replies to sort.

The cost is on the button before you send. STOP stops every text platform-wide in seconds. Automated reminders stay inside quiet hours and a strict budget, and the last nudge is a human with a call list, never a louder machine.

See the core loop that works today ›

One engine. Any code. Australian by default.

There is no rugby version and netball version. There is one competition engine, configured by data, so a new sport is new settings, not a new codebase. Rugby Union is the first because it is where we are starting, not because anything is wired to it.

Every club's data is isolated from every other's in the database itself, not only in the app. The primary data store is in Australia (Sydney), with named subprocessors listed. Club money moves through Stripe at a 0% platform fee, and association registration stays where it is. The full list of what we refuse to do ›

The committee's job, kept honest by the system.

A refund, a role change, a threshold raised: sensitive actions go through a second person before they take effect, every time. Nobody, including the person who proposed it, can wave it through alone. Every one of those actions writes itself into a record nobody can quietly edit, so "who approved this, and when" is always a plain answer, not a reconstruction.

Working-With-Children checks are kept as a record: who holds one, and when it expires, so the club can see a gap before it becomes a problem. MeetPi does not verify a check against a government register and never claims to; it keeps the record straight, and says so plainly rather than implying more than it does.

When a president, secretary or treasurer hands over, their whole picture, money position, open items, who to call, hands over with them in one packet, instead of living in one person's head or a folder nobody else can find.