Competitors, clubs and teams

Audience: Event organisers managing the list of people taking part.

This page covers the Competitors, Clubs and Relay teams pages and the competitor edit dialog. As with classes and courses, most events get their competitors from an import — see Importing event data — so you're usually reviewing and adjusting rather than typing everyone in by hand.

Note: Relay events organise competitors into teams with legs. The Relay teams page is summarised below; building and running teams is covered in Relay events.

The Competitors page

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

The table shows one row per competitor. Some columns are shown 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). The columns are:

• Competitor — the competitor's name. Click it to open the edit dialog.
• Class — an inline dropdown. Change it here to move the competitor to another class without opening the dialog. Pick No class to unassign.
• Club — the club they represent (read-only here; set it in the edit dialog or via import).
• Team and Leg — relay events only: the runner's team (shown by default) and their leg (hidden until you turn it on).
• Country — the flag and three-letter code of the competitor's club. A competitor has no country of their own, so to change it, change their club, or the club's country in Settings → Club registry. Hidden until you turn it on in the columns menu, the same way as Ranking below. Sort it to group each country's runners together.
• Start time — the effective allocated start, annotated with where it came from — 10:30:00 (individual), (class), or (event). See Start times.
• Card — an inline field for the card number. Type a new number to reassign; it saves automatically. A yellow Duplicate warning appears when the same card number is on more than one competitor. A flag beside the number marks a hire card, and a second icon anything else the competitor has on hire.
• Bib — the competitor's bib. Shown by default as soon as anyone in the event has one.
• External ID — the competitor's number in the registration system they were entered from, with that system's name beside it — 4521 Eventor, or External for a number typed in by hand. Blank for a competitor with none. Hidden until you turn it on in the columns menu.
• IOF ID — hidden until you turn it on.
• Ranking — the competitor's place on an external ranking list; see Ranking below. Hidden until you turn it on: use the columns button at the right-hand end of the header row and tick Ranking under Show columns. Sort it ascending and you get the seeding order: rank 1 at the top, and everyone with no ranking sunk to the bottom rather than floating above rank 1.
• Start request — what the entrant asked for; see Start requests. Hidden until you turn it on.
• EOD — ticked for a competitor entered by hand on the day rather than from an imported entry list. Hidden until you turn it on.
• Course and Variation — the course (and fork) the competitor runs. Shown by default when a course has fork variations.
• Last seen — what last saw this competitor: a radio punch (the check included), or a Start or Check station's memory. Shown for runners on course, or checked in and not back. Relevant during the event rather than at setup; see Radio punches.
• Race time — hidden until you turn it on.
• Points — on a score course, the points scored. Shown by default once anyone has been scored on points.
• Status — the competitor's status. A small course badge shows which course the result is on. Icons beside the status flag a status you set by hand (it stays as you set it), a competitor who completed the course but has no start time, and one timed from their check punch or from midnight because no start was recorded.
• Custom fields — one column per custom competitor field, hidden until you turn it on.

Filter the table with Search name, card or bib (matches the name, the card number and the bib — a relay runner's bib is their team's with the leg after it, so a team's bib, say 101, finds every leg of it), the Class filter (which includes No class), the Status filter, or — once a hire-card pool is set up — the Card type filter (Hire card or Own card). The status filter includes a synthetic OK - pending download option that picks out competitors who are provisionally OK on radio punches but whose card hasn't been downloaded yet.

The Actions menu (top right) has:

• Import… — open the Import event data dialog. See Importing event data.
• Add… — create a new competitor by hand (see below).
• Set competitors DNS… — bulk-mark non-starters as Did Not Start (see Marking non-starters).
• Bulk edit… — edit many competitors at once in a grid (see Editing many competitors at once).
• Changes report… — list the card numbers, classes, clubs and names changed during the event, and carry them into future events and the competitor registry. See Changes report.
• Allocate bib numbers… — number everyone's bibs, in blocks by class if you like, with one number per person across a whole carnival. See Bib numbers.
• Seed from IOF ranking… — give entrants with an IOF ID their world-ranking place. See Seeding from the IOF world ranking.
• Export entry list — Export IOF XML, Export JSON or Export CSV: write who has entered to a file. See Exporting the entry list.
• Start blocks — Start blocks (CSV) or (JSON): which start block each entrant is in, for the whole event. See Start blocks.
• Delete all competitors… — empty the list (see Clearing the whole competitor list).

Adding or editing a competitor

Click Actions → Add… to create one, or click a competitor's name to edit. The Add competitor / edit dialog opens.

When creating, you get a single form:

• First name and Surname — at least one is required. As you type, Manager suggests matches from the Competitor Registry (unless the event ignores it); picking a person fills in their club, card number, and Eventor/IOF IDs.
• Card number — numeric only. (During a card download this field is pre-filled and locked.) With a SportIdent reader connected, a button beside the field lets you fill it by presenting the runner's card instead of typing — the card is read for its number only, not downloaded, so you can enter someone who is still holding their card. The button's tooltip says whether it is listening (Insert a card in the card reader) or off (Card reading disabled); click it to switch.
• Eventor ID and IOF ID — optional external identifiers, used by exports and re-imports. The first is labelled with the system its number came from — Eventor ID, External ID for a number typed in by hand, or whatever system the entries were imported from. To change that system, use the small tag button inside the field: pick a system from the list (Eventor, External, and any other this event's entries already use) or type a new one. It can't be pressed until there is a number, and a system left blank is saved as External. To fill in IOF IDs for a whole field — from Eventor, an IOF XML file, or the IOF world ranking CSV — see Importing IOF IDs.
• Class — the class they run. Pick No class to leave them unassigned. Each class's course format is shown beside it in the list.
• Club — the club they represent, or No club. Type to search; only clubs Manager already knows are offered (add a new one in Settings → Club registry; an entry import also creates the clubs its file names — see Importing event data). The club's country flag shows beside it for reference. You can't edit the country here: it belongs to the club, and you set it in Settings → Club registry.
• Birth year and Sex — optional; see Birth year and sex.
• Course — appears only when the chosen class has two or more courses in its pool. Leave it on Any in the course pool to let Manager pick the best-matching course automatically, or lock the competitor to a specific course. See Course pools and locking. A Variation picker appears the same way when the course is forked.
• Allocated start time — an individual allocated start, plus an On start punch option controlling whether a start-box punch is allowed to override it. The event's and class's mass starts are shown above it for reference. The full rules live in Start times.

Click Save. Two checks may stop you first:

• No class selected — if you leave the class empty in an event that has classes, Manager asks, because a competitor with no class can't be scored or ranked. Pick a class there, or choose Add without a class.
• Possible duplicate — if somebody with the same name or card is already in the event, Manager lists them. Cancel to go back, or Add anyway.

Keep adding, at the bottom of the form, is for entering a queue of people one after another: with it on, Save stores the competitor and clears the form for the next one instead of closing, and the one just added is named beside the switch. Only the class is carried over — everything that identifies a person starts blank, so one runner's card can't end up on the next runner's entry.

Editing an existing competitor

Opening an existing competitor gives a wider dialog with tabs down the left:

• Details — the create form's fields (all but the start time, which moves to Start) plus a few that only make sense once a competitor exists, among them Bib, Ranking (see Ranking below), Birth year and Sex (see Birth year and sex) and Notes (see Notes). A relay runner's bib comes from their team, so in its place they get a read-only Relay team panel (team, leg, bib, start time). In edit mode changes save automatically: text fields a moment after you stop typing, dropdowns immediately. There's no Save button — just close the dialog when you're done.
• Start — where the competitor's start time comes from: the event or class mass start, their Allocated start time, and the On start punch choice, with a line explaining which wins. Also their start request. Not shown for a relay runner, whose leg starts at the changeover. See Start times.
• Result — the competitor's status, resolved course, and race time. You can override the status here; Manager won't let you reset a competitor to None if there's evidence they started (a download, radio punches, or a station-memory punch).
• Radio punches, Download, Unit downloads, Prints, Analysis, Overrides — these relate to running the event and resolving results; they're covered under Running the event and Resolving issues. Prints shows the competitor's splits print, or their result label, as it would print, and prints it — see Printing by hand, and reprinting. Analysis is left out for a score or scatter course.
• Audit trail — every recorded change to this competitor. See One competitor's history.
• Custom fields — the values of your custom fields, when any are defined.
• Hire items — what the competitor has borrowed, when any hire items are set up. See Hire items.

To remove a competitor, open them, go to Details, and click the red Delete button (bottom left, beside the magnifier). Confirm the prompt. Deletion is permanent.

Moving to another competitor without closing the dialog

To look at somebody else, you don't need to close the dialog and go back to the list. Press Ctrl+F (⌘F on a Mac) while the dialog is open, or click the magnifier at its bottom left, and type part of a name — or a bib or card number, the same as the Competitors page's search box. Matches are listed as you type, names beginning with what you typed first. Press Enter to show the first one, or click any of them. The dialog switches to that competitor on Details; anything you were typing for the previous one is saved first. Esc closes the search and leaves the dialog where it was.

The search is there whenever you're editing an existing competitor, on any tab — not while adding a new one.

Card numbers

The Card column and the Card number field hold the number of the card a competitor carries. A few things to know:

• Presenting a card. With a SportIdent reader connected, click into the Card number field on an existing competitor's Details tab and insert the card: its number is filled in, and nothing is downloaded. The field only listens while the cursor is in it — anywhere else on the manager, a presented card is a download. (For a new competitor, see the reader button described above.)
• Duplicates are allowed but flagged. Two competitors can hold the same card number — Manager shows a yellow Duplicate warning rather than blocking it. This is normal when a card is shared between two people running in different classes at different times, but a duplicate among people running at the same time will cause a download to land on the wrong competitor, so check any duplicates you didn't intend. A card that has gone astray or been shared on the day is covered in Lost cards and shared cards.
• A blank card is fine at setup. A competitor can be entered without a card and have one assigned later — including automatically, when their card is downloaded.
• Hire (rental) cards have dedicated support. You keep a shared pool of hire-card numbers under Settings → Hire card registry; any competitor whose card number is in the pool is automatically flagged as being on a hire card, and you can narrow the list with the Card type filter (hire vs own). Anything else you lend — a compass, a map board — is ticked on the competitor's own Hire items tab. See Hire items. The pool belongs to this computer rather than the event, so Manager also records on the competitor that their card was a hire card when it was handed out or read: an event restored on another machine, or pushed to the cloud, still knows which cards were hired.

Ranking

A competitor's Ranking is their place on an external ranking list — a national ranking, a squad's seeding order, whatever list you were handed for this event. 1 is the best-ranked athlete, and the number gets worse as it grows. Someone who isn't on the list has no ranking, which Manager shows as a blank rather than a zero.

It is a place, not a score. A ranking of 4 is better than a ranking of 40, and Manager will never treat a bigger number as better. (World Ranking points are the opposite — bigger is better — and are a different thing entirely; Manager doesn't store them, and won't read a points column as a ranking.)

Three things use it:

• The By ranking start draw, which seeds each class in ranking order.
• The Ranking column on this page, off until you turn it on in the columns menu.
• The spectator site: tap a competitor to open their card and the ranking is one of the details listed, for anyone who has one.

Nothing computes it and nothing changes it behind your back — it's yours to set. There are four ways to get it in:

1. Type it into the Ranking field on the Details tab of an existing competitor. It saves as you type, like the rest of that tab. Clear the box to mean "not ranked".
2. Import a ranking list — the usual route for a whole field. IOF XML, OJSON and CSV are all accepted; only the CSV asks you which column is which. See Importing rankings.
3. From an entry list, if yours happens to carry one. Most don't: there is no ranking field in the IOF XML standard, so Manager reads one only from an IOF entry list whose <Score> is explicitly labelled as a rank, and from an OJSON file. Anything else is left alone.
4. From the IOF world ranking, for entrants with an IOF ID: Actions → Seed from IOF ranking… downloads it and writes their world places. See Seeding from the IOF world ranking.

Rankings travel out as well: all three of the entry-list exports carry them, so a list you've seeded once can be handed on, or exported and re-imported next season.

Note: Rankings are held per event, not in the Competitor Registry. That is deliberate — a ranking list is republished every few weeks, so a value remembered from an event three months ago would be quietly wrong. Import the current list for each event that needs one.

Tip: Re-importing an entry list or a start list never wipes rankings you've already set. A file that says nothing about a ranking leaves the stored one alone; only a file that actually states one changes it.

Birth year and sex

A competitor's Birth year and Sex sit beside Ranking on the Details tab, and on the form for a new competitor. They are what tells two people of the same name in the same club apart when results are matched up later, so Manager keeps them whenever an entry list supplies them — an Eventor import, an IOF XML or OJSON entry list, or a CSV with year-of-birth and sex columns (SportSoftware's YB and S are picked up on their own).

• The year only. Where a file gives a full date of birth, Manager keeps its year and discards the rest, and never stores a full date. Type a four-digit year, or clear the box to remove it.
• Private. They are shown to you on Edit competitor and nowhere else: no spectator, kiosk or live-results screen receives them, they are never part of the competitor data a public link serves after you push the event to the cloud, and no export you run from Manager — entry list, start list or results, in any format — carries them. They do travel in a backup, and in a cloud push, because those are copies of the whole event. (If you have set an access PIN, only a signed-in operator can read them.)
• What counts. A birth year must be four digits, between 1900 and 2100. Sex is Female, Male or Not stated. A CSV cell with a two-digit year, or a sex Manager can't read, is reported in the import's warnings and skipped; the rest of the row still imports.
• Re-importing keeps them. A file that says nothing about a birth year or sex leaves what you already have alone.

Notes

Notes is a box for whatever you needed to write down about one entry that no other field holds — "paid cash", "hire card back after the run", "under 12, running with a parent", "asked us to hold their car keys". It runs the full width of the Details tab, under Ranking, and saves as you type like the rest of that tab.

Nothing in Manager reads it. It never affects a status, a time, a draw or a result — it is there so the thing you would otherwise have written on a sticky note is somewhere the next person on the desk will find it.

Two places write the same note:

• The Details tab of an existing competitor, as above.
• The registration desk — the note is a box on each search result, so somebody at the entry table can add one without opening the whole record. The class and the card number are editable there too.

Notes are held per event, like rankings and for a stronger reason: "paid cash" is true of one Saturday, not of a person. They are not kept in the Competitor Registry and they never follow a runner into next season's event.

Note: A note stays inside this event. It is not written to any of the entry-list exports — not the IOF XML, not the OJSON, not the CSV — and no spectator, kiosk or live-results screen displays it. It does travel in an event backup, because a backup is a copy of the whole event.

Not a private field, though. Nothing shows a note to spectators, but the competitor data those screens read does carry it — the same as it carries your custom competitor fields — and that data is readable by anything that can reach this Manager, or the public link if you have pushed the event to the cloud. Write what the next person on the desk needs; don't write what you would not want a competitor to read.

Tip: Re-importing an entry list never wipes notes, the same way it never wipes rankings: a file that says nothing about a note leaves the stored one alone. Emptying the box yourself does clear it.

Start requests

A start request is what an entrant asked for when they entered. There are four:

• Early start — they have to leave.
• Late start — they are arriving late.
• Away from competitor — they must not run at the same time as certain other people. Two parents splitting the childminding between them is the usual reason.
• Close to competitor — they want to go at about the same time as certain other people. A family or a car-load who travelled together and want to leave together.

The last two name other people, and they name a group rather than a partner: a family of three is one arrangement, not two overlapping ones. Set it on one of them and Manager writes the whole arrangement onto every member, so the group reads the same whichever of them you open. Name somebody who is already in a group and the two groups merge, because that is what naming them says.

Set a request on the Start tab of Edit competitor — pick the kind, then, for the last two, tick the people it is about. There is also a Start request column on this page, off until you turn it on in the columns menu, and a request column in the bulk-edit grid, where the kind can be filled down a selection (the people it names are read-only there).

Requests also travel in and out of files. An IOF XML entry list and an OJSON file carry them both ways, so an entry system that collects requests can hand them straight over. Both CSV exports write them too (as Start request and Start request group columns), but a CSV import does not read them back. The people in a group are named as people, never as an id, and Manager matches them back once every entry is in — so somebody named by a file who is not entered leaves the request standing with nobody attached, and tells you so rather than guessing.

What Manager does with one

The start draw reads it — Honour start requests is on by default, so unless you have switched it off, the draw decides who takes which start time accordingly. It moves no class: an early start means first of that person's own class, not first of the event. A second setting, also on, lets an early or late request be answered with a free minute outside the class's own window where the event runs on past it, so somebody who asked to start late in a class that finishes at 10:45 can be given 14:00.

Every screen that shows a request says what was asked, never what the person got — honouring is best effort, and a group request in particular is only answered as far as the classes involved allow.

Note: Requests are held per event, not in the Competitor Registry, for the same reason rankings are. "Has to leave early" is true of one Saturday, not of a person.

Tip: Deleting an entrant takes them out of any group they were in, and the rest keep each other. Anybody the departure leaves on their own loses their request too — a group of one is not an arrangement — and Manager says so, so you can put it back on somebody else if it still applies.

Exporting the entry list

Actions → Export entry list writes who has entered to a file. There are three formats, and they differ mainly in what they can carry:

Format	What it's for
Export IOF XML	Handing the entries to a federation system, or anything else that speaks the IOF standard. Manager writes an IOF 3.0 EntryList, which is what the standard says entries should be exchanged as.
Export JSON	Moving the entries to another meshO Manager, or to anything that wants everything Manager knows. This is the fullest of the three — it's OJSON, the same format the other JSON exports use.
Export CSV	Opening the list in a spreadsheet: to check it, to hand it round, or to edit it and put it back.

Pick one and the file downloads straight away, named after the event.

Note: This is an entry list, not a start list — it says who has entered, not when they run or how they got on. None of the three formats carries a start time or a result. To publish start times, use the Publish menu on the Start list tab, which offers the same three formats with the times; for results, see Exporting data.

The export is always the whole event

Whatever the list on screen is filtered to, the export contains every competitor in the event. The search box and the Class, Status and Card type filters are there to help you find somebody — none of them narrows the file. The menu says so above the three formats, because this is the thing about the export most likely to catch you out.

It works that way on purpose. The failure that would really hurt is handing a federation an entry list with one person in it because you'd searched for a name a minute earlier, with nothing on screen to tell you. Getting the whole list when you wanted a smaller one is obvious the moment you open the file.

The one exception: a competitor with no class is not exported. All three formats are organised by class — an entry list says who has entered what — so somebody with no class yet has nowhere to sit in the file, and every export leaves them out. This is the same rule the start list follows. It matters because an entry import that couldn't work out a competitor's class still enters them, without one, and warns you at the time. If your export is short by a few people, sort the Competitors list by Class and look for the blanks.

A mixed relay event asks which kind

An event with both relay classes and individual classes can't put both in one file — see Mixed events. So Manager asks before it exports: choose relay or individual, and the file holds that kind's classes only. Export twice if you need both. An ordinary event never sees the prompt.

In a relay export, each leg runner gets a row (or an entry) of their own, under their team and leg number. Entrants in a relay class who aren't on a team yet are included as well — an entry-per-person relay is a whole field of runners whose teams you have still to build, and leaving them out would lose them from the file.

The CSV round trip

The CSV is built to go back in. Its column headings are the ones Manager's CSV entry import already recognises, so the loop needs no column mapping:

1. Actions → Export entry list → Export CSV.
2. Open it in a spreadsheet. Fix names, classes, clubs, cards, bibs.
3. Import it back through the Import event data dialog → Local files → the Entries row. The columns map themselves; check the preview as usual and import.

Not every column comes back. The export writes more than the entry import reads, so be clear about which is which before you rely on it:

Column	Comes back through the entry import?
Database Id (your own competitor number)	Yes
IOF Id	Yes. A blank cell leaves a competitor's existing IOF ID alone; a number in it replaces the one they hold, as an IOF XML entry list does. (To fill in IOF IDs without touching anyone who already has one, use Importing IOF IDs instead.)
First name, Surname	Yes
Class	Yes — matched by name
Club	Yes — matched by name
Country	Yes, but only when the import has to create the club; an existing club keeps its own country
Card	Yes
Bib	Yes
Ranking	No. Import the same file a second time through the Rankings row instead — the Ranking column maps itself there too, and the identity columns beside it are what it matches on.
Start request, Start request group	No. Requests come back through IOF XML or OJSON only; a CSV round trip leaves the requests already on the entries alone.
Team name, Leg (relay exports only)	No. Teams aren't rebuilt from a CSV. The runners return as competitors in the relay class and you re-assemble the teams — or use the bib convention.
Your custom fields	Yes — each one is matched to its column by name, and the mapping dialog gives every custom field a picker of its own. A value in a cell replaces the one the competitor holds; a blank cell leaves it alone. Only fields already defined in Settings are read: a column for a field you haven't defined is ignored, so define the field first. If you have a custom field whose name Manager's own imports already use — Rank, Class, Card, Start and so on — its column is written as Rank (custom) to keep it apart from the real one, so the file never carries two headings that look like the same thing, and that is the heading it is read back from.

So the round trip is a good way to correct who is entered and in what — not a way to move an event. It carries people, not the event's shape: a class named in the file that this event doesn't have is created with just that name, and nothing about its courses, its leg count or its mass start comes with it. Import the classes and courses properly first, then use the CSV for the entries.

Two things about the file itself. It is comma-delimited, and it is saved with a UTF-8 marker so Excel on Windows opens accented names properly instead of mangling them — if you re-save it from a spreadsheet, keep it as UTF-8 CSV. And a competitor with no ranking exports as a blank cell rather than a 0: blank means "this file says nothing about a ranking", while 0 means "clear the stored one". See Clearing a ranking.

What the IOF XML file leaves out

An IOF EntryList has nowhere to put some of what Manager holds. Those facts are left out of the file rather than tucked somewhere no other system would look for them:

• Bib numbers — a competitor's and a team's alike.
• A course lock, and a fork variation — which course, or which fork of a forked course, someone is set to run. See Course pools and locking.
• Your custom fields.
• Where the entry came from — Eventor, a file import, or typed in by hand.
• Notes — and these are left out of every export, on purpose; see below.

A ranking does travel, as a score labelled as a rank, so rankings survive an IOF XML round trip in both directions.

If any of the rest has to travel, use Export JSON. It is the same document with all of it included — the bib, the ranking, the course and fork lock, your custom fields and the entry source. The one exception is Notes: they are your own remarks about the people in front of you, so no export carries them and nothing publishes them. Use a backup if the whole event has to move.

The Clubs page

Navigate to Clubs in the Event data section.

The table is read-only and lists the clubs that are actually used by competitors or teams in this event:

• Logo — the club logo, if one is available.
• Club — the club name.
• Short name — the abbreviation; its first four characters are used on Leaderboard when the club display is set to Abbreviation.
• Country — the ISO 3166-1 alpha-3 country code (e.g. AUS).
• External ID — the club's number in the system it's registered with; for an Eventor club, its Eventor organisation number.
• Provider — who gave the club that number: Eventor, or blank. An export to Eventor includes a club's ID only when this says Eventor — see Club registry.

Drag a column heading by its grip to reorder the columns, and use the Columns menu to hide the ones you don't need.

Filter with Search club name or the Country filter. The page deliberately shows only clubs that at least one competitor references — so a club left behind by a re-import won't clutter the list.

Why clubs are "global"

Clubs live in a global Club Registry that spans every event, not inside a single event. Enter "Newcastle Orienteering Club" once and it's recognised in every future event, with the same short name and logo. Each event holds its own copy of the clubs its competitors use, merged on top of the shared cache so per-event tweaks don't leak elsewhere.

Because of this, you add and edit clubs in Settings, not on the Clubs page. Go to Settings → Club registry, where the Actions menu has:

• Add club… — name, short name, and country.
• Refresh clubs from Eventor — pull the known-clubs list from Eventor (shown when Eventor is set up).
• Fetch default logos from Eventor — download club logos automatically (shown when Eventor is set up).
• Clear club registry… — empty the registry. Events keep their own clubs.

Click a club's name there to edit its short name, country, and logo. See the Club Registry reference and Settings.

Editing many competitors at once

Some jobs are the same small edit repeated: a ranking list has arrived for the elite classes, a club has handed in its members' card numbers, a group needs start times allocated. Opening each competitor in turn works, but Actions → Bulk edit is built for it.

The Bulk edit competitors dialog shows a grid — one row per competitor, and every cell an editor. It opens with Competitor, Class, Ranking and Allocated start time, plus Course and Variation where the event has a choice to make; turn on the rest as the job needs them.

Choosing what you can see

Only fields worth editing in bulk are offered, so the grid is not the whole competitor record. The columns button at the right-hand end of the header row turns them on and off, and headings can be dragged by their grip to reorder — the same header row as the Competitors page itself:

Column	Notes
Competitor	Read-only, and always shown. It is how you keep your place in the grid.
Class
Club
Course	A picker only where the class has two or more courses in its pool; elsewhere it just names the one course the class resolves to. Shown by default when the event has any such class.
Variation	The fork a competitor is locked to. Shown by default when a course has forks.
Card	A card number entered twice is flagged in amber — that is legal (a relay stick handed down the legs) but it is also how a typo shows itself.
Bib	Not editable for a relay runner: their bib comes from their team.
Ranking	See Ranking above.
External ID	The number; the system it belongs to is set in the ID provider column. A number typed onto a competitor who had none is marked External; correcting one keeps its system (an Eventor number stays Eventor); clearing the number clears the system too.
ID provider	The system the external ID belongs to. Pick one from the list or type your own; a cell left blank is saved as External. Greyed out on a row with no external ID.
IOF ID
Allocated start time	Not editable for a relay leg, which starts at the changeover.
On start punch	Whether a start-box punch may override the allocated time; Inherited means "whatever the class or event says".
Start request	The kind of request.
Other competitors	Who the request names. Read-only here — choose the people on the competitor's Start tab.
Custom fields	One column per custom competitor field, if you have any.

Your choice is remembered, so the dialog opens the way you left it next time.

Typing your way down the grid

Filling the grid in is nearly all typing, so it takes the keyboard:

• Return moves to the next field along the row, and on to the next competitor at the end of it.
• Down arrow and up arrow move down and up the same column — the way to work through a column of card numbers, rankings or start times.

Whatever is in the cell you land on is selected, so the first thing you type replaces it. Cells with nothing to type in are passed over rather than stopping you: the competitor's name, a relay runner's bib, a class with only one course.

A dropdown cell — Class, Course, Variation, On start punch — is passed through by the arrows in the same way, so a column of them can be walked without anything popping open. To open one, press Space or click it; or simply start typing the value, which picks the matching option without opening anything at all. Club searches as you type and offers a list. While any dropdown is open it owns the keys: the arrows move through its options and Return chooses one.

Setting a whole column at once

The common case is the same value for a group of people: everyone in a class onto a particular course, a club's runners moved to another class, a mass start time for a group. Narrow the grid with the filters below, then use the small set-column button in that column's heading. Pick the value and click Apply — it goes to every row the grid is showing, and no others.

It is offered on the columns where a shared value means something: Class, Club, Course, Variation, Start request, Allocated start time, On start punch, ID provider (rows with no external ID are left alone), and any custom fields. It is deliberately not offered on Card, Bib, External ID, IOF ID or Ranking — those identify a person, so one value across a whole club is never what was wanted.

Rows the value cannot apply to are left alone, and the dialog says so when that happens: a course a class does not offer, or a start time on a relay leg. The button counts the rows it will actually change, so the number you see is what you get.

Like everything else in the dialog, nothing is written until you click Save — so if a fill goes somewhere you did not intend, Cancel undoes all of it.

Narrowing the list

The filters across the top scope the grid to the job: search by name or card, and pick any number of classes, clubs or statuses. "All the elite classes" is one selection, not four separate visits. The count beside the title tells you how many competitors are showing out of the whole event.

The filter is remembered per event, so you can close the dialog, do something else, and come back to the same set.

Saving

Changed cells are highlighted, and a pencil appears against the row, so you can see at a glance what you have touched — including after you have moved on to the next field. Nothing is written until you click Save; Cancel discards the lot (it asks first if you have made changes).

Save applies every changed row in one request. If the server refuses one — a duplicate bib, a card number that is not valid, a course that is not in the class's pool — then:

• every other row is still saved, and stops being marked as changed;
• the refused row keeps what you typed, and a Problem column appears with the reason;
• the dialog stays open, with a Only rows with problems switch so you can work through just those rows;
• fix them and click Save again.

The dialog closes by itself once everything has saved.

Marking non-starters (Set DNS)

After the start window closes you'll usually have entries who never turned up. Rather than editing each one, use Actions → Set competitors DNS on the Competitors page.

The dialog lets you select who to mark by status — typically those with no status yet or on course with no radio punches (put on course by their allocated start, with no radio start punch, start station read or radio control to say they went) — optionally narrowed to particular classes, and shows how many competitors match. Anyone who checked in and hasn't come back is always left out — set them DNS by hand once you know they didn't go. Confirm to set them all to Did Not Start in one go.

DNS vs. delete: set DNS for someone who entered but didn't start — they stay in the results as a non-starter, which is what you usually want and what the safety check relies on. Delete only someone entered by mistake who should vanish entirely.

Clearing the whole competitor list

Actions → Delete all competitors… empties the list in one step. Use it when an import went in wrong and you want to start the entry list again from a clean slate — it's much quicker than deleting entries one at a time.

Manager confirms first and lists what else changes, because the effects reach beyond the list you're looking at:

• Every competitor goes, along with their result, status, start time and any punch corrections.
• Card downloads and radio punches are kept — they're records of what happened at the event, not of who entered — but they're no longer assigned to anybody. Re-importing the entry list and re-assigning the downloads gets the results back.
• In a relay event the teams stay, but their legs are left without runners.
• Classes, courses, clubs and controls are untouched.

There is no undo. On a live event, back the event up before you do this.

Relay teams have the same action on the Relay teams page (Actions → Delete all teams…). Deleting the teams keeps the runners as competitors, but they lose the bib number and leg they inherited from their team; their individual results, card downloads and radio punches are not touched, and classes keep their number of legs.

Custom fields

If your event needs to record something Manager has no field for — a membership number, a T-shirt size, an emergency contact — define a custom field in Settings → Custom fields (see Settings). Every competitor then has a box for it on the Custom fields tab of the edit dialog, a column you can turn on in the Competitors list and in the bulk-edit grid (where a whole column can be set at once), and a column in the CSV round trip.

Like notes, custom field values are not private: no screen shows them to spectators, but the competitor data those screens read carries them.

Relay teams

In a relay event, the Event data section of the side menu has a Relay teams page: one row per team, with its Team, Bib, Class, Club, Competitors (the runners, leg by leg), Variations, Start time, Last seen, Status and Official columns. Search it with Search team, competitor or bib, or filter by Class and Status. Click a team's name to edit it.

Its Actions menu has Import…, Add team…, Assign bibs… (give each relay class a bib range, numbering its teams in order), Set variations… (hand out a balanced set of fork variations at random so every team covers each fork) and Delete all teams… (see above).

Building teams, the one-leg-per-runner rule, team bibs and how relay results are worked out are all covered in Relay events.

Late entries and on-the-day registration

Adding a competitor after the event is under way works exactly the same as above — Actions → Add…, or let a card download create the entry. Manager doesn't lock the competitor list once the event starts. For the registration-desk workflow and assigning start times on the day, see Late entries.

Related

• Importing event data — the usual way to populate competitors and clubs
• Exporting data — the event's other exports, results included
• Relay events — teams, legs, and why a mixed event exports one kind at a time
• Classes and courses — the classes competitors are assigned to, and course pools
• Start times — allocating and overriding start times
• The start draw — the one thing that acts on a start request, and only when you ask it to
• Competitor Registry — the cross-event store of known competitors
• Club Registry — the cross-event store of clubs
• Downloading cards — how a download attaches to a competitor
• Late entries — adding competitors on event day
• Bib numbers — numbering everyone's bibs, across a carnival if need be