Youth & Club Tournament Registration

The vertical decides the vocabulary, the questions asked at checkout, the inventory model, the door, the payout terms and the theme. This page says "entry" and "tournament" because that is what a tournament says; a config whose primary call to action is generic ticketing wording fails validation rather than shipping.

A hundred players arrive and the only roster is in somebody's sent items

Entries reach a tournament office in every format a club can produce: a form, a spreadsheet attached to a reply, a text message with three late additions, a phone call on the Thursday about a player who has broken a wrist. The coach who paid is rarely the person who knows the squad, so the list moves between two people before it is right, and the version that gets printed for the gate was accurate on Wednesday. Nobody notices the gap until a volunteer is standing on a touchline holding a name that is not on their sheet, deciding on their own whether to let a child play.

What bindro does: The roster is part of the order rather than a document beside it. Paying for a squad creates exactly one place per place paid for, each place can be typed in by the coach or emailed to that player's family to complete themselves, and every place is validated in full whenever it is filled — a half-completed player is refused, and an answer key nobody declared is refused rather than quietly stored. A place that has never been named admits nobody and is not on the door list at all, so the unfilled ones are visible on the Saturday morning rather than in the post-mortem.

One signature is doing the work of twelve families

The coach ticks the box. That is how team entry works nearly everywhere, and it is the arrangement an insurer is least likely to have in mind: the person accepting the risk of a collision sport on behalf of a twelve-year-old is a volunteer who coaches them on Tuesdays, not the adult legally responsible for them. It holds up fine until the one weekend it matters, and the first anybody hears about the gap is a claim form asking which parent agreed to what, months after the tournament, when the only record is a checkbox with a club name against it.

What bindro does: Bindro is exact about which half is which, because the difference is the whole point. The signature is typed once at checkout; the ACCEPTANCE it writes names each player on the entry, inside the transaction that takes the money, stored with the requirement as it was worded, a digest of that wording, the retention period and the name that signed — and a player no acceptance covers is refused at the gate, which is what makes an unfilled place visible on the Saturday rather than in a claim. What is per FAMILY is the guardian consent: every player entered as under eighteen raises a request to the guardian's own address, and that child is refused at the gate and left off the offline door list until their guardian follows their own link and signs. For a squad of twelve minors that is twelve signatures from twelve people, each enforced where it matters rather than counted in a report.

A division filled a fortnight ago and two clubs have already booked hotels

Divisions do not fill evenly. The competitive bracket goes in a week, the recreational one is still half empty the night before, and a director watching a shared sheet finds out which is which by reading it. Turning a club away is bad enough on its own; turning one away after they have paid for two rooms and a minibus is the conversation that decides whether they enter next year. The usual defence is a manual entry cap that somebody has to remember to enforce on an evening when they are doing something else.

What bindro does: Each entry type carries its own capacity and its own on-sale window, and the counts move only under a row lock inside the transaction that confirms the order, with a database constraint behind it — two clubs cannot take the last place in the same second. A division that fills stops selling by itself and says so in this trade's own words rather than showing a generic sold-out badge, and the remaining count is live on the day-of screen while the weekend is running. An early tier that closes on a date and a standard tier behind it are real inventory: they open and shut at the minute you set, whether or not anyone is watching the console that evening.

The school team can only pay on a purchase order and entries close on Friday

A large share of youth sport is billed through somebody who has never heard of your tournament: a bursar, a district finance office, a parent association with its own approval cycle. They cannot put a card into a checkout, they need an invoice with their own reference on it, and their payment run is three weeks after the date you wanted entries closed. A platform that only takes cards does not remove that team; it moves them into a spreadsheet you maintain by hand alongside everything else, with a place held on trust and no way to tell whether it was ever paid for.

What bindro does: A club can choose to be invoiced, and the invariant behind it is worth knowing. The entry confirms with no card: the places are committed, the credentials exist, the bill is numbered in a gapless per-organisation sequence and emailed to the accounts address quoting the club's own purchase-order number, and the team is on the door list. Because nothing has been paid, nothing is credited to you — an invoiced entry writes no ledger entry at all — so no settlement can ever cover a sale nobody has paid for. Recording the remittance is a deliberate act by an owner or finance user against a reference, and a bill left unpaid past its due date is voided: the entry cancels, the places return to sale, and a stale door scan for it is reported as rejected rather than silently dropped.

Two fields, four gates and one bar of signal

Tournament sites are chosen for their pitches, not their coverage. The check-in that works in an office is a page that will not load in a field at half past seven on a Saturday, with a queue of coaches behind it and a volunteer who was handed the job ten minutes ago. So the gate falls back to paper, the paper is a printout of a list that has changed since, and every question that paper cannot answer — is this player signed for, is this team paid, did they already come through the other gate — becomes a judgement call made by whoever is holding it.

What bindro does: A door device syncs a signed manifest before it loses coverage and validates every scan locally, with no network call at all. Check-in here is name-list first, which is what a volunteer with a clipboard's worth of training can actually work, and the code in the entry email scans just as well. Shift logs replay when a signal comes back, a re-upload counts once rather than as a second admission, and a player returning through their own gate is readmitted as a re-entry while the same code at an unrelated gate lands in a conflict queue for a human. A named point further along counts as progress, not a return. The two refusals that matter travel with the manifest: a player whose guardian has not signed, and a place nobody has named, are not on it.

The facility's share gets agreed in a car park and worked out twice

A weekend that uses somebody else's fields has at least two parties with a claim on the entry fees, and often three once the officials' association is counted. The percentages are agreed verbally in February and reconstructed in July by two people with two spreadsheets, who disagree by a few dollars because one of them netted the refunds and the other did not. The argument is never about the money. It is about nobody being able to show how the number was reached, which is why it takes three emails.

What bindro does: Shares are set in basis points that must total the whole — the database refuses a split that is not one hundred per cent — and the allocation is largest-remainder, so the parts add up to the payout exactly, to the cent. The cut is frozen onto the payout when it is scheduled, so a later edit cannot move settled money, every party is named on your money screen with their allocation, and a refund re-cuts every share at the ratio that was frozen. The honest limit is stated everywhere it is relevant, including here: bindro holds no bank details for anyone except you, so it produces the arithmetic and the record and you still send the facility its money.

The standings spend the week after the weekend in a group chat

Results are the one thing every club asks for and the one thing that gets typed last. They go out as a photograph of a whiteboard, or a message thread where the third correction contradicts the first, and a fortnight later somebody asks who won the recreational division and nobody can find it. A half-finished ladder posted early is worse than none: it gets screenshotted, shared and quoted back at you by a club that read it before you fixed the second column.

What bindro does: A standings table is typed into the console — division, rank, competitor and an optional score — and every row stays a private draft until you publish that tournament's results in one deliberate act. Until then the public page is a 404 rather than an empty table, so a half-entered ladder is never on the internet with your name on it, and once published the page groups the rows by division at a stable address you can send a club. Both acts are role-gated and audit-logged. What this is not is live scoring, and it computes no ranking from match results, because bindro never sees a match.

One order for a squad, one roster that outlives it

Team entry is the purchasing unit this vertical is configured around, so the roster is not an add-on to a ticket sale — it is the thing the order creates. A coach buys the places, names the players whenever they know them, and the roster carries the team name the players appear under. The rules do not defer with the names, which is the part directors are usually surprised by in the right direction.

• Exactly one place per place paid for — a roster never mints a thirteenth player.
• A place filled in weeks later is validated exactly as one filled at checkout.
• Re-typing a place swaps the player, raises a fresh guardian request, and moves no money.

A guardian consent the gate enforces, not a box the coach ticks

When a player is entered as under eighteen the form asks for that guardian's own email address rather than the coach's, and confirming the entry raises one consent request per minor to that address. The link is unique, works with no account and no app, and a guessed one is a dead end; only the signature's cryptographic digest is stored. The enforcement is what makes it worth having rather than the record.

• A player added to the roster after payment raises the request in the same transaction as the fill.
• The waiver is separate: one typed signature at checkout, and an acceptance record naming each player, which the gate reads before it admits anybody.
• Signing once is enough; nothing asks a family to sign again at the gate.

Division requests you can overrule, and the one age rule that is actually enforced

Every entry asks which division the team wants, that request is kept as what the buyer said, and you get a separate assignment column: the division a team actually plays in is your decision, it is what the roster and the results page read, and the change is audit-logged. Be exact about age, though, because the form reads stricter than the engine is: the only rule enforced on the money path is a floor of five years old, and this vertical's divisions are skill bands rather than age grades.

• A requested division outside the published options is refused at registration, not stored.
• Recreational, competitive and elite are skill bands — nothing compares a birth date to a grade cut-off.
• A registration below the minimum age is refused with the rule named, before any order exists.
• Every player's date of birth is collected and kept; matching it to your grade is a human reading the roster.
• Proof of age is uploaded before payment and retained for you to open — nothing parses it.

An application queue for the weekends where who enters matters

Turn review on and an entry becomes an application: the club completes the whole form and uploads its documents, the places are held while you decide, and no payment intent exists until you approve — so "money cannot be taken before approval" is structural here rather than a status somebody has to remember to check. The queue is also the one screen in bindro that shows you what a club submitted, under your own field labels, with their uploads openable beside it.

• Approving emails the club a link to pay; rejecting releases the places, scrubs what they sent and tells them.
• An application nobody decides on expires with its hold, so an abandoned queue does not sit on your inventory.
• Insurance certificates and proof of age arrive here, before the money, where you can read them.
• Nothing in bindro checks a certificate's expiry or matches a document to a date of birth — that stays with you.

A weekend sold as one weekend, priced in tiers that close themselves

A tournament is modelled as a multi-day agenda, so Saturday and Sunday are sessions of one entry rather than two events a club has to find separately. Pricing is tiered: an early-entry price with an on-sale window, a standard price behind it, and promo codes for the clubs that came back from last season. Both are inventory that manages itself once published.

• One listing, as many sessions as the weekend runs, one entry covering them.
• A tier stops selling at the minute you set, without anyone watching the console.
• Promo codes are the discount that does work for returning clubs.
• Complimentary entries can be issued for a host side or an invited club without a payment.

Jerseys and add-ons with stock that runs out honestly

Apparel is sized per player at registration and sold as an add-on with its own stock per size, so the number your supplier needs is a number the platform actually holds. This is also the clearest example of a limit worth knowing before you plan around it: what you can read back afterwards is what was BOUGHT, not what was ANSWERED.

• An apparel add-on holds stock per size and shows sold against remaining on the event page.
• A size that sells out stops being offered rather than overselling your order to the supplier.
• Jersey size, emergency contact and medical notes are collected, validated and classified by sensitivity.
• Those answers are readable in the approvals queue before payment, on the player’s own record after it, on the players list and as a column each in your CSV export — but never arranged around the fixture.

Volunteers who can work a gate without seeing the money

A tournament runs on people who are there for one morning, and the safe thing to hand them is a login that can do exactly one job. Roles are checked in the handler rather than by hiding a button, so a gate login sees a name and whether the code admits, and not what anybody paid. There is a rota beside it, and today's shifts render on the day-of screen next to the numbers you are watching.

• Put a member on a session with a role and a start and end time; re-rostering edits their shift rather than stacking another.
• Inverted times, unknown roles and unknown sessions are refused.
• A shift is not permission — being on the rota grants access to nothing.
• Live remaining places per division show on the same screen while the weekend runs.

Entries taken from the club's own site, and the ones you key in yourself

Not every entry starts on a bindro page. There is a hosted entry page for the tournament, an embeddable checkout for the site the club already has, and a back-office order for the team that entered by phone or handed you a cheque at a league meeting. All three produce the same entry, the same roster and the same credentials at the gate.

• The hosted page carries the vocabulary of this trade, not a generic checkout with your badge on it.
• The embed puts the same entry flow inside your existing website.
• A back-office entry records a team that paid you outside the platform — and cannot be refunded through bindro, because no card was charged.
• Refunds otherwise run from the console, or from the signed link in the coach's own confirmation email where your policy allows it.

Everything exports, because next season is yours and not ours

Orders and players come out as CSV whenever you want them, behind a one-time code, with no export fee, no notice period and no contract to leave. The clubs that entered are a list you keep, so next season's announcement does not depend on us still being the platform you use.

• Entering clubs are retained as your own contacts, per organisation.
• A post-event email goes to the people who came, so the standings and next season's dates reach them.

Who pays the booking fee?

The player, unless you say otherwise. Every tournament carries its own setting — the player pays, you absorb it, or you split it — and the fee itself does not change with the choice, only which side of the sale it comes from. On a ten-entry $25.00 tournament that is $16.20 either added to what players pay or taken out of what you keep.

Because the default is the player, a tournament can go from signing up to a sold-out tournament without paying bindro anything up front, at any point, ever. We are paid out of sales that happened or we are not paid.

The word "event" is load-bearing and worth reading twice. The scheduler groups by tournament, admits one only once its LAST session has ended, and pays it once. A tournament sold as a run of dates therefore pays after the final date, not after each one — a season's float is not something an operator should discover halfway through the season.

Bindro never pays before delivery, in any vertical. A pre-event advance is a configuration violation platform-wide rather than a policy someone can be talked out of, because paying out on tournaments that have not happened is exactly how a cancellation becomes players with no refund. "Paid" also means the money moved: a payout only reaches its paid state with a real transfer reference attached, enforced by the database rather than by a status field someone can set.

• One payout per tournament, after its last session ends, one in flight at a time.
• T+2 for this vertical (medium risk tier), with 7.5% held as reserve and released later.
• Refunds reverse in a fixed order — your proceeds first, then tax, then our fee — so a refund never leaves you charged for a sale that was undone.
• Sales tax, where it applies, is held as a liability rather than mixed into your balance, so the payout figure is proceeds rather than a number you still have to do subtraction on.

Teams registered is the most direct of the four, because in this vertical the order IS the team: one order, one team name, one coach who paid. What the order holds is places — an entry IS a place, and whether a place is one player or one whole squad is decided by the entry type you publish. The dashboard counts those teams — withdrawn ones removed — over the tournaments you have actually delivered, and reads as an all-time count until you have delivered one, so an entry list for a weekend still to come is never divided by a denominator that does not exist. Both numbers are on that one screen, and the second only reads with the first: beside the team count the Sold tile says "entries sold vs capacity" and is counting places, so twelve clubs buying twelve player places each stand at a hundred and forty-four there rather than at twelve. Set the capacity in the unit you sell.

Division fill rate is teams entered against the minimums you declared, and it is read off the division a club REQUESTED on its entry — the answer on the order, which is what both the divisions board and the analytics figure join on. A division you have set no minimum against is in neither half of the fraction: that is a question you have not answered rather than evidence a bracket is short. The division a director later assigns to a player sits on that player's record, the players list and the export, and no fill rate reads it. The board itself says division by division whether it will run, and re-counts the moment a team withdraws.

Waiver completion arrives as both a percentage and an enforcement, and the enforcement is the half that matters on the Friday. The analytics page prints the rate with its counts underneath — players who have signed their own waiver, out of the players named on paid entries — while the roster names WHICH place is outstanding, so you chase a name rather than a ratio. And an unsigned player cannot walk through the gate anyway: the door refuses a participant no waiver covers and the manifest leaves them off.

One honest note about the segments this vertical is configured to report on: age group is among them, and this platform holds no age-grade rule. Segmenting by it here means segmenting on data you have, using a grade definition that lives in your competition rules rather than in our configuration.

What the console shows today, without an integration or a spreadsheet:

• Gross, platform fees and refunds per tournament, read from the ledger the payouts reconcile against.
• Entries sold against players checked in, with a no-show percentage per session.
• Live remaining capacity while the tournament is running, per pool, on the day-of screen.
• This tournament's own funnel — view → team created → roster added → waivers signed → paid → checked in — stage by stage with the drop-off between them, and any step the platform cannot see said so rather than shown as a zero.
• Refunds, transfers, turnout, no-shows, add-on attach and repeat buyers, each printed with the two numbers it was divided from.
• Orders and players as CSV, so anything not on the screen is one export away.

Two more that are worth stating plainly. Sensitive answers are classified on the field rather than by convention, and health data is excluded from analytics exports and from AI context absolutely, with no override in any vertical. And a tournament's own people see only what their role allows — a door login sees a name and whether the code admits, not what anyone paid — which is checked in the handler rather than by hiding a button.

• Brackets, schedules and scoring — there is no bracket generator, no fixture list, no court or field assignment, no seeding and no live scoring anywhere in bindro. Results are a table you type in yourself — division, rank, competitor, score — kept private until you publish them. If you draw brackets in a scheduling tool today, keep it: bindro takes the entries and works the gate.
• A waiver typed by every player's family — the acceptance record names each player and the gate refuses one it does not cover, but the signature it carries is the one the payer typed at checkout, or the name typed on a place filled in later. It is not twelve families each shown the wording at their own link. The one per-family signing act is the guardian countersign for under-eighteens. If your insurer expects a form signed by each player's own household, collect those yourself.
• Checking that a player is the right age for their division — the only age rule enforced on the money path is a floor of five years old, and this vertical's divisions are skill bands rather than age grades. Every date of birth is collected and kept, and no cut-off date is compared against it by anything. Age-grade eligibility is a human reading the roster.
• Sending the host club or the facility their share — bindro works out each party's cut to the cent, freezes it onto the tournament's payout and names it on your money screen, but it holds no bank details for anyone except you. A split tournament therefore settles to nobody until that changes, and the console says so rather than reporting a transfer that never happened. You still pay the facility.
• Collecting the balance of a payment plan automatically — you can publish a plan on the entry type and the deposit is taken at checkout, but bindro never charges the stored card for the rest of it. Off-session charging is armed by a separate switch that is set in no environment: a checkout happens with the payer watching and a sweep bills with nobody present. Collect the balance the way you collect anything else.
• A team rate that prices itself — the roster is real, but the group price and its threshold live on the entry type and nothing in the product writes them, so a per-team discount cannot be published. What works instead is an entry type priced for a squad, an early-entry tier that closes on a date, or a promo code you give returning clubs.
• A release ladder that hands over on its own — an early-bird entry type opens and closes on a date, and that much works. What is not here is the ladder proper: a wave selling out and announcing the next rung on the entry page, a fast-track type, or a price that varies by date. Price two entry types and close the first one.
• A touchline sheet arranged around the fixture — emergency contacts and medical notes by division, by pitch, by kick-off. Those answers are collected, validated, held under their sensitivity class and readable in four places: the approvals queue before you take the money, the player’s own record afterwards, the players list your gate works from, and a column each in your own CSV of your own players. What nothing builds is the sheet for the Friday, so print that yourself from the export.
• Selling a whole weekend day by day in the hosted checkout — the multi-day basket ships on the public JSON API, and the hosted entry page still sells one session per order. A Saturday-and-Sunday tournament is normally one entry covering the weekend; a day-by-day picker on the hosted page is not built yet.
• A waiting list when the divisions are full — waitlists are not declared for this vertical, so a full division says "Divisions full" and stops rather than collecting addresses nobody calls back. Raising the cap or opening another division is one form, and it sells entries.
• Handing a paid entry on — there is no ticket transfer for this vertical and no self-service move button. A coach can re-type a place on their own roster; a family cannot swap itself into another team and a club cannot sell its place on. Rolling an entry into next season IS covered, but as your act rather than theirs: you withdraw the team from the console and settle it as a credit, held against the captain's email for a future entry, and their places go back to the division the moment you do.
• Sales tax on an entry fee — tax is configured as optional for this vertical and is not turned on, so nothing is calculated, itemised or held as a liability. Whether a youth sports entry is taxable where you run is a question for your accountant.
• Checking the certificates you collect — the insurance certificate and the proof of age are uploaded before payment and retained, and nothing reads them. No expiry date is parsed, no document is matched against the date of birth on the form, and no team is ever suspended for a lapsed certificate. Watching for that stays with you.

If one of those is the thing you need, say so — the answer is a capability declared, built and gated properly, or a straight no. It is never a feature flag that collects the request and does nothing.

This is the first thing to settle because it decides whether the rest of the page is relevant to you. The tools this trade already uses are scheduling tools that grew a registration form; bindro is a registration and money platform configured for tournaments that will not pretend to draw a bracket. If your weekend lives or dies on automatic scheduling across eight courts, keep that tool and read the comparisons further down before you decide anything.

What running the entries here actually buys you is a set of refusals rather than a set of features. A place nobody has named does not admit a player. A minor whose guardian has not signed does not admit a player. A division that is full stops selling rather than going one over. An invoiced entry commits places without crediting you a cent. Each of those is enforced in the engine or in the database, and each of them is a Saturday-morning argument that never happens.

The one place the two halves meet is the standings, which bindro publishes for you once you have typed them — the address you can put on the entry page and in the post-event email without maintaining anything.

• Bindro: entries, rosters, waivers, guardian consent, divisions, money, the gate, published standings.
• Not bindro: brackets, seeding, fixtures, courts, schedules, live scores.

The order comes first and it is deliberately the only step that involves money. A coach chooses the entry, the number of places, the division they want and the team name their players will appear under, accepts the waiver in their own name, uploads what you asked for and pays — one order, one fee, one confirmation. If you have review turned on, everything up to the payment happens and then stops on your desk instead.

Naming comes second, and it is where most of the value sits. The confirming transaction creates precisely as many roster places as were paid for, and each one is either typed in by the coach or sent to that player's family to fill in themselves. Families filling in their own child is usually the better route: it is their spelling of the name, their emergency contact and their address on the consent request, and it takes the transcription errors out of the middle.

Consent comes third and runs on its own timetable. A player marked under eighteen raises a request to the guardian address given for that child, whenever the place is filled — at checkout in March or on a roster in May, in the same transaction as the fill either way. The signature is theirs, from their own inbox, with no account to create, and only its digest is kept.

The gate is fourth and it is the step that makes the other three true. The manifest a device syncs contains the players who are both named and signed, and nobody else. An unsigned minor is not a warning on a screen for a volunteer to weigh up at seven in the morning; they are absent from the list, which is the only form of enforcement that survives contact with a busy gate and no signal.

Per-player pricing is what unlocks this vertical's best behaviour. Twelve places means twelve roster entries, twelve credentials at the gate, a guardian consent per minor and a jersey size per child. A team-priced entry is one place and one credential — much simpler to reconcile, and it gives you none of that. Most directors who care about the safeguarding side price per player and set the number of places to the squad size they expect.

The fee arithmetic quietly favours the natural shape here, which is worth a sentence because it is the one place bindro is cheaper in a way that is not obvious. The platform fee is charged once on the ORDER, not once per place: a squad of 12 at $45.00 a place is a $540.00 entry carrying $14.49 of platform fee, where the same squad billed place by place would carry $25.44. Across 24 teams that is a $12,960.00 tournament paying $347.76.

Payment plans are the other thing families ask for, and the answer is a qualified yes stated plainly rather than left implied by a capability list. You publish the plan on the entry type — deposit share, number of charges, spacing — and the deposit is taken at checkout; part-paid money stays off your balance until the last charge clears. What bindro does not do is take the rest automatically, because it never charges a card with nobody present. In practice the clubs entering already collect from families across a season and pay you once, and the plan is for the ones that do not.

• Per-player pricing buys the roster, the consent per minor and a credential per child.
• Team pricing is one place and one credential: simpler, and much less per-child control.
• An automatic quantity discount cannot be published; use the entry price, a dated tier, or a promo code.
• 2.5% + $0.99 is charged once on the order, so a squad entered together is the cheaper shape as well as the natural one.
• A payment plan can be published on the entry type; the deposit is taken at checkout and you collect the balance yourself.

The float is the part to plan around. Entry fees taken in March for a June weekend stay with the platform until June, and a series published as one tournament with several sessions settles once, after the final session — so publish each weekend as its own tournament if you want each weekend's money on its own schedule. The lead time this vertical is modelled on is a little over a month, which is a planning horizon rather than a rule.

Splits are arithmetic plus a record, and it is worth being precise about where that stops. Every party's share is computed to the cent, frozen onto the payout when it is scheduled, named on your money screen and re-cut in the same proportions when a refund happens. What does not happen is a transfer: bindro holds bank details for you and nobody else, so the console reports what each party is owed rather than reporting a payment that never left. You still pay the facility.