I’m not sure JTPs get an expiration date. (We used to give them one 3 months in the past, because that version of the membership system did not allow a null expiration date field, but I don’t know what the Civi-CRM system does.)
Once the section is flagged as a JTP event, expiration dates are not checked. The validation report may show them as non-members, but it will be an alert (no action required).
There have been 19 K-3 JTP events rated so far this calendar year, involving 659 players (499 unique member IDs).
Of these, around 20 have no membership type or expiration date.
226 players (165 unique IDs) are type Q. All of these have an expiration date, some before the event, some after.
What do you mean by type Q?
Dating back several decades, letter codes have been to indicate the membership category. A for regular affiliate, etc.
Over the years the codes and their meanings have changed, and to be honest I’m not sure exactly what codes the CIVI-CRM system uses these days, though I do know some usages appear to have changed again. (For example, we used to have both L and Z life members, now I think they’re all Z except for a few.)
In the past, though:
Type Q was for JTP non-members.
Type X was for adult non-members.
Since I see many recent players in JTP events who are type Q, I am assuming that Q is still used for that purpose. It does appear that the expiration date might be set to the end of the month in which the JTP code is first assigned to that member ID, I’ll raise that with the office, though I don’t know if it is worth changing (see below.)
There are virtually no Q players in non-JTP events. During event validation in non-JTP events, those with type Q or X are treated as if their expiration date is 1900-01-01, so they would be treated as not current members.
Also MSA shows type X or Q players as non-members.