Judging guide

This guide is for judges and head judges. How a tournament is set up is covered in Tournament setup.

Access

After being assigned you receive an email with a direct link to the tournament’s judging interface.
Alternatively, all your assignments are listed under “My assignments” (judging overview) when signed in — including a live badge for running heats.
On competition day: charge your device, get on the venue network, open the link — the app automatically keeps the screen awake while a heat is running.

The flow (sequential model)

MOEP scores one run at a time — this prevents mix-ups:

The head judge releases a rider’s run (start).
All judges score exactly this run — other riders are locked (“Waiting for release”).
The head judge confirms the run — only then is the next rider up.
A new run pass only starts once all runs of the previous one are confirmed.

In wavepool mode the same model applies per pool side: each side (e.g. Left Wave / Right Wave) runs sequentially on its own, so a left and a right wave can be scored at the same time.

Rapid surfing: the first round is held back

For contests with the sport rapid surfing, the first run of every surfer follows a special rule — it mirrors the common practice of adjusting the opening scores only once every surfer has been through once:

The head judge releases surfer after surfer; the judges score as usual.
The scores are held back instead of being confirmed one by one. The next surfer may still start right away — otherwise the head judge could never see them together.
Once every surfer is through, the head judge sees all scores of the round side by side, can reject individual ones or set them personally …
… and then releases the whole round together. Only then are the scores published and the second run can start.

From run 2 onwards the normal model applies again: the head judge confirms each run individually, and confirming publishes the score.

No other sport is affected.

For judges: the judge app

Wavepool: when you open the heat, pick your pool side at the top. From then on you only see and score that side’s waves; the choice is remembered across reconnects.
Score three criteria: Composition (20%) · Variety (40%) · Execution (40%) — each 0.1–10 with one decimal. MOEP computes the total automatically.
On the phone you score criterion by criterion; in landscape you see all three columns side by side.
Everything in one column, top to bottom in the order you need it: the heat overview, then the scoring pad. Nothing is moved off to the right, not even in landscape.
The heat overview is the one table of the heat. One row per rider, one column per run, plus rank and total at the end of the row. Each cell shows your own score on top and, small below it, the published panel value for that run.
- Rows do not move. The order stays the order of the start slots even when the ranking changes — the rank is shown as a number next to it. That way you do not have to find your rider again after every run.
- The panel value only appears once the head judge has confirmed the run. It is the very same state the audience sees. Your colleagues’ scores in progress never reach you — and in a rapid-surf contest the first round stays empty until it is released as a whole.
- Tap an open run right in the table to score it. That is how you catch up on a wave you missed.
The mask starts empty. There is no default value any more — where nothing has been scored yet, a dash is shown. Sending stays locked until every criterion has a value, and the line below tells you how many are still missing. That way an accidental confirm can no longer send a score nobody actually gave.
Three ways to set a value: the suggestions below the value (steps across the whole scale, so 1 and 2 are there for a fall at the start), the +/− buttons for fine corrections, or type the number directly — tap the value, type, press Enter.
Values below 1: the scale starts at 0.1, not at 1 — so a fall right at the start can be scored 0.3. Type such values with a separator (0.5); otherwise the rule below applies and 5 becomes 5.0. The +/− buttons also go down to 0.1.
Type without a decimal point: just enter 72 and MOEP turns it into 7.2. The rule: anything that is already a valid value stays as it is (7 → 7.0, 10 → 10.0); anything above is read as a number with one decimal (72 → 7.2, 95 → 9.5, 100 → 10.0). Same on a 100 scale: 72 → 72.0, 725 → 72.5. If you type the separator yourself, your entry counts literally — 7.2 is always 7.2, never 72.
You cannot go above the scale: the field stops accepting a digit as soon as no valid value can come of it. 265 ends after 26 (= 2.6) — instead of silently jumping to the maximum.
The run timer at the top shows the remaining time of the current run.
“Last run” shows each rider’s previous score — helpful for calibration.
Heat overview: below the scoring area sits a grid with your own scores across the whole heat — riders (with lycra colour and bib number) by runs. Use it to compare backwards: was run 4 better than run 3? Was rider 1’s run 2 above it? The run currently being scored is highlighted. You do not see the other judges’ scores — that is deliberate and technically enforced, so every score stays independent.
Duplicate values are flagged: no value should appear twice within a heat. If you type a value you already gave here, the app points it out — before you submit. It is a hint, not a lock: the call stays yours.
Confirmation on submit: if you hit Send and your total already exists in this heat, the app asks back: “Identical score — are you sure?”, naming the surfer and run that carries the same value. You can send anyway — identical scores are allowed. The question returns for every affected score; there is deliberately no “don’t show again”, so the safeguard cannot be switched off with one annoyed tap. Only the total is compared: two equal individual criteria with different totals are normal and trigger nothing.

Fail run: one value instead of three

If the surfer falls mid-run, there is nothing left to split across C/V/E — and in a running heat there is often no time for three entries. The Fail Run — score a fall button below Send opens a small mask of its own:

Quick select from 0.1 to 3.0 — the range a fall lands in, in practice.
Or type the value freely: the whole scale is allowed, not just 0.1–3. The quick select is a shortcut, not a limit.
While the fail-run mask is open, the normal send button is hidden — there is exactly one action. The ✕ takes you back to normal scoring.

The value you enter is a perfectly normal score: it counts in the panel average, in the deviation check and towards drop scores like any other number. It simply has no breakdown into C/V/E — which is why a small F sits next to it in the heat overview and in the head judge’s panel. Here too the app asks back if the same value already exists in the heat.

Once submitted, your score is final. If the head judge rejects it, your field opens again and you re-score that run — as often as needed. Your previous number stays visible until then, and the fact that a re-score was requested is recorded with the tournament.

Practising without a contest

Under My assignments → Practice heat you score a made-up heat with four riders and five runs. The mask is the same as in a contest, but without a head judge: no waiting for a release, no confirmation — you score one run after another directly.

Nothing counts. The practice run is not stored anywhere; no tournament, ranking or bracket is affected. Reloading the page resets it, and the Reset button clears it at any time.

The practice heat is available to signed-in judges only.

When the network drops

The judge app buffers your score locally and re-sends it automatically once the connection is back (“buffered” notice). The connection indicator at the top shows the status; nothing is lost, and duplicate scores are technically impossible.

”Not signed in” or “Not assigned”

The connection indicator reports genuine network problems only. Two situations look similar at first glance but are not connection failures — so the app names them instead of loading forever:

Not signed in — your session expired, or you are not logged in on this device. Sign in via the button; you land back on the same heat afterwards. Any buffered scores are kept.
Not assigned — your account is not registered as a judge (or head judge) for this tournament. Only the organisers can change that: they add you under Judges in the tournament dashboard. An org admin account alone is not enough — scoring always requires a real judge assignment.

For head judges: the HJ panel

The matrix view shows athletes × judges: who has scored, what’s missing — the active rider is highlighted, the queue below.
Start run releases the next rider; restart resets the timer after a confirmation dialog (submitted scores are kept).
Heat overview: Below the matrix you see the same table the judges see — one row per rider, one column per run, plus rank and total. The matrix above only covers the current round; the overview covers the whole heat.
Deviations: if a judge deviates more than the configured threshold, the panel marks the cell. You can reset that single score — the judge then scores again. A rejected score now counts as not submitted: it feeds neither the average nor the comparison behind the deviation marker.
Confirm closes the run — and only works once every judge has scored. While a re-score is outstanding the button stays disabled and the next rider waits. If a judge does not deliver, set the value yourself via “Set yourself” (head judge override) and confirm afterwards.
Pad failure: emergency entry. If a judge’s device dies mid-heat they have not scored at all — so there is nothing to reject or override, and the run could never be confirmed. For this case, tap that judge’s empty cell in the matrix, enter the total score they called out, and confirm. Individual values (C/V/E) are not captured — the emergency entry only knows the total.
- The cell is then marked HJ*, distinct from the HJ of a score you set yourself. Who entered it and when is recorded.
- The value counts towards the run average and the result as usual. The per-criterion average and the deviation highlighting are computed without it — otherwise the remaining judges would be measured against a score that has no individual values.
- If the pad comes back and the judge should score after all: reject the emergency entry and their input opens again.
F in the matrix: a fail run. If a judge recorded a fall as a single value (see above), a small F sits next to the number. That cell has no individual values either and is therefore — like the emergency entry — excluded from the per-criterion average and the deviation highlighting; it counts perfectly normally towards the run average and the result. Rejecting and overriding work as for any other score.
After the last run: complete the heat — placements and advancers are computed automatically; ties are resolved by the tie-break cascade.

A surfer does not start or withdraws (DNS/DNF)

Below the matrix sits the heat’s starting field. That is where you mark a surfer who does not go into the water. Two cases, two buttons:

Did not start (DNS) — applies to this heat only. One click, no confirmation.
Withdraw (DNF) — the surfer is out of the contest (typically an injury). From here on they are listed that way in every following heat. Because that reaches beyond the running heat, MOEP asks once.

What happens:

The heat runs with one surfer fewer. Nobody moves up — that would re-score a round that has already been surfed.
The starting spot stays visible. The leaderboard, the bracket and the overlays show DNS or DNF where the rank would be, instead of letting the surfer disappear silently. A place already seeded further along (“winner of heat 1”) is resolved the same way.
Scores already earned remain. Someone who surfed through run 2 keeps those scores and their total — the withdrawal applies from that moment, not retroactively. Their still-open runs leave the heat so the next rider can start.
They do not advance. A withdrawn surfer gets no placement and is not drawn into any following round.

Undo uses the same button, as long as the affected heat is not finished — a mis-click in the middle of the contest is not final. The surfer gets back the runs that are still open; rounds already surfed are not handed to them retroactively. Undoing a DNF cancels the withdrawal as a whole; heats that have been finished in the meantime keep their DNF.

Head judge and contest director may mark (the latter has the same buttons on the heat page in the dashboard). Every marking is logged with author and timestamp.

Competition-day quick checklist

Open the link from the email — connection indicator green?
Head judge starts run 1 of the first rider.
Score → HJ confirms → next rider.
Complete the heat, activate the next one.
Scoring questions are decided by the head judge.