Divisions, eligibility and the age-grade check bindro will not do for you

What does the division request actually do?

It records what the team asked for, and nothing more. The entry form offers the divisions you published, a value outside that list is refused at registration rather than stored, and the answer stays where the buyer put it — as a request.

Your decision is a separate column. Assigning a division writes it against the player, the roster and the results page read the assignment rather than the request, and the action is role-gated and audit-logged with your name on it. An assignment can be cleared again. The reason the two are separate is that a roster which showed what people asked for would be a roster nobody could run a tournament from.

Why does nothing check the age grade?

Because the only eligibility rule this vertical carries is a floor. A date of birth below five years old is refused on the money path with the rule named and the error anchored to the field, before any order or payment exists, and an unparseable date is refused too rather than waved through. Above that floor, nothing compares a birth date to anything.

The divisions themselves are the other half of the explanation: recreational, competitive and elite are skill bands, not age grades, so there is no cut-off date on them for an engine to enforce. If you run age grades, you are running them on top of a platform that collects every date of birth accurately and leaves the comparison to you.

• Under five is refused on the money path; everything else is collected and kept.
• An unparseable date of birth is refused rather than stored as garbage.
• Divisions in this vertical are skill bands with no dates attached.
• Proof of age is uploaded per entry, and nobody but you ever opens it.

How should a director run age grades on this anyway?

Publish the cut-off in the listing, collect the birth dates through the form, and make the assignment step the checkpoint. The dates arrive per player, which is the part that would otherwise be a spreadsheet, and the assignment column exists precisely so that a human decision can override a hopeful request.

If age grade is a compliance matter rather than a fairness one, do the check against the uploaded proof of age before you assign, and treat entry review as the gate: with review turned on the club's documents and answers are in front of you before their money is taken, which is the cheapest moment to refuse an entry.

What about brackets, seeding and the schedule?

None of them exist here, and this is the honest headline of the whole vertical. There is no bracket generator, no seeding, no pools, no fixture list, no court or field assignment and no live scoring. Whatever you draw the tournament in today, keep it.

What bindro does after the weekend is a standings table you type — division, rank, competitor, an optional score — held as a private draft until you publish it in one deliberate act, at which point the public page groups it by division. Before that the page does not exist rather than showing an empty ladder. It is a results page, not a scoring system, and nothing computes a ranking from match results because bindro never sees a match.

• No brackets, no seeding, no fixtures, no courts, no live scores — none of it.
• Results are typed in and stay private until one explicit publish act.
• The published page groups by division and 404s while unpublished.
• Recording and publishing are both role-gated and audit-logged.