OEScore V12 is your comfortable and reliable tool to organise Score O events. It is based on OE12 V12 for (course based) individual O events. Specific features of score orienteering had been added to all functions of OE12.
In the course of time, many well known and (much more than I) experienced organisers all over the world had also contributed their ideas to improve the software. Thanks to you all! When developing OEScore V12, I learned much about Rogaining. Many thanks for that to Guntars Mankus (LAT)!
OEScore is mostly used for large MTB, Rogaining, or adventure events all over the world.

At score O, there are many controls with different point values. The competitors have to score as much as possible within a predefined time limit. Exceeding the limit leads to penalties. The order how to visit the controls is free.
If a competitor exceeds the time limit, this will punished by penalty points. Sometimes there are also credits awarded if a competitor is faster than the time limit. In most cases there are several time bands defined above the time limit. Each later time band means that every minute in that interval will cost the competitor more points per minute. OEScore supports 5 bands for credits and 30 bands for penalties as a maximum. For the last time band, it is possible to define that a runner will loose all his points if he reaches this time interval.
It is also possible to provide credits/penalties manually for special cases.

OEScore supports a special handling for teams. This kind of competition is common at Rogaining, mountain bike score and adventure events. Theoretically, OEScore can support teams with an unlimited number of members. In practice, this is limited by the space which is available in the result reports. The basic rule is that the team members start together, do their competition and finish together. Each competitor carries his own chip. The team’s time is calculated by the first start time and the last finish time of all members. For the score result, only those controls will be counted which had been punched by all team members. New in V12: you can define a maximum punch difference for teams. Also, there is a new mode how to handle control codes, the Hidden mode. Both features are standard in Rogaining but they can also be used for “ordinary” score competitions.
Compared to previous versions, OEScore V12 provides a much better and improved handling of team entries.

OEScore V12 allows courses with up to 192 controls. When creating a new event, you can choose between 3 different event types:
Standard: Individuals, normal score O, teams supported
This is the normal individual competition, and you can have teams. In all reports the teams are shown like a single competitor, with all names of the team mates in the name column. Just like so far.
Teams only, normal score O
You can edit an extra name for the team. Team mates can be from different clubs.
In all reports the teams are shown with their team name and optionally the names of the team mates in extra lines, just like you are used to from relay teams.
Teams only, Rogaining
A Rogaining competition follows special rules. The report layout is the same as given above.

OEScore Pro V12 is prepared to include the speaker and time taking functions of OE12/OE2010 in a suitable way. With a normal score O event, speaker functions (which provide intermediate results/times during the race) look to be not useful. However, there are intermediate results given on 24h Rogaining competitions like WRC. These solutions are completely web based. I am waiting for your feedback, whether something like that should be implemented in OEScore or not!

OEScore comes in different editions.

Standard Up to 400 competitors, courses up to 64 controls
Pro Up to 1000 competitors, including speaker und finish functions, courses up to 192 controls
Pro Large More than 1000 competitors, including speaker und finish functions, courses up to 192 controls

If you want to learn more about OEScore, then download and test the trial version and/or read the PDF handbook.