Try it first

See what your side of the app actually looks like

Not a features list — the real screens, running the real domain and database logic against one sample event, Belfast Feis 2026. Pick who you are and step into it.

Hands on

Run an event of your own, start to finish

Ask for a demo account and you get a sign-in and an empty event in the real console. Build the syllabus, book a panel, fill it with sample families or enter dancers yourself, number them, schedule the day, judge on a tablet, publish results and run the prize-giving — every step working on what you built in the last. The demo committee is deleted after two weeks.

Request a demo account

Or look around first

A worked example, from both sides

If you run events

You’re the committee secretary

Belfast Feis is five months out. The date is sanctioned, entries are open, and you’re still short adjudicators for one competition. You open the app to see where things stand.

You’ll land on your dashboard: what needs you right now, the numbers that matter, and every tool — booking, the syllabus, the schedule, the treasurer, safeguarding, the governing body’s return — one click away.

Try it as the organiser
If your child dances

You’re Aoife’s mother

It’s the morning of the feis. Aoife has three competitions today. You open the app on your phone between the second and third.

You’ll see her whole day on one screen: what time each competition starts, where, whether she’s placed yet, and what you paid when you entered her.

Try it as a parent

Both are the actual production logic — the same calculators, the same domain rules — running against sample data. Nothing you click there is saved; for that, request a demo account.

For a closer look

Every part of the platform, tool by tool

The dashboard and the family view are built from these. If you want to see the tabulator’s desk, the treasurer’s books, or the MC’s script cards individually, in the order a feis actually runs, they’re below.

Before entries open

  1. Booking the panel — invitations and the chase list, availability, registration currency, musician cover, expenses and rotation
  2. Published syllabus — generated from a discipline pack’s declared axes, with entries taken against it

Once entries close

  1. Numbering and paperwork — number cards, adjudicator sheets, running orders, line-up sheets, results and school packs
  2. The schedule and its clash detector — a dancer in two places at once, named on both sides

The day itself

  1. The day’s procedure — marshal, green room, stage desk and hall board, with the running-late estimate
  2. Marking a competition offline — the real op log and outbox; switch it to airplane mode and keep marking
  3. The tabulation desk — completeness, overrides and what is stopping a result being published
  4. Published results — what a parent opens on a phone, with the arithmetic behind any placing
  5. The microphone — script cards with pronunciation guides, the announcement queue, and what is waiting to be read out
  6. Prizegiving — who is called and in what order, perpetual trophies still out, certificates

Running alongside, and closing the year out

  1. The treasurer — a budget that produces the entry fee, trophy lead times, cash reconciliation, a P&L against budget, a sponsor fulfilment report
  2. Volunteers and safeguarding — the roster gap at 08:35, the lost-child log, the photographer’s suppression list, a protest bundle
  3. Governing body and close-out — the sanction, the return, retention and export, a ceili team, and next year’s seeded budget

Sample data throughout. These pages run the production domain and database builders; what does not exist yet is the API and the login in front of them — see plan/22-wiring-plan.md.

Ready to run your own?

Set up your committeeSee the pricing