Help · Where things stand
Where things stand
Every part of Rally Round, and where it is. This list is kept by the people who change the code, in the same change, and was last read against it on 24 September 2026. If something here is wrong, that is a bug, not a plan.
- Built
- On the live site, walked through by the product owner, covered by a browser test.
- Next
- Decided and in the current plan. Not on the site yet, or only part of it is.
- Later
- Wanted, and waiting on something: a decision, a real need, or a Moment that needs it.
- Not building
- Deliberately not built. Arguing for one means arguing in the open, and this list says why.
The Moment and its page
A page for each Moment
BuiltA poster at its own address on the moments host, with the facts read from the network. A draft is visible to its committee only.
Add to calendar and Share
BuiltA calendar file and the device’s share sheet. Neither needs an account or records anything.
I’d love to come
BuiltFirst name, email, one confirmation. The page shows a count, the committee sees the name.
Host a table, and join one from its link
BuiltA captain holds a private link; guests take a seat each. First names only, and only to those who should see them.
How: Host a table
Posts on the page
BuiltThe save the date first, then the club’s posts newest first, ten at most, with an end. Video and photos as links out.
How: Post an update
Comments and cheers from the room
BuiltOpened per Moment by an organiser. First names, no counts, nobody outside the room.
A seat price on the page
BuiltStated once, GST included, nothing added for paying by card. The price is a fact on the Moment.
How: Host a table
Paying for a seat
NextDecided in principle: a guest pays for one seat, on a hosted payment page, and the committee sees every seat paid or not. Not built yet.
A link to book through a ticketing provider
LaterWaits on a committee choosing a provider. Paying for a seat here may make it unnecessary.
A form for auction prizes
LaterFirst as a link to a form the committee already uses. An owned form only if volume asks for it.
A Moment with a start time and a time zone
LaterToday a Moment is a day. The evening starts when the page says it does, in words.
Photos and video uploaded to Rally Round
LaterAfter the first night. Comes with a permission attestation at the press and a takedown request any person can make.
Clubs and their pages
Start your club
BuiltA name, a first name, an email, one link. Invisible until it publishes a Moment.
How: Start your club
The club’s page
BuiltWhat it hosts, grouped by series, and what it supports. It exists once a Moment is published, and names nobody.
The club’s page shows its posts
NextThe next Moment first, then posts across its Moments, twenty at a time with “Show earlier”, and an end.
A page for a charity or a cause
BuiltWhat benefits it, and which Moments are raising money for it, each with the club presenting it.
A front page for rallyround.club
LaterToday it lists the words the network is made of. A real front page arrives when there is more than one club to show.
Home: posts from the clubs you joined
LaterIn time order, with filters you set. Once two clubs post.
Running a club
Create, preview, publish, edit
BuiltA draft, the real page as a preview, the missing facts named, publish behind a sheet, then the share link.
Mark as happened, cancel
BuiltOne press each, behind a sheet. Nothing goes back to a draft.
Mark bookings as open
NextThe status exists and the page can show it. Nothing in the console sets it yet; it arrives with paying for a seat.
Invite the committee
BuiltBy first name and email; resend, withdraw, remove, leave. Never the last organiser.
Import last year’s list
BuiltA CSV checked before anything is written, an attestation, counts only, the same file twice changes nothing.
Tell people
BuiltThe audience as counts, a test to yourself, twenty-five at a time, a stop link on every copy, bounces and complaints handled. Switched on per deployment.
Post from the console, and tell the list from a post
BuiltOne leftover: the words can still be edited on the announce page, so the email and the page can drift apart.
How: Post an update
Prize donors, sponsors and to do
BuiltEach conversation written down as it happens; what arrived settles it; you are told when you are caught up.
Who is coming, and sending a confirmation again
BuiltFirst names, tables, confirmed or not, and what happened to the confirmation email.
How: See who is coming
The door list and the auction results, imported after the night
LaterWho attended and what was raised, from the night’s own records, never typed from memory.
Merging two records that are one person
LaterA human’s decision, one at a time. Until then two rows stay two people.
Signing in and your information
Sign in by emailed link
BuiltNo password. One press to spend the link, thirty days signed in, both hosts at once.
Passkeys
BuiltOffered after the first confirmation, never required.
Consent as a record, with versions
BuiltEvery yes and every stop has a document, a version and a day. Every version of the terms stays readable.
Stop a club’s emails in one press
BuiltFrom the email, without signing in. It never expires.
How: Stop a club’s emails
Accounts for under-16s, through a guardian
LaterThe network has no age on a person yet. Until it does, reactions are closed until an organiser attests the room is adults, and no child’s surname, school or suburb is ever shown.
What we won’t build
Likes, counts of who follows a club, view counts
Not buildingA number beside a person’s name turns showing up into a performance. The only numbers are who is coming and what was raised.
A feed with no end, or a feed that decides for you
Not buildingEvery list ends and says when there will be more. Order is time, never engagement. Filters are yours.
Red badges, chains to keep unbroken, countdowns
Not buildingRed means something is wrong. A real deadline is said once, plainly, and let go.
Online-now dots, last seen, read receipts
Not buildingThey create a duty to respond. Volunteers already give enough.
Messaging inside Rally Round
Not buildingA table is a roster and a link; the conversation lives in the chat you already use. A message to a fourteen-year-old on a club’s page needs a safety model written first, and that is a decision made in the open, not a feature added quietly.
Push notifications
Not buildingA club tells its list by email, on purpose, once per person per version, with a stop link. Nothing pushes.
Contact-list import, friend suggestions, public profiles for children
Not buildingChildren are not a growth channel. This one is the law as well as the right way to treat somebody’s kid.
A retention offer on the way out
Not buildingLeaving is as easy as joining, and the least confident person here is the one who would pay for any friction we added.