Smart solutions

If you put a maximum number of teams in a class, Cup Manager handle it for you. The registration form will state, if you wish, how many seats remain.

If the class is fully booked, the system does not stop the notifications completely, but clearly informs that new notifications are placed on the reserve list. From this reserve list you can then pick up teams if a regular team withdraws.

The system creates a backup list for each class. The system can show the team that signs up for their place in the reserve list, but that behavior is completely optional. Sometimes it makes sense for the tournament to choose freely among the teams in the reserve list and then you do not want to communicate what place the teams are in.

All this behavior comes by simply putting the maximum number of teams on the class.

Read more about how our registration system works here.

To be able to merge classes, I think a lot of tournaments have had to do at some point. Usually it is of course because there are too few teams signed up for a few classes and then it is better if they get to play together.

The naïve solution to this is to move all teams from one class to the other, and then remove the first one. However, this creates some problems, such as the fact that they are very difficult to change their minds.

What Cup Manager do is distinguish between registration classes and drawing classes. When you merge two classes, only the drawing classes are merged, but in the registration system the two remain different.

The backward connection is maintained, and this has a number of advantages:

• Even after the merger, it is possible to register for the original classes, but the teams end up in the draw in the merged class
• It is possible to undo the merger afterwards and then all teams are restored back to the original classes
• The system also automatically names the law according to their original class name. So if you merge P6 and P7 into P6/7, for example, the law is called "P6" last in the name.

Tournaments often have different rules, offers and prizes for teams depending on whether they have an overnight stay or not. For example, it is common for teams to receive a cheaper registration fee if they are going to stay overnight.

However, the overnight stay is often booked only several months after the registration is made. In order to avoid that the discount comes only afterwards when the teams have booked an overnight stay, you as a tournament want to find out as early as possible which teams will book an overnight stay.

In Cup Manager we have a concept called Team Types that solves this problem.

For example, you can set up two team types: Overnight teams and Local teams.
When the teams sign up, they must choose one of these types of law and thus the information is collected in a structured way.

The team type can then be used to automatically give a discount on the registration fee or to limit the booking of participation fees, so that only those who chose the Overnight Team have the opportunity and coercion to book an overnight stay.

In addition, this information helps in the planning of the tournament as it is possible to see early how many overnight teams there will be.

Read more about how our registration system works here.

Our housing planning solution also includes a smart solution for planning food. By setting rules for meals based on the law's accommodation, the system can set food times on the law automatically.

You can set all teams staying at School 1 to have breakfast at School 1, lunch at Dining Room A and dinner at Dining Room B. These rules can also be different per day.

When you then place the law in schools, the system will automatically link the law to the right meals according to the rules. In addition to this, you can of course adapt with manual exceptions for certain teams if you wish.

The teams' meals and their accommodation can be presented nicely through the law's team account so they themselves can see in advance where to eat and stay.

You can take out custom lists for the dining rooms where staff can see how many people will eat each meal. Since the system also has information about special food requests for each team, the staff gets an overview of how many people have different types of special diet each meal.

Smart va?

Of course, Cup Manager support discounts. There are manual discounts where you as a tournament can give 25% discount to a specific team.

But we also have a system of smart discounts that are applied automatically according to criteria of your choice. For example, you can easily add a discount that allows anyone who signs up before a certain date for a 20% discount, or give 450 KR discount to all overnight teams.

These smart discounts are also "live" so you can even add them afterwards if you forget it before.

Read more about how our registration system works here.

If you wish, you can let the teams enter arrival information that includes how and when they arrive at the tournament. This is partly good for your planning and can be useful in check-in, for accommodation hosts and other logistics. You can also use the arrival information when scheduling your tournament to make sure teams don't get their first match before they arrive.

You may also offer airport/train station transfers at a cost or free of charge. There is also support in Cup Manager for selling transfers when the teams enter arrival information. Ask us!

In addition to arrival information, it is also possible to have the law enter departure information in order to receive the corresponding information about it.

A consistent goal in Cup Manager is that we try to use the information we collect to simplify as much as possible for you. An example of this is that in the administration of registered teams you can easily filter on all possible criteria one can imagine.

In addition to the obvious such as seeing all teams in a certain class, or choosing overnight stay, it is also possible to filter on payment status, if they entered arrival information, if they have entered the lineup.

But it is also possible to filter on things that are outside the registration system, such as everyone who has been drawn into groups, or anyone who plays on a particular playing field. These are criteria that many other systems might have seen as part of other isolated modules. But having access to these more detailed criteria means that you will find more information in the same place. Since these criteria are the same as those used for sending e-mails, it is important not to be restricted unnecessarily.

Once you have filtered the teams on what you want, you can also summarize e.g. money paid in, or number of players, or number of teams. This gives a hard-to-beat overview.

Read more about how our registration system works here.

A classic tournament structure is that you let the 1st and 2nd in each group go to Slutspel A and the rest to Slutspel B. What you call "2nd in Group A" is not a real team but a placeholder. Cup Manager fills in this team automatically when the group is finished.

In Cup Manager, we also have fully built-in support to automatically handle more complicated things like letting the top 3 advance to a playoff. It can be good for leveling playoff trees. The top 3 is also a placeholder but it is filled in with the team that performed best of all 3s in the groups in the group stage.

We think it is important that you at the tournament should not have to deal with this manually during the tournament when there are a lot of other stressful things happening. We have chosen to build in support so that when you make the lottery you decide how the teams proceed. During the tournament, the system handles all forwarding of teams automatically.

Of course, it's not just about the best 3, it's completely dynamic to things like the 3rd best 2.

To rank these teams and see which of the threes is the best, Cup Manager simply use the same rules as in the group table. If it is that the groups have different sizes, it does not work so easily because it can be beneficial to end up in a large group. Then there are 3 different strategies that you can choose from:

1. Count as usual even though the groups are different in size. Simple but unfair.
2. Divide each criterion by the number of games played, so you start by sorting the teams by number of goals per game, etc. A little fairer but not completely.
3. Exclude all matches played against the lowest ranked in the larger groups. Fairest.

In addition to the usual participation fee, we have developed a system to allow teams to easily book hotel rooms. The teams can search for hotel rooms for, for example, 15 people and then the system will show the cheapest configuration of rooms for each hotel, whether it is 5 triple rooms or a mix of different sizes.

You always control the stock of how many different rooms are available. Each room type at each hotel can have a unique price.

When you set up the system like this, all accommodation appointments are handled completely automatically, so the teams are placed in the system in the hotels in each room.

There is also the possibility to demand a so-called prepayment, so the law, for example, must pay 10% directly to make the booking.

You can read more about team account & accommodation bookings here.