Since our last major update in mid-October, we've been busy making Equipe more reliable, more intuitive, and better suited to the diverse needs of organisers across Europe and beyond. Rather than one headline feature, this period has been about dozens of refinements across the platform. These improvements may seem small individually, but they add up to a noticeably smoother experience.

The indoor season is in full swing, and as shows move into arenas across the continent, we've listened carefully to your feedback. From entry workflows and timekeeping to invoicing and online publishing, nearly every part of the system has received attention.

Under the Hood: A Modern Foundation

Before diving into visible changes, it's worth mentioning the work that happened behind the scenes. We upgraded all four of our interconnected applications to Rails 8.1, the latest version of our underlying framework. We started with our smaller services and finished with the main application, positioning the entire platform for future development with improved performance and modernised infrastructure. You won't see this change directly, but it ensures Equipe remains fast, secure, and ready for the features we're building next.

Smoother Entry Management

Managing entries is one of the most time-intensive parts of running a show, and we've made several changes to reduce friction. For those running regular shows, we heard that reconfiguring mandatory field settings every time was tedious. You can now copy these settings from previous shows for the same organiser, saving time on repetitive setup.

We also addressed an issue where riders were searching for their licence number and the system would automatically link the first federation result without asking. In rare cases, this led to accounts being linked to the wrong person. There's now a confirmation step showing all matches before any linking happens, so riders can verify they're selecting the correct profile.

British organisers will appreciate the addition of account number and sort code as payer information fields. The UK doesn't use IBAN for domestic transfers, and this was a missing piece for local workflows.

We've also added the organiser's email prominently to entry summaries, so riders know exactly who to contact with questions about their entries instead of reaching out to Equipe support.

Better Tools for Timekeeping and Judging

Show jumping timekeeping received several practical improvements. Two new output options let you display time and faults on external monitors and LED walls in the format your venue prefers. We also added validation for manual time entry to catch obviously incorrect values before they affect results.

For dressage, the headline improvement is our new dual countdown timer for freestyle tests. FEI Rule 420 specifies two timing intervals: 45 seconds from the bell to the music signal, then up to 30 seconds from music start to entry at A. Judge C now controls both timers, with the display synchronised across all judges' tablets in real time. After field testing at an international show, scribers told us this works well in practice.

The marking sheet system also received attention. You can now send sheets to multiple email addresses when needed, which is useful for junior riders where both parent and child should receive copies. The sorting options have been reorganised into logical groups, and we've fixed several edge cases around printing and missing email handling.

Invoicing and Economy Updates

Financial workflows keep getting smoother. The income statement now includes a subtotal row for easier reconciliation at a glance. You can edit IBAN, SWIFT, bank name, and account holder details directly in the people grid view without opening each record individually.

We fixed an annoying bug where line breaks disappeared in invoice email messages. Organisers would compose multi-paragraph messages, but recipients saw them as walls of text. That's corrected now.

A less visible but important fix ensures that withdrawn or no-show riders don't retain prize money when results are recalculated. The distribution logic now correctly clears prize money for non-finishers.

Publishing to Equipe Online

When you update start times, Equipe Online shows a "Change" label so competitors know the schedule has shifted. However, for shows with frequent adjustments, this created visual clutter. Based on a question from a Danish organiser, we added a simple checkbox to control whether these change markers appear. Within 24 hours of hearing about the issue, the feature was live.

For competitions using dropped-score methods, the online results view now indicates which scores were dropped. This matches functionality that was already available in the app. We've also fixed schedule section ordering issues that occurred when manual reordering conflicted with fixed start times.

Listening and Improving

We review every support question and issue report that comes in. When the same question appears repeatedly, it's a signal that something needs to change: the product itself, our documentation, or how features are surfaced in the interface.

For example, we noticed many organisers asking how to get sponsor logos to appear on online start lists. The feature works, but its workflow clearly isn't discoverable enough. Feedback like this helps us prioritise not just what to build, but what to explain better.

Some fixes came from individual reports: a rider whose account got linked to the wrong person due to having incomplete/wrong National ID, an organiser whose category filters broke because names contained hyphens, a user whose freestyle test failed because no fallback judgement was set. Each of these led to targeted improvements that benefit everyone.

Looking Ahead

As we close out 2025 and head into the new year, we remain committed to making Equipe work better for you every day. The improvements in this update reflect what we've heard from organisers, secretaries, judges, and riders across dozens of countries.

Keep your feedback coming. Whether it's a question about how something works, a feature request, or a report of something that doesn't quite behave as expected, we read everything. Your input directly shapes what we work on next.