Boyceville Invitational
Current policy
Nobody from this tournament has told us what they want. Until somebody does, these tests work like any other: people who have added a folder of their own can take them, and nobody else can.
What is here
Every test from this tournament, how many times each has been handed out, how many working copies answer for it, and how many times a moderator has opened one.
Handed out 0 times, 0 working copies, 0 admin reads.
The exact count is hidden while few people hold this test. An exact number beside a small number of copies can point at who brought it.
Scheduled to go public on 2026-08-20
Handed out 0 times, 0 working copies, 0 admin reads.
The exact count is hidden while few people hold this test. An exact number beside a small number of copies can point at who brought it.
Scheduled to go public on 2026-08-01
Handed out 0 times, 0 working copies, 0 admin reads.
The exact count is hidden while few people hold this test. An exact number beside a small number of copies can point at who brought it.
Scheduled to go public on 2025-08-07
Handed out 0 times, 0 working copies, 0 admin reads.
The exact count is hidden while few people hold this test. An exact number beside a small number of copies can point at who brought it.
Scheduled to go public on 2024-08-15
Handed out 0 times, 0 working copies, 0 admin reads.
The exact count is hidden while few people hold this test. An exact number beside a small number of copies can point at who brought it.
Scheduled to go public on 2024-08-15
- Boyceville - 2019-20 - Div B2019-20
Handed out 0 times, 0 working copies, 0 admin reads.
The exact count is hidden while few people hold this test. An exact number beside a small number of copies can point at who brought it.
No date yet
Admin reads count rows in the public log. A reviewer opening a folder from the queue writes one before the link is decrypted, so those show up here. The old admin screens open a link and write nothing, so those do not, which is why the charter publishes no number for reads outside the queue.
I ran this tournament
Enter the address the tournament uses. If it is on the tournament's own school domain we send a link straight away. Any other address goes to a person, who answers within 24 hours. Either way the address is stored so we know who asked, and it is never shown on this site.
If this is urgent, a takedown needs no account, no form and no checked address. Say so on the about page and a named person acts on it inside 24 hours.
What this doesn't do
- Do not trade cannot un-send what is already open. It retires every copy, gives back the week to everyone who had one open, and blocks the folder from being added again. It cannot reach a copy somebody already opened in Drive, and no site could. What it does is stop the next one.
- The block list cannot spot a bought packet in advance. Science Olympiad sells event packets with DRM and a watermark per buyer, so no two copies hash alike and there is nothing to load onto a list. Four things are supposed to stand there instead: refusing tests above invitational level, a promise made when the folder is added, a filename check a reviewer sees, and a report about a paid packet. None of the four is built. What this list catches is a folder a tournament has taken down or somebody has reported.
- Ageing is not running yet. The dates above are the schedule the job would follow, computed on every read rather than stored. Nothing is publishing anything on them yet. Do not trade suspends the schedule for as long as it stands, and the job reads this page before it publishes anything. The whole schedule.
- The do not post list names tournaments, not categories. This file names TOURNAMENTS. It cannot express the category rules, and the two