Trails
A charity that will not publish a review without consent
A charity that runs a youth sports clinic. The site takes paid places when a clinic is open, collects medical details and photo consent for every child, and gathers stories from families. Nothing a family has not agreed to can be published, and the server enforces that, not the page.
Running on this page
Two of the moving parts, live
Not screenshots. Both are the charity's real code, running here on sample families. They run themselves. Touch either one to take over.
1. What a family uses
2. What the charity's staff see
What is running
What is behind the enrolment and the reviews
Six mechanisms. One line each.
Questions before payment
Pressing pay turns the price card over and asks three short pages: the parent, the player, then a summary with the consent boxes. The answers are saved before the family is sent to pay, and each enrolment gets a reference that matches it to its payment. So a declined card or a closed tab does not lose the family.
The price set on the server
A parent can enrol several children at once, with a family discount where every fourth place is free. The page and the server use the same discount rule, but only the server's figure is ever charged. So nobody can change what they pay by editing the page.
Paid status read live, never guessed
The staff screen shows paid, not paid or unknown against every enrolment, read from Stripe by reference each time it opens, with a manual mark for families who pay by bank transfer. If Stripe cannot be reached it says unknown rather than not paid. So it never tells staff a family owes money when it simply does not know.
A consent form that opens only once the place is paid for
Medical details, emergency contacts, photo permission and signed declarations, asked one section at a time, once for each child. It stays shut while the payment record shows the enrolment unpaid, and a refused photo consent is called out at the top of the staff email. So staff can see at a glance which children still have no form, and a photo refusal is hard to miss.
Reviews that cannot be published without consent
Families choose: publish with my name, publish without it, or do not publish. A review marked no is refused by the server, not only greyed out on screen. Publishing sends only the review's id, so the words that go public are exactly what the person wrote. The star rating stays with staff and is never shown.
Published with one press, no rebuild
A review appears on the site the moment staff press Publish, and comes off just as fast. Only the name, connection and story are ever made public. So staff manage stories without touching the website, and nothing private can leak through it.
What this makes possible
Two sides of the same build
For families
- Enrol several children in one go, with the family discount shown before paying.
- Fill in the consent form later, from the link in the email, rather than on the spot.
- Give the parent and emergency details once, with only the child's own answers asked again.
- Decide whether a story is published, and whether a name goes with it.
For the charity
- Every enrolment is on record before the family goes to pay.
- Who has paid is read from the payment provider, with bank transfers marked by hand.
- Medical details and photo consent in one place, with a count of who has not sent theirs.
- A story goes up with one press, and only if the family said yes.
See it yourself
The site is public
Clinic enrolment opens when the charity runs a clinic. The review form is a private link sent to families, so it is not in the menu.
trails.org.auWorth saying plainly
No one client has done the whole journey yet
Every piece of it is live somewhere, and we can show you each one.
Book a call