meshO Manager

Appearance

Classes and courses ​

Audience: Event organisers defining the competition structure.

Classes are the categories competitors enter (e.g. M21A, W14, Open Moderate). Courses are the physical sequences of controls. Classes determine who runs against whom; courses determine what they run.

This page covers what they are, how they're related, and how to create, edit, and delete them in Manager. Most events get their classes and courses from an import — see Importing event data — so usually you're reviewing and adjusting rather than entering from scratch.

How classes and courses relate ​

A class can be assigned one or more courses, and a course can be assigned to one or more classes — the relationship is many-to-many. In practice you'll see two common patterns:

  • One course per class — typical of championship classes (M21A → "Hard 1" course).
  • Multiple classes sharing one course — typical of age-group classes that all run the same physical course (M21A and W21A both run "Hard 1"). Each class still appears separately on Leaderboard.

Manager doesn't require every class to have a course assigned during setup, but a class without a course can't produce results. The Classes page flags missing assignments (None assigned) so you can spot them at a glance.

The Classes page ​

Navigate to Classes in the Event data section of the side menu.

The table shows one row per class. Some columns appear only when they have something to say, and the columns button at the right-hand end of the header row turns any of them on or off (drag a heading by its grip to reorder):

  • Class — the class name. Click to open the edit dialog.
  • Round — the knock-out round a class belongs to. Only shown in a knock-out round event.
  • Class ID and Short name — hidden until you turn them on.
  • Mass start — the class's mass-start time, marked (class) or (event) for where it comes from. Shown by default only if the event or any class uses a mass start.
  • Courses — the courses assigned to this class, or None assigned.
  • Variations — the fork variations this class runs, when its course is forked. Shown by default only when a course has variations.
  • Course format — Scatter or Score for a class whose course is run in any order (a line class shows a dash). Shown by default only when the event has such a course.
  • Radio controls (including priority) — which radio controls report for this class, each with its display priority (see Marking radio controls and setting their priority). For relay classes the list is grouped by leg. A red None configured means the class shows no radio splits anywhere.
  • Competitors — entry count; click it to list them. Shown by default when the event has individual classes.
  • Teams — team count. Shown by default when the event has relay classes.
  • On course — how many competitors in this class are still out (started but not finished). Click the count to open the same On course list the dashboard tile opens, narrowed to this class.

Filter the table with Search class name or the Radio control filter.

The Actions menu (top right) has:

The Courses page ​

Navigate to Courses in the Event data section.

The table shows one row per course:

  • Course — the course name. Click to open the edit dialog.
  • Course ID and Climb — hidden until you turn them on in the columns menu.
  • Course format — Scatter (with how many controls it requires) or Score. Shown by default only when the event has such a course.
  • Variations — how many fork variations the course has. Shown by default only when a course has them.
  • Controls — the control codes on the course, in order. A forked course shows a chip per variation instead; click one to see that variation's controls. A red None configured appears if a course has no controls.
  • Length — the course length in km. Click it to open Course details, with the total length, climb, controls and a per-leg breakdown. Normally measured automatically as the sum of the leg distances (a dash if it isn't known); a ruler icon marks a course whose length has been set manually instead. A forked course shows the range of its variations' lengths.
  • Assigned classes — count of classes that use this course. Click to see the list.

Filter with Search course name or by Control code.

The Actions menu has:

  • Import… — open the Import event data dialog.
  • Add… — create a new course.
  • Assign to classes… — bulk-assign courses to classes (same dialog as on the Classes page).
  • Auto create classes from courses… — the same action as on the Classes page (see Auto-creating classes from courses below).
  • Combine into variations… — fold several courses that are really forks of one course into a single course with variations (see Combining forked courses into variations below).
  • Delete all courses… — see Deleting them all at once.

Leg distances have a page of their own, Legs — see Leg distances below.

Creating a class by hand ​

Click Actions → Add… on the Classes page. The Add class dialog opens (Edit class when you open an existing class).

Fields:

  • Class ID — filled in with the next free number. You can change it while adding the class; after that it is fixed.
  • Class name — required. The name shown everywhere (Leaderboard, start lists, results).
  • Short name — optional. A shorter label used where space is tight.
  • Courses — multi-select chips. Pick one or more courses for this class, or leave empty and assign later. Each course's format is shown beside it in the list. Once there are two or more, a Competitors do choice appears beside the field: Course pool (each competitor runs one of them — see Course pools) or All courses (each competitor runs every one — see Classes whose competitors do every course).
  • Course variations — appears when the class has one forked course. Click the variation chips to choose which of them this class runs (All turns them all back on). A competitor with no variation of their own is scored only against the ones left on, and at least one must stay on.
  • Score settings — appear when the class's course is a score course: Points per control, Time limit (minutes) and Penalty per minute late. Leave a box blank to use the event's setting; fill it in to give this class its own (a 2-hour and a 6-hour class off one set of controls, say). See Score and scatter courses.

In a relay event the dialog also asks for the Class type — Relay, or Individual for a side class run alongside the relay — and, for a relay class, the Number of legs. See Relay classes.

Start time section:

  • Class mass start — toggle on if this class starts together at a fixed time. When on, set Class mass start time (defaults to 10:00:00 the first time you enable it).
  • Exclude this class from event mass start — appears only when the event has a mass start and this class doesn't have its own class mass start. Turn it on if this class should start individually despite the event-wide mass start.
  • Restart and Exclude this class from the event restart — relay classes only. See Restarts.

Click Save. If Manager refuses the class, the reason is shown at the bottom of the dialog and the dialog stays open so you can put it right.

Class sort order ​

Actions → Sort order… on the Classes page sets the order classes appear in on results, the kiosk's live results, and other screens that list classes. Drag classes into place, or use Move to top and Move to bottom. Sort A→Z puts them in name order, and Auto order groups them for you: men's or women's classes first (you say which letter marks each, and whether it comes before the age, as in M21, or after, as in 21M), with elite classes at the top if you like. Classes that match neither marker go last. Fine-tune by dragging afterwards, then click Save.

Creating a course by hand ​

Click Actions → Add… on the Courses page. The Add course dialog opens (Edit course for an existing course), with four tabs: Details, Controls, Climb and Length.

Details ​

  • Course ID — filled in with the next free number; fixed once the course exists.
  • Course name — required.
  • Course information — optional free-text notes (course-setter notes, terrain notes, etc.).
  • Course format — Line (the controls in order), Scatter or Score. A new course starts with the event's own Course format; each course can be changed on its own. See Score and scatter courses.
  • Start — which Start this course uses. An event can have several Starts (e.g. "Start", "Start 2") at different locations; pick the one this course uses. A line course can also use First control — see Starting or finishing at a numbered control.
  • Finish — which Finish control this course ends at, chosen the same way (or Last control).

Controls ​

The ordered sequence of middle controls between the Start and the Finish.

To build it, type a control code into the input and press Enter. Each control appears as a chip in the order added. Drag chips to reorder. Click the close icon on a chip to remove it, or press Backspace to delete the last one. A code that isn't a control yet becomes one when the course is saved.

Note: The Start and Finish are picked from the event's Start and Finish controls on the Details tab — the Controls tab holds only the middle controls between them. An event can define multiple Start and Finish controls; see Controls and radio controls. To start or finish at one of the course's own numbered controls instead, choose First control or Last control there — see Starting or finishing at a numbered control.

On a forked course a Variation picker sits above the chips, and the controls common to every variation are highlighted. An edit here changes the selected variation only — use it for an on-the-day fix; a re-import of the course file replaces all the variations.

The Course with loops option is also on this tab — see Courses with loops.

A score or scatter course has no sequence, so this tab shows something else — see Score and scatter courses.

Climb ​

  • Total climb — total elevation gain over the whole course, in meters.

Length ​

Choose how this course's length is worked out:

  • Measured automatically — the length is the sum of the course's leg distances (the default), shown beside the option.
  • Manually calculated — enter the length in metres yourself. Use this for sprint courses, where the published length is the shortest sensible route around obstacles rather than the straight-line geometry, or whenever you need a deliberate figure (taped routes, remeasurement). A manual length must be a whole number of metres greater than zero. The value you set here is what Manager publishes to exports (Eventor / IOF XML) and printed splits, in place of the measured sum.

Below the length options is a read-only breakdown of the distance between each consecutive pair of controls on this course. Leg distances are shared across the whole event, keyed by the two controls' identities — if two courses both go from control 31 → 32 the same distance applies, but a leg from "Start 1 → 131" stays distinct from "Start 2 → 131". Edit them on the Legs page (see Leg distances).

If the course has no controls yet, the breakdown tells you to add them on the Controls tab first. On a forked course, pick the Variation whose length you want to see or set.

The Climb and Length tabs are left out for a score or scatter course: they describe a route, and a course run in any order has none.

Keep adding ​

At the bottom left of the Add course dialog is a Keep adding toggle, for typing in a list of courses one after another. With it on, Save stores the course and clears the dialog for the next one instead of closing it — the course just added is named beside the toggles, so a cleared form isn't mistaken for a save that failed. Close the dialog with Cancel when the list is done. It stays as you leave it for the rest of the session.

Create class ​

Beside it is a Create class toggle, off by default. Turn it on and saving the course also creates a class of the same name, running that course — the quickest way to build an event on the spot, where each course is its own class. If a class of that name already exists, nothing is created and Manager tells you so; the course itself is saved either way.

The toggle only appears when you are adding a course, and it resets to off each time the dialog opens — but it stays on across a Keep adding run, so a whole set of courses and their classes goes in without reopening anything.

Click Save.

Assigning courses to classes ​

Often you don't need to assign anything by hand: an imported course file that includes class-course assignments (ClassCourseAssignment entries — exported by Purple Pen, OCAD and others) sets each named class's courses automatically during the import, even when the course names ("Course 1") don't match the class names ("M21E"). After a course import, the bulk dialog below opens automatically only if at least one class is still without a course.

When you do need to assign manually, there are two ways:

  • One class at a time — open the class's edit dialog and pick courses in the Courses field.
  • Bulk — use Assign courses… (on the Classes page) or Assign to classes… (on the Courses page). Both open the same dialog, Assign courses to classes.

In the bulk dialog you see one row per class with a multi-select for its assigned courses. Edit any row, then click Save — only the changed rows are written, and a counter at the bottom shows how many.

Auto-assign (top of the dialog) matches each class to a course by name and fills in the suggestions. After auto-assign, an alert tells you how many classes matched and how many didn't — review the highlighted rows, edit anything that's wrong, then Save. Useful right after an import that brought in classes and courses with matching names.

Auto-creating classes from courses ​

For an event put together on the spot, the classes are often just the courses: an "Easy" class running the "Easy" course. Actions → Auto create classes from courses…, on either the Classes or the Courses page, does that in one go.

The dialog lists every course before anything is written, with what it would do to each:

  • Will be created — no class runs this course and no class carries its name. Ticked by default.
  • Class already exists — a class already runs this course, or already carries its name, or both. Unticked. A row whose name is taken cannot be ticked at all: two classes sharing a name are impossible to tell apart afterwards, in the results as much as on screen. Where only the course is spoken for — a class of some other name runs it — you can still tick the row, if you do want a second class on the same course.
  • This course has no name — nothing to copy. Also not tickable.

Because only the untouched courses start ticked, you can run it again later in the day and it picks up the courses added since without disturbing what is already set up. Click Create to make the ticked ones. Each new class is created with the course's name, that one course assigned, and nothing else — edit the rest (short name, mass start, radio controls) from the Classes page afterwards.

Tip: When you are typing courses in by hand, the Create class toggle in the Add course dialog does the same thing one course at a time — see Create class.

Combining forked courses into variations ​

A forked course — a butterfly, or a relay course where different runners take the loops in different orders — is one course in Manager, carrying a variation per fork combination. Each variation has the letter code the course setter printed on the maps ("BDAC") and its own control sequence.

Course-setting software doesn't always tell Manager that. When the course file groups the forks (IOF CourseFamily), the import folds them for you. When it doesn't, each fork arrives as a course in its own right and the list ends up with "Course 1 BDAC", "Course 1 ADBC", "Course 1 BCAD" and "Course 1 ACBD" side by side, none of them knowing about the others.

Actions → Combine into variations… puts them back together.

The dialog opens with Detected variation families at the top: sets of courses whose names share a prefix and whose control sequences are alike enough to be forks of one course. Ordinary course numbering ("Course 1", "Course 2") isn't offered, because those courses share no controls. Click Use on a family and the selection, the combined name and each variation code are filled in for you.

You can also do it by hand — tick any courses in the table, edit the Combined course name, and edit any Variation code. The codes must be unique, and they're what appear on results and splits, so keep them exactly as printed on the maps. A course with no controls can't become a variation.

Before you commit, the dialog says how many courses will be removed and how many classes and competitors will be updated. When you click Combine:

  • The first course in the list survives. It keeps its course id, its Start and Finish, its climb and its position in the list, and takes the combined name. If the selected courses don't all share the same Start and Finish, the dialog warns you whose are kept.
  • Every other selected course becomes a variation and is then deleted. Any manual length it had becomes that variation's length.
  • Classes that used any of them now point at the combined course. A class that used only some of them is restricted to just those variations; a class that used all of them stays unrestricted.
  • Competitors locked to one of the courses are moved to the combined course and locked to the matching variation — so a runner assigned "Course 1 BDAC" still runs the BDAC fork.

Leg distances need no attention: they're banked per control pair for the whole event, so every fork's measurements survive the fold.

You can run it again later. If a further fork turns up in a re-import, select the already-combined course together with the new one — the combined course keeps the variations it has and the new one is appended. Only one of the selected courses may already have variations.

Relay events ​

For relay events, the course list still holds the physical courses (one per leg variant), but leg structure — which leg punches which radio control — is configured on the class via its radio controls, not on the course. The course is just an ordered list of controls; the class decides how those controls are grouped by leg.

See Relay events for the full picture.

Leg distances ​

Leg distances are kept in one shared bank for the event, keyed by the identity of the from-control and to-control (not by control code). This means editing the distance for 31 → 32 once updates every course that traverses that leg — while a leg from "Start 1 → 131" stays distinct from "Start 2 → 131", since the event can have more than one Start. Editing the middle of a course leaves the surviving legs untouched.

Edit them on the Legs page, in the Event data section of the side menu. It lists every leg used by any course, plus any saved measurement, with columns From, To, Distance and Untimed time; narrow it with the Control filter. Click a leg to open Edit leg, or use Actions → Add leg… to enter one that no course uses yet. The breakdown on a course's Length tab, and the Course details dialog from the Courses page's Length column, show the same distances read-only.

Untimed legs (road crossings) ​

A leg can also carry an Untimed time — an allowance, entered as mm:ss, for a stretch the competitors are not raced over, typically a marshalled road crossing. When a card is downloaded, the competitor's time for that leg is reduced by up to the allowance, so waiting safely at the crossing costs nothing. Live radio results are not adjusted. Leave it blank for a normally-timed leg. The same allowance voids a leg on the day — see A leg that should not count.

Editing after the event has started ​

Classes and courses remain fully editable after the event has gone live — Manager doesn't lock them down. This is intentional: late entries land in classes, and you sometimes need to fix a wrongly-set control sequence mid-event.

That said, a few changes will affect already-finished competitors:

  • Adding, removing, or reordering controls on a course will re-classify every competitor on that course (anyone who matched the old course may now be Mispunched, and vice versa).
  • Removing a course from a class unassigns it for everyone in that class.
  • Renaming a class or course is safe — it's just a label change.

If you must edit a course after competitors have started, do it during a quiet moment and check the Results page afterwards. For a control that failed or was out of place, there is usually no need to edit the course at all — see Controls and hardware.

Deleting classes and courses ​

To delete a class, open its edit dialog and click the red Delete button at the bottom-left. Confirm the prompt.

Deleting a course is the same — open it, click Delete, confirm. If the course is assigned to any classes, Manager unassigns it from them automatically.

Deletion is permanent. There's no undo.

Deleting them all at once ​

The Classes page has Actions → Delete all classes… and the Courses page Actions → Delete all courses…, for when an import went in wrong and you want to redo it from an empty list rather than pick the entries off one by one.

Manager confirms first and lists what else changes:

  • Delete all classes takes each class's radio controls, start-time settings and course assignments with it. Courses, controls and clubs are not touched. The competitors stay, but they end up with no class and stop being evaluated until you give them one — usually by re-importing the class and entry lists. In a relay event the teams keep pointing at a class that no longer exists, so delete or reassign them too.
  • Delete all courses takes each course's control sequence and fork variations. The classes stay but are left without a course, so nobody can be evaluated until the courses are back. Controls, and the leg distances measured between them, are untouched.

Neither can be undone. On a live event, back the event up first.

Score and scatter courses ​

Not every course is a line. Set Course format on a course's Details tab:

FormatControlsOrderRanked on
Lineevery control on the courseas printedrace time
Scattera set number of the course's controlsanyrace time — fewer than required is a missing punch
Scoreany of the course's controls, all optionalanypoints, then race time

The event's own Course format (on the Details tab of Event details — see Creating an event) is only what a new course starts as. One event can hold line, scatter and score courses side by side — a club night with one score course beside the normal ones, or a Duo class (below).

A scatter or score course has no sequence, so its Controls tab shows a list of the event's controls instead of the chip editor. It starts as every control in the event, so a control put out on the morning joins it without anyone touching the course. To make two courses over one set of flags — a short and a long score course, say — take controls off one with ×, and put one back with +. The control stays in the event and on every other course; only this course stops counting it. A course needs at least one control left on it.

  • Scatter — set Controls required: how many of the controls a competitor must visit, in any order. 0 means all of them.
  • Score — each control shows its points, and Total possible sums them (a faulty control is greyed out and left out of the total). Leave a box blank to use the event's default. These are the controls' own points, shared by every score course at the event — change one here and it changes everywhere, the same as typing it into the Points column of the Controls page. The exception is a price the course file set for this course alone (some files price one control differently on two score courses); those are marked, and changing one changes this course only.

The score rules — Points per control (the default value of a control), Time limit (minutes) and Penalty per minute late — are set for the whole event on the Score tab of Event details (the tab appears once the event, or any of its courses, is Score), and a class can state its own in its edit dialog (see Creating a class by hand).

A scatter or score course is always scored on its own, so it can't be one of several courses in a course pool: give such a class a single course first. It can be one part of a class whose competitors do every course, below.

Classes whose competitors do every course ​

Some classes run several courses one after another on one card — a Duo class at an MTBO is a score ride, then a score run, with one result for the lot. In the Edit class dialog, once the class has two or more courses, set Competitors do to All courses (the other choice, Course pool, is the pool described below; when any of the courses is score or scatter, a pool isn't possible and the courses are always run one after another). Then:

  • Put the courses in the order they are run. The class's course list is the order of the parts. Set Order to Any order if competitors may run the parts in either order; Manager then works out the order from each card. Any order is allowed for up to four courses.
  • Choose a changeover for each boundary. A changeover is the control whose punch ends one part and starts the next — at a Duo class, the control on entry to the zone where the run map is collected. It does not have to be on either course, but it can't be one of a line or scatter course's own controls.
  • Score settings apply to the whole race as usual (the time limit is labelled Whole race limit (min)). Each score course can also have a limit of its own (shown as Duo Bike limit (min), named after the course), timed from the start or the changeover that began it; leave the whole-race limit at 0 if only the per-course limits should count.
  • Not for relays or forked courses. A relay class can't run its courses one after another, and a course with fork variations can't be one part of a class. The dialog says so before you save.

When a card is downloaded, Manager cuts it at the changeover punches and scores each part against its own course, at that course's own prices — a run control punched during the ride scores nothing. Points and penalties add up to one result.

  • A missed changeover is a missing punch, and the download screen names it. If the changeover unit failed, mark the control faulty, or mark it visited for the competitor, exactly as you would a control on a line course.
  • If a part's course is deleted, or the class's changeovers no longer match its courses, every competitor in the class is scored as a missing punch until you fix the class. An alert names the class, and so does the check when you start the event. Manager never scores such a class as if the competitors had only done the courses that are left.
  • Importing. A class-list or course-file import never undoes a class like this: it keeps its own courses and changeovers, and the import says so if the file listed other courses for it. An OJSON export carries the whole setup, so it comes back as it was.

Starting or finishing at a numbered control ​

A course doesn't need a start or finish unit: a normal (numbered) control can be its start, its finish, or both. On the Details tab of Edit course, the Start and Finish lists offer one more choice after the event's Start and Finish controls:

  • Start: First control — a competitor's punch at the course's first control is their start punch. Use it when the start unit was left behind (start the course from whichever control the group is standing at), or when one control does everything. The control is still one of the course's controls. Whether that punch or an allocated or mass start times the run follows the same rules as a start unit's punch.
  • Finish: Last control — a competitor's last punch at the course's last control is their finish punch, and a finish unit's punch is ignored. A competitor with no punch there has not finished.

These choices are offered on line courses only. Choose both for a single "meta" control that is the start, every transition and the finish — for example 90 31 32 90 41 42 90. The competitor is timed from their first punch at 90 to their last, and can't punch the wrong unit because there is only one.

In a class with several courses, the option counts only when every course in the class has it. A radio punch at the last control shows the competitor as finished straight away only when that control appears just once on the course, at the end. A control the competitor punches again and again (a meta control, or the common control of a course with loops), or the last control of a course whose loops can be run in any order, finishes them when their card is read. While an option is on, a radio punch at the start or finish unit is ignored, just as it is when the card is read.

Re-importing the course file keeps both options, and keeps the course's loops while the common control still comes between them, because a course file has nowhere to record them.

Courses with loops ​

A star relay, or a butterfly, is one course whose loops all go out from and back to a common control, run in any order. Instead of entering every order as a variation, enter one example and tick Course with loops:

  1. Type the course as one example, with the common control between the loops: 97 96 90 93 94 90 91 95 90 95 91 90 96 97 90 94 93 90.
  2. On the Controls tab, tick Course with loops and choose the Common control (Manager proposes the control the course visits most). It must come between the loops and cut the course into at least two of them.

Each stretch between two visits to the common control is one loop. A competitor who runs every loop is OK in whatever order they ran them. A loop is matched by its controls and their direction, so 91 95 and 95 91 are two different loops. Splits are listed in the example's order, so everyone on the course can be compared loop by loop.

For a star relay where a team shares one card, enter each team as one competitor in an individual class, with a mass start, and set Finish to Last control so the final punch at the pivot is the finish. Read the card once, at the end.

As in MeOS, nothing checks which order a competitor was given — a competitor who follows someone else's order is still OK. That makes loops best suited to training and school events.

Star relays walks through setting one up and running it on the day.

Courses with skips ​

Some line courses let a competitor leave out one or more controls and still finish OK. On the Controls tab of Edit course, tick Controls may be skipped, then say which skips are allowed:

  • Skip any — how many controls a competitor may leave out anywhere on the course. Tick Never two in a row if two skipped controls may not be next to each other ("skip three, but not consecutive ones").
  • Choice groups — controls next to one another on the course of which a competitor visits only some, as a course setter writes them: 31-32-33-(34 or 35)-36-37-38-(39 or 40 or 41)-42-(two of 43, 44, 45)-46. Add a group for each bracket, choose its controls, and set Must visit — 1 for "34 or 35", 2 for "two of 43, 44, 45". A group's skips are its own: they don't use up Skip any. Set Skip any to 0 when only the groups allow skips.

The controls a competitor does visit must still be visited in the printed order, choice groups included, and the course is still ranked on time.

The course shows a Skips chip in the Courses list, with its rules beside it, and in the class and course pickers. A competitor who kept to the rules is OK, and the controls they left out are shown as skipped — on the splits printout, on the Result and Overrides tabs of Edit competitor, on the download banner, and in the spectator splits. A competitor who skipped more than the rules allow is a mispunch, and every control they didn't visit is listed as missing.

A course with skips can't also be forked or have loops. Changing the rules re-scores everyone already downloaded on the course. Re-importing the course file keeps the rules while the choice groups still fit the new course, because a course file has nowhere to record them.

Course pools and locking a competitor to a course ​

A class can hold more than one course — a course pool. This is common where a class is split across forked courses, or where several map variants share a class. When a competitor's card is downloaded, Manager checks it against every course in the class's pool and records the one that produced the best result.

Some events allow any course for any competitor in a class, whereas some events lock a competitor to a specific course. Only the course a competitor is locked to is checked against their download.

To lock a competitor to a course:

  1. Open the competitor in the Competitors list.
  2. On the Details tab, use the Course picker (shown only when the competitor's class has a pool of two or more courses).
  3. Choose the course to lock them to, or leave it on Any in the course pool to let Manager pick the best match automatically.

When a course is locked:

  • The competitor download is checked against only that course. If their punches don't match it, they get a Missing Punch (or DNF) against the locked course — Manager will not quietly move them to a different course in the pool.
  • The lock is durable: it survives re-downloads, course edits, and class edits. (If you move the competitor to a class whose pool doesn't contain the locked course, the lock is cleared automatically.)
  • When the lock is left on Any, the course the automatic evaluation actually chose is shown read-only as the Course on the competitor's Result tab, so you can see which course produced their result.

On a forked course the same tab has a Course variation picker, which locks the competitor to one fork in the same way.

Course and variation locks can also be set for many competitors at once in the bulk-edit grid, or applied by importing an IOF course file that contains per-competitor course assignments.