Register and manage matches
The match does not belong only to the tournament or only to the independent sessions. It is a functional unit of the platform, with its own reading, capture, closing and validation logic, although it may appear within different competitive contexts.
Player
Confirms presence when you apply, takes your seat, registers or reviews hands and confirms the result that corresponds to you.
Organization
Gives institutional context to the match and consults its aggregate effect; does not modify results without operating authority.
Administrator
Initiates, corrects, reopens, records absences or fouls and validates the closure, preserving the traceability of the result.
Table and match reading
The table is the operating unit where the match actually occurs. It also helps to read two different things: the comparative expectation between pairs and the actual accumulated score.
Top bar
The top bar helps interpret what relative strength each pair brings before looking at the actual result of the match. Its reading is comparative: it guides the competitive expectation between both sides.
Bottom bar
The lower bar shows how the accumulated points are really distributed and helps to see if the match is balanced, inclined or almost resolved. Its reading is no longer one of expectation, but rather a real marker.
Match life cycle
The match does not experience a single closure. It is advisable to distinguish between the sports closing of the table and the formal closing that confirms that ballot within the platform.
- Created: there is not enough development yet.
- Started: the table can now register hands or deals.
- Finished: the game has already closed for sport.
- Validated: the closure has already been formally confirmed.
Deals or hands
What each hand records
Hand number, winning side, points and sequence of play help reconstruct how the match actually played out.
Operational reading
The hands are not a minor detail: they turn the match into a verifiable story and help to correct or confirm the closure when necessary.
Quick edit of many
This tool allows the administration to directly edit the accumulated points of each pair and let the platform reconstruct the minimum detail of hands necessary to maintain the consistency of the match.
How to get there
- Enter the tournament or independent session where the table you want to correct is located.
- Open the section Partidas.
- Change to list view, because this tool lives in that format.
- Use the administrative bar and press Edit listing.
- In the many columns, write the new values for each pair.
- When you're done, press Save changes.
When should it be used
- When the table has already been played and you need to quickly correct the score.
- When it is not necessary to redo hand by hand from the match details.
- When you want to maintain the operational rhythm without opening a complete domino tile for each correction.
- If only one pair has points and reaches the goal, a single winning hand is reconstructed.
- If only one pair has points and does not reach the goal, the platform completes a second hand for the opposing pair with the goal points.
- If both pairs have different point totals, both values are respected and two hands are created.
- If both pairs have the same value greater than zero, the reconstruction is rejected.
- If no pair reached the goal, the match can retain status started even if it already has a registered score.
Player and administrator
What the player does
Follow the score, view the history, participate in the capture when appropriate and confirm your part of the sports closure.
What management does
Annotate, correct, validate, remove validations when the flow allows it and maintain the general consistency of the match.
Absences and confirmation of attendance
The attendance of players at a table is governed by the tournament logic. The central variable is Use RSVP. That decision doesn't just change a clock or a visual detail: it changes how each player's presence is interpreted before actually starting the match.
If confirmation is enabled
- Each player in the match can be in three states: Pending, Present or Absent.
- Attendance is made visible on the table as part of the operational monitoring prior to start-up.
- As long as a person remains pending, the organization can follow that status and make decisions before starting or closing due to absence.
- If the closing automation due to absence is also activated, pending confirmations can be transformed into real absences upon expiration of the configured tolerance.
- If the round uses Continue Round, the affected tables end due to absence. If you use Reset Round, the round is recreated leaving out those who were missing.
If confirmation is disabled
- The platform considers by default that players are Present.
- Normal profiles do not need to see a pending status because that step is not part of the visible flow.
- The administration does retain the attendance chip as an entry point to manually dial Present or Absent when necessary.
- If an absence is finally declared, that absence becomes visible to the other profiles even if confirmation was not a mandatory phase.
From a visual point of view, support lives on the player's avatar. For administration, the chip functions as a work control; For the other profiles it works as a reading signal. When the confirmation flow is active, all people can recognize the presence status. When it is not, the organization continues to have control and the rest only see the issue if there really is a marked absence.
What management sees
- A direct entry point on each player to mark attendance.
- Ability to switch between Pending, Present and Absent.
- In tournaments without confirmation of attendance, the status Pending stops making operational sense and the platform itself normalizes it as presence.
- The possibility of causing the recalculation of the table based on the marked absence.
What other profiles see
- A clear readout when RSVP is part of the tournament flow.
- Visible absences even if the tournament has not activated confirmation as a general process.
- A cleaner interface when attendance does not require public intervention.
In the sports closing of the match, absence is not a cosmetic detail. If a tournament table registers at least one absence, the match may be closed for that reason. The winning pair becomes the one with players present on their side. At the individual level, the behavior has an important nuance: when the format calculates individual statistics, absence only drags the absent player; the present partner does not automatically inherit that individual defeat. If the format does not separate that individual reading, the absence can weigh on the entire side.
Fouls, penalties and sporting effect
The discipline of a match is recorded player by player. Each foul belongs to a specific match and keeps four pieces visible to the organization: date and time, card color, penalized points and reason. In the current version the reason is free text, intended as a simple base that can be classified in more detail in the future.
How a foul enters
- The administration opens the player's disciplinary details from the foul indicator on their avatar.
- In the modal you can add, edit or delete foul records for that specific match.
- When changing the color of the card, the platform automatically proposes the default points defined in the round configuration: yellow, red or black.
- Those points remain editable by the administration if the situation requires it.
How other profiles see it
- The same detail can be opened in read-only mode.
- The table does not become an extensive spreadsheet: the main reading remains compact and is supported by the disciplinary chip and the modal summary.
- The user can see how many fouls there are, what colors were recorded, how many points they add up and what reason was recorded.
The cumulative color logic does not take the worst individual color recorded; instead, it takes the total penalized points and compares it to the active thresholds for the round. If the accumulated total reaches or exceeds the black threshold, the accumulated color becomes black. If it does not reach black but does reach red, red is displayed. If it only reaches yellow, it shows yellow. If the total remains below the first threshold, the table retains a more neutral reading.
Yellow threshold
Marks the first visible disciplinary level. Upon reaching it, the chip and the summary are no longer seen as a mere minor observation.
Red threshold
Activated when the total sum exceeds the average penalty level defined for the round. It does not depend on the existence of an isolated individual red card.
Black threshold
Represents the most severe disciplinary accumulation. It is achieved by total points and not just by the presence of an individual black card.
That same accumulated color is also shown within the modal, along with the total points. This way, the organizer does not need to interpret isolated figures and can see how many fouls there are, how many penalized points they add up to and what disciplinary level the player falls into within that table.
In daily operation it is convenient to distinguish two planes. The first is the disciplinary reading of the match, which today is already reflected on the table, in the modal and in optional columns of lists of matches and competitors. The second is the sports effect, which is based on the competitor's penalty within the round. This is where the configuration option Penalties can change the winner comes into play.
When the option is activated
- When closing the match, the system subtracts the player's penalty from their individual points in favor.
- If this adjusted total is below the points received, the player can go from individual victory to individual defeat.
- This modifies the reading of JG, JP, TF, TC, point difference and individual effectiveness.
- This is a way of saying that the table may have won as a pair, but one player can individually bear the sporting cost of their penalties.
When the option is disabled
- The penalty still exists as a disciplinary reading.
- The organization continues to see fouls, accumulated points and resulting color.
- But the platform does not use that penalty to return the individual result inherited from the table to the player.
This has an important consequence for the organizer: the winning pair of the table is not rewritten with the same logic as the individual result of the player. The pair continues to close by points, time or absence as appropriate. The penalty adjustment is applied to the competitor's individual reading. That is why fouls strongly affect the personal result and the disciplinary interpretation of the tournament, without automatically converting each penalty into a rewrite of the winner of the pair.
At the tournament monitoring level, this information is also projected to the lists. Matches and competitors can display optional columns of number of fouls, points for fouls and accumulated color. This helps the discipline not to remain hidden in a single table, but rather integrated into the general reading of the event.
Recalculate historical chronology
In terminated independent sessions, this recalculation must start from actual start and not from the planned start. The idea is that the visible history of the event resembles what really happened on the court and not just the original intention of the calendar.
When should it be used
- When the actual start date was incorrectly recorded.
- When it is necessary to redo the temporal sequence of rounds, matches or deals.
- When the visible time does not match the local reading expected by the organization.
What does not change
- Does not recalculate winners or results.
- Does not change points, fouls or sports finishes.
- Does not play the event again: only corrects its chronology.
How to redo the times
- In tournaments, each reconstructed match is based on the configured time of its round.
- If the match has registered deals, that time is distributed evenly among its deals to avoid disproportionate historical durations.
- In independent sessions the same idea is applied and the consistency of occupation between reconstructed matches is preserved.