Changes between 09/04/26 - 09/08/26

Summary

This release closes the last gap in registration — team entries now get bib numbers and are enrolled into rounds like every other entry type — and fixes a class of bug that had been quietly getting dates wrong for anyone travelling. A competition's dates now read the same whether you open the site in Chicago, London, or Shanghai. The page also notices when a new version has been released instead of leaving you on a stale one, and the rules governing who may change entries, and when, have been consolidated into one consistent set.

System

Dates Are the Same Everywhere

Getting dates right matters more than it sounds. When you travel to a competition, the dates on the program are the competition's dates — not a translation into wherever your phone happens to think you are.

Recent work on competition banners and cards introduced date handling that could shift a competition by a day depending on where you were viewing from. That is fixed throughout. If an organizer sets a competition to July 29, 2026, then everyone sees July 29, 2026 — in Chicago, in London, in Shanghai, on a laptop or a phone. Competition and session dates are now treated as plain calendar dates everywhere they appear: listings, cards, banners, detail pages, dashboards, and the date pickers organizers use to set them.

Team Registration Completed

Team entries were previously recorded but never carried through into a round. Team events come in more than one shape — a team match where several teams each send couples or soloists to represent them, and a formation where a single team occupies the floor for the whole number — but either way the team needs an identifier on the floor.

Teams now register the way athletes do. A team gets its own registration for the competition, receives a bib number from the team bib range, and is enrolled into the first round alongside solo and partnered entries. How the number is displayed, and how many copies of it a team needs, is up to each organizer for now; more support for this will follow.

Bib management now shows teams alongside individual competitors, and a team's bib number can be viewed and changed there.

The Page Tells You When It's Out of Date

Dancesport.app is updated often, which means the page open in your browser can quietly fall behind the version running on our servers. Until now, a page left open through an update would keep trying to reach the version it was built against — sometimes doing nothing at all, sometimes failing silently — which looks indistinguishable from the site being broken. A refresh fixed it, but only if you thought to try.

The page now keeps track of this for you, and handles it two different ways on purpose:

• Coming back to a tab you left open for a while — it reloads on its own, before you start working. It looks like the page load you were expecting anyway.
• A new version arriving while you're actively working — a banner appears at the bottom offering to reload, rather than reloading underneath you. It warns that anything unsaved will be lost, and you can dismiss it and reload when you're ready.

A quick switch to another tab and back won't trigger either one.

Registration Rules, Consolidated

The rules covering who may add or remove an entry, and when, have been rewritten as one consistent set rather than being checked separately in each part of the system. The behavior organizers and dancers will notice:

• While registration is open — dancers may enter themselves, studios may enter the dancers they manage, and officials may enter anyone.
• Before registration opens, after it closes, and while the competition is running — officials only. Seeding entries early and correcting them on the day are both normal parts of running a competition; doing either as a dancer is not.
• Once a competition is being scored or has concluded — the entry list is closed to everyone, officials included. It's part of the record at that point.

Withdrawing an entry now follows the same window, and an event that has already started is closed to changes for everyone. Previously an entry could be dropped out from under a round that had already been danced.

When the last entry is withdrawn from an event that was created on demand by a Dynamic Event, that event is now removed rather than left behind empty.

Account

Enhancement

• A password reset link stops working the moment it's used. Previously the link still opened a working-looking form, and you'd only discover it was spent when submitting it failed. Following a used or expired link now says so up front.

Scrutineer

Bug Fixes

• Fixed team names not displaying properly in the Scrutineer's view of preliminary rounds.

Organizer

Enhancement

• Federation abbreviations no longer have to be unique across the whole system. Custom federations are being used more than expected, and reserving abbreviations globally meant one organizer could block an abbreviation that made perfect sense for someone else's competition — including one they couldn't see. Pick the abbreviation that suits your competition.
• Viewing Event Adjudicator assignments is faster.
• The Create Event and Edit Event forms disable their submit button as soon as it's clicked, so a fast double-click can no longer create the event twice.
• A Dynamic Event's entry type can no longer be changed after it's created. Events already generated from it were built as solo or partnered, and changing the template afterward would leave it describing something its own events are not.

Bug Fixes

• Fixed the competition date picker selecting a date one year off when choosing start and end dates in the following year.
• Fixed newly generated rounds having their dances marked as already queued rather than created.
• Fixed a team entry's bib number being read incorrectly when the first round's entries were created.

Deck Captain

Bug Fixes

• Fixed an issue that prevented team entries from being checked in.

Public

Features

• Added a Roadmap page setting out where the product is going: the standing priorities that come before anything else, what's being built now, and what's under consideration. It's a statement of intent rather than a delivery schedule, and says so.