Oftentimes when scoring a Cross Country race coaches are not required to declare their Varsity athletes, yet a different Scored Event is necessary for Varsity and Junior Varsity scoring. Data Actions provide an effective and efficient solution to this problem, by automatically updating Participant Data in real time based on an Action Trigger.


For this hypothetical situation, we have four Scored Events: Boys Varsity, Girls Varsity, Boys JV, and Girls JV. To set up the data action, create an extra event - we will refer to this as the “Holder Event” - into which you will import all participants.  (Note: each Scored Event needs at least one Registration Event assigned to them - take this into consideration when creating your initial setup)


Once you have set up your Scored Events, Data Actions for each scenario need to be set up - in this case four data actions would be created:

  • Moving a participant from the Holder Event to Boys Varsity

  • Moving a participant from the Holder Event to Boys JV

  • Moving a participant from the Holder Event to Girls Varsity

  • Moving a participant from the Holder Event to Girls JV


To set up a Data Action - go to the Data Actions/Checks menu, select Data Actions, and click Add:






Next, set up the Action Trigger that will fire the Data Action.  In this case, set Issue Type to Raw Read and Issue Subtype to Edit:


The first part of the Data Action is the Participant Data Filter that determines who the Data Action will run on.



It is a good practice to require the Action Trigger to require the Registration Event be set to your Holder Event to prevent the Data Action from operating on the same participant once they have finished their race. It is also worth making sure that other parameters for the participant be met before they are moved - in this example only Male participants are allowed to be moved to the Boys Varsity event.


The second piece of this Action Trigger is a Raw Read Filter that looks for only participants that meet the above Participant Data criteria that read at the Finish Location between two Timestamps:


It is worth noting that this is ANY read at that location between those times - not just used occurrences - so it is always a best practice to keep the finish line protected from stray reads.


Finally, set the Data to Change when the conditions set in the Action Trigger are met - in this case moving a Male participant from the Holder Event who read on the finish between 2:30PM and 2:55PM into the Registration Event named Boys Varsity.



It is still necessary to set up Scored Events as you normally would for a Cross Country race, but participants moved by a Data Action will automatically have the Scored Event’s parameters applied to their reads and timing data.