18 July 2026

Fixed: event invitations appear immediately

• New invitations now appear as soon as they are sent. The event panel updates its

invite count and rows immediately, and the full event-management page now does the same. Both quietly check the server copy without flashing or requiring a browser refresh. If that follow-up check fails or briefly returns stale information, the confirmed rows stay visible instead of incorrectly saying that no invitations have been sent.

Improved: clearer Communications navigation

• Communications is easier to move around. Messages, Comms Map, Automations,

Templates and Deliverability now sit in one centered icon menu using the same glass styling and responsive motion as member profiles. The menu remains swipeable on smaller screens, while existing routes and permissions are unchanged. The menu now stays above the page title throughout the Communications area, so switching sections no longer makes the header jump above and below it.

Fixed: invoice PDFs show their line items again

• Invoice PDFs now always show the real line items. A fault in how the lines were

fetched meant every invoice PDF rendered a “line item details are temporarily unavailable” placeholder instead of its contents. The lines now load reliably in a stable order, and if they genuinely can’t be read the PDF is held back with a clear error rather than producing an incomplete financial document. Previously-generated placeholder PDFs regenerate automatically. Totals are unchanged.

New: VAT support for VAT-registered clubs

• Clubs registered for VAT can now invoice with VAT end to end. With VAT enabled in

Settings → Billing, every invoice your club raises — memberships, joining fees, events, class packs, manual invoices and more — now carries the right VAT per line (inclusive or exclusive, at your default or a per-line rate), totals stay exact to the penny, and issued invoices are never altered afterwards — corrections flow through credit notes at the original rates. Clubs without VAT see no change at all.

• A new VAT summary report. Reports gains a VAT tab for VAT-enabled clubs: net, VAT

and gross by period, code and rate, with credit notes netted at their original rates and a CSV export. It’s a bookkeeping aid — clearly labelled as not a VAT return.

• Draft invoices can be recalculated. If you change VAT settings, existing drafts

keep their saved treatment unless you explicitly recalculate them (a logged action); issued history is never touched.

Improved: course and pathway reliability

• Course building, pathway assignment and reordering are now crash-proof. Reordering

sections, lessons, stages, tasks and portal messages applies as a single change (no more half-reordered lists if two people edit at once — the later editor is asked to refresh); assigning a pathway creates the member’s full task list atomically; and lesson watch-time is recorded exactly once even from two devices. Where information can’t be read, screens now say so instead of appearing empty.

Improved: card-payment invoices and invoice line ordering

• Card payments always produce a correct invoice for VAT clubs. When a card payment

settles an event booking, the resulting invoice now carries the club’s VAT treatment exactly like every other invoice — and if the VAT settings can’t be read at that moment, the payment is retried automatically rather than quietly recording an invoice without VAT. Clubs without VAT see no change.

• Invoice lines keep the order you arranged them in. New invoices remember the order

their lines were created or edited in — on screen and on the PDF — instead of falling back to insertion order. Existing invoices keep their familiar order, and issued invoices remain locked exactly as issued.

Improved: every remaining report fails safe, and event invoices self-repair

• The last six reports now say “couldn’t load” instead of zeros.

Financial, Insurance, Data Quality, Events, Trial Funnel and Class Pulse join the rest of Reports: a failed load shows a clear notice (never £0.00 revenue, an empty funnel or “no feedback” as if true), and a network failure can no longer leave the Financial report stuck on its loading screen.

• An event invoice can no longer end up empty. In the rare case where an invoice was

created but its line items failed to save, the payment flow now repairs the invoice automatically on retry — and if it can’t, the problem is flagged on Platform Health rather than leaving an invoice that looks settled but has no contents. The daily reconciliation now actively re-repairs any such flagged invoice, and the card payment retry always reconnects to the exact invoice it needs to fix rather than creating a duplicate.

• One reliable path for event-payment invoices. Whether the confirmation comes back

through the browser or the payment provider’s webhook, a paid booking’s invoice is now created, repaired and settled by a single authority — so two arriving at once can never produce a duplicate invoice or one without its line items, and the booking screen no longer raises the invoice separately. Paid bookings for another club’s event (a cross-club event that charges a different club) are declined at payment time rather than recorded under the wrong club’s VAT; free cross-club bookings are unaffected.

• Rapidly changing a report’s dates or programme no longer shows stale numbers.

On the Insurance, Data Quality, Events and Trial Funnel reports, switching filters quickly could briefly let an older, slower result overwrite the newer one; the report now always shows the result for the filter you actually chose.

Behind the scenes

• **The next database release now fails safely and runs in clearly separated

windows.** Blocking preflight checks return a real failure to the deployment runner, the card-payment invoice identity index is verified as usable rather than trusted by name alone, lock-taking audit maintenance runs only in its declared quiet window, and the post-code status-notification outbox no longer repeats unrelated database work. This is release hardening only; it does not enable a feature, send a communication or change live data.

Fixed: register saves for existing classes

• **Attendance saves work again for classes created before Programmes were

introduced.** Those classes already had a valid programme through their original target-programme setting, but the new attendance authority compared only the newer programme field and rejected the mark. Existing classes are safely reconciled to the canonical programme, new timetable saves keep that relationship populated, and the server now takes the attendance programme from the class rather than the browser’s current filter.

17 July 2026

Fixed: the top menu now uses your club's member terminology

• **The main navigation now uses the same member wording as the rest of the

app.** If your club calls people Members, Players, Gymnasts or another configured term, the top-bar link follows that setting instead of always saying Students. The mobile menu, command menu and Settings already used the configured wording; all of the app navigation now agrees.

Plan a sequence of scheduled member status changes

• **You can now plan a sequence of member status changes — e.g. pause on one

date, reactivate on another.** From a member’s profile, setting a future “Effective from” date on a status change now opens a planner where you can add, remove and reorder up to ten stages, each a status and a date. Save it and each stage applies automatically on its date; until the first stage, the member keeps their current status. A single scheduled change still works exactly as before — it’s just a one-stage plan.

• The profile shows the whole plan as a timeline. The scheduled banner lists every

stage in order, with the ones that have already applied ticked and the ones still to come marked as upcoming. “Edit” reopens the planner on the remaining stages, and “Cancel plan” drops the not-yet-applied stages while keeping anything that has already happened — applied history is never rewritten, and no automated messages fire for cancelled stages.

• The club-wide Scheduled Status Changes page groups by plan. Each plan shows its

next change and, for multi-stage plans, expands to reveal every stage. Cancelling from here uses the same confirmation and the same “keep what’s applied” rule.

• Plans are validated before they can be saved. Dates must be real calendar dates

in strictly increasing order with no repeats, two stages in a row can’t set the same status, the first stage can’t be in the past, and a plan can hold between one and ten stages — checked as you type and re-checked on our side. Replacing a plan is atomic: the previous pending plan is superseded and the new one saved together, so a member can never be left mid-change with a half-saved schedule.

Fixed: scheduled status plans — reliability and validation

• Scheduled plans no longer disappear behind a long history. The club-wide

Scheduled Status Changes page, and the daily job that applies due changes, used to read the whole history in one go — so a club with a large back-catalogue of already-applied changes could push the current, still-pending plans out of view and, worse, leave the tail of a big backlog unapplied. Both now fetch the pending plans first and page through the work in full, so every current plan shows and every due change is applied no matter how much history has built up.

• Cancelling a plan always leaves an audit trail. Cancelling a scheduled plan now

records the cancellation and drops the not-yet-applied stages together as a single step, so a cancel can never quietly succeed without a matching entry in the member’s activity history. Applied stages are still never touched.

• A first stage that repeats the member’s current status is refused. Setting up

a plan whose opening stage matches where the member already is (for example Active → Active) was a confusing no-op; it’s now rejected as you type and on our side. The planner also measures “not in the past” against your club’s local calendar — the same clock our side uses — so a plan starting today is never wrongly refused around midnight.

Schedule portal messages to appear and expire on set dates

• **You can now schedule a portal announcement to appear and expire on set

dates.** Each message in Settings → Member Portal has an optional “Show from” and “Show until” date. Set both to run a notice for a fixed window, set only one to open or close-ended it, or leave both blank to keep the old behaviour — shown whenever it’s enabled. A half-term closure or a “kit orders close Friday” reminder can go in ahead of time and clear itself, with no need to remember to turn it on and off. The dates are inclusive and use your club’s local calendar, so a message set to end today still shows all of today.

• Members only ever see what’s live right now. A message scheduled for

the future, or one whose end date has passed, never reaches the member portal — the filtering happens on our side before anything is sent to a member’s device, not in their browser. The manual on/off switch still works as an override, and archiving still hides a message immediately whatever its dates say.

• The Settings list shows each message’s status at a glance. Every

message carries a badge — Live, Scheduled, Expired, Off or Archived — worked out from its dates, its enabled switch and today’s club date, so you can see exactly what members are seeing without doing the mental arithmetic. Impossible dates and an end that falls before its start are refused rather than saved.

• Editing just one date can no longer create an impossible window. When you

change only the “Show until” date on a message that already has a “Show from” date (or the other way round), the new date is now checked against the one already saved — so an end that would fall before the existing start, or a start after the existing end, is refused rather than quietly stored. Clearing a date still works as before.

Copy a member's insurance number with one tap

• You can now copy a member's insurance/governing-body number with one tap. A

small copy button sits next to the membership number on a member's profile — tap it and the number is on your clipboard, ready to paste into an insurer's or governing body's system, with a quick tick and a confirmation to show it worked. If your browser blocks the clipboard for any reason, it tells you plainly rather than pretending it copied. Editing insurance details still works exactly as before — the copy button sits alongside the existing edit action, it doesn't replace it.

Safeguarding lead now works everywhere

• Designating a coach as safeguarding lead now takes effect across the app.

Being named your club's safeguarding lead is meant to unlock the restricted safeguarding views a coach otherwise can't see — retained accident reports and their PDFs, the accident detail screens, and the retained-record counts on the dashboard. Previously the designation was only honoured in one place and was silently ignored everywhere else, so a designated coach was still refused that data. The designation is now read from the club's own membership record on every one of these checks, so it grants exactly what it's supposed to — no more, no less. Owners and admins are unaffected (they already have this access), and a coach who has not been designated still sees no change.

• The designation is per club and reflects the current setting immediately. A

coach who is the safeguarding lead at one club gains nothing at another club, and removing the designation takes effect on the very next request — there is no cached access that outlives the change. If the membership record can't be read for any reason, access is refused rather than assumed, so this never opens a safeguarding record by accident.

Behind the scenes

• Security hardening: tighter club boundaries on three internal actions. Sending

event invitations, regenerating a class lesson plan, and firing an automation now each re-confirm that the member, class, or plan being acted on belongs to your own club before anything is read, written, or sent. A request that references another club's record is refused instead of proceeding. This has no effect on normal use — everything you do with your own club's data behaves exactly as before.

• Guessing an id no longer reveals whether it exists. A handful of endpoints

(a staff-access removal, an accident-report file link, a member data-erasure, and the member progress-report preview and send) used to answer "that belongs to another club" differently from "that doesn't exist". They now return the exact same *not found* response either way, so a stranger's id can't be confirmed by probing. Access was already correctly refused in every case; this only removes the tell.

• A club can no longer attach another club's record to its own data. Several

save actions — the charges and membership-plan editors, the member CSV importer, a team's season, a class recording's lesson, and an enrolment invite — now check that a referenced belt system, programme, plan, season, lesson or token actually belongs to your club before storing the link, rejecting anything that doesn't.

• Enrolment invites are now fully sealed to your own club. Sending an invite

used to trust a custom email template and an invite-token reference from the request without re-checking ownership: a crafted request could have rendered another club's template into the email or aimed delivery-tracking at a token it didn't own. An invite now only uses a template that belongs to your club (falling back to the standard wording otherwise) and refuses outright if the token it names isn't yours, and the later delivery-status stitch is likewise pinned to the originating club. Normal invites — sent from your own club's screens — are unaffected.

• Removing group-club access no longer reveals demo tenants. Trying to revoke a

staff access row you don't administer already returned a plain *not found*, but a guessed id that happened to land in a demo club leaked a different response — a tell that the id was real. All unauthorised attempts now return the identical *not found* regardless of the target club, while a club's own administrator still sees the usual read-only notice on the demo tenant.

• A momentary database problem is no longer reported as "not found". Those same

belonging-to-your-club checks (charges and membership-plan editors, a team's season, a class recording's lesson, and lesson-plan regeneration) previously treated a transient database error the same as a genuinely unknown id — quietly telling you the record didn't exist when the real problem was on our side. They now tell those two situations apart: a real database hiccup surfaces as a generic try-again error instead of a misleading "unknown" message, while a genuinely foreign id is still refused exactly as before.

• Sturdier event invitations. Sending event invitations now validates the selected

member list up front — rejecting malformed ids and capping how many can be invited in one go — counts a member picked twice only once, and stops with a clear error if the invite links can't be written, rather than reporting a partial success. Inviting members now also requires the same permission already needed to resend or cancel an invite, so the whole invitation workflow is gated consistently.

Fixed: event rosters, certificates and calendars showing empty

• Event and grading screens that had started coming up blank are working again.

After an earlier database update today, several places that list booked members could return nothing at all — event and grading day rosters, the register’s event roster, the printable attendance / scoring / certificate PDFs, the grading scores and analytics screens, the examiner scoring page, the member portal’s events list and its subscribed calendar feed, and the household lookup in support. Each of those reads has been corrected, so rosters, downloads and calendars are populated as normal.

• These screens now fail loudly instead of looking empty. Where a booking list

can’t be read, the screen or download now reports a clear error rather than quietly showing an empty roster or a blank PDF — so “no one’s booked” always means exactly that, and a genuine problem is never mistaken for it.

Fixed: more screens that could show empty (staff leave, certificates, membership counts)

• Staff leave no longer silently disappears. After the same database update, the staff-leave

panels on registers and calendars could come up blank because of an ambiguous lookup; leave now loads correctly, and if it genuinely can't be read the screen says so rather than pretending nobody's off.

• Examiner scoring, member certificates and the settings membership-plan counts were affected by

the same class of ambiguous lookup and are fixed too. A guard now checks the whole codebase against the live database's relationships, so this class of "silently empty" bug can't quietly return.

Missing-in-Action now counts "Late" as attended

• Late now counts as attended in Missing-in-Action reports and automations. A

member marked *Late* has clearly turned up, but the Attendance report's Missing-in-Action list and the automated absence reminders only recognised *Present*, so a member who was regularly late could be flagged as missing and even chased with a "we miss you" message. *Present* and *Late* are now treated the same everywhere attendance is judged — one shared rule drives the report, the automated reminders and the scheduled email summaries — so a Late mark keeps a member out of the missing list. *Late* is still shown as Late in the coach and staff breakdowns; it is only counted as attended, never relabelled.

• The missing list is no longer skewed by the dates you're viewing. The

Attendance report's Missing-in-Action list now measures each member against their genuine most-recent attendance, independent of the date range shown on screen. Previously, narrowing the report to a recent window could make a member who attended just before that window appear to have gone missing; the list now uses the member's real last-attended date, so it means what it says whatever range you have selected.

• A database hiccup can no longer fire absence reminders by mistake. If the

attendance lookup that powers the automated Missing-in-Action reminders can't be read, that check now stops for that run instead of assuming nobody attended — which would otherwise have flagged every member as missing and sent a wave of unwarranted messages. Every other automation (insurance, gradings, birthdays and the rest) is unaffected and continues as normal.

Missing-in-Action now respects the programme lens

• **When you view the Attendance report for a single programme, Missing-in-Action

now measures attendance within that programme.** Previously the missing list used each member’s most-recent attendance across the whole club, so a member who had stopped coming to, say, Football but was still attending another programme was wrongly kept off the Football missing list. With a programme selected, the list now looks only at recent attendance at that programme’s classes — over a fixed recent window, independent of the date range on screen — so a member absent from this programme shows up even if they are active elsewhere. A Late mark still counts as attended, and the whole-club view (no programme selected) is unchanged.

• A database hiccup can no longer send a misleading scheduled report. The

Missing-in-Action figure in the scheduled email report summaries now stops the report if its attendance lookup fails, instead of treating the failure as “nobody attended” and emailing a summary that flags every member as missing. The run is recorded as failed so it shows up in our health checks, and a correct report goes out on the next run once the read succeeds.

Kukkiwon is now a Taekwondo-scoped custom field

• **Kukkiwon number is now a Taekwondo-scoped custom field, not shown to unrelated

programmes.** The Kukkiwon dan-certificate number used to be a fixed field baked into every member's record, so a football, dance, gymnastics or karate club saw an empty "Kukkiwon No." box that meant nothing to them. Kukkiwon is now one of the custom member fields you opt into from Settings → Custom Fields and scope to your Taekwondo programme(s), so only the members it applies to ever see it. Clubs that don't track it never see it at all.

• Nothing you've already recorded is lost, and existing numbers keep working.

Any Kukkiwon numbers already on your members' records continue to show and remain editable exactly as before, whether or not you've adopted the new custom field — the record falls back to the original value so no data is hidden or dropped. Once a club adopts Kukkiwon as a custom field, the number is captured and edited alongside your other custom fields, and the existing values carry across untouched.

• The member's Grading tab now shows the field the way you've set it up. The

Kukkiwon line on a member's Grading tab now reads your custom field — using the value you've captured there and the label you've given it, so a renamed field shows its new name — and still falls back to the member's original number when you haven't adopted the field. A member of a programme the field doesn't apply to sees nothing there, as expected.

• Mixed clubs are never given a club-wide Taekwondo field by mistake. When

existing Kukkiwon numbers are migrated onto the custom-field model, the field is set up automatically only when every member who has one sits in a single, clear programme — in which case it's scoped to exactly that programme. If your members are spread across more than one programme, nothing club-wide is created; the original numbers are kept as-is and the clubs concerned are flagged so you can pick the right programme yourself, so a Taekwondo field can never appear on a football or dance member's record.

Fixed: MIA report count could be wrong for very busy clubs

• **The scheduled attendance report's "Missing in Action" count is now accurate no matter how

busy the club is.** For clubs logging thousands of attendances a fortnight, the report could read more members as missing than really were, because it only looked at the first slice of recent attendance. It now reads all of it, so the count is right.

Fixed: Attendance report’s missing list no longer shows a false “everyone missing”

• **The Attendance report’s Missing-in-Action list now says so plainly when it

can’t be worked out, instead of listing everyone.** When you view the report for a single programme, the missing list is built from a read of recent attendance. If that read failed, or was too large to load in full, the list used to fall back to treating it as “nobody attended” — flagging every member as missing on screen and in the export. It now shows a short “couldn’t load” notice for that one section instead, so a temporary hiccup or a very large club can never produce a false list of missing members. The rest of the report still loads as normal.

• The 14-day cut-off now follows your club’s local calendar. Whether a member

counts as missing is measured against your club’s own “today” rather than the server’s clock, so a member who attended right on the edge of the window near midnight is judged by the correct day.

• Every source the missing list depends on now has to load in full. As well as the

attendance read, the class list and the member roster behind the list are now read completely, and if any of them fails or is too large to load in full the section shows the same “couldn’t load” notice rather than risk a false list. The missing list is also now built from who is currently enrolled in the programme — so someone who has left the programme is never shown as missing (even when you’re looking at an older date range), while a current member who hasn’t attended still is.

• Five more reports now say “couldn’t load” instead of showing zeros.

Membership, Households, Owner Overview, Accidents and Student Analytics now treat a failed or partial read as a problem to show you — the report (or just the affected section, such as Attendance Alerts or Revenue by program) displays an unavailable notice rather than “0 households”, “£0.00 revenue”, “no accident reports” or a false attendance alert. A genuinely empty result still shows as zero.

• Very large clubs can no longer see quietly understated totals. The reads behind the

Households and Owner Overview figures (including invoices) are now read in full, and if a dataset is too large to read completely the report says so instead of showing a lower number as if it were the truth.

• Student Analytics grades every member against the right ladder. In a club running more

than one grading system, each member’s belt or grade now resolves against their own programme’s ladder (and a programme filter uses that programme’s ladder), so nobody shows as ungraded or sorted against another discipline’s ranks.

Improved: reports fail safe instead of showing a misleading zero

• **The Attendance report’s totals now say “couldn’t load” when a

read fails, instead of a believable zero.** Every dataset behind the headline numbers (attendance, classes, enrolments and staff) is now read completely; if a required read fails or is too large to load in full, the report — or just the affected section — shows a clear notice rather than an under-count. Nothing you see is stale from a slower, superseded request either.

• Program-lens reports count the right people for the dates you picked. For

Membership, Progression, Student Analytics, Accidents, Households and Owner Overview, who counts under a program filter is now measured against your club’s own calendar days (correct across the March/October clock changes), so a member who joined late on the final day of the range is included; and if that lookup fails, the report shows an error instead of a false zero.

• Scheduled email reports read your whole report list and flag failures. The list of

enabled reports is now read completely (a large list is never silently truncated), and a read failure is reported rather than quietly skipping due reports. A test send is reported honestly — if every recipient fails, it no longer says it succeeded.

• Member profiles tell you when a scheduled-status check couldn’t run. A failed

check now shows a short “couldn’t check” notice with a retry button instead of looking like there are no scheduled changes, and it clears itself once it loads or you save a change.

Improved: scheduled status-change notifications are now recoverable

• A scheduled status change never silently loses its follow-up notification. When a

scheduled change is applied, its notifications are now recorded durably at the same moment as the change itself, and a background repair step re-sends any that didn’t go out (for example if the system restarted at exactly the wrong moment) — without ever sending a duplicate.

• The repair step now runs automatically and reports honestly. The recovery sweep is

scheduled every five minutes, and if recording a notification’s outcome fails, the run is flagged for attention instead of quietly counting it as done — nothing can look “delivered” unless it truly was.

• **The scheduled email report’s “Upcoming Trials” section can no longer show

a false “None”.** If the trials list can’t be read in full, the report is held back and the failure flagged, rather than emailing an empty section as if no trials were booked. A genuinely empty week still shows “None” as before.

16 July 2026

Smoother navigation

• Returning from What's new no longer flashes the public homepage. The

changelog now preserves an authenticated staff session, so using the browser Back button returns directly to the dashboard shell without a marketing-page flicker.

Honest calendars and team views

• Subscribed family calendars now fail visibly when their source data is unavailable.

A temporary database problem can no longer publish a believable empty calendar that makes booked classes or events appear to have disappeared.

• Calendar events now keep a valid duration. Events without a recorded end time

use a 90-minute fallback, while events that finish after midnight end on the next day rather than before they start.

• Team Sports no longer turns read failures into empty teams, rosters or results.

Team lists, fixture details, report cards and player search show a retryable unavailable state instead of zero counts or blank selections.

• Matchday updates remain honest after a successful write. If the optional

automation fan-out cannot load its recipients after a fixture is published or a result is recorded, the failure is reported for operators without telling staff the completed update failed and inviting a duplicate submission.

• Modules & Programs preserves its last known-good configuration. Failed core

reads now show the shared Retry state; only the documented not-yet-migrated vertical column may continue in deploy-safe mode.

Safer enrolment and event configuration

• Enrolment questions are checked before payment or member creation. Required

programme-specific questions can no longer fail late after an enrolment token has been consumed or a partial member record has been created.

• Duplicate enrolment add-ons are rejected. Prices, invoice lines and onboarding

tasks now all use the same server-verified selection, preventing repeated items from producing mismatched totals.

• Progression filters stay within their programme. Class and event-type minimum

and maximum levels must belong to the selected club-owned progression system, and reversed ranges are rejected.

• Group-event booking policy comes from the host club. Required booking

checklists and demo protection now follow the club running the event while the invited member remains correctly linked to their own club.

• Concurrent member transfers no longer clean up the wrong club. If another

request moves the member first, the stale request stops before removing class enrolments or changing invoices and asks staff to refresh.

• Uncertain refund outcomes are held for reconciliation. A Stripe timeout or

connection failure no longer restores a stale balance and invites a second refund; staff receive an honest pending-check response instead. Refund amounts must also be exact, safe whole pence values.

Release groundwork

• Member-portal sign-in is ready for atomic credential handling. Login-code

and magic-link issuance/consumption, trusted-device sign-in and session rotation now use one-time transactional authorities, preventing two concurrent clicks from creating two valid sessions. Sign-in sets the secure cookie directly, trusted devices are tied to the issued login attempt and session lineage, and removing an authorised contact revokes their pending and active credentials in the same transaction. Staff status and bulk-invite views now ignore preserved login history for contacts whose access was removed, while retaining those rows for audit. Trusted-device revoke retries converge on one rotated session after a lost response instead of revoking the retry underneath itself. The authority is applied and verified in persistent local Docker only, not live; production still requires the reviewed migration-before-code release step.

• Attendance usage recovery is installed locally behind a compatibility bridge. The

transaction records the obligation to adjust class usage alongside the attendance change, so a temporary accounting failure can be retried instead of being lost. It snapshots the billing owner, rejects cross-club identities, and leaves impossible negative counters pending for repair instead of silently clamping them. It is applied and verified in persistent local Docker only and remains in compatibility: 23,066 historical rows are still unclassified, with zero approvals or classifications. It has no live effect, and switching to v2_only is not authorised.

• The full trial lifecycle is ready for a migration-before-code release.

Public and staff booking, rescheduling, cancellation, pipeline status changes, and add-student conversion now share transaction authorities and expected-state locks. Exact replays return the recorded response; changed payloads and terminal source revival are rejected. Reminder and communication work is durably leased after commit; a delayed send carries an immutable trial-recipient snapshot and remains visibly queued until its worker records the real delivery result. Known failures remain repairable, while ambiguous provider outcomes make repair health non-green and require an explicit operator decision instead of a blind resend. An authorized delayed-send retry reopens its lifecycle and queue records together, and Admin Health shows a stale or failing repair heartbeat. Browser roles lose direct trial-booking and automation-queue writes while retaining tenant-scoped reads; staff cancellation/rescheduling requires the effective trials-management capability and demo guard, and public token routes remain available. Token-scoped, staff, and cron repair paths keep committed moves and cancellations recoverable. The authority is applied and readiness-verified in persistent local Docker only, not live; generated types still require final reconciliation after all reviewed supplemental authorities.

• Class capacity and waiting-list enrolment now have one rehearsed authority.

Recurring rosters and dated bookable occurrences share an exact lock-and-count contract, including active/new member semantics, scheduled extra classes and ad-hoc pins. Offers are persisted before email or automation work, ambiguous provider outcomes remain visible for explicit resolution, and claiming the final place reserves it until the matching enrolment atomically creates the roster link. Browser roles no longer own queue, roster, occurrence-booking or capacity writes, and direct settings, import, member-profile, portal and cleanup paths are cut over to tenant-bound authorities. Rollback and real two-session disposable proofs now cover final-seat configuration, claim, consume/expiry and promotion races. Email scanners land on GET confirmation pages and only signed POST confirmation mutates. Dispatch evidence has a five-attempt/dead policy, cancellation automation is repairable, historical offered rows are retired safely, and staff/trial enrolment cannot reach the legacy class writer. The authority is applied, double-applied and readiness- verified in persistent local Docker only, not live; the pinned production- clone readiness/rollback gate remains mandatory before release.

• Waitlist sibling identity and transfer-date rosters are now closed for review.

Guardian email is contact data rather than a child key: known student identity is preferred, anonymous joins use a child fingerprint, legacy duplicates are remediated explicitly, and converting one child does not remove their sibling. Staff cancellation accepts an exact secondary-club access grant behind the same route capability gate. Member transfer now waits for concurrent occurrence booking, transactionally cancels every transfer-date/future source booking with durable cancellation evidence before moving the member, preserves past source history, and rejects target live preassignment. The authorities are applied and verified in persistent local Docker only, not live.

• Platform subscription checkout has a locally rehearsed concurrency design.

The proposed authority prevents a club and its group from opening competing subscriptions, reuses an exact checkout request safely, and rejects a changed Stripe-session replay. Ambiguous provider calls remain blocked for reconciliation, and a stale webhook cannot overwrite a newer canonical subscription. It remains unapplied and does not alter live checkout until the matching routes and webhook are reviewed and deliberately cut over.

• Empty-household deletion is guarded against financial-history loss. The

proposed lifecycle authority now refuses deletion while a membership, course-package subscription, or GoCardless relationship remains, rather than allowing parent-table cascades to erase those records.

• Cross-club member transfers have a rehearsed all-or-nothing authority. The

wired authority moves membership, class, invoice and activity state in one transaction, while refusing provider-backed memberships and shared invoices that require deliberate finance review. The proposal is verified only through rollback/concurrency proofs and persistent local Docker readiness; it is not live.

• Online enrolment is ready for an atomic migration-before-code release. The

wizard now prepares one immutable server-priced quote before Stripe, binds the PaymentIntent and webhook to that operation, and finalizes token, household, contact, member, consent, formally issued invoice, classes, programme, onboarding and optional trial conversion in one exact-replay transaction. Shared guardian email never selects a student or household; staff must make an explicit trusted choice, and ambiguous household email fails safely. Provider success followed by a local failure enters reconciliation and tells the parent not to pay again. Rollback and disposable two-session proofs cover contention, changed payloads, faults and two siblings sharing one email. A five-minute repair worker reclaims pending or expired post-finalize effects, so a process crash cannot strand welcome automations. The SQL is applied and readiness- verified in persistent local Docker only; the dependency migration must still land immediately before this runtime cutover in production.

• Enrolment owner alerts are retry-safe. Telegram notifications to club

owners now claim a durable, club-scoped delivery record before sending. A replay cannot notify the same owner twice after an uncertain completion, failed deliveries remain retryable, and stored delivery keys contain only a one-way hash of the Telegram chat identity.

• Grading result writes and publishing now have a rehearsed causal authority.

Versioned authorities tie each award to its exact booking, prevent publish and result edits from racing, and refuse an undo if the member's level has since changed. The application routes are wired and the authority is applied and readiness-verified in persistent local Docker only; production still requires the data preflight and migration-before-code release.

• Refund and external-entry races have rehearsed transaction designs. The

refund operation ledger now has its runtime cutover described below, while its SQL remains unapplied outside local Docker. The broader external-event creation authority is wired and applied/readiness-verified in persistent local Docker only; it creates the invoice, canonical entry and paired entry as one unit with database uniqueness under contention.

Safer payments and invoices

• Opening a one-off payment page no longer creates a Stripe customer. Member

payments keep their receipt email and local identity without generating a new provider customer before any money moves. Long-lived Allsorted subscription customers remain unchanged and are now created with recoverable idempotency.

• Stripe refund and dispute records now reflect what actually happened. Partial

refunds retain exact whole-pence totals and only the affected subject is updated; a later full refund can complete correctly. A lost dispute reopens the debt rather than pretending the invoice was void, and paid insurance renewals can repair a transient local-write failure on replay.

• GoCardless settlement is more recoverable. Authoritative read/write failures

stay retryable, missing provider mappings create visible reconciliation work, package access is verified after settlement, and subscription amounts must be exact positive integer pence. Provider success is no longer hidden by a local write that quietly failed.

• **Refunds, module purchases, vertical add-ons and platform subscription checkout

now have durable authorities ready for release.** Each operation is claimed locally before Stripe is called, replays use the same provider idempotency key, and ambiguous or pending outcomes remain blocked for reconciliation rather than being submitted twice. The proposal SQL is rehearsed and applied locally only, so it must still be applied remotely before these runtime cutovers are deployed.

• Refund problems are now visible and repairable. A bounded background worker

and owner-operator queue cover pending, provider-unknown and provider-succeeded/ local-repair states. Event cancellations and failed paid waitlist claims use the same authority, so they cannot report a refund that Stripe has not confirmed.

• Formal invoice issuance has a single frozen contract. The proposed authority

allocates one club-scoped number and freezes the customer, supplier, dates, currency, whole-pence totals and tax facts. Owners can configure supplier billing identity in Settings; issued invoices are immutable, corrections use separately numbered credit notes, and public invoice links are opaque, expiring and revocable.

• Future payment providers now have a defined integration seam. Small capability

contracts cover connections, one-off payments, recurring collection, refunds, normalised events and reconciliation without adding provider-specific columns to every feature. Stripe and GoCardless adapters and provider-health reporting now exercise that seam; moving every historical call site behind it remains an incremental architecture task. No additional provider was enabled in this pass.

15 July 2026

Safer trials, grading and staff invitations

• Trial bookings now stay on the timetable. A public booking or reschedule

can no longer be submitted for a date when the selected class does not run; date checks follow the club calendar rather than the server’s timezone.

• Staff invitations find existing accounts reliably, even when the person

already belongs to another club and sits beyond the first page of Auth users. A temporary Auth lookup problem now stops safely instead of creating a second account.

• External examiner arrangements are session-bound. A lead examiner’s

lines, pairs and current participant can only contain bookings from that scoring link’s own club and assessment session.

• Publishing assessment results is one-winner safe. A double-click or two

devices publishing together can no longer queue duplicate certificate work; a session containing several linked events only queues the events this request actually published.

Billing and reporting reliability

• Platform checkout now protects clubs from a second Stripe subscription.

Active, trialling, past-due, unpaid, paused and incomplete subscriptions must be managed rather than duplicated. A genuinely cancelled or expired subscription can still be replaced with a fresh checkout.

• **Stripe subscription updates fail visibly if their club or group cannot be

read or updated.** The webhook remains retryable instead of being marked complete while the local subscription record is stale.

• Owner revenue reporting now prefers exact stored pence for invoices and

line items, with the older decimal fields retained only as a compatibility fallback.

• Scheduled reports require a durable delivery claim. A temporary outbox

database fault no longer falls through to a direct send that could be repeated; installations that genuinely do not have the outbox table yet retain the old direct-send behaviour.

Data access and exports

• **Member data exports now issue fresh signed links for retained accident-report

files**, whether an older row stored a full Supabase URL or a newer row stores the private object path.

• Portal sign-in is more fail-closed. A one-time link sets its cookie from

the same successful consume operation, and the optional trusted-device cookie is only issued when its revocation record was stored successfully.

Communications and registers

• **Scheduled Email, SMS and Telegram now have matching previews and honest

labels.** Single- and multi-channel messages show only the channels actually selected, SMS is no longer described as Telegram, and scheduled history can preview each stored channel snapshot through the guarded send-detail view.

• **Scheduled sends now reject incomplete channel content before they enter the

queue.** Email requires its subject and body, while SMS and Telegram each require their own message text; one channel can no longer borrow another channel’s content.

• Register counts now use the same current-member rule everywhere. Expected

counts, opened rosters, capacity figures, member search and attendance writes include only members whose current lifecycle is New or Active. Paused, leaving, archived and unknown statuses remain in historical data but no longer inflate today’s expected attendance.

Under the bonnet

• A five-part transactional hardening pack has been authored for portal

credentials, refunds, platform checkout, external-event settlement and legacy assessment undo. It is not wired, not applied and has no live effect. The SQL compiles in local Docker with service-role-only privileges and is rolled back after rehearsal; the sensitive behaviours still require review before any deployment.

• The wider household, enrolment, attendance and waiting-list transaction wave

remains deliberately paused until that review is complete.

13 July 2026

Clearer menus

• “Comms” is now “Communications” in the main menu, and it links

straight through to Automations, Templates and Flows (with the same access rules as the Comms Centre — staff only see what they’re allowed to).

• “Money” is now “Finance”.

Finance — see how everyone pays at a glance

• A new Payment options page under Finance shows, for each household, whether

a Direct Debit is set up (active or pending) and whether a card payment is on file — a single place to spot who still needs to set up payment. Read-only, admin only.

Feedback stays on the timetable

• Class Pulse now only asks about regular timetable sessions — not events

or one-off / ad-hoc classes — so the “How was today’s class?” prompt only appears where it makes sense.

Staff leave — set your own availability

• “My availability” now opens a proper editor. From My Leave a staff

member can set which days they normally work, which is what their leave is measured against — previously the link went to a settings tab with nowhere to actually set it.

Your words, your way

• Call things what your club calls them. A new Settings → Terminology

control lets you set what you call members (Members, Students, Players, Participants…), assessments and grades. The whole app follows your choice. The default is now vertical-neutral — “Member” and “Assessment” — so a brand-new club of any sport reads naturally out of the box; martial-arts clubs just set it to “Students” / “Grading” and everything switches back.

Custom fields — track what matters to your club

• A new Settings → Custom Fields builder lets you add your own fields to

track per member or per programme — a squad number, an exam board, a registration date, whatever your sport needs. Add them yourself, mark any as sensitive, and they show on the member profile and come out in your CSV export. Suggested fields for your sport are one tap away.

Under the bonnet

• Vertical-neutral wording. More of the app’s progression wording (belt /

rank / grading headings on reports and grading screens) now follows each club’s own terminology, so a gymnastics or dance club sees its own words rather than martial-arts defaults. Martial-arts clubs are unchanged.

• Household leaver state stays in step. When the last active member of a

household leaves, the household record now reflects that too.

• Reliability hardening (from a code review). Several correctness fixes:

saving a member’s custom fields can no longer wipe others if a read hiccups; approving or declining the same leave request from two devices at once can’t both “win”; the after-class feedback prompt can no longer be sent twice for the same class; the feedback save/skip actions now enforce the same “only real, recent timetable classes” rule as the card itself; a department cover-limit that can’t be checked now blocks rather than silently letting a booking through; a failed programme creation no longer leaves a half-made programme behind; and an add-on subscription that hasn’t actually collected payment (incomplete, past-due, unpaid or paused) is now flagged as needing attention instead of counting as paid. Feedback data older than 24 months is now automatically anonymised.

• Groundwork for a smarter dashboard. We’ve started building an

“action centre” that will gather the things needing your attention — overdue payments, failed messages, cover clashes and the like — into one prioritised list on your dashboard. It’s switched off for now while we pilot it, so nothing changes on your screen yet; more soon.

12 July 2026

Class Pulse — hear how every session landed

• Members can now rate each class with a tap. After a class, the Member

Portal shows a simple card with four hand-drawn faces — Exceptional, Great, Okay and Not great — asking exactly the right question: “How did the 6pm class on Tuesday go?” For under-16s it gently asks the parent to check in with their child first. One tap saves it; adding a written comment is optional, and there’s always a no-pressure Skip. Only people who actually attended are asked, and only within 48 hours — fresh, honest feedback, never a nag.

• A push notification 15 minutes after class (“How did it go today?”)

brings members straight to the card — one notification per household, and never for a cancelled class.

• The feedback card got a glow-up. Four hand-drawn line faces — lime,

green, amber and red (Exceptional / Great / Okay / Not great written centred underneath each) — a proper Skip button, and a little celebration when you answer — a burst of confetti and a “Thanks — feedback saved!” toast. And so it never gets missed, a few seconds after opening the portal the card gently steps forward into the centre of the screen while the page behind dims — one tap anywhere puts it back if now’s not the moment (it only does this once per visit).

• Comments only when they count. A sad or middling face always offers the

optional comment box (that’s where the detail matters); a happy face just celebrates and moves on, only asking for a comment about one time in three — quick taps, no chore.

• A new Class Pulse report collates every rating by class, coach, grade,

age and gender, with trends over time — and the dashboard now shows this week’s pulse at a glance, flagging any unhappy faces so you can follow up while it matters. Coaches see their own scores; written comments stay with owners and admins.

• The report now uses the same hand-drawn faces as the member card —

each comment carries the lime, green, amber or red face the member chose, instead of a stock emoji, so the report reads as one with the portal.

• Exceptional is broken out on its own. The report counts Exceptional

ratings separately (its own stat next to the pulse score), and the weekly trend and every breakdown bar now show a distinct lime band for Exceptional above the green “Great” band — with a colour key — so you can see at a glance how many members loved a class, not just that they were happy.

Staff Leave — a holiday planner built into your club

• A new Staff page with a wall chart: everyone’s time off on one

colour-coded calendar — annual leave, sick days, and your own custom leave types — with balances, carry-over and bank holidays handled properly (including coaches who work Saturdays).

• Request and approve in a couple of taps. Staff request time off, the

right person gets notified and can approve or decline with one click — and because the planner knows your timetable, it warns when leave clashes with classes that person teaches, and marks those days “needs cover” on the club calendar.

• Half days look like half days. A morning off colours the top half of

the day on the wall chart, an afternoon the bottom half — and hovering tells you which. Full days stay full blocks.

• Leave shows on your main calendar as a toggleable layer, so planning

around absences is finally one screen, not three spreadsheets.

• The whole module can be switched off in Settings if you don’t need it.

Pay for AllSorted your way — including annually

• The Billing page now takes payment for your AllSorted subscription —

add a card during your trial and you’re set.

• New annual option: pay for 10 months, get 12. Choose Monthly or Annual

at checkout; annual plans include a 30-day cooling-off period, after which the payment is non-refundable (you keep full access to the end of your paid year).

One price, everything included — £69 covers your whole sport

• Everything is now included in the £69 plan — courses, training

pathways, competitions, team sports, timed events, apparatus assessment, routine performance and multi-discipline support. No more per-feature add-ons: another reason to move from a system that charges for every module.

• The only add-on is a genuine additional sport. Run as many programmes

as you like within one sport for £69 — Taekwondo, Taekwondo Tots and Kickboxing are all one martial-arts club. Add a truly different sport (say Gymnastics, then Yoga) and each extra one is £20/month.

• Tell us your sport in Settings → Modules. Each programme now has a

simple “Vertical” picker (Martial arts, Gymnastics, Dance, Swimming and more). The Billing page shows exactly which sports you run and what — if anything — the extras cost. Unclassified programmes are never charged.

• Adding a programme is now a proper guided step, not a bare form: a big

“Add programme” button, pick your sport as you go, and a clear preview of exactly what it means for your bill before you confirm anything.

• Then a few quick questions set everything up for you. Plain-English

yes/no questions — “Do members earn belts, grades or levels?”, “Do you enter competitions?” — pre-answered sensibly for your sport, switch on exactly the right features and leave the rest off. A dance club is never asked about gymnastics apparatus; a swimming club gets race times suggested automatically. Everything can still be changed later with one toggle.

• The Programs section now leads the page — no more hunting halfway down

for the Add programme button.

• Friendly confirmations everywhere. Adding, changing, archiving or

restoring a programme now shows a proper toast instead of leaving you guessing whether it worked.

• Programmes can now be archived. Nothing is ever deleted — archive a

programme you’ve stopped running and it tucks itself out of the way; restore it any time and everything’s exactly as you left it.

Adding a sport mid-year — billing sorts itself out

• Add an extra sport any time and the billing works itself out. If

you’re paying annually, you’ll be offered a one-off top-up covering the rest of your year at the same discounted annual rate, or a simple £20 a month if you’d rather keep it separate. If you’re paying monthly, the extra £20 just appears on next month’s bill — nothing to set up.

Settings — tidier, clearer, honest about add-ons

• Settings is now organised into a handful of clear groups, with

communications settings living in the Comms Centre where they belong.

• Module switches and purchases are now separate. The Modules page is a

clean set of on/off switches that tells you honestly when something is switched on but not part of your plan; anything to do with buying lives on the Billing page. No more prices shown for things that can’t be bought.

• Dozens of small fixes: clearer error messages, safer buttons that can’t

double-submit, mobile-friendly forms, and “4th student” finally spelt correctly in family pricing.

Register

• The “Add ad-hoc” button now works the same on desktop as on your phone:

a compact button that expands into the search when you need it, and tucks itself away when you don’t — clearer than a permanently-open search box. (The event register’s “Add walk-in” matches.)

Memberships — include courses in a plan

• A membership plan can now include courses. Tick “Courses included” on

a plan, pick the courses, and everyone on that plan automatically gets them in their Member Portal — granted when they join, removed when the membership ends. A clear note on the plan form explains exactly how it works, and it’s entirely separate from one-off course purchases.

• Leavers no longer keep portal extras. Anything gated by an access grant

— courses, video review, pathways — is available while a member is active or paused, and switches off if they leave. Purchase pages now say this plainly before anyone pays.

Staff Leave on the register

• The register now knows who’s off. If a coach or helper has approved

leave covering a class, the register shows a simple “On leave” note and won’t let them be added to that session (half-days respected — a morning off doesn’t block an evening class). Pending requests show for awareness but don’t block, and someone already on the register can still be taken off. What KIND of leave it is stays private to the leave pages.

Certificates — bigger text, clearer saves

• Certificate text can now be any size — with a slider. Drag the new

size slider (6–300px) or type any number straight in, even beyond 300. Typing big sizes works properly now too (entering “250” no longer snaps to the minimum as you type).

• Saving a certificate template now confirms with a toast — success or

failure, uploads included — instead of a message tucked at the top of the page.

Dashboard — a cleaner, more useful home screen

• Your numbers come first. Active members, attendance, revenue, overdue

and this week’s pulse now sit in a row right under your club name — the glance you open the dashboard for, before any scrolling.

• The setup checklist gets out of the way. Once you’re half set up it

folds into a slim “Finish setup” pill with a progress ring, tapping to expand — so “Needs you” and “Today” are no longer pushed below the fold.

• A two-column layout on desktop. What needs your attention (Needs you and

the health charts) sits on the left; your day (Today, Class Pulse, activity) on the right — less endless scrolling, clearer priorities.

• Better charts. Attendance is now the hero chart, joins-vs-leavers and

revenue share the row beneath it, and revenue is drawn as a trend line so money reads differently from head-counts.

Polish across the app

• The member profile’s status stands out. The Active/Paused/Leaver pill

now sits snugly above the grade colour with a soft matching glow, and the colour square is slightly smaller so the whole header sits level.

• Dozens of confirmation prompts that used the browser’s plain pop-up now

use proper in-app dialogs (promoting from a waitlist, archiving plans and fees, cancelling events, and more), and renewing a requirement now names the member in the confirmation.

• On the public booking page, if something needs completing before you can

book, the page now scrolls straight to it.

• Event form date mistakes are flagged on the fields themselves; settings

pages share one heading style; back links look and behave the same everywhere; and lots of icon-only buttons gained proper screen-reader labels.

New clubs start ready to go

• Signing up now sets everything up properly. A brand-new club gets its

trial plan the moment it registers, so features like progression and grading are switched on from the first login instead of showing “Not active” everywhere. Nothing is charged — the trial is just recorded correctly.

• Setting up your grading also creates your first programme. When a new

club creates its belt or level system, a matching programme appears automatically — no more finishing setup with an empty Programs list.

• Every module’s setup wizard is now reachable. Apparatus assessment,

fixtures, timed events and disciplines each have their own “Set up” link (previously only progression had one), each starting with the right questions for that sport.

Under the bonnet

• Every change to a programme — archiving, restoring, or changing its sport —

is now recorded in the audit trail with who did it and what changed.

• Members-portal access to pathways is now double-locked behind its access

grant, matching courses and video review.

11 July 2026

Member profile: frosted-glass tabs and a flingable Actions button

• The desktop tab bar is now translucent frosted glass, edge to edge —

it sits flush at the top with the member's status colour flowing behind it, and the bar is slimmer now that Actions has moved out of the row. The selected tab lights up in the app's vibrant teal with a soft glow (the same treatment as the register), picking one has the register's satisfying fill and pop, and when the window gets narrow — or you zoom the browser — the items that don't fit tuck into a tidy three-dots menu instead of clipping or scrolling. The bar double-checks itself as the page loads (and whenever fonts or zoom settle), so a tab can never sit half-cut at the edge. SMS is now the first button on the bar itself — always visible, always in the same place — and the three-dots menu only appears when the window is too narrow to fit every tab, holding just the tabs that folded away.

• Actions is now a floating button you can drag. Fling it to any corner —

it tracks the speed of your throw and lands where the fling was headed, not just where you let go. Park it on the left or right edge and it tucks into a small round menu button. It grips as it nears a resting spot, and it remembers where you left it.

• Every tab keeps the essentials in view: name, grade, age and contact

stay pinned whatever tab you're on, while the status chips and family card now belong to the Profile tab — so Billing, Attendance and the rest start clean.

• Nothing changes on your phone.

10 July 2026

A dashboard that earns its place

The home dashboard has been rebuilt around the three questions you actually open it to answer.

• "What needs me?" — one prioritised list at the top, and every line now

takes you somewhere real: overdue payments (with the amount) open the arrears page, missing-in-action members open the filtered inbox, trials to chase open the calendar's trials view, accident drafts open the draft list. The old "data checks" counts that dumped you on an unfiltered directory now expand in place to show the actual member names, each one a link. When there's nothing to do, it says so and gets out of the way.

• "What's happening?" — a new Today panel: tonight's classes with one-tap

register links, this week's events with a booking fill bar, today's trials, and a closure notice when the club is shut.

• "Are we healthy?" — real charts at last: attendance over the last 12

weeks, joiners vs leavers, a 12-month revenue trend (owners and admins only), and a programme-mix donut with the counts alongside. The number tiles now share one style, each with an up/down arrow against last week — and the two tiles that showed the same number are one tile.

• Coaches get a coach's dashboard: schedule first, no money tiles. On a

phone everything stacks in priority order — needs-you, today, then health.

• Recent activity knows when to stop. On a phone it shows the latest 10

with a "Show older" tap for the rest; on desktop it lives in a fixed-height panel that scrolls within itself, with a fade hinting when more sits below — either way, the page no longer trails off into an endless scroll.

Telegram: the whole family can now connect

Until now each member could be linked to exactly one Telegram account — if dad connected after mum, mum silently stopped receiving updates. That's gone.

• **Two parents (or a parent and an older member) can each link their own

Telegram** to the same member. A second connection adds, never replaces.

• One parent's Telegram covers all their children. Linking a second child

to the same phone used to fail silently — the app said "Welcome!" and linked nothing. Now it just works.

• Messages go to every connected chat, and a reply from either parent

lands on each linked child's timeline, exactly as replies always have.

• The member profile shows who's connected — "2 linked: @mum, @dad" — with

the option to unlink one chat or all of them.

• Also fixed: the "don't ask me again" link in Telegram invite emails

never actually worked — every click showed "Something went wrong". It now opts you out properly.

Clearer invoice actions: "Mark unpaid"

On a paid invoice, the action that reverses a manually-recorded payment is now called "Mark unpaid" (previously "Undo", which sat confusingly next to Refund). It does exactly what it says: the invoice returns to unpaid and no money moves. Refund is unchanged and still the button that returns money.

Grading: published really means locked — everywhere

• Examiner scoring links go read-only once results are published. Marks,

notes and score-clears are all refused by the server, and the examiner's screen shows a clear banner explaining why. If only part of a multi-event grading is published, only those candidates lock. Unpublishing re-opens scoring.

• Standalone grading events can be archived, just like grading sessions —

one "Show archived" toggle covers both, and Restore is one click. Archiving only tidies the grading workspace: the event stays on the calendar (cancel it there if it genuinely isn't happening), and nothing is deleted. Published events must be unpublished first — enforced by the server, not just the button.

• Unpublishing is confirmed safe, and now guaranteed by tests: it never

reverses anyone's grade or progression. It simply re-opens the grading so you can fix a missed double promotion or add notes, then publish again — certificate numbers are preserved throughout.

Accident report drafts: one draft, however many reloads

Saving a draft, reloading the page, and saving again used to quietly create a second copy of the report. The form now remembers which draft it's working on across reloads and keeps updating the same one. If the draft was completed or removed from another device in the meantime, the form says so plainly and offers a one-click way to start fresh.

Scheduled changes: failures can't hide any more

If any member's scheduled status change fails to apply, the daily job is now recorded as a failed run in platform health and raises an alert — previously it could show green while changes silently failed. The run summary still shows exactly how many applied and what went wrong.

Portal invites always arrive

Confirmed and locked in by tests: portal login invites are account emails, not marketing — so a family that opted out of promotional email still receives them.

Schedule a plan change for a future date

Record a membership plan switch today — "move the Smiths to Unlimited from 1 September" — and the system applies it on the right day, for every billing type.

• Nothing is charged when you schedule it. The first bill on or after the

chosen date is the first at the new price; the confirmation tells you the exact date that will be.

• A pending change is visible and cancellable. The household's billing

panel shows a chip ("→ Unlimited from 1 Sep") with a Cancel change button — usable any time before it applies. The member profile shows the pending change too.

• Term plans join in: instalments already invoiced keep their price;

instalments from the chosen date bill at the new plan's rate (the form cautions you when a date lands mid-term). Per-class members switch rate on the date for future class-pack purchases — credits already bought keep full value.

• Agreed price adjustments don't silently carry over. A discount

negotiated against the old plan is removed when the change applies — the confirmation says so up front, and you can re-add it on the new plan if it still applies.

• Family discounts recalculate automatically on the new plan, and "Upgrade

now" (with its pro-rata charge) is unchanged for when the switch shouldn't wait.

Telegram: bulk messages and automations reach the whole family

Yesterday's change let two parents link to the same member; today bulk composer sends and automation messages (reminders, follow-ups) go to every linked chat too — previously they only reached whoever linked first.

One "Comms" entry in the sidebar

Communications, Comms Map and Automations were three separate sidebar entries that are really one area. They're now a single Comms entry landing on Messages, with the familiar pills across the top taking you everywhere else — Comms Map is promoted to second, right after the composer. Coaches no longer see an Automations pill that would refuse them; nothing moved for bookmarks or saved links.

Member profile: one status row and a summary that stays put

• The three stacked strips above a member's tabs (needs-attention, four status

cards, badges) are now one row of colour-coded chips — a problem and its tile are the same thing, and everything the old strips showed is still there, including who's connected on Telegram.

• Medical information now only surfaces for coaches and above, matching

the server's own rules — a read-only account sees whether an emergency contact exists, but not medical details.

• On a wide screen the profile is one full-width view: name, contact and

status across the top, the status chips using the whole width, and the section tabs pinned in a bar at the top that stays put while you scroll — always one click from Billing or Attendance. The tabs use the same icon + label styling as the phone's bottom bar, with a thin sliding underline marking where you are. On a phone, nothing moves.

Insurance display: your choice, per club

Not every sport tracks member insurance. Settings → Modules now has an Insurance toggle — on by default (nothing changes unless you switch it off), per club or per programme. Turning it off hides the Insurance chip from member profiles; your insurance data, edits and reports are untouched and the chip returns the moment you re-enable it.

Comms pills now on the phone's landing view

Opening Comms on a phone lands on the recipient picker — and the section pills (Comms Map, Automations, Templates, Deliverability) lived only on the compose step, so on mobile there was no way to reach the rest of the area. The pills now sit at the top of the landing view too, in the same swipeable row.

Medical notes: double-locked on screen

The Emergency & Medical popup now checks permissions itself before showing medical notes — a second lock behind the button that already did. Staff with medical access see no difference; everyone else can't see medical notes even if a future screen accidentally offered the popup.

More background jobs that can't fail silently

The same honesty applied yesterday to scheduled status changes now covers five more daily jobs — annual requirements, audit housekeeping, the billing run, tomorrow's lesson plans, and the comms-flow dispatcher. A failed run shows red in platform health and alerts the team, while routine notices (like a monthly housekeeping reminder) don't cry wolf. The "Mark unpaid" confirmation dialog also now says "Mark unpaid" throughout, instead of mixing in "Reverse payment" wording.

9 July 2026

Search finds people the way you actually have them

Paste a number straight out of WhatsApp — "+44 7392 945872" — and the member whose mobile is stored as "07392 945872" comes straight up. Those are the same number, and every search box now knows it.

• Quick search (⌘K), the students screen and the message recipient picker all

now match by email and phone as well as name — one shared matcher, one set of rules everywhere.

• Any spelling of a phone number works: +44 or 07, spaces or not, or just the

last six digits.

• A parent or guardian's name finds the child on the students screen — often

the only name a message gives you.

• Surname first works: "Okafor Sam" finds Sam Okafor, as does "sam ok".

Date pickers that fit on a phone

Three forms — the task reminder, the grading event's date, and the accident form — could push their whole window sideways on a phone, because a native date box refuses to shrink below its built-in width. They now share one date-and-time field that stays inside its column, uses your phone's own calendar and clock wheels, and stacks neatly on small screens.

The students screen says what it will do

• "Individual view" replaces "Flat view" — it pairs with "Group by family" and

matches the "Individuals (no household)" heading you already see.

• Export is honest about scope: the button reads "Export selected (3)" when

you've ticked people, "Export all (142)" when you haven't — and does exactly what it says.

• "Invite to Telegram" respects your selection. Tick five members and only

those five are invited; the confirmation names the count before anything sends. With nothing selected it still offers everyone — and says so.

• New: chase the portal invites that never landed. One action finds everyone

who was given portal access but has never actually logged in, shows you the exact list, and re-sends their login link. If mum uses the portal and dad never has, dad still gets his.

Member profile, tidied for the phone

• Actions now lives top-right, in line with the back link, instead of a row of

buttons pushing the record down the page.

• The status pill sits under the belt colour on mobile, so name and email keep

the full width. Desktop is unchanged.

• The household panel uses its whole width: family members flow in a grid and

the classes list gets room, rather than everything squeezing into one narrow column with the right half empty.

• The bottom tab bar stays pinned to the bottom of the screen while the page

animates in — it could briefly ride up with the content before.

Promotions: two small things that weren't small

• Collapsing a grade group now sticks. Closing a section used to snap it

straight back open.

• Opening a member from promotions now offers "Back to promotions" instead of

dropping you in the directory.

Fixed: invoice PDFs wouldn't open

Every invoice PDF was failing with "We couldn't load this invoice right now" — the document asked the database for address fields that don't exist, so the whole fetch failed. Fixed; the "Bill to" block now prints the household's address correctly.

Grading events: published means finished

• A published grading is visibly locked. The event card shows a locked marker,

"Live scores" becomes "View scoring", and on the grading day screen the Pass/Unsuccessful/Undo buttons are replaced by a padlock with a note explaining why. The server refuses late edits too — including panel notes, which could previously still be edited after publishing.

• Unpublish was checked end to end, since it's the scary one: certificates are

removed, their numbers are kept for the audit trail, and only an admin with a password confirmation can do it.

• Archive old gradings. An unpublished grading you never ran can now be

archived — it's hidden from the working list (with a "Show archived" toggle), and any calendar events linked to it are unlinked automatically. Published gradings can't be archived; restore is one click.

• New: a post-event analysis PDF. Once results are published, download a

summary with attendance and outcome figures, the words your examiners used most in their feedback, and where red and amber scores concentrated — so the next course focuses on what the last grading showed. Candidate names are kept out of the word analysis by design.

• The Sessions/Events and Upcoming/Past selectors now share one row on mobile,

and the new-event date no longer overflows the modal.

Trials & Enrolments

• Opens on "Upcoming" rather than everything ever.
• One Actions button replaces the row of three (Embed, Book Trial, Send

Invite) — same actions, less furniture.

Video review

• The Pending/Reviewed switch is now the same animated selector used across the

app, and the counts no longer make the buttons change width as they load.

• Wording now says member, not parent/student, matching the portal rename.

Accident reports

• The list opens on the last 7 days — with 30, 90 and custom ranges one tap

away — instead of loading every report ever recorded.

• On a phone, reports are cards with a clear View action; no more dragging a

wide table sideways.

• Save as draft. Part-way through recording an incident, save it and finish

later — drafts are labelled, filterable (Complete / Draft), and don't produce a PDF until they're completed. The form itself no longer scrolls sideways on mobile.

Communications & automations

• Template filters (All / Manual / Automation) use the house animated selector.
• The automations Build list works on a phone — cards instead of a 760px-wide

table that dragged the page sideways.

• The SMS gateway page no longer scrolls sideways — the 90-day volume chart

scrolls inside its own box.

• Scheduled changes speaks English: "checked automatically every morning"

rather than CRON jargon, and "Overdue (not yet applied)" instead of just "Overdue".

• The arrears page gained the same breathing space every other billing page has.

Housekeeping

• The changelog is hidden on the demo account. What's new is for customers,

not a public feed of everything we're building.

8 July 2026

Events can now run past midnight — and across several days

A late-finishing event used to be stored as if it ended earlier the same morning, which quietly hid it from the next day's calendar. Events now record when they truly finish.

• A late event keeps running into the next day. Create a 10pm event that runs

four hours and it now finishes at 2am *tomorrow* — the calendar shows it on both days, and the form tells you so: *"Runs 10pm–2am, ending 01/02/2026 (next day)."* Previously the finish date stayed on the start day, so the event vanished from the next morning's view even while it was still happening.

• Multi-day events ask for what they actually need. Turn on Multi-day and

the form swaps the length chips for a proper end date *and* end time. A duration can't describe a 50-hour residential camp, and the chips were misleading: with multi-day on they were setting the finishing clock time on the last day, not the event's length. Now the control matches the question.

• An impossible time is caught in the right way. With multi-day on, an end

that's before the start on the same day is a typo, and the form says so. With it off, the same pair means "it runs past midnight" — so it's accepted and the finish date moves on a day. Same clocks, two different mistakes, two different messages.

• Every repeat of a recurring event carries the right span. A recurring

10pm–2am class used to store each occurrence as finishing on the day it started, so only the first evening ever showed correctly. Each repeat now spans the same number of days as the first.

• Rescheduling honours it too. Moving an event to a late slot now updates its

finish date, and the server independently re-checks the finishing *instant* — a check that only looked at the clocks would have read a legitimate 1 Feb 10pm → 3 Feb 9am camp as running backwards.

Existing events are untouched: a stored event whose end time is earlier than its start time is still read the way it was always meant — as finishing the next morning.

Classes can run past midnight too

Some clubs run a late session. You can now save one — a class from 11pm to 12:30am, on the timetable, in onboarding, or as an ad-hoc lesson on the register.

• The register knows a late class is live. "Present" lights up at 11:30pm, and

stays lit at 12:15am while you're still on that class's register. Marking someone present at 12:30am records it against the night the class *started*, which is where it belongs.

• The club-wide attendance count includes it. Just after midnight it still

counts the people in a class that began last night.

• A late class shows properly everywhere it's drawn. On the calendar's day view

it's a real block rather than a sliver, and it no longer overlaps the class before it. On the printed timetable it sits inside the grid instead of over the footer, and it keeps its own lane. The trial-booking page shows its length again.

• A parent's calendar subscription gets it right. The iCal feed was putting the

finish time *before* the start for any late class, so phones dropped the entry. Fixed — along with the same fault for any class with no finish time recorded.

• Editing a late class no longer resets its length. Opening one for an unrelated

change (renaming it, say) used to quietly reset its length to 60 minutes, and saving made that permanent.

A class that finishes *earlier the same day* than it starts is still what it always was — and now it just means "it runs past midnight", the same reading events use.

No club owns a mat

"On the mat" only makes sense if you teach on one. Allsorted is used by swimming, football, dance and rugby clubs, so the phrase has gone — replaced by wording that says what the number actually is.

Three different things were sharing the phrase, so each got its own word:

• The register's live count is now "Present" (and "Attended" once the class has

finished), matching the marks you actually make — Present, Late, Absent.

• The club-wide sidebar count is now "Current attendance", with the same

per-venue breakdown underneath.

• The Assessments filter is now "Present today", which is exactly what it does:

show only members marked Present or Late on today's register, whatever class.

• In grading, a line is now "Scoring" rather than "on the mat", and the lead's

button reads Score rather than On mat. Being scored and being present are different things, so they no longer share a word.

Behind the scenes the example wording offered when you write a waitlist-promotion email lost its "See you on the mat!" sign-off too, and the printed features guide no longer assumes you coach on one. No email anyone has already written has changed.

The accident form still asks whether an incident happened "on the mats or playing surface" — there it means a real floor, and it already covers both.

Trials: read what the family actually told you

When someone books a trial they answer up to four questions. Until now only the register showed them — the person triaging trials in the calendar never saw that a parent had asked something, or declared an injury.

• Every trial row has an "Answers" button. It opens a popup with how they heard

about you, why they want to try, and anything they wanted to ask before coming. It's there for cancelled and past trials too — those are often the ones you want to read back.

• The medical answer is on the same popup, and it's protected. Coaches, admins

and owners see it. A read-only account sees the panel but not the answer. The wording is identical whether or not the family declared anything, so a locked panel gives nothing away.

• If the answer can't be loaded, it says so. It will never quietly show an empty

medical box that reads like "nothing declared" when the truth is "we couldn't ask".

Also fixed — a real safeguarding gap

The register's Health quick-view was fetching every rostered child's medical information without checking who was asking. Any staff account in the club could read it, including read-only accounts. It now needs the same permission as the trials popup: coach and above. Coaches keep it, because they need it mid-class. If you have read-only staff who relied on this, they'll now see nothing there.

Households: the search now tells you why a family matched

Searching a member's name already found their family — it just never said *which* member you'd hit. On a family of five you scanned. In compact view, which draws no member names at all, you couldn't scan.

• Every result now shows what matched, highlighted, right on the card — in both

compact and expanded view. Search "Sam", and the Okafor family's card says *"Sam Okafor · member"*.

• Search by email or phone number too. Paste a parent's email from an enquiry, or

type the last six digits of a mobile, and you'll land on the family. A number stored as "+44 7123 456789" is found by typing "07123" — those are the same number, and the search now knows it.

• Surname first works. "Okafor Sam" finds Sam Okafor, as does "sam ok".
• The guardian's name is searchable — often the only name you were given.
• An ex-member still finds the family, and says so. The child you remember is

frequently the one who left, so a leaver match is shown with their name struck through and a LEAVER tag, and the family's own status pill tells you the rest.

The matched field is always named — "email", "mobile", "guardian" — so a hit on a phone number never looks like a mystery.

Behind the scenes — the safeguarding-lead permission now works

Four permissions are meant to open only to admins, owners, and a coach who is the club's designated safeguarding lead (full medical detail, accident detail, safeguarding notes, DBS credentials). The "safeguarding lead" half was never wired up: the check always assumed *not* a lead, so the modifier could only ever *restrict* — a lead coach would have been refused the very records the role exists to see.

That path is now plumbed end to end and covered by tests. No visible change yet: nothing in the app grants these four to a coach today, and turning it on for a real club still needs a small database change to be applied first. This is the groundwork so that, when it is, a safeguarding lead is let through rather than locked out.

7 July 2026

Mobile: read your sent emails without fighting the layout

A round of mobile fixes so the Communications and student screens work properly on a phone — no more sideways scrolling to reach things that were off-screen.

• Sent and scheduled email history now reads as cards on a phone. In

Communications → History, the Sent and Scheduled lists used to be wide tables that ran off the side of the screen on mobile — so the "View" link and the status/actions were out of reach. They now stack into tap-friendly cards on a phone (and stay as full tables on a larger screen), so you can open any historic email straight away.

• Sent emails open properly from a student's timeline. Opening a sent email

from a student's activity timeline on a phone would clip the message so you couldn't read it. The preview now sizes itself to the email and scrolls, so the whole message is readable on any screen.

• Automations filters sit still. The filter and category controls at the top

of the Automations screens no longer jump around as you type or toggle them on a phone — they line up in a single, tidy row you can swipe across.

• A student's sections are now a bottom bar on your phone. Instead of a

horizontal-scrolling strip of tab labels, a student's record shows a fixed bottom bar with the four you reach for most — Profile, Billing, Attendance, Timeline — and a "More" button for Achievements, Credentials, Pathways and the SMS conversation. It works like the member portal's bottom bar. On a larger screen the familiar top tabs are unchanged.

• Register: an "Add ad-hoc" button instead of a second search box. On a

phone the register no longer shows two search boxes stacked up. The ad-hoc / catch-up search is now a compact + Add ad-hoc button; tap it and it slides open into the search field (tap again to close). It resets to a button each time you open the register, so the screen stays tidy. On a larger screen the full search box shows as before. An event register's walk-in search works the same way.

Register polish

• Class times read as 6–7pm. The class and event pickers now show times the

way you'd say them — "6–7pm" rather than "18:00–19:00" — which frees up room for the class name on a phone.

• More of the class name fits. The class rows are tighter, the fixed time

column is gone, and the decorative "›" arrow at the end of each row has been removed (the whole row was always tappable). Venue and the signed-up count still show whenever there's room.

• The rank colour on the register is now the same swatch used elsewhere.

Marking members present/absent/late shows the wide horizontal progression swatch — the same chip the grading screens use — instead of a thin vertical bar. (It's a belt in martial arts, a level, stage or grade elsewhere.)

Class times: one control everywhere, and four bugs fixed

Every screen that asks when a session runs — the register's ad-hoc lesson, the calendar's event form and reschedule, both timetable pages, the onboarding timetable, coach availability and quiet hours — now uses the same control.

• A class can no longer end before it starts. Four of those screens would

happily save a class running "7pm to 6pm". A class like that never counts as live, so the register never showed it in session. Where a length makes sense, you now set a start and a length and the finish is worked out for you — so an impossible time simply can't be entered. The others check as you type. Every one is checked again on the server.

• Say when it starts and how long it runs. Timetable classes, events and

reschedules take a start plus a length (30/45/60/90 minutes, or your own), and show you the result: *"Runs 6:30–7:30pm."*

• Quiet hours can still cross midnight (10pm–8am), and a coach's

availability window still takes an explicit finish — those genuinely need one.

Adding an ad-hoc lesson is quicker to fill in

The + button on the register opens a friendlier form for a one-off lesson.

• Say when it starts and how long it runs, rather than filling in two

separate time boxes. The start is prefilled to the current time (rounded to five minutes), the length is a tap — 30, 45, 60 or 90 minutes, or a custom number — and the form tells you when it'll finish: *"Runs 6:30–7:30pm."*

• You can't create a lesson that ends before it starts. Previously nothing

stopped you saving one, and the register would then never think the class was live. A lesson that would run past midnight is refused too, with an explanation — a register covers a single day.

• A lesson always has a real time now. Leaving the times blank used to store

it as midnight-to-midnight behind the scenes, which showed up as "12am–11:59pm" on the class list. The form now always sets a proper time.

• A member with no rank set no longer shows as a dark blob in light mode.

Several screens — the student record, the timeline, promotions, grading lists, the assess rail and the rank settings — were drawing an un-ranked member with a hardcoded dark navy instead of following your theme. They now all use the same swatch, which picks up light or dark mode properly.

• Ranks with three or more colours now show every colour. A rank can carry up

to six colours, but most screens only ever drew the first two — the third onward were silently dropped. Multi-colour ranks now render as equal horizontal bands everywhere on screen, matching how they already printed on grading sheets. Single and two-colour ranks look exactly as before.

• "Select a class or event to begin" has breathing room. The panel no longer

runs edge-to-edge on a phone.

• The Lesson Plan button looks selected when it is. Opening the lesson plan

now fills the button in, so it's obvious at a glance which state you're in.

6 July 2026

Courses builder: reorder by dragging, and a live Preview

The staff Courses area has had a round of polish so building a course feels quick and predictable.

• Drag to reorder. You can now drag sections into the order you want, and

drag lessons within a section — grab the grip handle on the left and drop it where it should go. Previously new sections and lessons could only ever sit in the order they were added.

• Preview what members see. A Preview button on the course builder opens

the member's view of the course in a new tab, so you can check how it reads before you publish.

• Tidier course list. The Courses list now uses the same edit-pencil and

"…" menu as the rest of the app — Edit opens the builder, and the menu holds Publish / Unpublish and Archive / Restore — with a clear status badge (Draft · Published · Archived) on every course.

• Clearer confirmations. Removing a section or a lesson now asks first with a

proper confirmation dialog (and keeps member progress history), instead of removing on a single click.

Courses for members: work through lessons in order

Members now move through a course step by step, so nobody skips ahead.

• Lessons unlock in order. A lesson opens only once the earlier required

lessons are finished — and a required quiz has to be passed before the next lesson unlocks. Optional lessons never hold anyone up. Upcoming lessons show a small lock until they're reachable.

• Always know what's next. After you mark a lesson complete or pass a quiz,

a Continue to next lesson button takes you straight to the next one — or tells you the course is complete when there's nothing left.

• Pick up where you left off. The Continue button on a course jumps to

the right place: the lesson you were last on, or the first one you haven't finished.

• Clear quiz results. After submitting a quiz you see your score and whether

you passed the pass mark, with the option to try again if you have attempts left. Correct answers are never shown.

• A clearer course screen. Lessons now sit in an outline down the side (a

tap-through list on a phone) with type icons, a progress bar and ticks against what you've finished, so it's always clear where you are and what's left.

Courses: choose who each course is for

Courses now have the same audience control as Pathways.

• "Who can see this?" Each course has an audience setting — **All

programmes, or Specific programmes** with a tick-list of your programmes. Clubs with a single programme stay on "all" automatically, and the Courses list shows each course's audience at a glance (flagging any set to specific programmes with none chosen).

• Members only see courses for their programme. A member sees a course they've

been given only when it's offered to everyone or to a programme they're currently in — nothing that doesn't apply to them.

• Publish check. A course set to specific programmes can't be published until

at least one programme is chosen, so it can never go live invisible to everyone.

Courses: see how members are getting on

The staff course view now shows real progress, not just who's enrolled.

• Progress at a glance. For each enrolled member you can see how far through

they are, when they were last active, how long they've spent, and — for a course with a quiz — their latest score, whether they passed and how many attempts they've had.

• Activity is tracked automatically. Opening a lesson marks it started, and

time spent on a lesson is recorded as members work (capped sensibly so the figures stay honest) to feed the progress above.

Pathways: a clearer, Courses-style builder and member view

Training Pathways now works like Courses — a list of stages on the left, the detail on the right.

• Two-pane layout. Building a pathway (and following one in the member

portal) now shows the stages down the left and the selected stage's tasks and content on the right, with the current step highlighted and finished steps ticked. On a phone the outline collapses into a simple stage picker.

• Drag to reorder. Stages and tasks can be dragged into order (with up/down

buttons as a fallback) — previously they only sat in the order they were added.

• Clearer progress. A progress bar and per-step badges show exactly where a

member is up to; staff sign-off still works the same way.

Pathways: choose who each pathway is for

You can now target a pathway at specific programmes, the same way Courses work.

• "Who can see this?" Each pathway has an audience setting — **All

programmes, or Specific programmes** with a tick-list of your programmes. Clubs with a single programme stay on "all" automatically. The pathways list shows each pathway's audience at a glance (and flags any set to specific programmes with none chosen).

• Members only see pathways for their programme. In the member portal, a

member sees a pathway only when it's offered to everyone or to a programme they're currently in — so nothing shows up that doesn't apply to them.

• Publish check. A pathway set to specific programmes can't be published

until at least one programme is chosen, so it can never go live invisible to everyone.

Pathways: a task that completes when a course is done

A pathway task can now be "Complete a course."

• Pick a course. When building a task, choose *Complete a course* and select

one of your published courses. The member sees the course name and a link straight to it.

• Completes itself. The task ticks off automatically once the member finishes

the linked course — they can't mark it done themselves, and there's nothing extra for a coach to sign.

Sell a course as a one-off purchase

Courses can now be sold, not just assigned.

• Choose how a course is obtained. Each course has an access setting — free

(open to whoever the audience allows), staff-assigned (grant or comp it yourself, as before), or purchase (members buy it themselves). A purchasable course carries a price, and you can attach a certificate template to it.

• Members buy and unlock instantly. When a member opens a paid course they

haven't got yet, they see the price and a Buy button. Payment goes straight to your club's connected Stripe account (no platform cut), and access unlocks the moment the payment is confirmed — never before. A refund made in Stripe removes the purchased access automatically (any access you granted separately stays put).

• No double-charging. A member who already has a course — bought, assigned or

comped — is never asked to pay for it again.

Courses: target a course by level or stage

Alongside programme/lens targeting, a course can now be aimed at specific levels or stages too.

• Level/stage audience. In a course's audience settings you can limit it to

chosen levels/stages (belts, grades — whatever your club uses), on top of the programme rule. A member sees or buys the course only when they match both the programme rule and the level rule — so, e.g., an "advanced" course can be aimed at your senior grades only.

• Enforced everywhere. The rule is applied on the server, so a member who

doesn't match simply never sees the course (and can't reach it by link).

Courses: upload videos and files

Course lessons now take real uploads instead of pasted links.

• Upload a video or file. A video or file lesson has an upload control with

progress, the file name, and replace/remove — no more copy-pasting a URL.

• Kept private. Uploaded course media lives in private storage and is only

served to a member through a short-lived link once they have access to the course — never a public URL.

Courses: award a completion certificate

A course can now hand out a certificate when a member finishes it.

• Attach a template. Pick one of your existing certificate templates (the

same ones under Settings → Certificates) on the course. When a member completes the course, their certificate is generated automatically and they can download it from the course page.

• Reuses your designs. It uses the same certificate designer and merge tags

(name, course, completion date, club, certificate number) as grading certificates — nothing new to learn.

Courses: a dashboard and better filtering

The staff Courses page is now a proper dashboard, not just a list.

• At-a-glance tiles. Totals for published / draft / archived, enrolled

learners, average completion, and a "needs attention" count (courses with no audience, no lessons, or a draft that already has learners) — each tile is a one-click filter.

• Filter and search. Filter by status, programme/lens (defaulting to your

current lens, with an "All programmes" escape), audience, and access type (free / staff-assigned / purchase), or search by title.

• Richer rows. Each course shows its status, audience, price/access model,

learner count, completion % and last-updated, with the same "…" actions menu as the rest of the app. (Revoking a member's access now asks for confirmation first — it used to remove on a single click.)

Team Sports now opens when it's set up

Fixed a bug where the Team Sports page said the module "isn't available" even though it was switched on for a programme and included on the plan. It now opens whenever it's set up for at least one programme — the same fix also covers Competitions, Timed Events and the other programme-level features.

Courses: hardening pass ahead of wider testing

A round of smaller fixes and polish on top of everything above, found while preparing Courses for a wider test — nothing here changes how the features work, just makes them more reliable.

• A course can't go live with nobody able to see it. Publishing now checks

that the course's audience actually resolves to someone — a course restricted to "specific programmes" with none chosen, for example, can no longer be published invisible to everyone.

• Staff can now see which of their own paid courses are still up for grabs.

The library shows a purchasable course's price and access type clearly, so it's obvious at a glance which courses are free, staff-assigned, or for sale — and how much they cost.

• A failed certificate is never a mystery. If a completion certificate

can't be generated (for example, a template with no design attached yet), the member's completion still goes through — staff now see a clear "failed" status with a reason, and can retry generating it once the template is fixed, rather than a certificate that quietly never appears.

• Fixed uploaded course videos not playing for some members. A video

lesson using an uploaded file (rather than a pasted link) now plays correctly every time.

• The dashboard's price and level filters now actually work. The Courses

dashboard's paid/free filter and level-or-stage filter were previously wired to fields the page didn't have — both now filter correctly.

Courses: monthly course packages, billed on your existing Direct Debit

Alongside buying a single course outright, members can now subscribe to a course package — a bundle of courses for one monthly price, collected on the same Direct Debit you already pay your fees on. No new payment method to set up, no card details to re-enter.

• Subscribe from the Courses page. A package shows its name, the courses

it includes, and its monthly price. If your household has Direct Debit set up, you can subscribe with one tap — if not, you're told clearly ("This package is billed by monthly Direct Debit — set up Direct Debit or buy courses individually") rather than being offered a payment method that won't work.

• Access starts once the first payment is confirmed. Subscribing adds the

package to your next Direct Debit collection; your course access unlocks the moment that first payment is confirmed — never before, and never on a promise.

• Cancel any time, no early cut-off. Cancelling stops future monthly

charges straight away, but you keep access to every included course until the period you've already paid for ends — nothing is removed early.

• Buying individually is always available too. A course package never

gets in the way of buying a course as a one-off — and if a course is already included in your active package, the one-off purchase screen tells you so instead of asking you to pay again.

• For staff: course packages are a separate, optional product from

programme membership — you define which courses go in a package and its monthly price, and members' subscriptions ride your existing GoCardless Direct Debit collection (this is deliberately not a new Stripe subscription product).

5 July 2026

The Parent Portal is now the Member Portal

The Parent Portal is now the Member Portal — same features, a name that fits every member, not just parents. Nothing changes about how it works or who can sign in; adult members and parents alike get the same portal, now with a name that suits everyone.

The marketing site now lists the newer modules

Our public site was still describing only the original six areas. It now also reflects the modules added since — Courses & Learning, Training Pathways, Team Sports & Fixtures, Pro Shop, Referrals, Automations, Email Deliverability, Video Review, Permissions & Roles, the any-sport terminology system, and Event Booking & Requirements — so what people see before they sign up matches what they get.

Older message content is tidied after 2 years

To keep things lean and privacy-friendly, the actual content of older messages — the body of emails, texts and Telegram messages — is now automatically cleared after 2 years. Your delivery history is kept: you'll still see who a message went to, when, on what channel, its subject, and whether it delivered, bounced or was opened. When you open a message whose content has been cleared, it now says clearly *"Message content removed per retention policy (delivery record retained)"* rather than showing a blank. Nothing changes for recent messages, and the 2-year window can be adjusted later.

Roles & Permissions — a place to fine-tune who can do what

Settings gains a new Roles & Permissions section under People & Access. Start with ready-made responsibility presets — Billing Manager, Refund Manager, Event Manager, Safeguarding Lead and more — and assign them to a staff member in one click, with an optional expiry date. For finer control you can adjust what each base role (Owner, Admin, Coach, Read-only) can do, grouped tidily by area so you're never scrolling a wall of switches. High-risk or safeguarding changes ask for a short reason, which is recorded in the audit log, and settings the platform protects show a clear lock.

Every staff member now has a Permissions action and, for support, a View effective permissions panel that lists exactly what they can and can't do right now — and *why* (their role, a preset, an individual grant, a switched- off module, an expired grant, and so on). Their assigned presets also show as chips right on the staff list. Where this isn't yet switched on for your platform, a banner makes clear that any setup you do here is prepared and simply waits until it's activated.

Starter automation templates — one click to a useful setup

New clubs (and existing ones) no longer start with an empty Automations area. A "Starter templates available" card now offers a one-click install of ready-made draft automations for the moments that matter — trial bookings and reminders, event changes, expiring requirements, failed payments, membership changes, shop orders, and match-day updates — 34 in all, each with sensibly written email and text message templates. Everything installs as a draft: nothing sends until you've reviewed the wording and published it yourself. Drafts you haven't published yet can be reset back to the original starter content at any time; anything you've published, and any templates you've written yourself, are never touched. A few starters wait politely until their module (like Team Sports or Video Review) is switched on.

Automations now live in one place

Automations are now created and managed only in the dedicated Automations area. The old builder that lived under Settings has been retired: that screen now shows a short notice pointing you to the new home, with a link to the migration console. Nothing has been turned off — any rules you set up previously keep running exactly as before, and all your history is intact. This is purely a tidy-up so there's a single, clear place to build and review communications triggers.

Team Sports: matchday messages

For clubs using the Team Sports module, three matchday moments can now drive automations from the Automations builder: when a fixture is published, when the selection (team sheet) is published, and when a result is recorded. Pick one of these as a trigger and the message goes to the right families — everyone rostered for a published fixture or result, and just the selected players for a team sheet. Merge tags let you drop the opponent, kick-off time, venue, the player's role (starter or bench) and the final score straight into the message. As with the rest of Team Sports, this stays completely hidden until the module is enabled per program in Settings → Modules, and it works for any team sport.

Data export is now admin-only and audited

Downloading a member's full data export (the GDPR subject-access bundle, including any accident-report attachments) now requires admin access and is recorded in the club audit trail. Previously any signed-in staff member could download it. Day-to-day member screens are unchanged — this only affects the full export.

More accurate dashboard for large clubs

Clubs with very large member lists could previously see slightly under-counted dashboard KPIs (active members, retention, attendance rate) because a background query capped out silently. The dashboard now reads the full list, so the numbers are exact at any club size.

Penny-accurate membership revenue

The Membership report's Total Monthly Revenue and per-plan revenue now calculate in exact pence, in line with the rest of your money reports. For monthly plans nothing changes. If you have weekly, quarterly or annual plans, you may notice the total shift by a penny or two versus before — this corrects a tiny rounding drift in the old calculation, so the figure is now exact.

Deleting a member now protects safeguarding and accounting records

When you permanently delete a member's data (a GDPR erasure request), the app now does the right thing automatically instead of removing everything.

• Accident and incident reports are kept. Safeguarding records must be

retained under club policy and statutory guidance, so they're no longer deleted — they're moved to a restricted, retained state with a recorded retention reason and review date. Their attached PDFs are kept too. From then on, only staff with safeguarding accident-detail access (admins and your safeguarding lead) can see or open them; they no longer appear in the ordinary accident-report list — nor in the Accidents report — for other staff. (The review date is exactly that: a reminder to review, never an automatic deletion.)

• Financial records are kept, but personal details are removed. Invoices and

shop orders stay on file for your accounts — invoice numbers, amounts, dates and payment references are all preserved exactly — but the person's name, email and other contact details are stripped (the name shows as *"Removed (data request)"*). This also fixes a case where a member's shop orders could be removed along with their household; those accounting records are now retained.

• You're told exactly what happened. The delete confirmation now reports how

many records were retained or anonymised, not just what was removed — nothing is retained silently.

The retention review window (currently defaulting to six years) is a club-policy setting your club should confirm.

Event documents, competition music and syllabus videos now use secure links

Files you upload — organiser entry-document PDFs, competitors' freestyle music tracks, and syllabus/technique videos — are now served through secure, expiring links instead of permanent public web addresses. Nothing changes in how you use them: you upload the same way, and coaches, parents and event organisers open and download them exactly as before (including from a parent's competition-entry link and in the student portal). The difference is behind the scenes — these files can no longer be reached by anyone who happens to guess or share a raw file address, so a child's video or an event PDF is only opened by someone actually signed in (or holding the specific entry link). YouTube and Vimeo links you've pasted are unaffected.

Separately, the demo club no longer accepts real video uploads — the sample videos in the tour still play, but visitors can't add or remove media, keeping the demo clean for the next person.

Subscription billing, paid upgrades and payment-provider setup are now owner-only

The highest-risk financial controls now sit with the club owner only, not every admin:

• Your Allsorted subscription — starting or managing the club's (or group's)

subscription, and opening the Stripe billing portal — is now owner-only.

• Paid upgrades — subscribing to a paid add-on module or upgrading your plan

tier is owner-only. Admins can still start free trials as before.

• Connecting or disconnecting a payment provider (GoCardless Direct Debit) is

owner-only, and locked so it can never be delegated to another role.

Admins keep running the club day-to-day; these specific pay-provider and subscription actions are reserved for owners. Where an admin previously saw one of these buttons, they now see a short note explaining it's owner-only, so there's no confusing error.

Communications config is now admin-only

Creating, editing, or deleting communication configuration — automation flows, email templates, email skins and snippets, telegram recipients, and suppression entries — now requires admin access. Coaches and read-only staff can still view these, and everyday sending is unchanged. This closes a gap where a read-only staff member could alter club comms setup.

Safer data erasure and complete data exports

Two behind-the-scenes improvements to data protection. First, a member data export (the GDPR subject-access bundle) now includes the full set of records held about a member — attendance, assessments, communications, orders, course progress and more — so an export is genuinely complete. Second, the erase-member action now refuses to run unless the safeguarding-retention safeguards are active on the database, preventing any possibility of accidentally deleting records that must be retained.

Early-bird event pricing fix

Fixed an issue where an event booking paid at the early-bird price could be left unconfirmed if the payment settled after the early-bird deadline. Bookings are now always reconciled against the price that applied when the payment was made.

Event manage page works properly on phones

The Bookings and Invites lists on an event's manage page now switch to a stacked card layout on small screens, so every control — attendance (Present/Late/Absent), Cancel, Re-invite, Promote, status and payment info — is reachable on a phone instead of being cut off at the edge. Attendance buttons are now a comfortable tap size on mobile. The desktop layout is unchanged.

Safer buttons and clearer confirmations

A round of consistency work across settings and event tools: buttons that create charges, save automation categories, cancel-and-notify a closure, or save club details can no longer fire twice from a fast double-tap (no duplicate rows or double notifications). And a few important actions — renewing a member's annual requirement, deleting a booking requirement, and archiving a requirement — now show a proper confirmation dialog with clear success and error messages instead of a plain browser prompt.

The same treatment now covers the busiest day-to-day screens. Taking the register (sealing a register, cancelling a booking, and knowingly marking an expired member present), grading days (publishing certificates for an event or a whole session, and cancelling an unpaid grading booking), and external competitions (confirming or rejecting an entry, with a clear refund warning when a paid entry is rejected, and deleting a division) all now use the same tidy confirmation dialogs and slide-in success/error messages, in place of the old browser pop-ups. The actions themselves are unchanged.

A refreshed marketing site

The public marketing pages have had a visual refresh and now show the full product: Courses, Training Pathways, Team Sports, Pro Shop, Referrals, the Automations builder, email deliverability, video review, permissions and more — alongside the "one platform, any sport" story. Every page (home, features, pricing, who-it's-for and each sport page) now shares one polished, consistent layout with subtle motion, so the site feels of a piece.

Privacy & Terms tidy-up

The Privacy Policy and Terms pages now show a clean header with just the logo (back to the homepage) and a login link — they no longer accidentally display the logged-in staff navigation.

Settings: clearer, less martial-arts-specific (phase 1)

Settings has had a first round of clarity fixes so it reads correctly for every kind of club, not just martial-arts ones.

• Programs no longer all say "Martial arts." The Modules & Programs screen

used to label every program "Martial arts"; it now shows what the program actually does (e.g. "Team sports", "Timed events", "Progression") or a plain "Program" when there's nothing distinctive to show.

• Add-ons show status, not a misleading price. The old "£20/month" tag on

add-on modules has been replaced with plain status (Included / on trial / available / not entitled). Nothing about billing has changed.

• Team Sports and other add-ons explain themselves. When an add-on is

switched on for a program but your club isn't entitled to it yet, Settings now says so clearly, instead of the toggle silently having no effect.

• "Your subscription & add-ons" is now clearly separate from the module

on/off switches, so "plan" no longer means two different things on one screen.

• Less belt/Kup/Dan/"your art" wording across grading, certificates,

imports, waiting lists and the member portal — labels now follow each club's own terminology, and members are called "members" rather than "parents". Existing martial-arts clubs see the same wording as before.

• Comms, Templates, Deliverability and Automations in Settings now point to

the Comms Centre, which is their proper home.

Settings: smoother module toggles + clearer program access

• Module switches animate smoothly instead of flashing "Saving…". The

switch slides to its new position the instant you click; the change still saves safely in the background (and reverts if the save fails).

• Tidier module rows. Each module now shows a short name with an "i" you can

hover for the detail — so the rows line up neatly and the switches don't jump around. Where a module is switched on but not included on your plan, a small "Not active" tag explains why its screens don't appear yet.

• Programs "Belts" button follows your wording. In Settings → Programs the

per-program shortcut now uses your club's own term (Belts, Levels, Grades…), not "Belts" for every club.

Settings: clearer navigation (phase 2)

The Settings menu has been reorganised so it's quicker to find things.

• Clearer groups. Sections are now grouped as Club & Schedule, Programmes &

Grading, Money, Enrolment, Communications, People & Access, and Advanced — with vertical-agnostic names (no more "Curriculum").

• Enrolment split out of Money. Annual Requirements, Waiting Lists and Forms

now sit together under Enrolment, instead of being mixed in with billing.

• Comms live in the Comms Centre. Email Templates and Deliverability have

moved to the Comms Centre (their proper home); opening the old Settings links now takes you straight there. The multi-step Comms Flows editor stays in Settings. The retired Automations settings link now goes straight to the Automations area.

Settings: add-on clarity + safer nav (phase 2.5)

• Add-ons are shown by status, not sold in Settings. The "Your subscription &

add-ons" list is now read-only: no prices, and no "Subscribe"/"Upgrade" buttons (there's no self-serve checkout). You can still start a free module trial; subscription changes live in Your Plan, and support can add a module on request.

• Clearer "not available" screens. Team Sports, Courses and Pathways now

explain that a module you've switched on may still need to be included on your plan (rather than telling you to switch on something that's already on).

• Tidier menu for non-owners. The Roles & Permissions section is only shown

to owners (it was always owner-only — the link just used to error for others).

Settings: reliability & mobile polish (backlog wave)

• No accidental duplicates. A batch of save/add buttons across Settings —

message templates, email skins & snippets, comms flows, the SMS test-send, belt/level ranks, grading checklists, charges, closed-dates, 2FA and forms — are now click-safe, so a fast double-click can't create duplicate rows (or a duplicate SMS).

• Failures no longer look like successes. In Club Group, a failed rename or

action now shows a clear red error instead of the green "done" banner.

• Audit log paging fixed. "Next" now correctly stops at the last page, and

the footer no longer implies the page size is the total.

• Waiting-list edits give feedback. Changing a list's capacity now shows a

Saving / Saved / Couldn't-save state and reverts if the save fails.

• Small-screen fixes. The Memberships "Terms" table, the Staff inline-edit

row, and the Deliverability suppression list no longer clip their controls on narrow phones. Email templates now show the correct SMS channel badge.

Settings: simpler features model + clearer navigation (phase 3)

• Courses and Training Pathways now work end-to-end for clubs they're

granted to — they were built but couldn't be switched on because they were never registered in the platform's module catalogue.

• Modules & Programs is now about access, not sales. The old commercial

block is a read-only "Your enabled features" summary using plain states — Included, Granted, Active, Available, or Not available (contact support). No prices, no trials, no subscribe/upgrade buttons; your subscription lives in Your Plan.

• Set up once, then settings. A program's setup wizard now shows

"Set up progression" only until you've completed it — after that the action reads "Progression settings".

• Tidier program rows. The Programs list now uses the same edit-pencil and

"…" menu as the rest of the app (Edit program / Manage stages / Archive), and no longer says "Belts" for every club — wording follows your club's own terminology, with a neutral "Stages" default.

• Clearer Settings menu. Groups are now Club Setup · Programs & Activities ·

Payments · Members & Enrolment · Communications · People & Permissions · Advanced, with Member Portal settings under Members & Enrolment. All existing links keep working.

Settings: a calmer, card-based navigation (phase 4)

• Settings now opens on a home screen of clear areas — Club Setup, Programs

& Activities, Members & Enrolment, Payments, Communications, People & Permissions and Advanced — each with a plain-English description and its most common tasks one click away. No more wall of 30+ options.

• Pick an area, see just that area. Opening a group shows only its settings;

opening a setting shows a simple breadcrumb and a side list of its siblings — so you always know where you are, and rare/technical tools sit under Advanced rather than crowding everything else.

• Mobile is card-based — the cramped dropdown and grid overlay are gone;

tap through areas and use "Back" to step out. No sideways scrolling.

• Memberships is now a scannable table — name, status, price/billing model,

linked programme and member count at a glance — with the full plan editor tucked behind "New membership" / Edit instead of always on screen.

• Annual Requirements is now a matrix: each requirement as a row with its

cover, renewal, cost and what happens once it expires, shown at a glance.

• Every existing Settings link keeps working.

Grading scoring: mat lines that switch, and tidier grade groups

• Click a mat line to bring it on — on the scoring page the lead can now tap

any line in the left rail to put it on the mat (the same as its "On the mat" button), so running down the lines is one click each.

• Hover a line to see who's on it — on a computer, hovering a line in the

rail slides out a preview of the whole line in mat order before you switch to it. (Tablets keep the always-visible rail.)

• Smoother arranging — in Arrange mode you can now drag a student to an exact

spot in a line (a marker shows where they'll land) and reorder within a line, instead of always dropping to the end.

• Neater grade groups — a grade group with only a couple of students no

longer stretches its coloured band across the whole row; each group now sizes to the students standing in it.

Grading scoring: lines on top, clearer marks, faster notes

• Mat lines moved to the top. The lines now run left→right in a strip across

the top of the scoring area instead of down the left side, so a big line (6-across) keeps the full width for scoring. The strip stays stuck to the top as you scroll, so you can switch lines without scrolling back up. Hovering a line still previews who's on it; clicking still brings it on.

• RAG buttons match the assessments screen — Red, Amber, Green, in that

order, everywhere marks are set.

• See who's been marked. In a line with more than one student, a card that's

been scored for the item on screen gets a green tick and tint — so a mark landing just before the line auto-advances is unmistakable.

• Tidier student cards. Narrower cards showing the first name (full name on

hover), reclaiming space when several students are up.

• Faster notes. Long-pressing a Red/Amber/Green now opens the note with that

mark already selected and the cursor in the note box, ready to type; the mark buttons sit just above Save.

• Removed the "Needs a chat / Fine" key from the scoring screen (it's on the

live scores page).

Member portal: Courses now reachable

• Fixed a gap where a course assigned to a student never appeared in their

member portal — the Courses page existed but nothing linked to it. A Courses tab now shows in the portal (desktop sidebar + mobile More menu) whenever the selected child has a course, so assigned learning is one tap away.

4 July 2026

Team Sports — first foundations (behind a flag)

Groundwork for a new Team Sports area: run a squad that plays fixtures against opponents across a season, let families say whether their child is available, pick a team, and record the result — all without touching classes, the register or gradings. This first slice adds team and fixture management, a tap-to-pick selection board, touchline result entry, a season report card (played / won / drawn / lost, availability rate, appearances), and a parent-facing fixtures list with one-tap availability. It stays completely hidden until enabled per program in Settings → Modules, and it works for any team sport — the wording and any sport-specific stats are configuration, never baked in. More to come.

Portal shop polish + safer removals

Three small fixes from a full review of the parent portal on phones and desktops: the basket bar no longer hides behind the bottom navigation on phones, the shop's loading placeholder now matches the real layout (no more content jump), and an order whose payment window has lapsed now explains that the reservation expired and to order again, instead of sitting silently on "Awaiting payment". For staff, deleting a household and removing a contact now use the standard confirmation dialog — with the action spelled out and any problem shown inside the dialog — instead of a plain browser pop-up.

A cleaner main menu on desktop

On larger screens the main menu is now a wider "command centre" panel: the same links, organised into clear groups — Daily Operations, Members, Communications, Money, Development and Settings — each with an icon, laid out so everything fits on a laptop screen without scrolling. It's fully keyboard-friendly (Tab moves through the links, Escape closes and puts you back where you were). On phones and tablets the menu is exactly as before, and nothing has moved: every link goes to the same place and the same people see the same items.

Certificates: your own fonts, Oxanium, and grade number tags

Certificate templates get three upgrades. Oxanium joins Helvetica, Times and Courier as a built-in font — it's bundled into the app, so the editor preview and the printed PDF match exactly and nothing is fetched from the internet when certificates generate. Custom fonts: Settings → Certificates now has a Fonts section where you can upload your club's own TrueType (.ttf) font — it appears in the editor's font picker, previews live on the canvas, and is embedded into every generated PDF so certificates print identically anywhere. Fonts are private to your club, can be archived safely (templates that still use one fall back and show a clear warning rather than quietly restyling), and uploads are checked server-side so a broken file can never jam certificate generation — if a font ever fails at print time, that certificate falls back to a standard font and the batch still comes out. New template tags: {grade_number} (e.g. 9), {grade_type} (KUP or DAN) and {grade_number_type} (9 KUP) — taken straight from the belt's own grade settings, rendering blank when a belt has no numbered grade. All existing templates and tags carry on unchanged.

Follow-up fixes: the older {grade_awarded_full} tag no longer assumes "Kup" — a 1st Dan certificate now reads "… – 1st Dan" (Kup certificates are unchanged, and the grade word comes from each belt's own settings, so any club vertical gets its own term). The Fonts section also now shows a clean empty state rather than an error if the database update behind it hasn't been applied yet, and .otf uploads are labelled accurately (.otf works when it contains TrueType outlines; CFF/WOFF still need exporting to .ttf).

Grading day sheet: pass students in bulk, with one confirmation

Recording a grading day used to mean tapping Pass or Unsuccessful on every student one at a time, with the sheet reloading after each tap. The day sheet now has tick boxes: tick the students who are ready (or use Select all to grade), press Review outcomes, and check the full list in one place — every line shows who's being promoted from what to what, and you can flip any line to Unsuccessful, change the awarded belt, or remove it before anything is saved. Accept then records the lot in one go, or Back and amend returns to the sheet with your ticks kept. Students your club's own policy blocks from grading (expired insurance or licence) are never swept up by Select all — they can still be ticked individually, and the review list spells out the block so including one is always a deliberate choice. If any outcome can't be saved, the ones that worked are recorded and the review list stays open showing exactly which students still need doing — nothing is silently lost.

Grading day sheet: steadier rows, correct "from" belt

Two smaller fixes from a real grading day. The From → Belt → To display now sits in fixed columns, so the arrows line up down the whole sheet instead of drifting left and right with each student's name length; the "lessons since last graded" chip has been removed from this screen to reduce noise. And after recording a pass, a graded row now shows the belt the student actually graded from (e.g. White Belt → Yellow Tag) — previously it showed the new belt on both sides of the arrow, because the student had already been promoted by the time the row refreshed.

Double promotions recorded on the day sheet now stick

If the panel changed the awarded belt in the confirm step — a double promotion, or a booking that was targeted at a specific belt — the day sheet wasn't passing that choice to the server in the way the server expects, so the student was quietly promoted to the plain next belt instead. The confirmed belt on screen is now exactly what gets awarded, on both the single-event and whole-session day sheets, and saving a panel note on an already-graded row can no longer disturb the recorded award.

Courses: a built-in learning management module

Clubs can now build and share courses with members — a new optional module (off by default; switch it on under Settings → Modules). Staff create a course, organise it into sections and lessons (text, an embedded video, a file, or a quiz), then publish it. Access is granted per member: assign or comp a course to a student and it appears in their portal; remove the grant and it disappears again straight away. A per-course dashboard shows who's been assigned and how far each member has got.

For members, the portal gains a Courses area: work through each lesson, mark it complete, and take quizzes that are marked automatically — the correct answers stay on the server and are never sent to the device. A course counts as finished once every required lesson (and its quizzes) is done, and members can pick up where they left off. Membership-plan inclusion and completion certificates are designed in and will follow; for now courses are assigned manually.

Training pathways: development tracks for members and staff

A new Training Pathways area (off by default; an owner or admin switches it on in Settings → Modules) lets a club run structured development tracks — an assistant-coach induction, a volunteer or junior-leader programme, an officials ladder, a safeguarding-role checklist. Build a pathway from ordered stages, each holding tasks with an evidence type: a simple checkbox the person marks themselves, a written reflection, an off-platform certificate reference, or a staff sign-off. Publish it, then assign it to a member or a staff volunteer — each assignment takes its own snapshot, so editing the template later never rewrites someone's in-flight track.

Staff get a progress board per assignment: every task's state, the person's reflection, a feedback box, and Sign off / Return actions (who can sign off is role-controlled). A pathway completes automatically once every required task is signed off — optional tasks never block — and a "Pathways" tab on each member's profile shows their tracks and progress at a glance.

Members see a Pathways area in the portal: each track as a card with a progress bar and a "Next: …" line, and a detail view where they can tick off checkbox tasks, write reflections, and record certificates. Staff-only notes are never sent to the portal. Training pathways are kept completely separate from grading — finishing a pathway never changes a belt or grade, and a grading never advances a pathway. Certificates on completion, course-linked tasks, reminders and bulk assignment are designed in and will follow.

2026-07-03

The parent portal gets a Pro Shop, club announcements, and useful links

Three additions for families, all managed from Settings. Pro Shop: clubs can now sell kit and merchandise to their members — create products with variants (sizes, colours), set prices and stock, and choose who can see each product (all members, specific programmes, or specific levels). Parents browse the shop in the portal, pay by card exactly like any other club payment (money goes straight to the club's own Stripe account), and see their order history. Stock is reserved during checkout so two families can't buy the last hoodie at once, and unfinished checkouts release their stock automatically after 30 minutes. Staff get an orders dashboard — filter, search, move orders through processing → ready for collection → fulfilled — and low-stock warnings. Parents can request a refund with a reason; staff approve or decline, and the money itself is only ever refunded through Stripe directly, with the order updating automatically when that happens. A new Product Sales report shows revenue by product and variant, kept fully separate from membership fees. Announcements: a message strip across every portal page — one message shows as a notice, several as a gentle ticker that pauses when you hover and stays still for anyone who prefers reduced motion. Useful links: a club-managed list of helpful links on the portal home page. And a full portal check-up fixed five pages that used to go silently blank when a request failed — including the insurance page — plus a long-standing annoyance: a flaky connection no longer signs parents out; the portal now says "Can't reach the club right now — you haven't been signed out" and offers to try again.

Payments now leave a visible trail, and asking "are you sure?" looks the same everywhere

A platform reliability batch. Payments: every card and Direct Debit payment now writes its life story to a permanent ledger — payment started, succeeded, failed, refunded, disputed, and any mismatch the nightly reconciliation finds — without changing a single payment behaviour; operators see the last 24 hours of it on the platform health page. The platform health page itself was reorganised into clear sections (Messaging, Payments, Automations, Cron, Configuration, Tenants), each with a status chip and a "Needs attention" summary that says what failed, when, for which provider, and what to do next — and a data source that can't be read now shows as degraded instead of pretending all is well. Support gets a first cockpit: platform operators can look up a family by name, email, invoice or booking and see their communications (with delivery history), invoices, bookings and automation runs in one place — read-only, and invisible to anyone who isn't a platform operator. Clubs get a plain-English health card on Settings → Deliverability: "Email sending is ready", "Telegram is not connected", "Real sending is off — messages are simulated" — with no internal technical details leaked. And the last native browser pop-ups in the event form, message composer, API tokens, snippets and staff screens were replaced with the app's own clear confirmation dialogs — including a proper warning before a price change on an event that already has paid bookings (existing bookings are never charged the difference), and a "Replace my draft / Keep my draft" choice before a template overwrites typed content. Failures keep the dialog open with the reason; nothing you typed is ever lost.

You can now see what happened to every email after you pressed send

Email visibility used to stop at "sent". Every message now keeps a per-recipient delivery history: open a send in Communications (or an automation run) and each recipient shows their own timeline — sent, delivered, delayed (the receiving server asked us to retry), opened, link clicked, bounced (with the reason), or marked as spam. Statuses can never move backwards, and a provider re-sending us the same notification can't duplicate history. Recipients the app deliberately skipped are now labelled honestly too — "skipped — suppressed" or "skipped — unsubscribed" with a pointer to Settings → Deliverability — instead of looking like the email went out (one message even wrongly blamed the demo mode; fixed). And a new Domain & authentication panel on Settings → Deliverability shows whether your sending domain is verified (SPF/DKIM/DMARC), whether open/click tracking is on, and whether delivery tracking is wired up — with plain-English warnings when something needs attention.

Programme filters count everyone again, and forms fail safely

Three follow-ups from the audit decisions. Filtering the dashboard or a report by programme used to show 0 members for clubs set up before the newer enrolment model — those views now fall back to the programme's belt-system assignment, so the numbers match the "Active Students by Programme" card while the enrolment model is back-filled. On public forms, a question type the app doesn't recognise no longer renders as a label with nothing to type in: it clearly says the question isn't supported online and, if the question is required, the form can't be submitted with it unanswered — a clear failure beats a wrong medical or consent answer. And the password reset page no longer spins forever on a bad link: a link with no code is called out immediately, a stuck verification gives up after 12 seconds, and either way you get a calm explanation and a button to request a fresh link.

Cleaner settings, honest errors, and one way of asking "are you sure?"

A consistency pass from the product audit. The Automations settings page now speaks to club owners in plain language — the internal platform maintenance schedule and raw technical switches it used to print are reserved for platform operators, while your club's own readiness view (channels, send safety, warnings) is unchanged. The Charges page now shows every charge, whatever category it was saved under — charges in older or imported categories used to be silently invisible and impossible to edit. Pages that hit a database problem (Club Details, the platform overview) now say so in plain English instead of printing raw database text. Saving an event now shows problems in the form itself rather than a browser pop-up, and cancelling a scheduled message opens the same clear confirmation window used for money actions — stating exactly what will and won't happen — instead of a bare browser prompt. The demo's "writes are disabled" notice now reads the same everywhere.

Payment links and other family-facing links now open properly

A routing gap meant several links meant for families and visitors bounced to the staff sign-in screen instead of the page they were promised: invoice "Pay now" links, competition entry and cancellation links, the public waiting-list signup page, the Telegram opt-out link, the return page after setting up a Direct Debit, and the "thanks, you're enrolled" page. All of them now open directly — no staff account needed — while every link still checks its own secure token before showing anything. The staff Add Student wizard, which could get stuck on "Preparing Wizard…", now loads properly too, and the changelog page opens for visitors from the website footer. A permanent automated check now keeps the public-page list from drifting again.

The app now behaves properly on phones and tablets

Four layout fixes from the audit. "+ Event" works on phones again — a page animation was quietly breaking every pop-up dialog opened from the main content area (event forms, closure forms, series and bulk-cancel dialogs), leaving them stranded thousands of pixels below the screen; one CSS correction fixes them all. On a household's invoice list, the Mark Paid / Credit / Write off / PDF buttons no longer spill off the edge of a phone screen — they wrap neatly onto the next line — and a hidden markup problem that made React complain on every household page is gone. Tablet-portrait horizontal scrolling is fixed everywhere: the top bar was slightly too wide at 768px, nudging every single page into a sideways wobble; the search box and two lower-priority icons now wait for wider screens (they stay reachable from the menu drawer). And the platform admin and billing pages show one header instead of two — they no longer stack the normal staff navigation on top of their own.

Broken pages fixed, and failures now say so instead of pretending

Five reliability fixes from the full product audit. The competition (external event) detail page and the Progression report were both broken by queries against mis-named database columns — the competition page failed outright, and the Progression report loaded as a convincing "all clear" (0 promotions, nobody overdue) when it had actually failed. Both now load correctly, the report shows a clear "couldn't load — try again" message if anything goes wrong, and an automated check now scans the whole codebase for that same class of column mistake (it caught and fixed two more on the way: empty rank pickers on the event manage page and a silent rank lookup in Assess). On the register, a tap that the server rejected used to look saved — the button lit up and the on-mat count went up anyway. It now shows an error and puts the register back the way it was. And on the waitlist claim page, a payment set-up failure used to leave families staring at "Preparing payment…" forever; it now explains what happened, confirms nothing was charged, and offers the button again. The grading day sheet also now distinguishes "this session doesn't exist" from "loading failed — try again".

Waiting-list controls now go through the same safety checks as every other setting

The per-class waiting-list controls (turning a class's list on or off, setting its capacity, choosing how offers are made, removing someone from the queue, and adding someone by hand) used to write to the database directly from the browser. They now go through the same guarded server path as the rest of Settings: only staff with the settings permission can change them, the demo club properly says "writes are disabled here" instead of quietly saving, and the manage link for a hand-added entry is generated on the server. If a change can't be saved, the page tells you why — nothing pretends to have worked.

Money actions now ask properly before they act

Anything that moves money or changes a member's status now gets a clear, deliberate confirmation — no more one-click surprises or bare browser pop-ups. Mark Paid, Refund, Undo payment and invoice edits open a proper window that states exactly what will happen ("Record a manual payment of £25 for Sam — no card is charged"), whether it can be undone, and asks for a reason where one is recorded. Cancelling a trial now confirms first — naming the child, date and class — and is honest that no message goes to the family automatically. Household credit and write-off amounts get a real form with validation instead of a browser prompt box, and the button tells you the exact amount before you press it ("Credit £5.00"). If the server rejects anything, the window stays open with the reason — nothing is lost and nothing pretends to have worked.

The app now speaks your club's language

Allsorted grew up around martial arts, and it showed: tooltips, examples, report columns and page headings said "belts", "gradings" and "students" even for dance schools, swim clubs and football academies. That's fixed across the whole app. Screens now use each club's own terminology — a gymnastics club sees "Gymnasts", "Levels" and "Assessments" where a martial-arts club sees "Students", "Belts" and "Gradings" — and shared examples read for every club type ("e.g. Gum shield, swim cap, ballet shoes"). The privacy policy no longer describes every club as a martial arts club, the writing assistant stops assuming martial arts when drafting messages, and the parent portal uses the club's words too. Existing martial-arts clubs see exactly the wording they had before — nothing changes unless a club's activity type says it should.

Table actions now work the same way everywhere (first wave)

Every list used to do actions its own way — some buttons appeared on hover, some sat inline, some hid in different menus. The app now has one house pattern: each row keeps at most one main action button (Edit, Publish, Retry), and everything else lives in a consistent ⋯ menu at the end of the row — same position, same look, destructive options always last and always asking before they act. The menus open in available space (never off-screen), work fully from the keyboard, and rows never resize or jump when you hover. The first wave covers automations, tasks, scheduled changes, the communications send history, and the venues, memberships, timetable and drill-library settings tables — with every action doing exactly what it did before. More screens follow in later waves.

Table actions: second wave

The consistent row-actions pattern now reaches more screens. On an event's Invites tab, Resend stays the one-tap button and History + Revoke move into the row's ⋯ menu (Revoke still asks first, with the same wording). The Staff settings list gets the same treatment: Edit stays up front, and Resend invite, Reset MFA and Remove sit in the ⋯ menu — with exactly the same confirmation steps as before. Event types in settings now match the other settings tables (Edit up front, Delete in the menu, reorder arrows unchanged), and their actions no longer hide from keyboard users. The External events list is now fully keyboard-navigable — Tab to a row and press Enter to open it — and event rosters, reports and the comms map all use the same subtle row highlight. The event Bookings tab keeps its buttons exactly as they are (they touch payments, so they change in a later, carefully-reviewed wave), but its rows no longer shift about as statuses change.

The platform health page now shows payment-webhook trouble, not just job trouble

The internal health page used to tell you *that* scheduled jobs ran and *how many* webhook deliveries failed — but not what failed or what the recovery sweeps actually caught. It now surfaces the newest failure signals directly:

• Card-payment webhooks get their own headline tile and section: how many

deliveries failed in the last 24 hours, how many have been stuck "in progress" for over an hour (the crashed-mid-flight case the new durable ledger exists to catch), and a table of the failed deliveries themselves — which event, what the error said, and when it arrived. On a database that hasn't received the ledger upgrade yet, the section says so plainly ("ledger not yet migrated") instead of showing a falsely reassuring zero.

• Direct-debit webhook failures now show the same detail table — operators see

*what* failed, not just a count. (The count itself was quietly broken by a wrong column name and always read zero; that's fixed.)

• Recovery sweep counters: the latest run of the two safety-net jobs — the one

that re-schedules automation waits the external scheduler dropped, and the one that reconciles provider payments against the ledger — now shows its numbers on the page: missed wake-ups and reclaimed stuck jobs, payments checked, new findings and auto-resolved findings, with anything above zero on the "the primary path dropped something" counters highlighted in red.

The page stays strictly read-only, and any single section that can't load shows a small "query failed" note while the rest of the page carries on.

The Comms Trigger Map now shows every automation, not just the old ones

The Trigger Map (Comms Map → Trigger Map) used to only know about flows built in the older Settings → Comms Flows editor — anything set up in the newer Automations builder was invisible here, even when it was live and sending messages, which made the map's count of active flows misleadingly low. It now shows both: each lane carries a small label — "Legacy flow" for the older editor, "Builder" for the new one, or "Scheduled" for a builder automation that runs on a schedule rather than an event — so it's always clear which editor owns it and where to go to make changes. The active flow count and the category/status filters now count both kinds together.

What's On now shows your child's own classes, not just things you can book

The parent portal's What's On calendar used to only show sessions you could book — if your child's regular class wasn't one you needed to book separately, it never appeared, so there was no easy way to answer "when is training this week?" from the calendar. It now also shows My Classes: your child's own enrolled recurring classes, marked in amber on the month grid and clearly separate from bookable Sessions (blue), Events (green) and Competitions (indigo). Tap a day to see the class name, time, venue and which child it's for. Nothing about booking, cancelling or paying for anything has changed — this is purely an extra read-only view of classes you're already enrolled in.

2026-07-02

The student profile looks finished at every window size

On wide screens (or zoomed out), the coloured wash at the top of a student's profile used to stop at a fixed width, leaving bare strips either side that made the page look unfinished. The background now runs edge-to-edge at any window size while the profile content stays comfortably centred — and nothing about the mobile layout changed. A sweep confirmed no other screen shares the old pattern.

Cancel many event bookings at once — with or without refunds

Emptying an event used to mean cancelling every booking one by one. The event manage page's Bookings tab now has checkboxes on the booked and attended rows and a Cancel selected button: tick the people to cancel (or select all), confirm, and the whole batch is processed in one go. Confirmation happens in a proper window rather than a browser pop-up: it shows how many bookings are selected, how many are paid and how many are free, and reminds you that waitlist spot offers won't be sent during a bulk cancel. If any of the selected bookings are paid, you choose up front whether refunds go out — the default matches cancelling a single booking (refunds are issued automatically), and cancelling without refunds is always an explicit choice, never an accident: it's a separate option, and you must also tick an "I understand paid bookings will remain paid and no refund will be issued" acknowledgement before the button — which spells out exactly what will happen, e.g. *"Cancel 8 bookings and issue 3 refunds"* — will fire.

Each booking is handled individually and honestly: one that can't be cancelled (or whose refund hits a problem) never blocks the rest, and the result tells you exactly what happened — "7 cancelled (5 refunded) · 1 skipped", with a named message for anyone whose refund or invoice needs a follow-up. Refunds are spaced out behind the scenes so a big paid event cancels reliably, and the same double-refund protection as single cancels applies: retrying a booking can never refund the same payment twice. One deliberate difference from cancelling a single booking: a bulk cancel does not email the waitlist that spots have opened up — when you're clearing an event, those seats aren't really becoming available. The cancelled members themselves still get their normal cancellation messages.

Windows and menus appear reliably on top (first wave)

Dialogs, drawers and menus now sit on one carefully ordered layering system, and the first wave of screens has moved onto it: the main app's student profile, household, settings and key event/calendar dialogs. Most visibly: opening a dialog from a student's profile (editing contact details, changing a plan, confirming a status change, the belt history, and friends) could previously render behind the student name list on the left, leaving it half-covered and seemingly broken. Every one of those dialogs now reliably appears on top, along with the equivalent windows on the households, events and settings screens. On the migrated screens the order is guaranteed: menus float above panels, dialogs above menus, a confirmation opened from a dialog above that dialog, the security timeout above everything except toasts — which always win. Nothing about what the windows *do* has changed; they just show up where you can see them.

Not every screen is on the new system yet: a number of older dialogs — the register screen's overlays, the grading and external-events windows, some communications pop-ups, and the public sign-up and member-portal pages — still use the previous layering. They behave correctly on their own pages today and will be brought across in later waves (the calendar's closure form, the trial-embed window and the voice-note editor came across with this release). An automated check now stops badly layered windows sneaking back into the new system; it polices the new-style layer values, so the older screens stay on a tracked backlog rather than under the check.

A second batch follows in the same release: the new-task dialog, the automations "how would you like to build this?" chooser, the communications template picker and its test-send / confirm-send / invite-to-event windows, the staff trial-booking dialog, the password-confirmation gate used for sensitive undo actions, the add-student wizard's saving screen and duplicate-email warning, and the video-review flag/archive/delete confirmations. As always, nothing about what these windows *do* has changed — same buttons, same behaviour — they simply can never be trapped behind other parts of the page any more. The communications preview and history side panels deliberately stay as slide-over drawers; that's their correct layer, and the automated checks now assert it.

A database hiccup no longer masquerades as "not found"

Across nine more areas — saving a student signature, changing a student's status, student achievements, household details and contacts, communication flow steps, email template versions, lesson drill tags and lesson plan feedback — a temporary database problem during the ownership check used to come back as a flat "not found", exactly as if the record didn't exist. Staff would retry, assume the record was gone, or file a confusing bug. Those checks now tell the truth: a record that genuinely doesn't exist (or belongs to another club) still says "not found", word for word as before, but an infrastructure error now surfaces as a proper server error that's visible in monitoring — so a wobble can't silently pretend your data has vanished. 114 automated tests pin the exact wording and behaviour of every one of these responses.

Two people editing the same thing no longer overwrite each other

If two staff members have the same record open — an automation draft, or an event's details — the second save used to silently wipe out whatever the first person had just changed, with nobody the wiser. The app now notices the record was changed since you opened it and warns instead of overwriting: *"This was changed elsewhere. Refresh to see the latest, then re-apply your edit."* Nothing you typed is lost — your form stays on screen, so you can check the latest version and apply your change again. This protection covers the automation builder's Save draft and event editing from the calendar first, with more screens to follow. (Rescheduling an event that already has bookings takes a separate path that isn't covered yet.) The same protection now also covers three settings screens: editing an event type, editing a class on the timetable, and editing an automation category.

Automations know exactly who they're talking to

Owner and admin Telegram alerts are now resolved strictly per club — your bot token and your admin recipient list, nothing shared, no hidden fallback. And if an automation asks to notify the owner before Telegram is set up (no bot connected, or no admin recipients added under Settings → Club Details → Telegram Integration), the step no longer pretends it succeeded: the run log shows a clear "owner Telegram not configured" skip, and the rest of the automation's actions carry on regardless. The "Member + Admin" copy on a Telegram step now records whether the admin copy actually went out, too.

Emails about a member can now be addressed to the household bill payer — the household's billing address, or its primary contact — which is usually the right inbox for payment reminders about a child. When no payer can be resolved (no household, or no address on file), the message falls back to the member's own contact and the run log records exactly why. Test mode is unchanged and watertight: every address, including a payer's, obeys the same live/production/test-allowlist rules on every path — including reminders that wake from a schedule.

Automations → Upcoming has grown up. Every durable scheduled job — a paused "wait 2 days" step or a timed trial/event reminder — now shows who it's about ("Trial — Sam Smith, 17/07 18:00", "Event — Autumn Camp — Ava Evans"), who will receive it, what it will do (email, SMS, task…), exactly when, and which automation (and version) created it. Jobs whose wake-up is held by the external scheduler carry a small badge so you can see how they'll fire.

It's no longer just the future, either: new filters let you flip between what's still Scheduled, what already Fired, what was Cancelled or Superseded (say, after a reschedule — with the reason shown right on the row), and what Failed or Skipped, plus a trigger-type filter and a due-date range. The default view is unchanged: what's due to go out next, soonest first.

Cancelling or rescheduling now tidies up its reminders

When a trial or event is cancelled, its pending timed reminders are retired on the spot — not left to quietly expire. When one is rescheduled, the old reminders are marked superseded and fresh ones are scheduled against the new start time automatically. And when you publish a reminder automation with a timing, it now also picks up bookings that already exist — so "2 hours before" applies to everyone, not just people who book after you press publish. If a reminder's background job can't be reached to cancel, no matter: the database is the authority, and a stale wake-up always stands down without sending. Any genuine database error at send time now fails loudly (visible in monitoring) rather than being mistaken for "booking gone".

Timed trial and event reminders — "2 hours before start"

Trial and event reminder automations gain a "Send when?" control: keep the default day-before reminder, or choose an exact offset — say, 2 hours before the trial starts. Timed reminders are scheduled the moment the booking is made, anchored to the real start time (not a blind delay), and re-check everything before sending: the booking still stands, the event isn't cancelled, the start time hasn't moved, the automation is still published and the club still has automations on. If any of that changed, the reminder quietly stands down instead of sending something stale. Each automation owns its reminder exactly once — a timed automation is skipped by the old daily sweep, so there's no double-send path.

The builder also now refuses impossible condition combinations at publish (e.g. using a date window on a text field), so imported or hand-edited automations can't sneak past validation.

Scheduled automation waits are now durable

Behind the scenes, every scheduled automation wait (the "wait 2 days then continue" steps) is now always recorded in the database before any external scheduler is involved, so a configuration change mid-wait can no longer lose a pending automation. When a wait wakes up it also re-checks that the club still has automations enabled (and isn't the demo club) before sending anything — a long wait can't outlive a decision to switch automations off. A light daily tidy-up job recovers anything that gets stuck.

Dropdowns and popovers now stay on screen

Small anchored menus — the equipment checklist on a grading event row, the ⋯ actions menu in the automations table, the timetable Export menu — used to open blindly downwards. Near the bottom of the window they could run off-screen or stretch the page with an extra scrollbar, and inside scrolling tables they could be clipped mid-menu.

They now share one smarter popup system: each menu opens above or below its button depending on where there's room, slides in from the button rather than popping from nowhere, never crosses the edge of the screen, scrolls internally when space is tight, and follows its button when you scroll. Escape or a click elsewhere closes them, and keyboard focus lands back on the button you started from. Everything the menus *do* — ticking checklist items, archiving automations, exporting PDFs — is unchanged.

A second wave brings the everyday header and comms dropdowns onto the same system: the top-bar navigation menus, the club switcher, the program lens, the little "i" info popovers on settings headings, and the Test SMS / Test Telegram popovers on the bulk-send page. Same upgrade, same promise: what each menu does hasn't changed, it just can't fall off the screen any more.

A fourth wave covers search-as-you-type and the last everyday menus: the register's add-student search, the task screen's student search (including inside the new-task window), the tasks mobile action and status menus, the student list's bulk status menu, the household "+ Add Member" menu, and the grading rubric's icon picker. Search lists now follow their box, flip upward near the bottom of the screen, support full keyboard navigation (arrow keys, Enter to pick, Escape to close), and announce themselves properly to screen readers.

A third wave finishes the job on the busiest screens: the Sort panel and the Send-options and Add-student menus on the Students page, the Sort panel on the Communications recipient sidebar, the "+ Insert tag" picker in the event editor (which now reliably sits on top of the event window instead of hiding behind it), and the Insert form link / Insert snippet pickers in the email composer. As before, everything these menus *do* — sorting, sending forms, adding students, inserting tags and snippets — is exactly as it was; they just position themselves properly, close on Escape or a click elsewhere, and hand focus back to the button that opened them. A new automated check now stands guard so old-style, clippable dropdowns can't sneak back into the app.

Waitlist promotions get their timed reminders too

Timed event reminders ("2 hours before start") were scheduled when a booking was first made — but a member who reached "booked" from the waitlist slipped past that moment. Now every route to a seat schedules the same reminders: a staff promotion from the waitlist, a member claiming a freed spot on a free event, and a paid claim the instant the payment is confirmed and the seat is actually won. Retries can't create duplicates, and a reminder hiccup can never interfere with the promotion or the payment itself.

The automation builder now speaks plain English

Simple setup has had a polish pass so building an automation reads like a sentence: when this happens → only continue if… → then do this. The conditions section stays out of the way until you actually add one, and everything the builder says about your automation — the plain-English summary, the preview chips, each step's one-liner — now uses friendly wording throughout ("Previous status is Active", never raw internal field names).

The Annual requirement due trigger gets the same treatment the status-change trigger already had: instead of a technical field/operator/value row, you set a simple "Expires within [30] days" window — and the summary reads exactly that, e.g. "expires within 30 days" for an insurance renewal chase. It's stored as an ordinary condition underneath, so anything built before (or anything more unusual) still opens in the familiar condition editor with nothing hidden.

Email steps also gain a Send to choice: the member's own contact (as always), or the household payer — the right inbox for payment and renewal emails about a child. If no payer address is on file, the message safely falls back to the member's contact and the run log says why. And timed reminders now spell out their one honest edge case: someone who books *after* the reminder's send time has already passed won't get that reminder.

Going back from an event returns you to the day you came from

Opening an event from a calendar day and clicking "Calendar" used to drop you back at the calendar root, losing the day you were working through. The event page's breadcrumb now reads Calendar › the event's day › event name, and the new middle link takes you straight back to that day's view. It's worked out from the event itself, so it still points at the right day after a refresh or when following a shared link.

Coach notes, session feedback and incident reports survive bad venue signal too

The same keep-and-retry protection that assessment comments gained now covers two more places staff type things at the venue: coach handover notes on a session's register card, and the session feedback form. If the save can't reach the server, the card shows an amber "waiting to send — will retry when you're back online" note, keeps your text exactly as typed, and sends it the moment the connection returns (or on Retry now). Retries can never save a duplicate or an older version over a newer one.

The two places this mattered most are now covered too: notes typed on a grading day. The day panel's booking notes used to be able to vanish silently if the connection dropped at the wrong moment — the save looked fine but never happened. And an examiner's judging notes could actually be erased from the screen after a second of bad signal. Both now keep your text exactly as typed, show the same amber "waiting to send" state, and send the moment the connection returns — an examiner's note even survives reloading the page mid-outage. Scores themselves behave exactly as before.

The accident/incident form gets a different, equally important safety net: everything you type into the report now autosaves to this device as you go. If the page reloads or the tab closes mid-report — exactly the moment that tends to happen during a real incident — reopening the form offers to restore your draft ("Draft restored from this device"), which you can keep or discard. Submitting still happens in one deliberate step, exactly as before, and clears the draft.

Assessment comments survive bad venue signal

Sports-hall Wi-Fi drops mid-session; typed comments shouldn't drop with it. On the assessment grid, a comment you write with bad signal is now kept and retried — never silently lost. If the save can't reach the server, the comment stays visible with an amber "waiting to send — will retry when you're back online" banner (and inside the technique's comment list), then sends itself the moment your connection returns — or immediately via the Retry now button. It even survives closing or reloading the tab: pending comments are stored on the device until the server confirms them. Nothing is ever marked as saved until the server actually says so, a retry can never create a duplicate comment, and a genuine rejection (say, an expired session) is shown to you straight away rather than retried forever.

Repeating events — and a quicker way to create any event

Events can now repeat properly. When you create an event, a new repeat picker offers options built from the date you chose: every X days, weekly or fortnightly on that weekday, monthly on the same date, or patterns like "monthly on the 3rd Tuesday" and "monthly on the last Friday" — with a chip preview of every date before you save, so there are no surprises. The old monthly repeat could drift at the end of a month (a 31st sliding into early the month after); the new date maths can't. Repeating events are saved as a linked series, and cancelling one now asks the honest question: just this event, or this and all future events in the series? Cancelling the future events follows the same bookings-first rule as always — any occurrence that still has active bookings is skipped, never silently cancelled, and the result tells you exactly what happened ("4 cancelled · 1 skipped — still has active bookings"), listing the dates that need a follow-up. This same choice now appears everywhere an event can be cancelled — the day view and the event's own manage page both offer it for events in a series.

Creating any event got faster too. The type picker is now a single step — every event type on one screen, grouped under its category heading — and if you only have one type, you land straight on the details. The end date stays out of the way behind a Multi-day event toggle (most events are one day; the end date simply follows the start date until you say otherwise). The form also remembers the start time you last used for each event type, and the sign-up cut-off and early-bird deadline gain one-tap presets — "1 day before", "3 days before", "1 week before" — computed from the event's own date and time, with anything that would land in the past sensibly greyed out.

Invoices for paid items now show their real line amounts everywhere

A paid invoice could show £0.00 against its line items — on the PDF a parent downloads from their confirmation email, on the public "pay this invoice" page, and in the household billing view — even though the invoice total at the bottom was right. It affected competition/external-event entries and older event-booking and enrolment invoices, and it was purely a display fault: the money taken and the totals stored were always correct. Every place an invoice renders now computes each line the same way, preferring the exactly-stored amount and otherwise deriving it from quantity × unit price — so a £20 entry fee reads as £20.00, never £0.00. New competition-entry invoices also store their line totals outright so they're right at the source.

Behind the scenes, the invoice screens are more honest when something goes wrong. Previously a database hiccup could quietly render a PDF with no line items at all, show a parent an empty "no invoices" payments page, or turn a legitimate pay link into "Invalid link". Now: the PDF says plainly that line details are temporarily unavailable (with the correct total still shown), the portal and staff billing views show a clear error instead of pretending there's nothing there, and every such failure is logged with the invoice reference so it can be chased. Promoting someone off an event waitlist also now ties the invoice it raises to that booking — so when the family pays, the payment settles that exact invoice rather than ever creating a second one.

Two follow-up polish points from the independent verification of this fix: invoice PDFs downloaded earlier the same day can no longer serve a stale pre-fix copy (the PDF cache now refreshes itself the moment the invoice rendering changes, not just when the data does), and the public pay page now distinguishes a temporary problem — "could not load this invoice right now, try again in a few minutes" — from a genuinely dead link, so a parent with a valid link is never wrongly told it's invalid during a brief outage.

2026-07-01

Smarter automation triggers: status transitions and expiry windows

The automation builder now understands *changes*, not just states. For "Student status changed" you pick a simple From / To (e.g. From Active → To Leaver) instead of wrestling with raw fields — and the automation reads the actual change, so it fires on the transition itself, never on whatever the record looks like afterwards. Requirement-expiry triggers gain a friendly "expires within [X] days" condition (checked against server time; a missing or invalid date simply doesn't match). Your existing automations carry on exactly as before.

Onboarding saves now fail visibly, never silently

During club setup, removing a grade type or a programme used to *look* done even if the save failed behind the scenes. Those steps (and the club details / membership plan / preset saves around them) now show a clear error and keep your data on screen when something goes wrong, so nothing quietly disappears — and remove buttons can't be double-clicked into duplicates.

Safer "request a new booking link" for event invites

When a guardian asks for a fresh event booking link — from the public booking page or when staff resend an already-used invite — the old link now stays working until the new one has actually been sent. Previously the old link could be invalidated a moment before the email was queued, so a delivery hiccup could leave the recipient with no usable link at all.

Now the flow is delivery-safe: the new link is emailed first, and only once it's safely queued does the invite swap over to the new link. If the email can't be sent, nothing changes and the original link keeps working — the guardian can simply try again. Bulk "resend invites" follows the same rule: a row whose email fails is reported as skipped rather than counted as sent, and never loses its existing link.

Booking requirements for events (checklists, waivers, info)

Events can now carry their own booking requirements — reusable blocks a parent completes before their place is confirmed:

• Checklists — a list of things to confirm (e.g. "I have my sparring gear"), each optionally required.
• Waivers / acknowledgements — text the parent must accept before booking.
• Information — a read-only note shown during booking (parking, what to bring, arrival time).

Add them when editing an event, mark any as required, and the public booking form shows them under "Before booking". A place can't be confirmed until every required item is done — on both free and paid bookings — and what the parent agreed to is saved against the booking exactly as it read at the time, so later edits never rewrite historical consent. Staff who confirm a booking directly have it recorded as completed by staff.

This replaces the old, martial-arts-specific grading equipment checklist with one generic system that works for any club, event type or vertical. Existing grading events keep their equipment checklist automatically — it now simply flows through the new system.

Default booking requirements per event type

You can now set booking requirements once on an event type (Settings → Event types) and have every new event of that type start with them — no more re-adding the same checklist or waiver to each event.

• Set them up under "Default booking requirements" when editing an event type.
• New events of that type are created with their own copy of those requirements, ready to tweak per

event.

• Existing events are never changed — the defaults only apply to events created afterwards, and each

event's requirements stay independently editable. Changing a type's defaults later won't rewrite events you already made.

• Grading events still get their automatic equipment checklist on top of any custom defaults — no

duplicates.

If those defaults ever can't be copied onto a new event, the event still saves and you get a clear non-blocking notice to open the event and check its requirements — creating an event is never blocked. Deleting a default now spells out that it only affects new events of that type from now on; existing events are never changed.

2026-06-30

Six new automation triggers

The automation builder gains six new triggers you can build email automations on. They appear in the trigger picker alongside the existing ones (New student enrolled, Trial booked, Event booked, …), each with their own merge tags ready in the editor.

Trial triggers

• Trial cancelled — fires when a trial booking is cancelled (by staff or via the public

cancel link). Carries the trial date, class name and the contact's details.

• Trial rescheduled — fires when a trial is moved to a new date/time. Carries the

previous and new trial date/time, so you can send a clear "we've moved your trial" note.

• Trial reminder — sent the day before an upcoming trial, as a gentle reminder. Runs from a

daily background job; each booking is reminded at most once.

Event triggers

• Event booking cancelled — fires when a student's event booking is cancelled. Carries the

event name, date, time and location. (Any refund is handled by the event screen exactly as before — this trigger never touches money.)

• Event rescheduled — fires when an event is moved, once per booked or invited student.

Carries the from date/time and the to date/time plus the new location.

• Event reminder — sent the day before an upcoming event to every booked student. Runs from

a daily background job; each student is reminded at most once per event.

Each new trigger runs through the same safe pipeline as the existing ones: it only sends when a club has published an automation for it and the runtime is switched on, never sends on the demo club, and every send is visible in the Command Centre. Where the older notification system also covers one of these events, it now steps aside once you publish a builder automation for it — so there's no risk of a member getting the message twice.

2026-06-29

Booking Status for gradings

The grading event screen has a new Booking Status button, sitting next to Belts required in the Print & prep group. It opens a calm, scannable view of how your grading is filling up — per grade, how many students you've invited versus how many have actually booked, with running totals at the bottom.

• Expand any grade with the chevron to see the underlying students, their status

(Booked, Invited, Waitlisted or Cancelled) and when they were invited.

• Resend an invite to a student who hasn't booked yet — it goes out only after the

server confirms, so you never get a false "sent".

• Cancel a booking that has no payment attached, straight from the row (with a

confirmation prompt). Paid bookings are intentionally left to the event screen so a cancellation never triggers a refund from here.

Permissions tightened along the way: resending an invite now needs event-booking permission (instructor and up), and the staff cancel action needs the event-financial permission (admin and up — it can issue refunds). Members cancelling their own booking via their personal link are unaffected.

It's read-only data pulled together on the server and scoped to your club — nothing about inviting, booking, cancelling or payments has changed; this just makes the invited-vs-booked picture easy to see at a glance while you prep for grading day.

Grade chips on linked events

Each linked event in a grading group now shows small belt/grade chips for the grades that event is intended for (from the event type's grade range) — so you can see at a glance which ranks each linked event covers without opening it. Two-tone belts show their real stripe, a long list collapses to +N more (hover for the full list), and an event with no grade filter shows a quiet All grades. Display-only, derived on the server and scoped to your club.

2026-06-28

One Comms Centre

The communications areas now share one navigation so they read as a single Comms Centre instead of separate pages. The same row of sections — Messages · Templates · Automations · Comms Map · Deliverability — appears across the area with your current spot highlighted, so it's always clear where to go to:

• Messages — send a one-off email, SMS or Telegram (the composer, renamed from

"Comms").

• Templates — your reusable email/SMS/Telegram messages.
• Automations — build triggers and check what ran, is queued, or failed. This

area now sits inside the Comms Centre rather than off on its own.

• Comms Map — see every trigger and what's wired to it.
• Deliverability — check your email/SMS/Telegram is landing.

SMS Gateway and the advanced email options (Skins, Snippets, Template Matrix) stay in Settings and are linked from where you need them. Nothing about sending, automations or provider setup has changed — this is purely making the area easier to move around.

Automate around Video Review

The Automations builder now has Video Review triggers, so you can set up emails, SMS or Telegram messages to fire when:

• a member is granted or has revoked Video Review access,
• a member submits a video,
• a coach reviews one, or
• a clip is flagged.

Each trigger comes with Video Review merge tags (syllabus item, score, feedback, status, and more). Automations are a side effect only — if one fails it never stops the actual grant, upload or review.

Automations now live in one place

Building automations has moved fully into the Automations area. The old Settings → Automations tab has been retired — opening it now shows a short notice pointing you to the new home (and the migration console for bringing old rules across). Any automation rules you already set up keep running exactly as before; nothing has been turned off.

Voice Notes has been retired

Voice Notes is no longer an active feature. It's been removed from the sidebar, and new voice notes, audio uploads, pasted transcripts, and class recordings can no longer be created. Any notes and audio you already have remain fully viewable — open /voice-notes directly to review them. Nothing has been deleted.

Event cards now show invited *and* booked

Event cards in the calendar's day view now read "X invited · Y booked" (e.g. *8 invited · 3 booked / 20*), so you can see take-up at a glance — how many you invited versus how many have actually booked — without opening the event.

"Classes attended since last grading" now matches everywhere

The blue ATT count on the Assessment grid was under-counting — it only counted classes tagged to that belt system and skipped untagged or no-lesson attendance. It now counts all attended classes since the student's last grading, using the exact same calculation as the Grading page, so the two screens always agree.

No more dashboard "flash" when pages load

Navigating to Automations — or opening a public link like a trial booking — no longer briefly flashes the dashboard layout while the page loads. Public pages now show a clean Allsorted-branded loader, and each staff section shows its own section shell. Links from staff pages into public flows (add a student) now load the public page fresh, without the staff frame wrapping it.

Automations: a better Email & Telegram step

Building an email step now starts with a clear choice:

• Use a template — pick a saved email template, then preview it to confirm it's the

right one before saving.

• Create new — the same editor as the Communications composer: merge-tag picker

(showing only tags that resolve for the trigger), visual/HTML editing, and a live preview.

Telegram steps gain a "Notify club owner" option — tick it to also send the message to the club's admin Telegram recipients.

Automations email/Telegram step — follow-ups

• Create-email "Preview text" now works. The preheader (inbox snippet) field in the

embedded composer is wired end-to-end, so you can type into it and it's sent as the email's preview text.

• Telegram "who gets this" choice. A Telegram step can now send to: the member only;

the member *and* notify the club owner; or only notify the club owner / admins — for alerts (e.g. trial bookings) where the member shouldn't receive anything. Owner/admin notifications go to your club's Telegram admin recipients and are production-gated.

Automations: Discard a draft you didn't mean to keep

Building a new automation creates a draft as soon as you start. There's now a Discard button in the builder (both Simple and Advanced) — it deletes the draft and takes you back to the list, so you don't leave behind an automation you never finished. It's only offered for never-published drafts; anything with run history or a previous publish must be Archived instead (so its history is preserved).

Fix: grading results can't be published before outcomes are confirmed

When the grading review/confirm flow is on, recording an outcome creates a DRAFT — the rank, history and certificate side-effects only apply when you Confirm. Publishing now checks for confirmation, not just "an outcome exists", so draft outcomes can no longer be published before they're confirmed. (Clubs without the confirm flow are unaffected.)

Fix: SMS & Telegram automations send the right message

An SMS or Telegram automation step that used a saved template was rendering the template's EMAIL body instead of its SMS/Telegram text — risking blank or wrong sends. SMS now uses the template's SMS text and Telegram uses its Telegram text.

Automations: send yourself a test of any message step

Each Email, SMS and Telegram step in the automation builder now has a "Send a test" box at the bottom — type a recipient (email/mobile) and send the actual message with sample data filled in, so you can check it renders before going live. Telegram tests go to your club's admin Telegram recipients. It tests the real content — whether the step uses a saved template or your own text — so what you see is what your members would get.

Automations builder: cleaner list, view-and-edit, and a History link

• The automations list no longer has a per-row "send test" button (it sent to a fixed address

and wasn't useful) — use the per-step "Send a test" while building, or the end-to-end test in Settings → Automation Enablement.

• Opening a published trigger now shows it in the builder straight away (no "create a draft to

edit" step) — just make a change and Save, and it creates the draft for you, leaving the live version untouched until you publish.

• Each trigger now has a "History" link to its recent send activity.

What's new

Things that look saved really are saved

A reliability pass across the app so the screen never tells you something worked unless it actually did:

• Register — adding a walk-in. If adding a student to a register doesn't go through (locked register,

weak signal, a future date), the row now rolls back and you get a clear message — instead of a student who looks added but was never saved. Walk-ins still don't count against class limits.

• Student notes. Adding, editing, or deleting an internal note is now handled by our secured server.

If a save fails, your typed text, your edit, or the note itself stays put with a clear message — nothing silently disappears.

• Video reviews. A submission is only ever marked "reviewed" once the score is safely recorded, so a

green/amber/red can't go missing while the submission looks done.

• Closure notifications. Closures added from the calendar now actually notify affected members

(previously only the Settings → Closures path did) — within 14 days they queue a *lesson cancelled* message per affected member. The confirmation says notifications are *queued for affected members* rather than implying guaranteed delivery.

Student Profile → Billing tab no longer breaks on older records

The membership tab could show "We couldn't load this membership information" if a single background detail failed to load. It now shows everything it can and a gentle note about the rest, instead of hiding the whole tab.

Events can't be saved with impossible dates

Creating or editing an event now blocks date combinations that don't make sense — an end before the start, a booking cut-off after the event has started, or an early-bird deadline after the cut-off. You get a clear message and the save is prevented (on the form and on the server), so links can't go out with a cut-off in the past. Existing events are untouched.

Dialogs no longer hide behind the menu

Groundwork to stop pop-up dialogs ever appearing *behind* the side menu or student list: shared dialogs now render above everything on a consistent layering scale.

Automations — "Save draft" works again, and the builder is tidier

• Fixed: saving a Communications Trigger draft was failing silently (a 405 error) — it now saves

reliably in both the simple and advanced builders. Existing published triggers were unaffected.

• The trigger builder is now a focused workspace — the section nav pills are hidden while you're

editing, so it doesn't feel like another settings page.

• Picking when a trigger fires uses clear, scannable cards instead of a dropdown — now with a

search box and category filter pills so the right trigger is quick to find as the list grows. Choosing what it does (Email / SMS / Telegram / Delay) uses matching cards.

• The right-hand flow summary is restyled as an obvious view-only preview (it no longer looks editable).
• The builder title now updates live as you rename a trigger — no more stale "Untitled trigger" while

you're editing.

Safer refunds when a paid competition/event entry is cancelled

Cancelling a paid external-event entry is now protected against accidental duplicate refunds: a double-click, page refresh, or network retry can no longer create a second Stripe refund or double-count the refund on a shared (bundled) invoice — the refund is keyed so it happens exactly once. Partial refunds on bundled invoices and paired-entry cancellations are unchanged, and if a refund fails you now get a clear message and the entry is not marked cancelled.

Automations made simpler

The Automations area is now organised around three clear places instead of six engine-flavoured tabs: Build (make and manage your automations — the main screen), Activity (what ran, what's queued and anything that failed, now grouped together), and Settings (safety, sending state, Trigger.dev status, test recipients and any legacy-rule conflict warnings). Opening Automations now lands you on Build. None of the sending behaviour changed — this is purely how it's laid out and labelled.

Calendar week view now reads in time order

In week view, classes and events are now listed together in time order — a 9am event shows above a 6pm class, instead of all classes first then all events. Colours, trial markers, venue/location and click behaviour are unchanged. The day pop-out also scrolls properly now on desktop and mobile (no more cramped/stuck scrolling), with the date header and "Add event" button staying put.

Calendar: a proper full-page day view

Clicking a day in the calendar now opens a dedicated day page (/calendar/day/…) instead of the cramped slide-over, so it scrolls normally on desktop and mobile, has a clear Back to calendar button, and gives classes, events, trials and bookings real room. The day list is in time order, and add/edit/ cancel events, trials, invites and bookings work exactly as before. (Deep-linkable too — you can bookmark a specific day.)

Automations: archive, steadier tables, categories & a Templates home

• Archive a trigger or flow instead of deleting it. Archived automations stop

running but keep every version, run and delivery record, and you can restore them anytime (they come back as a draft to re-publish). A new Archived view lists them. Drafts that were never published and have no history can be Discarded outright. Archiving and discarding are owner/admin-only and fully audited.

• Tidier tables everywhere in Automations — long trigger names, error messages,

recipient addresses, provider IDs and cron routes no longer stretch or wrap the columns; they truncate with the full value on hover, and tables scroll sideways on small screens instead of crushing. Status, type, channel, version, date and action columns stay on one line.

• Categories on the Build list — quick category chips (Membership, Payments,

Trials, Events…) plus a small category tag on each row, and search now matches the category too.

• Templates under Automations — the message templates your automations send now

have a home right next to Build, alongside the existing Settings location.

A clearer Comms Centre

The communications area now hangs together as a Comms Centre: from the message composer you can jump straight to Templates and Deliverability, which now have their own pages alongside Comms, Automations and the Comms Map — all reusing the same panels you already knew from Settings (Settings keeps them too, so nothing moved out from under you). Email templates are much easier to find from the comms area.

In Automations → Build, each trigger now has a tidy ⋯ More menu to Archive it (it stops running but keeps its history) or Discard an unpublished draft, with an Archived view to restore from. Nothing about how messages send has changed.

Fix: archived legacy automations no longer block new triggers

Archiving a legacy automation in Settings now fully retires it — the new Communications Triggers area no longer flags it as a conflict, and it can never make a builder trigger defer. (The legacy guard now ignores archived rules, and archiving also disables the rule.) No change to how anything sends.

Automation builder: club + member merge tags now resolve

Builder-trigger emails can now use the club and member personalisation tags — {{club_name}}, {{club_logo_url}}, {{club_email}}, {{club_contact}}, plus {{belt_rank}}, {{belt_system}}, {{membership_plan}}, {{mobile}}, {{household_name}}, {{age}} and more — not just the recipient name + each trigger's own tags. The builder's tag picker now offers exactly the tags that will resolve for the selected trigger (so no more tags that render as literal {{…}} text). No change to who is emailed or whether — only what the message can say.

Domain-proof email logos (inline/CID embedding)

For gold-standard multi-tenant deliverability: the club logo can now be embedded directly in each email as an inline (CID) attachment instead of linking to an external image URL. With no external image, there's nothing to mismatch the sending domain — so the "host images on your sending domain" warning can't apply, no matter which domain a club sends from. Behind a flag (EMAIL_INLINE_IMAGES, off by default) and fully fail-safe: if the logo can't be embedded for any reason, the email still sends exactly as before with the logo as a normal image. The in-app "view email" preview keeps the image URL so it still renders in the dashboard.

Fix: no more duplicate booking/automation confirmations

When a club publishes a Communications Trigger for an event (e.g. event booked), the legacy automation engine's built-in default email no longer also fires — so members get ONE confirmation, not two. The legacy default now stands aside whenever a live builder trigger covers the event; clubs that haven't built a trigger keep their default as before.

Automations Activity: see a preview of what was sent

Each delivery row in a run's detail now shows a short preview of the message that went out, so you can tell at a glance what was sent. The full rendered email remains in Communications history.

Cleaner, honest automation merge tags

One canonical merge-tag registry now drives the automation builder, the email-template editor, previews, and docs — so every tag a club is offered genuinely fills in.

• Builder pickers only show tags that resolve for the chosen trigger. Member details

(belt, plan, etc.) are no longer offered on trial/waiting-list triggers, where there's no member record yet — they'd otherwise have shown up blank.

• Event automations got the full event pack. An "Event booked" automation can now use

{{event_time}}, {{event_end_time}}, {{event_location}}, {{event_cost}}, {{earlybird_price}}, {{earlybird_deadline}}, {{booking_cutoff}}, {{cancel_link}} and {{invoice_pdf_url}} — the same details the confirmation email already used.

• Unknown-tag warning in the template editor. If a template uses a tag that won't fill in

(a typo, or a tag that doesn't apply to automations), the editor flags it — without blocking your save.

• New "Automation tags" reference doc; nothing about how emails actually send has changed.

What's new

More payment flows are now self-healing after a successful payment

• The same protection that makes paid event bookings recoverable now covers insurance renewals,

waitlist "claim your spot" payments, and external-event entries. If a parent's device drops the connection right after their card is charged, our Stripe safety net finishes the job automatically — the renewal is recorded, the waitlist spot is promoted (or refunded if the event filled in the meantime), and competition entries are confirmed and locked.

• These public payment pages now never show a "failed / try again" message after a payment has

actually gone through. Instead they show a reassuring "Payment received — we're confirming this automatically" message with a payment reference, so no one is ever prompted to pay twice.

• A grading/event booking link now refuses to start a second charge if that place is already

booked or paid for.

Staff can confirm an invited student straight onto the booked list

• On an event's invite list, staff now have a "Confirm" action: it adds the invited student

directly to the booked list without the parent needing to use the public booking link.

• A confirmation prompt makes the money state obvious — for paid events it warns that *payment

will remain unpaid/pending unless you collect it separately*. It never marks a booking as paid unless a real payment exists.

• It's safe to click more than once (already-booked is a no-op), respects event capacity (a full event

adds them to the waitlist, and promotes a waitlisted student only if a place is free), and only ever sends one confirmation. Owners/admins can use it; it's blocked in demo mode.

Paid event/grading bookings can no longer "fail" after a successful payment

• Previously, if the booking step hiccuped *after* a card payment had gone through (a dropped

connection, the page closing), the parent could see a scary "Booking failed" message even though the money had been taken.

• Now a successful payment is always recoverable. The booking is confirmed by our secured server,

and a Stripe safety net finishes the job automatically even if the parent's device never completes the flow. The confirmation step is idempotent, so retries can never double-book or double-charge.

• If for any reason the booking can't be confirmed instantly, the parent sees a reassuring **"Payment

received — we're confirming your booking automatically"** message with a payment reference, instead of an error.

• A booking link can now only ever create one Stripe payment, even if it's opened on two devices.

_Behind the scenes: a shared reconcilePaidEventBooking path is now used by both the payment-confirm route and the Stripe webhook; if an event fills up between the invite and payment, the booking is kept as waitlisted + paid (unchanged behaviour) for staff to promote or refund._

Member data is loaded through our secured server — everywhere

A privacy/data-protection pass: every screen that lists members — including the grading panel roster — now loads names, dates of birth and grade info through our secured server with the club checked on every request, instead of the browser reading the database directly. Nothing changes in how the screens look or work; the data just takes a safer path. (This completes the work so that no member list is read directly by the browser anymore.)

Grading results: tighter controls

• Recording a grading outcome (pass / late / no-show / unsuccessful) now requires a coach or above —

view-only accounts can no longer record results.

• Grading promotions are being moved so the server decides and validates the awarded grade (you

can't promote a member sideways, backwards, into the wrong belt system, or skip grades unless an examiner deliberately chooses a different belt). The double-promotion option on the panel is unchanged. _(This stronger validation switches on with a database update; until then the existing checks stay in place.)_

• New: a review-and-confirm step for grading results is being introduced behind a per-club setting (off by

default — nothing changes for your club until it's switched on). When it's on, marking results saves them as drafts; each member shows a status (Draft / Ready / Needs attention / Confirmed / Published); and a Review promotions screen lets an admin see each "current grade → new grade", spot any blocked awards, and Confirm them all at once. After confirming, a change goes through an audited correction (reason required) rather than a silent undo. Publishing and certificates are unchanged for now.

Event booking cut-off dates are checked as you type

The booking cut-off on the event form now validates immediately instead of only when you hit Save:

• The field shows a friendly inline error the moment a date is out of range, and Save is disabled until

it's fixed — no more typing a whole event then getting rejected on Save.

• The rules are now clearer and consistent: the cut-off must be on or before the event date, can't be

before today on a new event, and can't be before the date the event was created when you edit one.

• Move an event's date earlier than its cut-off and the cut-off field highlights so you can correct it.
• The form also now loads the existing cut-off when you edit an event (it previously didn't show it).
• Older events with an invalid cut-off still open normally, but you'll be asked to fix the cut-off before

saving any change. The server enforces the exact same rules, so nothing slips through.

What's new

Behind the scenes — Settings tabs now fetch their member data through our secured server

• The Settings tabs that show member-impact info — the Grades & Programs archive warnings ("N

members are on this"), the Schedule Insights capacity planner, and the Closed Dates conflict previews (which trials/regulars a closure affects) — now load that data through our secured server, with your club always taken from your signed-in session.

• Everything is unchanged: same counts, warnings, capacity figures and conflict lists. The archive

warnings now receive only a count (no member details at all), and member contact details are no longer read directly by the browser. Purely a security/hardening change.

Behind the scenes — the calendar's trial lists and event invites now fetch through our secured server

• The calendar trial views — the day-detail panel, the Trials list, the calendar trial counts, the

closure-conflict check, and the event-invite student search — now load their data through our secured server, with your club always taken from your signed-in session.

• Everything behaves exactly as before: same trials, dates, statuses, counts, ordering and search

results. Trial contact details (and members' dates of birth, except where the "convert to student" step genuinely needs them) are no longer read directly by the browser. Purely a security/hardening change.

Behind the scenes — search, the dashboard activity feed and the staff inbox now fetch through our secured server

• The ⌘K command palette search index, the dashboard's Recent Activity feed, and the **staff

action inbox** now load their member data through our secured server, with your club always taken from your signed-in session.

• Everything looks and works the same — same search results, labels, ordering and inbox items. Member

contact details and SMS message text are no longer read directly by the browser. Purely a security/hardening change.

Behind the scenes — the Student Analytics report now fetches its students through our secured server

• The Student Analytics report (age/grade/tenure distributions, attendance alerts, promotion

analytics, timetable utilisation and the top-attenders/overdue tables) now pulls its student roster through our secured server, with the club always taken from your signed-in session.

• Members' dates of birth no longer leave the server for this report. The age groups and ages it

shows are now worked out server-side and only the age (and age band) are sent to your browser — the raw date of birth stays put. Every figure, chart bucket and the programme-lens behaviour are identical; only where the date of birth is handled changed. A privacy/data-minimisation improvement.

Behind the scenes — the Progression report now fetches its members through our secured server

• The Progression report (rank distribution, promotions, grading pass rate, the per-event

breakdown and the overdue-for-grading list) now pulls its student roster through our secured server instead of reading it directly in your browser. The club + permission checks live on the server, and your club is always determined from your signed-in session.

• Nothing on the report changes — every count, label, colour and the programme-lens filter behave

exactly as before. This is purely a security/hardening change.

Behind the scenes — the Membership report now fetches its members through our secured server

• The Membership report (active/joiner/leaver/retention stats, plan and syllabus distribution,

the plan-breakdown revenue table and the joiners-vs-leavers charts) now pulls its student roster and its household-membership records through our secured server, with the club always taken from your signed-in session.

• Every figure is identical — including Total Monthly Revenue and the per-plan revenue column.

The revenue calculation itself is unchanged; we only moved where the member and household lists are read from. Purely a security/hardening change.

What's new

Saves now fail loudly, not silently

• If a save ever doesn't go through — your session quietly expired, the connection dropped, or the

server said no — the app now tells you and undoes the change on screen, instead of looking saved when it wasn't. Tap again once you're back and it'll save properly.

• This now covers: register (sealing/unsealing a class, adding coaches/volunteers and their

status, marking event attendance, adding an ad-hoc booking), trials (status changes from the trials list, the pipeline, and the register), grading (the examiner equipment/criteria checklist), tasks (create, edit, status, delete), and venues + timetable (add, edit, archive, restore).

• On the register, if an event's attendee list can't load, you'll now see a clear "couldn't load —

retry" message instead of an empty list that looks like nobody's booked.

• All of these now save through our secured server with the same club + permission checks as the

rest of the app — so nothing important relies on the browser quietly succeeding.

Behind the scenes — the Insurance report now fetches through our secured server

• The Insurance report (valid / expiring / expired counts and the renewal rate) now pulls its

member data through our secured server, the same way the other reports already do.

• Your numbers are unchanged — only where the data is fetched moved. The figures are still

calculated exactly as before, so every total stays identical.

• This continues the work of keeping member information off the browser and behind server checks.

Security — stronger throttling on public links

• Some public links (the insurance renewal page and the external-event cancellation page)

now apply the same rate-limiting on their initial load that they already used on submit — closing a small gap so the links can't be hammered or enumerated.

• No links changed or expired; this is purely an extra layer of protection.

Behind the scenes (no action needed)

• Completed a full audit pass of the platform's reports, public links, file storage, and the

workflows that touch money — documenting exactly where data is shaped server-side, where public links stand on expiry/throttling, and which money workflows still need extra protection. These audits guide the next rounds of hardening; nothing in them changes how the app behaves today.

What's new

Fix — "On the mat now" in Assessments now shows everyone present

• In Assessments, the "On the mat now" filter could leave some grades looking empty even

when members of that grade were marked Present/Late on today's register — most noticeably for certain tag grades.

• The cause: that filter was also (incorrectly) requiring the member's class to be tagged to the

grade's programme. If today's class was untagged, or tagged to a different programme, the member was hidden — even though they were clearly on the mat.

• Now fixed — "On the mat now" shows any member of that grade who's Present/Late today,

regardless of which class it was logged against. The separate "lessons since last grading" count still only counts that programme's classes (so a member's other-discipline sessions don't inflate it), and that count now reads the programme from the grade itself rather than guessing from the first student in the list — so one mis-tagged member can no longer skew a whole grade.

Behind the scenes — your Reports now fetch data through our secured server

• Every figure on the Reports screen — Trial Funnel, Events, Households, the Owner

Overview dashboard, and the Financial report — now pulls its underlying data through our secured server rather than directly from your browser. This keeps each club's member and money data more strictly separated.

• Nothing about the numbers has changed. Every total, conversion rate, revenue figure,

household count and chart is calculated exactly as before — we only changed *where* the raw data is fetched, not the maths. The programme lens (filtering a report to one programme) works exactly as it did.

• Money is still counted to the penny, and the Financial report still falls back gracefully

if an optional feature isn't switched on — so you'll never see a misleading "£0".

• If a report ever can't load, it fails safely with no risk of showing another club's data.

Behind the scenes — a new automatic safety check

• We added an automatic check to our build process that **flags any new screen that tries to

read sensitive member data (child details, payment records, safeguarding notes) directly in the browser** instead of through the secured server.

• This is purely an internal safeguard for us as we keep tightening data protection ahead of

the wider rollout — there is no change to anything you see or do in the app.

What's new

Fix — your allowed embed websites now stay visible in Settings

• In Settings → Club details, the list of websites allowed to embed your trial

booking form (the "embed origins") saved correctly, but after leaving the page and coming back the list could appear empty — even though the saved sites were still in place and still working on your real booking pages.

• This was a load-order glitch on the settings page: the page loaded your saved sites,

then a moment later overwrote the on-screen list with a blank one. Your data was never lost — only the on-screen display was wrong.

• Now fixed — the saved websites reload and stay shown every time you open the page.

Nothing about how the trial booking embed actually works has changed.

Behind the scenes — stronger protection for member data

• We continued moving sensitive member information (membership details and now **grading /

assessment progress) so it's fetched through our secured server** rather than directly by your browser. This tightens how member data is kept separate between clubs.

• No change to what you see or do — your grading screen, RAG syllabus scoring, belt history

and rank switching all work exactly as before, and grading, rank changes and publishing are untouched.

• If one of these screens ever fails to load, you'll now see a clear **"couldn't load — try

again"** message instead of a screen that silently stays blank.

Behind the scenes — student notes now load through the secured server

• Student profile → Notes now loads the notes list through our secured server (same as the

grading and membership data), keeping member information cleanly separated between clubs.

• No change to what you see or do — notes look the same, the newest stays on top, "important"

notes are still highlighted, and adding/editing/deleting a note works exactly as before. If the list ever fails to load you'll now see a clear "couldn't load — try again" message.

Behind the scenes — class enrolment list loads through the secured server

• On a student's Membership / assessment screen, the class enrolment list and member types

now load through our secured server (same approach as the other member screens), keeping each club's data cleanly separated.

• No change to what you see or do — your classes show in the same order, the day filter and the

enrol/edit controls work exactly as before. If the class list ever fails to load you'll see a small "couldn't load — try again" prompt.

Behind the scenes — membership details on the assessment screen

• On a student's Membership / assessment screen, the **plan, household plan, and

family-discount details** now load through the same secured server route as the main Membership tab, keeping each club's data cleanly separated.

• No change to what you see — the current plan, household plan panel, family-discount price and

sibling position all display exactly as before. A small "couldn't load — try again" prompt now shows if that information fails to load.

Behind the scenes — grading details on the assessment screen

• On a student's Membership / assessment screen, the **syllabus grid, RAG scores, classes-since-

grade and belt history** now load through the same secured server route as the standalone Grading tab, keeping each club's data cleanly separated.

• No change to what you see or do — the RAG grid, readiness percentage, rank switching, belt

history and assessor names display exactly as before, and scoring/grading actions work unchanged. A small "couldn't load — try again" prompt shows if grading info fails to load.

What's new

Security — settings/config writes moved behind guarded server routes

Status: Pending enablement (deploys with the next release)

• Several Settings screens used to save straight from the browser to the

database. They now go through guarded server routes that check your role, block the demo club, scope every change to your own club, and record an audit entry — the same as billing, member and automation changes already do.

• Covered in this release: email templates (create / edit / archive /

restore / duplicate), closure dates (including the "add UK bank holidays" bulk action and calendar closures), event types, coach availability windows, and club terms.

• Nothing changes in how these screens work for you — the same buttons save

the same things with the same results. The difference is that the server is now the authority: it sets the club, validates the input, and ignores anything it isn't expecting, so a stale browser tab or a non-admin account can't make a change it shouldn't.

• A small hardening along the way: removing a coach availability window is now

scoped to your club on the server, so a window can only ever be removed from your own club.

Security — grades & syllabus setup now saved server-side

Status: Pending enablement (deploys with the next release)

• The Grades, Syllabus, Requirements and Grade-types setup screens

(plus the matching onboarding steps) used to save straight from the browser. They now go through guarded server routes that check your role, block the demo club, and record an audit entry — exactly like the other settings screens.

• Covered: belt systems / programs, grades (belt ranks), syllabus items, grade

types, and program requirements — create, edit, archive, restore, reorder, and the grading checklist/requirements configuration.

• No change to how grading itself works — recording results, scores,

rank changes, publishing and the register are untouched. This release only moves where the *setup* of your grades and syllabus is saved.

• The server also checks that a grade belongs to one of your own belt systems (and a

syllabus item to one of your own grades) before saving, so nothing from another club can ever be referenced.

Security — the register now saves attendance through a guarded route

Status: Pending enablement (deploys with the next release)

• Marking the register (present / absent / late, adding or removing an ad-hoc

member) used to write to the database straight from the browser. It now goes through a guarded server route that checks your role, blocks the demo club, and confirms the class and member belong to your club before saving.

• The register works exactly as before — same buttons, same speed, same

optimistic updates, same class-usage counting, lens/programme filtering, and trial marking (trials are saved the same way they always were). Nothing about how you take a register changes.

• Marking is idempotent: tapping a member twice, or two coaches marking the

same member, always lands on the latest status — it can never create duplicate attendance rows (the database already enforces one row per class / member / day).

Security — assessment scores now saved through a guarded route

Status: Pending enablement (deploys with the next release)

• Recording syllabus assessment scores (the red / amber / green taps on the

assessment grid, the student grading tab, and the membership assessment tab) used to write straight from the browser. They now go through a guarded server route that checks your role, blocks the demo club, and confirms the member and syllabus item belong to your club before saving.

• Assessing works exactly as before — same red/amber/green taps, comments,

tapping a score again to clear it, and the same instant (optimistic) updates. Nothing about how you assess changes.

• A score tap can only ever write a score — it can't touch a member's rank, grade,

grading result, or anything that gets published. Scoring stays cleanly separate from grading outcomes.

• Scores are idempotent (one row per member + syllabus item): re-tapping, or two

coaches scoring the same item, always lands on the latest value — never duplicates.

Security — first-run club setup now saved through a guarded route

Status: Pending enablement (deploys with the next release)

• The new-club setup wizard (your club name / contact / email / currency on the first

step, and the "finish setup" step) used to save straight from the browser. It now goes through a guarded server route that confirms you're signed in and only ever updates your own club, with a strict list of allowed fields — it can't be used to touch anything else about a club.

• Setting up a new club works exactly as before — same steps, same result.
• With this change, every sensitive write across the app now goes through a checked

server route. None of these are behaviour changes for you — they're the last pieces of a behind-the-scenes hardening pass that makes the app safer to run for multiple clubs.

Reliability — class-usage counting can no longer be over-counted on the register

Status: Pending enablement (deploys with the next release)

• For members on a per-class or class-limited plan, the register counts how many

classes they've used. Previously the browser worked out whether a mark should add or remove a class from that count, using its own (possibly out-of-date) view of the member's last status. If two coaches marked the same member at the same moment, both could add a class — over-counting their usage.

• Marking the register now records the attendance and adjusts the class-usage

count in one server step, worked out from the member's true saved status — so a class is counted exactly once, no matter how many coaches or taps land together. Re-tapping the same status, or switching Present ↔ Late, never changes the count; the count never drops below zero.

• Taking a register feels exactly the same — same buttons, same speed, same

optimistic updates, the same "reached their class limit" warning. The fix is entirely behind the scenes.

What's new

Security — internal error details no longer surfaced

Status: Pending enablement (deploys with the next release)

• When something goes wrong on the server, the app used to occasionally pass

the raw underlying database/system error text back to the browser. Across the whole API that's now scrubbed — you get a clear, generic "something went wrong" message instead, while the full technical detail is logged securely on the server for us to diagnose

• This closes an information-disclosure gap on 159 API routes (sign-up,

billing, invoices, households, the member portal, staff management, events, automations, voice notes and more) without changing any behaviour: the same actions still succeed or fail in exactly the same way, with the same status codes — only the error *wording* shown to the browser is tightened

• Friendly, action-specific messages you actually need (e.g. "This person is

already a staff member of this club", "effective_date must be YYYY-MM-DD") are preserved untouched — only leaked internal detail is removed

• A new automated guard keeps it that way: the build now fails if a future

change reintroduces a raw internal error message into an API response

Part of an ongoing security-hardening pass. No prices, permissions, or workflows are changed — this is purely a tightening of what error information leaves the server.

Security — staff permissions always reflect your role in *this* club

Status: Pending enablement (deploys with the next release)

• Across payment connections, module/billing settings, certificate templates,

grading publish/certificates and event actions, the app now always checks the role you hold in the club you're working in — read from the authoritative per-club membership — rather than an older "primary club" role that could be out of date

• This closes a gap where someone demoted in a club could briefly keep a

higher level of access there, and fixes the opposite case where staff who help at more than one club were sometimes wrongly blocked from a club they genuinely manage

• For the vast majority of staff (a single club, one role) nothing changes —

same access, same screens. No permissions are widened; if anything this is slightly stricter and more accurate

• A new automated check keeps every staff-facing route on this single, correct

source of truth so the inconsistency can't creep back in

Security — demo, public links and club boundaries, locked down

Status: Pending enablement (deploys with the next release)

• The demo is now fully look-but-don't-touch. Anyone exploring the

try-it-out demo club is in a genuine sandbox — every save, edit and delete across the whole app is blocked from ever changing demo data, so the demo always looks clean for the next visitor and can never spill into a real club

• Shared/public links now carry only what they need. Where the app hands out

a link that doesn't require a login (e.g. an invitation or a form), the page behind it now receives just the data needed to do that one job — nothing extra about other members or your club is sent to the browser

• Your club's data stays inside your club — automatically. We've added an

automated guard that checks every place the server writes data and confirms it is tied to a specific club. If a future change ever tried to write without that club boundary, the build stops it before it can ship. This makes "one club can never see or touch another club's records" a rule the system enforces for us, not something we have to remember

• For you day-to-day, nothing changes — same screens, same actions, same

data. These are guard-rails working quietly in the background to keep every club's information separate and the demo safe

All part of the same security-hardening pass: no prices, permissions or workflows change — just stronger, automatically-enforced boundaries around who can touch what.

Security — grading routes moved onto the shared safety wrapper

Status: Pending enablement (deploys with the next release)

• The grading and examiner endpoints (publish/unpublish results for a single

event or a whole session, scoring criteria, the live "who's on the mat" scoring group, and examiner scoring-link management) now run through the same central safety wrapper the rest of the app uses — one place that checks you're signed in, holds the right role, and isn't the demo club, before any write

• Publishing and unpublishing grading results stays owner/admin-only, exactly

as before; the live scoring tools and criteria stay open to all staff, exactly as before. Nothing about who can do what changes — this just routes those checks through the shared, automatically-tested path instead of hand-written copies in each file

• The login-free examiner scoring links are untouched: still throttled, still

scoped to one club + one session, and still sending the panel only a student's name and rank — never a date of birth or household detail

• New focused tests pin the high-risk grading actions (record an outcome,

publish, unpublish, save a judge's score): another club's record is refused, the demo is blocked, and the right role still succeeds — so these can't quietly regress in future refactors

For you day-to-day, nothing changes — same screens, same actions, same results. This is internal plumbing on the same hardening pass.

Security — public links that age out safely

Status: Pending enablement (deploys with the next release)

• We reviewed every login-free link the app sends out — examiner scoring

links, insurance-renewal links, enrollment invites, competition-entry invites, trial cancel/reschedule links, invoice PDFs, the family calendar feed and unsubscribe links — and confirmed each one is throttled against abuse and only ever shows data for the right club

• Competition-entry invite links now age out. A very old, unused

competition-entry invitation link is now politely declined instead of staying live indefinitely — staff can simply re-send a fresh one. The window is deliberately generous (far longer than any real entry deadline), so links parents are actually using are completely unaffected

• Nothing already in your inbox breaks. This was done carefully so that

links already sent out keep working exactly as before — we only close down links that are effectively dead anyway

• A new automated guard keeps an inventory of every one of these public links

and fails the build if a future link ever ships without abuse-throttling or a documented reason — so the standard is enforced for us, not just remembered

Security — admin-only actions locked down server-side

Status: Pending enablement (deploys with the next release)

• Bulk member import and transferring a student to another club now

require an admin role on the server, not just in the screen. These were always admin-only buttons in the app, but a determined non-admin could previously have triggered them by other means — now the server enforces it too. If you use these features as an owner or admin, nothing changes

• Behind the scenes we moved refunds, GDPR erasure, student transfer and

several grading actions onto a single shared permission-and-safety checkpoint, so every one of them is consistently blocked on the demo club, consistently scoped to your own club, and returns a consistent "not allowed" message. No change to how any of these work for the right person on the right club

What's new

New — Programme Review export

Status: Pending enablement (deploys with the next release)

• From the Assessments screen there's a new Export Review action that

produces a clean PDF of the students and syllabus items that need review — defaulting to the Red and Amber scores, so you get a ready-made worklist for the next few weeks

• The PDF is grouped by grade, then syllabus item, and each line shows

the student, their RAG status, the latest comment, how many comments there are, and when the score was last updated

• You can tune it before exporting: choose the programme and grade

(or all grades), pick which of Red / Amber / Green to include, limit it to just the candidates you currently have filtered on screen, and decide whether to include the latest comment, all comments, or none

New — Student assessment progress PDF

Status: Pending enablement (deploys with the next release)

• A parent/member-friendly progress report for a student's current grade,

available from the student profile actions menu and as a quick one-tap download on each assessment row

• Uses friendly language instead of traffic-light jargon — **Red → Needs

practice, Amber → Developing, Green → Secure** — with an at-a-glance "percent secure" and a clear summary of where they're up to

• Options let you include the coach's comments, show or hide the

already-secure items, and show or hide items not yet assessed

Both exports are generated securely on the server, scoped strictly to your own club's data, and don't change anything about how assessments are scored. They carry your club logo and name, a clean heading and the date generated, and show a tidy empty state when there's nothing to report.

Reliability — Exact-pence money model (behind the scenes)

Status: Pending enablement (rolls out in stacked, reviewed releases)

• Money across invoices, line items, membership plans, charges and events is

moving to exact integer pence alongside the existing decimal amounts, so there's never any rounding drift in what you're invoiced, what's collected by card or Direct Debit, or what your reports add up to

• Every place that writes money now records the exact pence at the same time,

and the change is fully backwards-compatible — existing amounts are preserved untouched and keep working

• Card and Direct Debit collections, recurring Direct Debit set-ups, and

insurance/renewal payments of an existing invoice or plan now charge the exact stored amount

• Reports, invoice and billing screens, payment pages and invoice PDFs now

read from the exact pence too (falling back to the older decimal only for historical records), so every figure on screen matches what's charged

• Fix: the Financial report's headline revenue, outstanding and refund

figures were being shown at 1/100th of their true value (a recent display bug); they now show the correct amounts. No prices changed — only the Financial report's displayed totals are corrected

• No prices or plan amounts are changed anywhere — this is a correctness and

reliability improvement to how money is stored, processed and displayed

What's new

Improved — One clean icon set everywhere

Status: Pending enablement (deploys with the next release)

• The main navigation, top bar and parent portal now use a single,

professionally drawn icon set instead of a mix of inline graphics and emoji — so every menu, tab and button looks like part of one product

• The automation builder's step icons (email, SMS, wait, condition,

notify, tag, and so on) now share that same crisp set, in both the visual flow view and the simple list view

• Activity feeds — both the dashboard "what just happened" widget and a

student's own timeline — now draw promotions, payments, notes, emails and the rest from one shared icon map, so the same event always looks the same wherever you see it

• Tasks, Smart Planning tabs and the register's lock / warning / booking

banners have all moved to the new icons too

• The register screen is now fully consistent end to end — class lists,

venue and headcount markers, trial counts, the health and lesson-plan buttons, over-capacity and closed-club notices, birthday and blocked markers, and the catch-up / cancel-booking controls all share one set

• A student's activity timeline matches too: empty state, View PDF link,

the newer/older pagination controls and the email-preview close button

• Reports now share the set as well — the summary stat cards on the

Accident, Owner Overview and Portal Analytics reports, the attendance alert flags (ghost, declining, comeback and the rest) on the Student Analytics report, and the field tick in scheduled-report setup

This is a polish pass: nothing about how these features work has changed — they just look sharper and more consistent. Icons that are purely decorative are hidden from screen readers, while icon-only buttons keep their proper labels.

Improved — Reports tell the truth about your programme lens

Status: Pending enablement (deploys with the next release)

For clubs running more than one programme (e.g. Martial Arts and Dance), reports are now honest and consistent about which programme's numbers you're looking at:

• Every report now says exactly what it's showing — **"<Programme> lens

applied", "All programmes", "Club-wide report", or "Lens filtering not available for this report yet"** — so you never see a programme label sitting over whole-club numbers

• Many more reports now actually filter by the lens: Membership, Renewals,

Progression, Student Analytics, Accidents, Waiting Lists, Households and the Owner Overview, alongside the ones that already did

• Financial figures are attributed per programme from invoice line items,

so one programme's revenue is never visible under another's lens (outstanding, aging and refunds stay club-wide and say so)

• Reports can now look back through an archived programme — archived

programmes are hidden from day-to-day menus but available in the reports lens picker under "Archived"

• Historic reports attribute records to the programme they happened in

(and to who was enrolled at the time), so moving a member between programmes no longer rewrites their history

Under the hood, programmes are now lifecycle-safe: they're archived rather than deleted (a programme with linked history can't be hard-deleted), a member changing programme properly closes the old enrolment and opens a new one, and attendance now records which programme it was for.

What's new

Improved — Every page now shares one layout shell

Status: Pending enablement (deploys with the next release)

• All signed-in pages now share a single layout foundation — the same

background colour, content width, padding and section rhythm — so moving between Dashboard, Households, Students, Automations, Tasks, Enrolments, Reports and the rest no longer shifts or jumps

• Reading-style pages (changelog, feedback, inbox) use a narrower column

of the same shell so forms and articles stay comfortable to read

• Menus, the navigation drawer and the mobile menu now share the same

panel colour as dialogs, so every floating panel feels like part of one product

Today is about consistency: one shared design system across the whole platform, so every page uses the same buttons, the same status colours and the same layout rhythm.

Fixed — Top-nav menus now work by tap and keyboard, not just hover

Status: Pending enablement (deploys with the next release)

• The Students / Calendar / Gradings / More menus in the top bar were

hover-only, which is unreliable on tablets where the desktop nav shows but there's no mouse. They now open on click/tap, close on Escape (returning focus to the button), close when you click outside, and expose proper open/closed state to screen readers

Improved — Dialogs keep keyboard focus where it belongs

Status: Pending enablement (deploys with the next release)

• Shared dialogs now trap keyboard focus inside while open and return it

to the control that opened them on close — the standard behaviour keyboard and screen-reader users expect

Fixed — Rounded corners no longer leak onto mobile

Status: Pending enablement (deploys with the next release)

• Cards and panels that are only meant to be rounded on larger screens

(e.g. a layout that goes flush-to-edge on a phone) were getting a rounded corner on mobile anyway, because of how the global corner styling matched class names. The flat-12px corner rule now uses proper theme radius tokens, so responsive corners behave per screen size and the "bold" / "minimal" themes still get their own corner treatment

Fixed — Top navigation no longer overflows on smaller laptops

Status: Pending enablement (deploys with the next release)

• On ~1280px-wide screens the top bar's right-hand icons could run off

the edge of the screen. The bar now uses tighter spacing on mid-size screens and tucks the two lowest-priority icons (Reports, Accident Report) into a "More" menu until there's room to show them inline

Improved — Bigger touch targets on phones and tablets

Status: Pending enablement (deploys with the next release)

• Navigation pills, in-page tabs and the top-bar icons now meet the

44px minimum touch-target size on touch devices, so they're easier to tap accurately (no change on desktop with a mouse)

Improved — More status badges share the global colour language

Status: Pending enablement (deploys with the next release)

• The household member list, external events, communications map and

email-template versions now draw their status chips from the same five-colour vocabulary as the rest of the app — so, for example, a "leaver" reads as a calm neutral grey everywhere instead of alarming red in one place and grey in another

• Extended in a follow-up to the external-event detail page (event,

payment and organiser-approval chips) and the member profile header, with shared colours added for awaiting / confirmed / rejected, open / closed and partial-refund states

Fixed — The whole app now actually renders in its intended font

Status: Pending enablement (deploys with the next release)

• The platform ships the Geist typeface, but a leftover line in the

base styles was silently overriding it with Arial everywhere — so the whole app had been rendering in the system fallback font. Geist now applies app-wide, with a clean fallback stack if it ever fails to load

• Tightened the type scale for a more premium feel: a consistent base

body size and slightly larger card titles, matching the rest of the spacing and heading rhythm

Improved — Subtle motion (first pass)

Status: Pending enablement (deploys with the next release)

• Introduced a shared motion system: the dashboard's sections and stat

tiles now ease in gently as the page loads, and dialogs animate both open and closed (previously they only animated open and then vanished)

• All of it respects the "reduce motion" accessibility setting — if your

device asks for reduced motion, the movement is dropped and only a quick fade remains

Improved — Every page now eases in

Status: Pending enablement (deploys with the next release)

• Navigating between pages now plays a quick, subtle fade-and-rise so the

app feels alive as you move around — applied globally to every signed-in page in one place, rather than page by page

• Slightly more present than the first pass (a touch more movement, still

well under a third of a second), and dashboard cards now lift gently on hover. Fully disabled for anyone who's asked for reduced motion

Improved — Subtle motion (second pass)

Status: Pending enablement (deploys with the next release)

• Building the steps of an automation now animates: adding a step slides

it gently into place, removing one eases it out, and re-ordering steps glides them to their new position instead of jumping

• New shared building blocks for the rest of the rollout: page headers

ease in on load, a "Save → Saving… → ✓ Saved" button state for forms, and a soft one-time row highlight after a table row is saved, paused or retried (so tiny updates don't need a full pop-up notification)

• Reordered the motion so heavy, frequently-used libraries only load

where they're needed (the automation builder), keeping everyday pages lean

Improved — Builder step editor + more consistent status colours

Status: Pending enablement (deploys with the next release)

• The automation builder's step editor now uses the shared dialog, so it

gets the same focus trapping, Escape-to-close and open animation as every other dialog

• The top-nav menu arrows now flip based on whether the menu is actually

open (they previously keyed off hover, which didn't fit the new tap-to-open menus)

• Status chips on the Trials list, the Comms Flows settings tab and the

automation queue panel now use the shared colour vocabulary too

Improved — One colour language for every status

Status: Pending enablement (deploys with the next release)

• Every status the platform shows — active, paused, sent, delivered,

failed, bounced, overdue, scheduled, running, succeeded, cancelled, suppressed and more — now draws from a single five-colour vocabulary: green = healthy, blue = in flight, amber = needs attention, red = failed or blocked, grey = inactive or historical

• The same status is now the same colour and the same word on every

page, and a status the system hasn't seen before still renders as a tidy neutral chip instead of breaking

Improved — Shared building blocks for every page

Status: Pending enablement (deploys with the next release; pages adopt these progressively)

• One standard kit now powers page headers, stat tiles, cards, forms,

tabs, tables and dialogs — so every page gets the same layout rhythm, the same loading and empty states, and the same button behaviour (including the double-click protection on anything that saves)

• Tab strips that overflow on small screens now show a soft fade at the

edge so it's obvious there are more tabs, and the active tab always scrolls into view when you arrive from a link

• Confirmation dialogs follow one pattern: they tell you exactly what

will happen ("This will send to 142 recipients") before you commit, and the confirm button can't be double-pressed

• Tables get a consistent treatment everywhere: a loading shimmer, a

friendly empty state with a next step, a clear error with "Try again", and a card layout on phones instead of a squashed table

Improved — Students directory: clearer confirmations

Status: Pending enablement (deploys with the next release)

• Bulk actions in the member directory now confirm in a proper dialog

that says exactly what will happen — "This will email 23 students who aren't linked to Telegram yet" or "This will set 8 selected students to leaver" — instead of a bare browser pop-up

• Results arrive as quiet corner notifications ("Telegram invites

sent — 23 emailed, 2 skipped") rather than blocking alert boxes, and a failed bulk update keeps your selection so you can retry

Improved — Automations statuses join the shared colour language

Status: Pending enablement (deploys with the next release)

• Run, send and delivery statuses across the Automations Command Centre

now use the platform-wide status colours — a failed run is the same red as a failed email everywhere else, and the colours follow your light/dark theme instead of fixed palette values

Improved — Invoice statuses match everywhere

Status: Pending enablement (deploys with the next release)

• Paid / Unpaid / Overdue chips on the member transactions tab, the

household invoices view and the parent portal now share one colour treatment — previously each surface had its own slightly different shades

Improved — A focused top bar

Status: Pending enablement (deploys with the next release)

• The top navigation bar now shows just the day-to-day essentials —

Dashboard, Households, Students and Register. Smart Planning and Settings have moved out of the top bar (they still live in the menu drawer), so the bar stays focused on what you reach for every session

Fixed — The number pad now appears for security codes on mobile

Status: Pending enablement (deploys with the next release)

• Entering a two-factor / one-time login code on a phone was popping

the full text keyboard, which made no sense for a 6-digit number. The staff login, onboarding setup, parent-portal login and the security settings code fields now bring up the numeric keypad directly, so the digits are right there under your thumb

Improved — Marketing pages: clearer pricing, tidier copy

Status: Pending enablement (deploys with the next release)

• Tightened the public homepage: fixed a sizing glitch on the price,

corrected the brand wording in the header to "AllSorted", and added the same "no per-student fees, no add-ons, no card required" reassurance the rest of the marketing pages carry

Improved — Pricing updated to £69 / month

Status: Pending enablement (deploys with the next release)

• AllSorted's headline price is now £69 per month per club, flat — still

every feature included, unlimited students and staff, 14-day free trial with no card. Updated consistently across the homepage, pricing page, feature page, sport landing pages, comparison tables and the structured data search engines read

Improved — Marketing pages feel alive (and on-brand)

Status: Pending enablement (deploys with the next release)

• Five new club-type landing pages: football, rugby, basketball,

cheerleading and performing arts — alongside the existing martial arts, gymnastics, dance, swimming and multi-sport pages

• The animated 3D scene behind marketing headlines now picks up the

brand accent colour automatically (it was stuck on a hardcoded blue/purple), drifts gently as you scroll, and subtly follows your cursor — and it now stops rendering entirely once it's off screen, so scrolling the rest of the page costs nothing

• Headlines, subheads and buttons now arrive in a quick sequence when

a page loads instead of all at once; the club-type grid cascades in as you reach it

• The product mock-up panels now drift at different rates as you

scroll, giving the stack a sense of depth, and the dashboard numbers count up when they come into view

• All of it is skipped for anyone who has asked their device for

reduced motion

Improved — Attendance marking now slides into place

Status: Pending enablement (deploys with the next release)

• On the register, each student's Absent / Present / Late control is now

a proper segmented switch: a single highlight pill slides smoothly to the option you tap (green for present, amber for late, neutral for absent) instead of the state snapping on and off

• The selected label settles in just after the pill starts moving, so

the change feels deliberate and tactile rather than instant — quick and confident, not bouncy

• Bigger, easier tap targets on phones and tablets (44px), and the

movement is dropped entirely for anyone who's asked their device for reduced motion (the colour still changes, just without the slide)

• Marking logic and saved attendance are unchanged — this is purely how

the control looks and feels

Fixed — Mobile header no longer overflows; bigger tap targets

Status: Pending enablement (deploys with the next release)

• On narrow phones the top bar could run its icons off the right edge.

The changelog, theme and sign-out controls now move into the menu drawer's new "Account" section below the small breakpoint, leaving just the essentials (menu, logo, search, notifications) in the bar — so it fits cleanly even at 320px

• Header buttons (menu, logo, search, notifications, drawer close) are

now full 44px touch targets, easier to tap accurately on phones

• The dashboard activity feed's refresh and filter buttons, and the

inbox cards, also get 44px targets; long activity and inbox text now wraps to two lines instead of being cut off mid-word

• The comms trigger-map gains a mobile pan hint and a soft right-edge

fade so it's obvious each flow scrolls sideways

Improved — A subtle buzz when you mark a register on mobile

Status: Pending enablement (deploys with the next release)

• On phones and tablets that support it, marking a student Present or

Late now gives a tiny confirmation buzz — like a light native-app tap — so coaches taking a register quickly can feel each mark land without looking

• Marking Absent doesn't buzz, and re-tapping a state that's already set

doesn't either; it only fires on a real change you tapped

• It's progressive enhancement: devices without vibration (including

iPhones) behave exactly as before, and it's suppressed if you've asked your device for reduced motion. Attendance saving is unchanged

Improved — Settings tables now read as cards on phones

Status: Pending enablement (deploys with the next release)

• A batch of dense settings and data tables that used to squash into an

unreadable grid on phones now render as clean stacked cards below the medium breakpoint — each row becomes a card with its key fields labelled and full-size (44px) action buttons

• Covered in this pass: Venues, Fees, Timetable (classes), Event types,

Syllabus tags, Audit log (mutations + access), SMS gateway history, the drill library, the automation queue + send history, the billing arrears list and the external-events list

• Desktop is unchanged — the existing tables still show at medium width

and up; this only adds the mobile card layout underneath

Improved — Phone-first grading and calendar screens

Status: Pending enablement (deploys with the next release)

• Grading on a phone now uses a dedicated flow: instead of one

enormous flat list of every candidate, students are grouped into collapsible programme → rank sections (one open at a time) with a sticky filter/summary header and big promote/defer buttons. Desktop keeps its existing two-pane list unchanged

• The calendar now opens to a clean "Agenda" view on phones — a

scannable, date-grouped list of upcoming classes, events and closures — instead of a cramped week grid. A new Agenda toggle appears on mobile only; the month / week / day views and the whole desktop calendar are unchanged

Improved — Class-limit warning is now a corner toast

Status: Pending enablement (deploys with the next release)

• When you mark a student who's over their class limit for the period,

the "still recorded" warning no longer pushes the register down the page. It now appears as a toast in the bottom-right corner, keeping the same orange styling, with an ✕ to dismiss and an automatic fade-out after 10 seconds. Attendance is still recorded exactly as before

Improved — Attendance toggle slide now has momentum

Status: Pending enablement (deploys with the next release)

• The Absent / Present / Late highlight pill now eases in and out as it

slides — building speed from rest and settling into place — instead of the previous snap-and-glide. Still quick (under a third of a second) and still dropped entirely for reduced-motion users

Improved — More pages tuned for phones

Status: Pending enablement (deploys with the next release)

• A pass of page-level mobile polish across the app: the Tasks list gets

a proper mobile card with tap-to-pick status and action menus (instead of cycle-on-tap); grading-day and event-day screens get full-size 44px pass/unsuccessful/undo controls and stacked layouts; the bar charts in Reports become tap-selectable on touch; row actions that were hover-only (event detail, student notes) now stay visible on phones; and the accident-reports filters, Communications composer, Reports and Settings headers stack and size correctly on small screens

Improved — Register status filter matches the attendance switches

Status: Pending enablement (deploys with the next release)

• The All / Present / Late / Absent filter at the top of the register now

uses the same sliding-pill control as the Present/Late/Absent switches on each student: the highlight glides between options with the same momentum easing, tinted to match the filter (green/amber/red, or the accent for "All"). Same look, same motion, reduced-motion respected

Improved — Trial students get the same attendance switch

Status: Pending enablement (deploys with the next release)

• Trial students on the register now use the same sliding-pill attendance

control as regular members — No Show / Present / Late, with the same motion, colours and subtle haptic. A trial you haven't marked yet shows no highlight (so "unmarked" stays distinct from "No Show") and the pill glides in the moment you tap a choice

Improved — Register ad-hoc box moved + clearer input styling

Status: Pending enablement (deploys with the next release)

• The "Ad-Hoc / Catch-up" student search on the register now sits below

the coaches & volunteers section and just above the roster filter, and matches the filter search box (search icon, same shape) so the two read as a set

• Trialling a subtle blue-teal glow on input boxes so it's obvious at a

glance what's editable — applied first to the ad-hoc search and the ⌘K command palette. If it lands well it'll roll out to inputs app-wide

Fixed — Class usage now counts the attendance record, not taps

Status: Pending enablement (deploys with the next release)

• Switching a student between Present, Late and Absent on the register

was nudging their billed class-usage counter every time, so flipping Present↔Late could show silly totals like "17/1 classes used". Usage now only moves when a student genuinely changes in or out of the "attended" state — marking present/late counts one class, switching between present and late (or re-tapping the same state) counts nothing, and going back to absent removes it. The attendance record itself was always saved correctly; this only fixes the usage tally and its warning

Added — Green confirmation toast when a catch-up student is added

Status: Pending enablement (deploys with the next release)

• Adding an Ad-Hoc / Catch-up student to the register now shows a green

success toast in the top-right corner ("… added to the register"), matching the orange limit warning's style — it slides and fades in, holds, then fades down and out after 10 seconds, with an ✕ to dismiss early. If both toasts are showing they stack neatly

Fixed — Could not mark today's register late in the evening

Status: Pending enablement (deploys with the next release)

• Marking attendance and adding ad-hoc / catch-up students could silently

do nothing on the current day at certain times of the evening. The register compares the selected day against "today", but that check used UTC while the selected day is your local date — so in UK summer time (and any timezone ahead of UTC) today's register briefly read as a future date and blocked edits. All these checks now use your local date

Improved — Teal glow on the header search box

Status: Pending enablement (deploys with the next release)

• The Search / ⌘K box in the header now carries the same subtle blue-teal

input glow, so it's clearly an interactive search field

Improved — Every toast now drops in from below the header

Status: Pending enablement (deploys with the next release)

• All pop-up notifications (toasts) across the app now behave the same:

they drop in from the very top and settle just below the menu header on the right, ease in over about 3 seconds with a gentle bounce, sit there for 10 seconds at a softly translucent 80% (with a blur behind so text stays crisp), then take a further 3 seconds to fade down and out — and can still be dismissed early with the ✕. Previously the app's general toasts slid up from the bottom and cleared after 4–6 seconds. Reduced-motion users get a plain fade instead of the drop/bounce

Improved — Register page header + stats rearranged

Status: Pending enablement (deploys with the next release)

• The register top area is tidier and wastes less space. The "Class

Register" title is gone — the selected day is now the heading (weekday + date), with the live "On Mat" total beside it. The + button to add a class/ad-hoc session stays.

• A small inline month calendar now sits top-right (tap any day to jump

there) in place of the date box with prev/next arrows. Future days are disabled; today and the selected day are highlighted in teal.

• The "Updated · Refresh" control moved to a small button in the very

top-right corner instead of taking its own line.

• Roster / On Mat / Health / Lesson Plan now sit in one even four-up row.

The Lesson Plan cell is a toggle that expands the full plan in place below the row (tap again to close).

• Roster and Lesson Plan tiles, plus the selected class pill, now use the

teal-glow / no-fill style; volunteers in the staff panel now match the coaches' teal styling.

Improved — "On Mat" live count is snappier

Status: Pending enablement (deploys with the next release)

• The live On-Mat total already updates the instant a register mark lands

(realtime, no polling); the class live/ended indicator now re-checks the clock every 20s (was 60s) so it flips promptly when a class starts or ends. No extra database load — it's a local clock check

Improved — Register header is now a day-view layout

Status: Pending enablement (deploys with the next release)

• The register top area is now split 40 / 60: on the left, the day title,

the live "On the Mat" total (now bigger, with more room) and the month calendar; on the right, the day's classes listed top-to-bottom like a calendar day view (time on the left, class name beside it), newest-first by start time. The calendar moved from the right to the left.

• The Roster / On Mat / Health / Lesson Plan tiles now have their labels

centred.

• Coaches and Volunteers: Volunteers keep their purple panel; the Coaches

panel now uses the same soft translucent tint treatment (in teal) so the two match in weight.

Improved — Register day-view rows are richer

Status: Pending enablement (deploys with the next release)

• The register header split is now 30 / 70 (calendar narrower). To fill

the wider class list, each class row now shows its venue under the name, a pulsing "Live" badge when the class is in session right now, and a chevron — so the day view reads as a proper agenda instead of leaving empty space. Events get an "Event" tag and chevron to match.

Improved — Class rows show headcounts; mobile keeps simple date nav

Status: Pending enablement (deploys with the next release)

• Each class in the register day view now shows a head-count on the right:

how many are on the roster (or booked, for bookable classes) plus a trials count when there are any — so you can see the size of each class at a glance without opening it.

• On phones the date control is the simple date box with ‹ › arrows again

(the full month calendar is desktop-only, where there's room for it).

Improved — Register header is now three columns

Status: Pending enablement (deploys with the next release)

• The register top area is split 20 / 25 / 55: a left column with the

"Register" title, the selected day + date, the add + refresh buttons and the "On the Mat" card; a middle column with the month calendar; and the day's classes filling the right. The On-the-Mat card now breaks its headcount down by venue when more than one venue is live at once. The class rows have a little more breathing room between them.

Internal — UI system guide

Status: Local-only (developer documentation)

• New docs/ui-system.md: the shared component kit, the status-tone

vocabulary, motion rules, the confirmation pattern and the standard trust microcopy ("Saved", "Queued", "This will send to X recipients"), plus the page-by-page migration playbook

Improved — Register header puts the class list first

Status: Pending enablement (deploys with the next release)

• The day's classes now sit on the far left of the register — it's the

first thing you reach for, so it's the first thing you see

• The big month calendar is now a compact single-week strip

(Monday–Sunday) tucked into the right sidebar, reclaiming a lot of wasted vertical space

• The selected day, quick refresh and "add a lesson" controls move up

into a tidy title bar across the top

• On phones the day picker (date + ‹ › arrows) stays on top so you set

the day first, then scroll the class list underneath

• "On the Mat" live count keeps its place in the sidebar, with the

per-venue breakdown when more than one venue is running

Improved — The register now follows your programme lens

Status: Pending enablement (deploys with the next release)

For clubs running more than one programme (e.g. Dance + Martial Arts + Gymnastics), the register no longer mixes everything together:

• Pick a programme from the lens switcher and the class list shows only

that programme's sessions — a Dance coach no longer scrolls past Taekwondo and Gymnastics to find their class

• Classes that aren't tagged to any programme stay visible in every

lens, so nothing gets accidentally hidden

• A clear banner shows which register you're viewing ("Showing Dance

register") with a one-tap "All programmes" escape hatch for owners and admins

• The roster is always authoritative: once a class is selected, everyone

booked, ad-hoc or on trial for that class appears — even if their main programme is different. The lesson is the source of truth, not the lens

• If you switch lens while a class from another programme is open, it

isn't yanked away — the banner turns amber to tell you the class is outside the current lens, with the switch-to-all option right there

• Single-programme clubs see no change at all

Fix — Register lens now reads the programme each class is actually tagged with

The first cut of the register programme lens checked a column the timetable doesn't populate, so switching lens appeared to do nothing. The register now resolves a class's programme from its "Target Programme" (the same value shown in the timetable), so Dance really does show only Dance classes. Classes left as "Open" stay visible in every lens, as intended.

Improved — Programme lens works everywhere, and a new timetable filter

Status: Pending enablement (deploys with the next release)

• The programme lens now reads a class's programme correctly across the

whole app — the register, the calendar and the day view all honour the same logic, so classes set up before the multi-programme switchover (which only carry the older "Target Programme" link) filter properly

• Pick Dance and you see Dance everywhere; classes left as "Open" stay

visible in every lens, as before

• New Programme filter on the Settings → Timetable page (shown only

when you run more than one programme) so you can quickly narrow the class list to Taekwondo, Dance, Gymnastics, or "Open" classes

Improved — The register's polish, spread across the app

Status: Pending enablement (deploys with the next release)

The sliding-pill toggle and the teal focus-glow that debuted on the register now show up in more places, for a more consistent feel:

• Sliding-pill filters — the animated highlight that slides between

options is now used on the Households status / member-count / plan filters, the Calendar view switch (Month / Week / Day / Agenda) and event time filter, and the Dashboard retention period selector

• Teal search glow — the Students, Households and Calendar search

boxes now carry the same subtle teal halo that brightens on focus

• Dashboard header — gains a small "Dashboard" eyebrow above the

club name to match the register's title styling

Single-programme/simple pages are unaffected; this is styling only — no change to what any filter does.

Improved — Inbox now uses the standard page width

Status: Pending enablement (deploys with the next release)

• The Action Inbox previously sat in a narrow reading column; it now

uses the same content width as Dashboard, Students, Households and the other main pages, so moving between them no longer shifts the layout.

Improved — Comms-flow pages now use the standard width

Status: Pending enablement (deploys with the next release)

• The Trigger Map, Comms Flows hub and Flow Simulator all sat at

different widths (1400px / 1024px). They now use the same content width as the rest of the app, so the layout no longer jumps when you move between them.

Improved — Accident report pages now use the standard width

Status: Pending enablement (deploys with the next release)

• The Accident Reports list and the individual report view were full

width (and uncapped); they now sit in the same content width and padding as Dashboard, Students, Households and the other main pages.

Improved — Every form field now has the teal glow

Status: Pending enablement (deploys with the next release)

• The teal focus-glow that started on the search boxes now applies to

every text field, dropdown and text area across the signed-in app — search bars, settings forms, modals, everywhere — for one consistent, on-brand input style

• The halo is gently visible at rest and brightens when you click into a

field, so it's always clear what's editable

• Public pages (login, member portal, trial booking, the marketing site)

are deliberately left with their own styling

Improved — One consistent control language (rolling out)

Status: Pending enablement (deploys with the next release)

We're standardising the look of filters, status chips and buttons across the app so every page speaks the same visual language as the register:

• Shared status chips and action/filter chips with one colour vocabulary
• Sliding-pill filters (the register's animated toggle) replacing

hand-rolled tab/filter rows, page by page

• Consistent press feedback on buttons and controls

This entry will grow as each area is converted.

Improved — Status chips share one colour vocabulary

Status: Pending enablement (deploys with the next release)

• The SMS delivery log and the comms-flow trigger map had their own

hand-rolled status colours; they now read from the single app-wide status palette, so "failed" is the same red and "delivered" the same green everywhere.

Improved — Student record reads like a professional member file

Status: Pending enablement (deploys with the next release)

The student page is calmer and easier to scan — less "wall of edit buttons", more SaaS member record:

• A single top-right Actions menu now holds every profile-level

action, grouped into Profile · Membership & Training · Communication · Finance · Admin · Danger zone (with "Forget student" clearly separated and still behind its confirmation)

• The quick status tiles (Insurance, Direct Debit, Emergency & Medical,

Telegram) are now clean read-only summaries — no more "click to edit"

• Inline Edit buttons removed from the read-only cards; editing happens

from the Actions menu, so there's one obvious place to make changes

• A new Needs attention strip under the header surfaces urgent

states at a glance: insurance expiring/expired, no emergency contact, medical notes on file, unpaid invoices, no direct debit, portal invite not accessed, SMS unsubscribed — each jumps to the right place

• All existing edit forms, status changes, transfers and exports work

exactly as before; this is a layout/placement refresh, not a rewrite

Improved — Student record polish (calmer, less blocky)

Status: Pending enablement (deploys with the next release)

Continuing the student-record refresh:

• Actions menu labels are now uppercase for a tidier, more deliberate menu
• Family and classes are combined into one "Household & Enrolment" card

instead of two loose chip rows

• The Portal card is now status-only — invite/impersonate live solely in

the Actions menu, so no action appears in two places

• The four quick tiles (Insurance, Direct Debit, Emergency & Medical,

Telegram) now look consistent, and only turn amber/red when the data genuinely needs attention — a healthy record stays calm and neutral

• The attendance strip reads as a slim "Snapshot" row

Improved — Student view tabs slide like the register

Status: Pending enablement (deploys with the next release)

• The student "view" tabs (Profile, Billing, Attendance, …) now use the

register's pill styling — squarer corners and a teal sliding highlight that glides to the selected tab

• Switching tabs is instant client-side state — it no longer touches the

URL router, so the page never reloads

Improved — Student record header polish

Status: Pending enablement (deploys with the next release)

• Household, Family and Classes now sit side-by-side as three short

sections (instead of stacked rows), using the full width

• Photo consent is shown in a bordered box with a camera icon
• Removed the redundant "View" label from the tab strip
• A subtle status-coloured wash now fades down the top of the record

(green for active, amber paused, red leaver, …) for instant context

Improved — Student list mobile toolbar

Status: Pending enablement (deploys with the next release)

• On mobile the student-list toolbar keeps the everyday controls

prominent — Search, Add, Sort and Filter — and tucks the rest (Select/bulk, Hide names, Group by family, Export CSV, Send enrolment form, Invite to Telegram) into a single "More" menu, so the toolbar is far less cluttered. Desktop is unchanged.

Improved — Student Actions is now a full command centre

Status: Pending enablement (deploys with the next release)

• The student "Actions" button now opens a proper slide-over panel

instead of a small dropdown: a right-side drawer on desktop with grouped, multi-column sections, and a near-full-screen bottom sheet on mobile with large, easy-to-tap rows (icon, title and a one-line hint)

• Actions are organised into clear groups — Status & Membership;

Personal & Household; Progression, Grades & Achievements; Communication & Portal; Billing, Export & Admin; and a visually separated Danger Zone

• Unavailable actions explain why (e.g. "No email on file"); destructive

actions still ask for confirmation

• Fully keyboard accessible (focus trap, Esc/!outside to close, focus

returns to the button) and respects reduced-motion

Improved — Student tab switches feel like a deliberate transition

Status: Pending enablement (deploys with the next release)

• Switching student tabs now plays a subtle ~180ms fade-and-lift on the

new content, and the content area holds a minimum height while a tab loads — so the page no longer shifts under you mid-switch.

Improved — Dashboard & Reports follow the programme lens

Status: Pending enablement (deploys with the next release)

For clubs running more than one programme, picking a lens (e.g. Dance) now scopes the numbers, not just the lists:

• The Dashboard shows that programme's members, attendance, trials,

insurance, direct-debit, retention and data-quality figures, with a "Showing Dance lens" cue in the header. "All programmes" is unchanged.

• Reports gain a context chip ("All programmes" / "Dance lens"), and

the Attendance, Trial Funnel, Events, Insurance and Data-Quality reports now filter to the selected programme.

• Single-programme clubs and "All programmes" behave exactly as before.

Improved — App-wide brand consistency pass

Status: Pending enablement (deploys with the next release)

A sweep across Reports, Settings, Communications, Calendar, Households and the public/enrolment pages to make everything look like one product:

• Hard-coded colours (slate/blue/grey) swapped for the app's tokens, so

light/dark themes stay correct and "blue" reads as the brand accent

• Emoji removed from report/tab/section icons in favour of clean text
• Corner radii normalised (no more oversized one-off rounding)
• Buttons, inputs, cards, tabs, modals and empty states aligned to the

same patterns used on the Dashboard and Students pages

• Calendar/Register keep their full-width operational layout — only their

controls and chrome were restyled to match

Improved — Brand follow-up: Settings icons, Reports header

Status: Pending enablement (deploys with the next release)

• The Settings navigation now uses clean line icons (lucide) instead of

emoji — on both the desktop sidebar and the mobile grid; the mobile dropdown is text-only.

• Reports gains a compact header showing the current report, date range

and active programme lens at a glance.

• Scheduled-report toggle knob now matches the rest of the app's toggles.
• Functional white surfaces (QR codes, email previews, logo plates) and

the semantic category colours (event types, tags) are intentionally preserved.

What's new

A big day: enrolment got family-smart, every vertical can now have its own annual costs, and the whole platform got faster and tighter under the hood.

All of today's work is pending enablement — committed locally, not yet deployed, and the new tables/indexes need migration items 23–25 applied (item 26 is a deliberate apply-later step).

Added — Annual Requirements (per-vertical costs & tracking)

Status: Pending enablement (migration item 25; item 26 later)

• Every programme can now define its own annual requirements: TKD

insurance, a dance registration fee, or a gymnastics governing-body membership — each answering three questions: *is there a cost?* (£0 = track-only), *is a date tracked?*, and *can members continue once expired?* (block / warn / nothing)

• Fees are billed automatically onto the family's one consolidated

invoice by a new nightly job — safe to re-run, can never double-charge

• Three new automation events (requirement due / expired / renewed)

so you can build your own chase emails in the Automations builder

• New Settings → Annual Requirements tab with one-click presets, and

a status card on each member profile with a "Mark renewed" button

• Existing insurance keeps working untouched; a later switch-over step

converges it onto the new system when you're ready

Added — Enrolment recognises returning families

Status: Pending enablement (migration items 22–23)

• When a trial parent or a staff invite uses an email the club already

knows, the enrolment link is automatically family-linked: details pre-filled, the new member joins the right household, and the email says "enrol another family member" instead of a cold welcome

• The "Add Another Family Member" button on the enrolment success screen

now works for parents (it previously only worked for logged-in staff)

• New families at GoCardless-connected clubs can set up their Direct

Debit right from the enrolment success screen — and a same-household second child is never asked twice

• Members can switch bank accounts from the portal with no gap and no

double-collection window

Fixed — Enrolment form answers now save properly

Status: Pending enablement (deploys with the next release)

• Custom "about the new member" questions answered on the public

enrolment form were not being saved — they now land on the member's profile and in Forms responses

• Programme-specific enrolment links now strictly enforce their

programme — a tampered request can't sign up onto another programme's plan or classes

• No-payment enrolments no longer record a "payment received" note

against an unpaid invoice (history and welcome emails now say "invoiced — to be collected")

Security — Trial links and webhooks tightened

Status: Pending enablement (deploys with the next release)

• Rescheduling a trial now requires the secret link from the email — a

leaked booking reference can no longer be used to view or move someone's trial (and rescheduled trials get working cancel links, which they previously lacked)

• The trial-count checker is rate-limited so it can't be used to test

whether an email address belongs to a club

• All emailed links are built from the club's canonical web address, so

preview/proxy domains can't end up in parents' inboxes

• Telegram account-linking codes only work through the club that issued

them

Performance — Built for 1,000 clubs

Status: Pending enablement (index pack = migration items 23–24)

• The nightly billing run now processes whole clubs in a few queries

instead of thousands — it stays well inside its time budget at scale

• Staff pages load noticeably faster: the app's startup data is fetched

in one parallel batch and cached for five minutes

• A new database index pack makes portal login, duplicate checking and

email suppression checks instant even with hundreds of thousands of members (apply migration item 23)

• Portal pages no longer download a family's entire multi-year history

on every visit

Internal — Local test data for multi-vertical clubs

Status: Local-only (developer tooling, never runs in production)

• npm run seed:verticals builds a complete test club on the local

database: Taekwondo + Gymnastics + Dance with belts/badges/grades, timetables, pricing, 60 households (some spanning two or all three verticals), 90 days of registers, billing agreements and trials

Security — Trial endpoints sweep-proofed (follow-up)

Status: Pending enablement (deploys with the next release)

• The trial-count checker and trial enrolment-link sender now share one

request budget per visitor — previously each email address checked got its own allowance, so a script could still sweep a mailing list

Internal — Release confidence

Status: Local-only (docs + developer tooling)

• New release checklist (docs/release-checklist.md) answering "what turns

on when we deploy vs what's built but off" — flags, crons, migrations and the staged rollout order for real automation sends

• New npm run smoke:requirements proves the annual-requirements engine

against realistic seeded data: 105 members billed onto 60 consolidated family invoices, a re-run bills nothing twice, and expiry blocking only affects genuinely lapsed members

• The smoke immediately caught and fixed two would-be production issues:

an invoice status the database would have rejected, and a filter on a column that doesn't exist

Fixed — Duplicate-member check actually works now

Status: Pending enablement (deploys with the next release)

• The duplicate-email warning on public enrolment was silently disabled

by a filter on a database column that doesn't exist — the same family could create duplicate member records without any warning. Fixed in both enrolment endpoints

• The club-closure notification list had the same hidden fault and could

show no affected members; it now correctly lists everyone except leavers

• A new automated guard stops this class of bug from being reintroduced

Security — Trial booking privacy pass

Status: Pending enablement (deploys with the next release; embedding clubs need their website added to the new embed allowlist before launch)

• The public trial-availability check no longer reveals how many trial

sessions a child or family has already used — it now answers only "can this email book a trial?", with the real limit still enforced at the moment of booking

• Class capacity is shown as "Spaces available" or "Last spot" instead

of exact numbers — operational detail stays private without hurting the booking experience

• Trial pages can no longer be embedded inside arbitrary websites: only

the club sites you approve can iframe the booking flow, protecting parents from fake-embed and clickjacking tricks

Fixed — Event waitlist promotion is now race-proof

Status: Pending enablement (deploys with the next release)

• Two staff members promoting from an event waitlist at the same moment

(or a promote racing a parent's claim link) could both win the last seat. Staff promotion now goes through the same capacity-checked path as the public claim link, so the second attempt gets a clear "back at capacity" message instead of an overbooked event

• A draft event can no longer have waitlisted members promoted onto it

Added — Waiting lists for full classes

Status: Pending enablement (migration item 27; waitlists are OFF per class until staff switch them on)

• Clubs can now run a waiting list for any full class — built for dance,

gymnastics and swim schools. Share one public signup link; parents give just their name, email and the child's first name (full details are only asked for if a space opens and they enrol)

• New Settings → Waiting Lists tab: switch a class's list on, set its

capacity, see the queue in joined order, add or remove people

• Automatic offers (email the longest-waiting with a time window, or

everyone at once, or staff-picked) come in the next phase — the plan is agreed and the queue collection works today

• Staff adding members directly to an event now see a clear warning when

the booking takes the event over capacity (the override still works — it's just never silent)

Added — The Join page: trials, waiting lists and multi-activity in one flow

Status: Pending enablement (migration items 27–28; per-class waitlists stay off until staff enable them)

• Every club now has a public Join page (/join/your-club): parents pick

the activity (for multi-activity clubs), enter just their name, email and child's birth month, and see exactly the classes that fit — each one either "Spaces available — book a trial" or "Full — join the waiting list"

• Parents can join the waiting list for several full classes at once;

winning a space in one automatically takes them off the others

• When a space opens, offers go out automatically per class policy:

first refusal for the longest-waiting (48-hour window), everyone at once with first-to-claim-wins, or staff-picked — claiming is race-proof and leads straight into the normal enrolment wizard

• Two new automation events (space offered / space claimed) for custom

follow-ups, and a "Send offer" button on the Waiting Lists settings tab

Improved — Waiting lists: club policies, self-removal and demand insight

Status: Pending enablement (migration item 29)

• Every offer email now includes a one-click "remove from the waiting

list" link, and quiet entries lapse automatically after a configurable period (checked weekly)

• New settings (behind the ⚙ on Waiting Lists): how long offers are held,

the default offer mode, and what happens when an offer isn't actioned — removed, kept at the front for the next space, or moved to the back

• Classes at member capacity no longer offer trial bookings — a trial for

a class nobody can join led nowhere

• "Book a trial" from the Join page now lands with that class pre-selected
• New Reports → Waiting Lists view: queue depth by class — the signal for

when to open a second session

Security — Public endpoint hardening (third review pass)

Status: Pending enablement (deploys with the next release)

• Rate limits added across the remaining public endpoints: trial

availability, the examiner scoring links (generous for live scoring, per-examiner so a venue's shared wifi can't stall a panel), insurance renewal links, and external-event invites

• Coach review clips can only be saved to their own member's storage

area — a crafted request can no longer point a member's playback at an arbitrary file

• Audio, recording and certificate uploads are now checked by file

CONTENT, not just the declared type — a disguised file is rejected

• External-event invite pages return only the fields the entry form

needs, and event payment confirmations build links from the club's canonical web address

Internal — Audit follow-through

Status: Pending enablement / Local-only (docs + guard tests)

• All seven P1/P2 items from the independent SaaS audit were already

fixed in the preceding security passes — confirmed line by line

• Eight more external-event emails (invites, entry confirmations,

organiser updates) now build their links from the club's canonical address, and an automated guard prevents any future route from baking a preview/proxy domain into an emailed link

• The public class-availability lookup is cached for 30 seconds per

club — an open-day rush re-reads one snapshot instead of hitting the database per family

• The release checklist gains three audit-recommended gates: live

database schema verification SQL, automation volume watching before wide enablement, and a manual accessibility pass before public launch

Added — Expired requirements now actually block (with a human override)

Status: Pending enablement (needs migration item 25; only affects clubs that set a requirement to "block")

• When a club's annual requirement (e.g. insurance) is set to block and

a member's has expired, the class register and grading day now show a clear red marker on that member

• Marking them present or recording a grading outcome asks staff to

confirm first — the kid already on the mat can still be recorded, but never by accident

• Members with no recorded date are chased, never locked out — switching

the feature on can't strand a class

Internal — Local testing unblocked

Status: Local-only

• The local development database now allows two-factor enrolment, so the

full app (including everything behind login) can finally be tested in a local browser

What's new

The big Phase 16 work has landed. ClubCRM is now public-ready and we can finally tell people about it without "but…" disclaimers.

Public signup

• New marketing landing page at the root URL for unauthenticated visitors
• 14-day free trial; no card required
• One-click demo at /demo — poke around a fully populated club without

signing up

• Founder tier (Creative Ways Taekwondo) is grandfathered, no billing

changes

Parent payments (Stripe Connect)

• Each club connects its own Stripe account
• Parent payments land in your balance directly; we take a small platform

fee per transaction

• Set up under Settings → Payments

Customer ops layer

• Changelog (you're looking at it) — bell icon pulses red when there's

a new entry

• Feedback board at /feedback — submit + upvote requests for things

you'd like to see next

• Status page at /status — green/amber/red across API, crons,

webhooks

Mobile-first sweep

We did a thorough mobile audit:

• iOS auto-zoom on inputs killed
• Hover-only action buttons now tappable on phones
• Filter rows + cards no longer overflow on narrow screens
• Sticky save bars on long forms so the keyboard doesn't bury the action
• Activity timeline now paginates (50 per page)
• Attendance date pills swap in place rather than re-loading the page

Smaller wins

• Demo club seeded with 300 fake students, 12 months of attendance,

household structure, grading history

• Settings → Billing tab with trial countdown
• Ardent Edge admin dashboard (super-admin only)