Process map Implemented

Create and operate tournaments and rounds

Here the manual develops the tournament as a complete event: setup, participants, rounds and execution.

Updated on 07/27/2026 32 minutes of reading

Create and operate tournaments and rounds

Here the manual develops the tournament as a complete event: configuration, participants, rounds and execution. Independent sessions and matches are explained in their own sections so as not to confuse their levels.

Player or competitor

Request participation or accept an invitation, RSVP when applicable, and compete in assigned rounds.

Owning organization

Defines the institutional framework, the circuit if applicable, visibility and the administrators responsible for the event.

Tournament Manager

Configure formats and times, manage participations, run rounds, attend to issues and close the tournament.

Configurations and formats

The format defines the main competitive unit.
The criteria and grouping determine the pairing before playing.
The variants by pair, team, four-player team or individual by team change the sports reading.

Participation and life cycle

Publishing is not equivalent to having participants ready to play.
Request, invitation, acceptance and check-in explain the step towards actual execution.
A match goes through different stages, and each one represents a different moment in the experience.

Rounds, tables and validations

The rounds organize the matches that belong to the tournament.
The platform helps to follow tables, attendance and results within each stage.
Hands, confirmations and the order of play make this layer especially sensitive.
When there is already recorded deals, an operational correction requires more care than a simple change of entry.

Tournament

This block brings together the reading of the tournament as a complete competitive event: how it is configured, how it incorporates participants and how it organizes the general route of the event.

Step-by-step tournament setup

It is best to read the tournament setup as a sequence. First the general framework of the event is defined, then times and automations are ready, then the initial table capacity is set, later the round blocks are designed and finally a compact confirmation is reviewed before creating the tournament. This sequence makes subsequent execution clearer.

Step 1. General framework

Name, organization, person responsible, capacity and planned chronology.
Place, country and general references of the event.
The base identity of the tournament and the type of experience you want to build.

Step 2. Rhythm and automation

Round, waiting, review and automatic closing times when applicable.
Expected behavior of the operating bar during the life of the tournament.
Decisions about how much to leave to automatic mode and how much to reserve for manual control.

Step 3. Tables and rounds

Initial number of tables to generate the base structure of the event.
Round blocks with their actual numbering range and their sports configuration.
A compact final commit with name, date, capacity, tables and rounds before creating.

Recommended approach: first define what tournament you want to build, then how the participating people will enter and confirm, then at what pace the event will advance and finally with what sports rules each round will be played.

Why it is not recommended to delete an advanced tournament: when a tournament has already entered its operational stage or has already ended, it is no longer just an internal configuration. From that moment on, it is part of the real history of the event: it incorporates participants, organizes rounds, generates matches, reflects results and can influence the general competitive reading. Therefore, in these stages, the normal thing is not to eliminate it but to manage it by closing, reopening or correcting its route. This route better preserves the traceability of the event, avoids loss of context and reduces the risk of deleting information that already has operational, historical or institutional value. The definitive elimination should be understood as an exceptional measure, reserved for situations of high responsibility.

Post, requests and invitations of participants

Once the tournament is published, a participant management phase opens, which is not yet a game, but it does define who will actually compete. In this layer the organizer manages requests received, invitations issued, status changes and confirmations of attendance, all from the same operational session.

Participation request

It is initiated by the competitor himself when he sees a published tournament and does not yet have an active relationship with that event. For the organization, that creates a pending engagement ready to review.

Tournament invitation

It is initiated by the organizer to bring a specific competitor to the event without waiting for that person to take the first step. It serves both to call and to complete the tournament table.

Addition to the tournament

It is used by the organization when the tournament is already in an operational phase where it is convenient to directly bring a profile to the competitive table, without treating it as a simple pending invitation. It is a more executive and immediate form of entry.

Confirmation of attendance

Appears when the participation has already been accepted and the tournament enters its day phase. It is the layer that separates who was admitted from who is actually present to play.

Practical difference

Invite proposes to participate, incorporate puts the profile in the operational table when the flow allows it, and confirm attendance registers that this profile is already present to compete.

Reading for the organizer

These three actions do not mean the same nor do they occur at the same time. Understanding this difference helps to avoid confusing construction of the table, administrative admission and actual presence at the event.

Main actions of the organizer

Invite players, pairs and teams: opens the corresponding selector to invite profiles to the published tournament.
Incorporate players, pairs and teams: allows profiles to be brought to the competitive table when the tournament flow already supports a direct operational incorporation.
Accept: approves a pending participation and brings it to the accepted state.
Reject: discards a pending participation when it is not appropriate to incorporate it.
Confirm attendance: records that the person or entity is already present to compete.
Revert: returns a share to a previous state when a decision needs to be corrected or a validation redone.
Eliminate: withdraws participation from the tournament when it should no longer be part of the tour.

State reading

Pending: there is a request or invitation, but it has not been approved yet.
Accepted: participation has already been admitted, but it is not yet equivalent to confirmed presence.
Confirmed: attendance has already been registered for the operational phase of the tournament.
Rejected: the incorporation was rejected by the organization or by the flow itself.
Cancelled or deleted: participation stops counting within the active tour of the tournament.

Top counters

Pending: shows how many entries need review.
Approved: summarizes how many have already been accepted into the tournament.
Capacity: helps you read if the tournament still accepts new entries or if it has already reached its limit.

Administrative Actions Bar

The organizer works with a top bar to select several rows and apply actions on the set.
The most important actions are kept visible on the desktop to speed up work.
The others are grouped in a contextual menu organized by type of action.

Actions Menu

Incorporate competitors: groups invitations or direct incorporations by type of entity.
Change status: concentrates accept, reject, confirm attendance or revert.
Other actions: gathers support operations such as marking the entire selection or eliminating participations.

Operational criterion: the post of the tournament opens the recruitment and organization of participants; acceptance builds the picture; The incorporation allows profiles to be added directly when the flow is already operational; and the RSVP defines who is actually ready to compete when the tournament enters its open phase.

Time and automation configuration

This block defines the rhythm of the tournament and the way in which the platform accompanies that rhythm. It's not just about activating automations: it's about deciding how much direct control the organization wants to retain and how much it wants to leave ready for the tournament to move forward without hindrance.

Where to configure

Can be left ready from the tournament creation wizard.
Can also be fine-tuned later from the tournament's Automation and Timing panel.
The important thing is that these decisions are made before entering the sensitive section of the game.

What it really is for

Makes the tournament rhythm visible in the operating bar.
Reduces forgetfulness and repetitive manual transitions.
Helps players, administrators, and the public understand why the tournament is waiting, playing, reviewing, or ready to move forward.

Key timing settings

Minutes to start round: is the wait between creating the round and actually opening it. It is used to review pairings, locate tables and order the players.
Absence tolerance: defines how long an confirmed presence is expected before resolving absences or startup issues.
Minutes of review: gives a small window to review results before formally closing the round.
Pause between rounds: marks the operational break between an already closed round and the next round to be created.

Tournament Automations

Auto start round: avoids having to manually open each round when its time comes.
Auto close round: advances the event when the review no longer detects pending issues.
Auto create next round: chains the preparation of the next competitive block.
Auto close tournament: ends the event when the last round has completed its cycle.

A key idea

Automate does not mean losing control. It means letting the platform do the predictable on its own and reserving human intervention for the delicate: complaints, complex absences, changes of pace or sensitive sporting decisions.

Confirmation of Attendance

If active, the round uses an availability pre-read before starting.
The administration can still mark presences and absences manually from the player list.
It is recommended when the tournament needs visible confirmation before starting play.

What changes for the administrator

Attendance stops being an assumption and becomes an explicit reading layer.
The operating bar and the round are better understood because the system knows if it is waiting for play or resolving availability.
When someone is absent, the decision between keeping the current draw or redoing it makes immediate sense.

Continue Round

It is the default option.
If before starting the round you mark someone as absent, the round draw remains as it was created.
When executing Start round, the affected matches are terminated due to absence and the rest of the round continues.
It is appropriate when the assembly is already considered correct and you do not want to alter the overall draw due to one or more specific absences.

Reset Round

If there are absences before starting the round, the system does not blindly preserve the original draw.
When executing Start round, the open round is discarded, those absent go to Out and that same round is created again with those who are available.
The round number is retained as the expected competitive phase, but the tables and pairings may change.
It is appropriate when the absence alters too much the sporting sense of the original assembly.

Operational bar reading: if the bar shows Waiting for start of round {n} and before that moment you mark an absence, the consequence is not only seen on the player's record. It will be seen in the behavior of the following button Start round. With Continue Round, the table is preserved and some matches will be closed due to absence. With Reset Round, the system rebuilds the draw before play begins.

General flow sequence

First the tournament is ready to create the corresponding round.
Then the round goes on hold until its start time arrives.
Then the round moves into play and table tracking begins.
Later comes the review, the closure and the pause before the next block.
Finally the next round is created or the tournament is closed.

When should it be automated

When the event has fairly predictable schedules.
When the organization wants a more continuous and less manual rhythm.
When there is enough personnel to intervene only in exceptional cases.

When it is appropriate to intervene

When the actual pace of the event deviates greatly from the planned schedule.
When an absence, complaint or table incident requires sporting criteria.
When the tournament is ready to advance and the administrator prefers to execute the next step without waiting for the counter.

Round Configurations

Round settings are the part that defines how the tournament is actually played. Not all rounds have to behave the same. The same event can use a sequence of rounds with different configurations if the organizer understands that this improves the sporting sense of the tournament.

A single logic or multiple logic

The tournament can maintain the same configuration in all its rounds when stability and direct comparison are sought.
You can also alternate configurations when the organizer wants to build a more varied route or with different stages.
This opens the door to tournaments with mixed formats or with changes in focus between phases.

Sports sense of a mixed sequence

There is no single correct way to combine rounds.
The decision depends on the criteria of the organizer and the sporting value that he finds in mixing formats, rhythms or forms of confrontation.
The important thing is that the sequence has a clear idea and that the participants can understand it.

What can vary between rounds

Group of competitors.
Order criterion prior to matching.
Main mode of the competition.
Disciplinary parameters and operational rules of the table.

Reading for client

This configuration decides the sporting form of each tournament block.
It's not just a technical detail: it changes how fairness, balance and the rhythm of the tournament are read.
It is advisable to make it clear before starting the actual execution of the event.

Relationship with the operating bar

The operating bar does not invent the flow of the tournament.
Only makes visible, step by step, what this configuration and the times have already defined.
That is why it is first configured and then the execution is interpreted.

Mind map to configure a round

To manage a round well, it is best to see it as a preparation flow and not just as a list of fields. The system does not create the tables immediately. First it builds the active universe of competitors, then it organizes it with previous rules and finally the format converts that universe into pairs, tables and matches.

Be part of the competitors actually available for that round.
Waiting or exclusion rules determine who temporarily exits the main flow.
The grouping defines whether the universe is separated into subsets with a sporting meaning.
The order criterion establishes the priority with which the format will read the competitors.
If the round works with teams, internal positions and also the pairs within the team can be recalculated.
Finally, the format executes its own algorithm and forms the real game tables.

This order matters because many configuration questions arise from mixing responsibilities. The format does not always decide who to order first, and the order criterion does not always define on its own how a table is formed. Each piece fulfills a function within the chain.

Layer 1. Who enters

Here the active universe of the round is decided. Putting competitors on hold or leaving them out changes the sports equipment that everything else will work with.

Layer 2. How to prepare

The grouping, order and internal team rules convert this universe into a readable sequence for the format. It is the phase where balance, mixture, progression or comparison between equivalents is designed.

Layer 3. How to play

The format takes that prepared sequence and defines the main competitive unit, the way of constructing pairs and the way in which those pairs end up sitting at the tables.

Quick reading of controls

Grouping: cuts or separates the universe before matching.
Order criterion: decides with what priority that universe is processed.
Put on hold: temporarily excludes competitors from the active stream.
Update position in the team: reorders members within the collective structure.
Update pairs in the team: redefines internal combinations when the format needs it.
Format: acts as the final orchestrator of the sports algorithm.

Key to use the configuration well

An administrator should not look at these fields as isolated options. You need to ask yourself what sporting story you want to produce and what path competitors should take before they get to the table. When you think about it like this, the round configuration becomes a real arsenal of sports design and not a simple parameter sheet.

Main parameters

Type of round: in person or virtual. It does not change the sports logic, but it does help to interpret the context of the block.
Format: defines the main competitive unit and the way matchups are created.
Grouping: decides how the universe is cropped before sorting.
Order criterion: decides with what priority the competitors are arranged before the final pairing.

General parameters

Points per match: marks the basic sports goal of the table.
Even time and Round time: help structure the rhythm of the game.
The stopwatch marks time out: allows the end of time to be automatically signaled.
Confirmation of Attendance and the decision between Continue Round and Reset Round govern the actual start of the block.

Specific parameters

Team: number of pairs, position updates and rotations.
Absences and out: points for absence and being out.
Penalties: cards and actual ability to change winner.
Bonuses: extra points per round section or per table.

Use grouping

The definition and available types are explained in Grouping and Grouping Types. In this process the question is no longer what it means to group, but how to choose and check the separation that the round will receive.

Define the comparison you want to favor. Decide if everyone should enter together or if the round needs to separate levels, countries, genders, internal positions or another supported characteristic.
Check the quality of the field. Before automatically grouping, verify that the competitors are informed of the chosen data. An empty value can end up in the base group.
Select the method. Use Ungrouped for a single universe; Manual for direct control; Unique value for a group by value; Multiple values to bring together several values; o Range for intervals.
Complete the method configuration. In Manual, assign the groups from the operation; in Multiple Values relate each value to its group; in Range defines intervals without gaps or unintentional overlaps.
Check the result before the pairing. Check how many competitors remain in each group, who remains in the base group and if the resulting number allows valid tables to be built.
Combines grouping with order. The order criterion will act within the prepared universe; therefore the grouping must be validated before interpreting the final sequence.

Signs of successful grouping

The groups express a sporting intention that can be explained.
Competitors without data are not hidden or assigned by accident.
Each group keeps an amount compatible with the selected format.

Errors to avoid

Choose an incomplete field and discover the problem when creating the tables.
Use overlapping ranges or leave important values out of all ranges.
Confusing grouping with order: one separates the universe; the other defines its priority.

Cross reference: return to Grouping Types if you need to review a method definition. Continue with Use the ordering criterion to define how each set is processed.

Use ordering criteria

The catalog and semantics of each alternative are in Order Criterion and Order Criterion Types. Here's how to turn the sporting objective of the round into an operational priority.

Define the desired effect. Decide whether you need to retain a manual placement, produce a neutral output, avoid repetitions, rotate previous tables, or prioritize cumulative performance.
Interprets the competitive identity. In players, the history can refer to previous teammates; in pairs and teams it refers to opponents. Do not use the same name without considering that difference.
Select system logic or composite criteria. Manual, Random, Random without repetition and Rotate Table have their own resolution. Composite criteria evaluate fields configured in sequence.
Check address and data. In composite criteria, check the order of evaluation, whether each field is ascending or descending, and whether all competitors have comparable values.
Checks the previous result. Validates that the sequence obtained respects the grouping, the active competitors and the intention of the phase before creating the matches.
Document the stage criteria. If the tournament changes criteria between rounds, explain why a phase prioritizes mix, progression, performance or continuity.

Internal system logic

Manual retains the existing operating position.
Random generates a new permutation.
No repetition tries to avoid recent relationships and may resort to random if it does not find a valid solution.
Rotate Table is intended primarily for player modes and uses the previous round from the second block.

List of criteria

The first field resolves the top priority.
The following break the tie or refine the reading.
Ascending and descending change the sporting meaning of each field.
An empty list is not a valid criterion.

Cross reference: query Types of order criteria to interpret each alternative and Choose and apply a format to check how that sequence ends up converted into tables.

Choose and apply a format

Competitive units, junction construction, and structural fields are defined in Format and in Modal Functional Matrix. The practical work consists of preparing the structure required by the format and validating the round before releasing the game.

Decide which result should tell the main story. Determine whether the axis will be the player, the stable pair, the team or a player compared within teams.
Prepare the competitive structure. Confirm that there are active players, pairs or teams as appropriate and that their internal memberships are complete.
Select the mode in the round configuration. Immediately review the controls that appear, disappear or are fixed by that selection.
Configures grouping and order criteria. Both pieces prepare the universe that the format will receive; they should not be chosen as independent fields.
Complete your own parameters. In collective structures, review the number of pairs, internal positions, rotation, control of repetitions, teams per group and pairing patterns when applicable.
Check cardinality and coherence. Verify that each group can form complete blocks and that there are no pairs, teams, positions or active players missing.
Explain the rule to participants and clubs. Communicate what is rewarded, whether pairs remain stable or are rebuilt, and how absences and penalties will be interpreted.
Create the round and review the result. Before starting it, confirm that tables, pairs and crosses reflect the expected configuration.

Quick guide to deciding

Use Individual if you want the main story to be the player's story.
Use Per pair if the duo must remain stable throughout the event.
Use By team if the collective result is above the isolated performance.
Use Four-player team 1 to mix different teams within each table.
Use Four-player team 2 for the level or position of the team to organize the crossings.
Use Individual by team to combine personal competition with groups and team pairings.

What to check before choosing

Which competitor do you want to reward: player, pair or team.
Whether pairs should be stable or can be rebuilt each round.
If there is a real team structure and what weight do you want to give it.
How much operational complexity can you sustain during the event.

Individual and pair

Individual needs enough active players to form full blocks of four.
Per pair you need enough active pairs to build valid confrontations.
In both, the team structure is no longer the axis of the configuration.

By team

Requires active teams and internal pairs capable of producing the matchup tables.
It is advisable to review the number of pairs, positions, rotations and repetitions before creating the round.
The results of the tables feed a higher collective reading.

Mixed team formats

Four-player team 1 requires at least four teams, four active players per team and unique and consecutive internal positions.
Cuarteta 2 works in blocks of four teams and can regroup surpluses.
Individual by team requires complete groups of four players and coherence between Teams by group and the pairings.

Individual calculation and discipline

Checks if the format separates the individual calculation before publishing the round.
With individual calculation, the absence or penalty weighs on the affected player without automatically dragging the teammate.
Without that separation, the pair or competitive unit can charge the effect as a whole.

Operational communication

Do not communicate only the name of the format: explain which identity competes.
Clarifies whether pairs are kept, recalculated or rotated.
Indicates what conditions may prevent the creation of the round and how leftovers or absences will be resolved.

Cross reference: uses the Functional Format Matrix to review semantics and structural fields. Return to this process when you need to prepare competitors, check requirements, and validate generated tables.

Complete reading of round parameters

A round configuration is not summarized in format, grouping and criteria. It also defines times, points, discipline, extra prizes, behavior in the event of absences and specific team rules. Each family of court language options is explained below.

Round type

In-Person and Virtual do not change the heart of the pairing, but they do help to read the context. For the administrator, this signal better organizes the logistics and communication of the block.

Numbers per match

It is the sports goal of the table. Changing it alters the expected duration of the match and the weight that a comeback, a penalty or a time-out may have.

Pair time and round time

Time Pair helps estimate the internal intensity of each table. Round time defines the duration of the entire block and is the one that most impacts the tournament's operating bar.

The stopwatch marks time out

If active, when the round time expires the system marks that the time has expired. This helps not to depend only on memory or verbal judgment when later reviewing a table.

Points for absence

Defines the sporting weight of not showing up. It's not just a disciplinary notation; influences how the result of the tournament or round will be read.

Points for being left out

It serves to leave a stable rule when a competitor does not continue within the competitive section. It is a way to maintain coherence in events with cuts, exclusions or partial continuities.

Penalties

Yellow card: slight discount.
Red card: stronger discount.
Black card: more severe punishment.
Change winner: decides if the sum of penalties can turn around the final result of the table.

Bonuses

Points per round: rewards certain sections of the tournament.
Points per table: allows you to give additional weight to certain tables.
From round: indicates from which the bonus begins to run.
Until table: marks which table remains active until.

Number of pairs

In team formats it defines how many active pairs each team can present in the round. It directly affects the number of tables that a collective confrontation can generate.

Update internal position

Allows you to recalculate the internal position of competitors within the team according to the cumulative total of the tournament. This is useful when the tournament wants to keep the internal hierarchy alive between rounds.

Update pair members

Manual: the pairs remain as defined by the operation.
Position in the Team: the pairs are reconstructed according to equivalent roles.
Rotation Without Repeating: seeks to vary partners and avoid repetitions.

Avoid repeated opposite pairs

Makes the system try not to face the same direct rivals over and over again. It gives more variety to the tournament and can make the experience richer for players and spectators.

Pairing 1, Pairing 2 and Teams per group

These options are especially sensitive in Individual by team. They define how the table is set up within each group of teams and how many teams will enter that block before crossing each other.

Tournament execution

Once the tournament is set up, the reading changes. It is no longer about defining what you want to do, but rather about following the central thread of the actual execution. This thread is the operational bar of the tournament, because it summarizes the current state, the timer, the next action and the ability to intervene when necessary.

Tournament operating bar

The operating bar converts the tournament status into an immediate readout. Its value is not only in showing a clock: it helps to understand in what real phase the event is, how long until the next step and who should act when something cannot advance on its own.

Its design responds to a simple idea: the tournament must be able to be read in a single strip. Instead of forcing the organizer to go through several cards, tabs or lists to know what to do, the bar concentrates the actual phase of the flow, the pending time and the next possible administrative transition.

The bar is not just for administrators. Current Status, Stopwatch and Next Action also serve as a public readout for players, captains and observers. What is reserved for those who have management permissions is execution control, because only that profile can manually trigger the transition.

What always shows

Current state: describes the actual operational phase of the tournament and avoids ambiguous pseudo-states.
Stopwatch: only appears as an effective clock when there is a timeout in effect for the next transition.
Next action: names the concrete next step in the flow, not a generic intent.
No clock: appears when there is no configured wait or when the step depends directly on administrative action.

What administrators see

Run now: allows you to advance or manually resolve the visible transition.
Badge Auto / Manual: indicates whether that action is intended to be executed on its own or if it depends on human intervention.
The badge changes only the temporary mode of the visible action and does not rewrite the persistent tournament settings.
When the action stops applying or is executed, the bar reads the base configuration of the flow again.

How should it be read

The correct reading is vertical and causal. First, is identified where the tournament is at using the current state. is then checked if there is a real wait using the stopwatch. Finally, is confirmed which step is next in the next action column or block. This sequence avoids interpreting a clock as if it were an ongoing activity when in reality the tournament is stopped due to foul of premises.

This also explains why the bar distinguishes between information and execution. A tournament can clearly show that it is waiting to create a round and still keep the administrative button blocked if the preconditions are not met. The bar should not promise an action that the backend cannot safely complete.

Enable key rule

Each action visible in the bar first goes through a check of operational premises. If the next transition is not feasible, the UI should leave the control disabled and show the reason for the crash. This rule is important because it avoids two very common problems: triggering actions that then fail mid-process and giving the impression that the tournament is ready to move forward when the competitive base does not yet exist.

In practice, this means that the bar is not limited to translating states. It also works as feasibility traffic light. When the backend detects a crash, the bar retains the next visible action as a reference to the flow, but does not present it as something executable at that time.

Important checks in Create round

The action Create round {n} is the one that depends most on previous structure, because it is not enough for the tournament to be at the correct chronological point. There must also be the necessary competitive basis for the format configured in that round.

If the format is per pair, there must be active pairs and in sufficient quantity to create valid crossings.
If the format is per team, there must be active teams and, in addition, the pair structure that allows the tables to be built according to that format.
If the round works with formats grouped by teams, such as variants of four-player team or individual by team, there must be the minimum base of teams and active players so that the round is not born incomplete or inconsistent.
If any of these premises are foul, the bar keeps Create round visible as the next logical step, but leaves it blocked until the organizer completes the necessary structure.

Functional Criterion: the operating bar should not hide the next action just because it is locked. It should continue to show what the expected step of the tournament is, but clearly differentiating between what is next in the flow and what can already be executed.

The recommended tournament operating bar reading can be summarized as follows:

Current status	Stopwatch	Next action	Functional reading
Tournament created	No clock	Publish tournament	The tournament already exists, but it has not yet entered a visible recruitment phase.
Tournament published	No clock	Open tournament	In this state it is expected to invite participants and receive applications or registrations.
Open tournament	No clock	Start tournament	In this state, participants are expected to confirm their participation before starting the competition.
Waiting for round creation {n}	Wait for next round	Create round {n}	The previous round has already finished and organization time is running out before preparing the next one.
Waiting for start of round {n}	Wait for start of round	Start round {n}	The round has already been created and is ready to start when its operational time arrives.
Playing round {n}	Round duration	End round {n}	The round is running and the clock uses the time configured for its duration.
Round Review {n}	Round Review	Close round {n}	The round has ended its play phase and enters a brief review window before consolidating.
Tournament ready to finish	No clock	End tournament	This step appears when there are no more rounds configured to execute and the only thing left to do is close the event.
Tournament over	No clock	No action	Final status of the tournament.

What the bar expresses

What phase is the event in?
How long until the next milestone.
What is the action expected next.
Whether the next transition is supported in Auto or Manual.

What prevents

That the organizer has to constantly explain whether the round has already started or not.
That players and observers depend on external messages to understand the rhythm of the event.
A well-configured automation continues to appear opaque to those watching the tournament.

Functional Criteria: Attendance Confirmation is not recommended as the main tournament status. It works best as the key phase within Open, while Active marks the actual beginning of the competition.

RSV and live reading

Confirmation of attendance well understood

The RSVP does not exist just to block or allow booting. It also serves as a visual dashboard to quickly detect which tables are full, which are still pending, and where the organizer's attention should be focused.

When disabled

The round can start without depending on presence confirmations.
No visual presence indicators are displayed on the tables.
The experience focuses on the general flow of the round, without adding an extra layer of control per player.

When activated

The tables show the presence status of their players so that the organizer can quickly detect where someone is foul.
The round can come into play, but each match waits for the actual presence of its players before it is ready to play.
This allows the tournament to follow its overall clock without losing fine control over each table.

Relationship with absences

Automatic closing due to absence only makes sense when RSVP is activated.
If confirmation is not used, it is not advisable to show signs of presence or rely on them to decide absences.
This way the client avoids visual noise and maintains a coherent logic between what he sees and what the system can resolve.

What each actor sees

What the organizer sees

See the operational status bar in tournament and rounds, with current phase, remaining time and next action.
You also see the Run Now button when the system recognizes a possible manual transition.
Also see the Auto or Manual badge when the following action supports temporarily changing its execution mode.
If RSVP is active, you can quickly detect tables with pending players and take action before the problem spreads to the rest of the event.

What the player sees

See the same status bar to understand if the round has already started, if there is still time left, or if the tournament is waiting for another step.
If RSVP is active, you better understand when to RSVP before playing.
You see no organizational controls, so your experience remains clear and focused on participating, not managing.

What other profiles see

They can follow the operational moment of the tournament even if they do not participate directly at the table.
See if a round is about to start, is being played, or is already under review.
This improves the public reading of the event and reduces the feeling that the tournament is progressing invisibly or confusingly.

Operational summary: the times organize the rhythm of the tournament, the options decide what is allowed to be automated, the status bar makes that rhythm visible to everyone and the organizer retains the ability to advance the next step when the event is ready to continue.