The number of submissions are taken from highest scores, complicated by consideration of only one submission per hardware model and one submission per competitor.
Say I submit two GPUPI scores with a GTX 1080 and one with a GTX 1060 (which I am very likely to do.) Also say ttOne submits one with a GTX1080 ti. One of my 1080 scores will be higher that the other and higher than the 1060 score. The higher 1080 score will count regardless of which was submitted first. The other can't count because there is a higher 1080 score. The 1080ti score will surely be higher than the 1080, but both count because those are different GPU models and were submitted by different competitors. The 1060 score will not count because I already count the 1080. When someone beats my 1080 score, the 1060 score could count if it is the team's top 1060 score and in the team's top five scores for the stage. None of that has anything to do with the order of submissions as long as they are in before the contest closes.
All this selecting of higher scores, one representative of a hardware model and one submission per competitor is done by HWBOT programming as the scores are submitted.
The stages I can do:
XTU 5GHz with 6700K, 7700K andd7350K -- M9A
HWBOT Prime with 4970K, 4770K and G3258 -- M6E
GPUPI 32B with GTX 1080 and GTX 1060 -- M9A?
3DMark Vantage with GTX 980 -- R5E10
Memory Frequency with DDR4 and DDR3 -- M9A and M6E
3DMark11 Physics with 5820K (Haswell, not Broadwell) -- R5E10
GPUPI for CPU 100m with 6950X and 5820K -- R5E10
Geekbench3 with 4970K, 4770K and G3258 -- M6E
I can submit more than once in many of these stages, but only one will count. That's one reason I'm glad this is a team contest. The other is that I can't cover even half of the stages. It'll be fun watching teammates come up with scores for stages I can't touch.