Why constraints must be written as formulas
"Over 35 tournament" is not a constraint: it is an intention. Is someone who turned 35 two weeks after the tournament in or out? And what about someone who turns 34 the day before? A usable constraint answers three questions:
- What is it measured on? Year of birth, or age reached on a specific date.
- What is the threshold? A year or an age, with the correct sign (greater than or equal to, less than).
- Are there exceptions? How many, and with what limits.
With these three answers, the check is mechanical and no one can argue.
The two ways to calculate age
By year of birth. "Players born in 1990 or earlier can play." This is the method used by federal youth categories and has a huge advantage: verification is instantaneous and does not depend on the date of the tournament. The downside is that two people born twelve months apart can end up in different categories despite being practically the same age.
By age reached on the date. "They must have turned 35 by the day of the tournament." Conceptually more precise, more annoying to check, and ambiguous if the tournament lasts two days (in that case, set the reference date: the first day).
For amateur tournaments, calculation by year of birth is almost always the best choice: it is verified by reading four digits, and in an over or under category a difference of a few months changes nothing.
Under and over
- Under N: players born in the reference year or after can play. An Under 21 in 2026, calculated by year of birth, admits those born from 2005.
- Over N: players born in the reference year or earlier can play. An Over 40 in 2026 admits those born up to 1986.
Always write the explicit year next to the wording: "Over 40 (born in 1986 or earlier)". The wording alone is interpreted in three different ways by three different captains.
Over-age players
A rigid age limit excludes teams that would have only one player over the threshold. The standard solution is the over-age player: N players beyond the limit are allowed, with constraints on how many can be on the court at the same time. To be written:
- how many over-age players in the roster (typically one or two);
- how many on the court at the same time (often only one);
- by how much they can exceed the limit, if there is a second limit.
Beware of a side effect: if you allow two over-age players on the court out of six players, the age constraint stops characterising the tournament. One over-age player out of six is a safety valve; two is a different formula.
Gender quotas in mixed tournaments
The constraint is almost always written as a minimum number of female players on the court at all times: two out of six and three out of six are the most common formulations. The difference between the two is not quantitative, it is tactical: with three out of six the tournament is truly mixed, with two out of six it remains a men's team with two female players.
There are two details that make the difference between a working constraint and an unmanageable one.
First: the minimum on the court determines the minimum in the roster. If two female players are needed on the court at all times, a roster with exactly two female players leaves no margin: at the first injury or the first substitution, the team is out of compliance with the rules. If you accept such a roster, state what happens in that case. In general, require at least one more female player than the minimum on the court.
Second: the positioning on the court. With two mandatory female players and rotation, if the two female players are in adjacent positions, they will periodically find themselves both in the front row or both in the back row. Placing them diagonally distributes the load across all six rotations. This is not a regulatory obligation: it is advice to be given to captains in the regulations.
Some tournaments add constraints on touches (for example: at least one female touch per play). These are rules that work in 4 against 4 and in beach, while in 6 against 6 they become difficult to control without a referee: evaluate them carefully.
Registered players and levels
The least written and most discussed constraint. "Amateur tournament" means nothing: in Italy, many people have an active federal registration or have had one in the past. If you want a tournament of a homogeneous level, the constraint must be made objective:
- maximum number of registered players in the roster and/or on the court;
- possible exclusion of those who have played in certain categories in the last N years;
- request for a declaration from the captain at the time of registration.
A practical criterion that reduces disputes without impossible checks: ask for the declaration, state that it is accepted in good faith, and that a team clearly out of their depth can be excluded from the prize-giving. In practice, this works better than a strict set of regulations that no one can verify.
Verifying without becoming an office
Checking constraints is tedious and must be done at the time of registration, not the morning of the tournament. You need the date of birth of each player and to know who is in the gender quota: two columns in a list. A detail to foresee: if a player is added to the roster after registration, the constraints must be rechecked — and that is exactly when no one does it.
In VolleyFriends, constraints are tournament parameters and roster eligibility is verified when the team registers and every time the roster changes, so the check does not depend on someone remembering to do it manually.