Items
The match is the unit where the result actually occurs. It can live within a tournament or an independent session, but it has its own functional value: scoreboard, hands, validation, closure and differentiated reading for players and administration.
Quick edit of many
Quick score editing allows management to correct or complete a match score without points hand-by-hand from scratch. It is not a simple scoreboard: when saving, the platform reconstructs the minimum hands necessary for the match to maintain sporting and administrative coherence.
When should it be used
- When you need to quickly correct the score of a table.
- When not all hands were recorded, but the accumulated result is known.
- When the organization needs to repair an item before validating it.
When not available
- Not allowed if the round has already been closed.
- Not allowed if the match is already validated.
- If the match has already been validated, you must first use Modify Match.
| What the administration introduces | What the platform does | Expected result |
|---|---|---|
| Only one pair has that many and reaches or exceeds the goal | A single winning hand is created for that pair. | The match is ready to move to finished. |
| Only one pair has points and does not reach the goal | Two hands are created: one with the written value and another for the opposing pair with the goal points. | The platform interprets that the opposing pair was the one that closed the match. |
| Both pairs have points different | Two hands are created, one for each pair, respecting exactly those values. | If no one reached the goal, the match continues started. If any pair reached it, go to finished. |
| Both pairs have the same value and is greater than zero | The platform does not accept the reconstruction. | An error is displayed because this path does not allow ties in the translation to hands. |
Absences and confirmation of attendance
Within a match, attendance is not just treated as an informal observation. It can be part of the operational flow of the table, especially when the tournament activates RSVP before starting the round. This allows us to distinguish between those who have already confirmed presence, those who are still pending and those who are finally marked as absent.
When the commit is active
Attendance becomes a visible layer of the table. The organization can track who is foul to confirm and use that reading to start the round with more order or automatically close a match due to absence when the configuration allows it.
When confirmation is not active
The platform assumes by default that the people present at the table are available to play. Even so, the administration retains the ability to declare an absence manually if operational reality requires it.
Fouls and penalties
Fouls introduce a disciplinary reading within the match. Its objective is not to reload the screen, but to allow the table to keep a clear trace of the issues that affect a player: card color, points to be deducted, time of registration and associated reason.
Compact reading
Discipline is summarized visually with a chip above the player's avatar. That chip isn't trying to tell the whole story; summarizes whether there are fouls and what cumulative severity they reach at that moment.
Detailed reading
When opening the detail, the platform shows the foul history of that player in that specific match. The administration can manage it and the other profiles can consult it in read-only mode.
What it expresses
- The concrete result of a table and its visible development.
- The relationship between marker, hands, validation and closure.
- A sports reading that can be public, operational or administrative depending on the context.
Why is it central
- It is the point where the previous configuration becomes the real result.
- Feeds ranking, history, positions and subsequent reading.
- Makes visible the difference between playing, finishing and definitively confirming a table.
Participation and check-in
- Publishing a tournament is not equivalent to having all competitors confirmed.
- Between publishing and playing there is request, invitation, acceptance and confirmation.
- That explains the difference between participant and competitor already incorporated.
Match life cycle
- A match goes through different stages before being completely closed.
- Finishing a table does not always mean that everything has been definitively confirmed.
- The organization can accompany closures, corrections and confirmations when necessary.
Deals, hands, and table
- The hands are part of the central detail of the match and not a hidden flow.
- The table and the scoreboard translate comparative expectation and actual accumulated result.
- Player and administration do not read the same match in the same way.
Independent sessions
- Allow competitive activity outside of the full tournament.
- They group matches, players, states, seats and active table.
- They are valuable for fast, traceable and shareable activity.
Warnings and verifications
- The system can warn if a player is already at another active table.
- Validates compatible profile, seat availability and absence of duplication.
- If the session requires membership, membership becomes an actual operating condition.