Enter Absent Runner Data: Difference between revisions

From Mulka2
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
== Summary ==
== Summary ==
As soon as every runner has started, ask the organizers at start for information about runners who did not start (due to absence, injury, etc.). Enter DNS(absent) runners data in Mulka2 as shown below.
As soon as every runner has started, ask the organizers at start for information about runners who did not start (due to absence, injury, etc.). We call this DNS runners. Enter DNS runner data in Mulka2 as shown below.


=Communication with Organizers at Start=
=Communication with Organizers at Start=

Revision as of 19:19, 26 July 2017

Summary

As soon as every runner has started, ask the organizers at start for information about runners who did not start (due to absence, injury, etc.). We call this DNS runners. Enter DNS runner data in Mulka2 as shown below.

Communication with Organizers at Start

Communication with the organizer who handles Mulka2 and the organizer at start is very important. Before the event, make sure to decide "when, who, whom" will tell information about runners who did not start.
It will be convenient if you prepare a startlist with a column in which the organizer at start can record competitors' absence/late start. You can download a sample startlist from here (.xls file) You should also prepare paper where the organizer can write down late starters' actual start time.