Every school’s chess season, on one page.
Schools run their own events, families finish paid entry with the organizer, and the office sees participation totals by school, never a student’s browsing.
Chess is the working surface today; other types can be hosted. A pilot uses the same organization workspace as schools, not a custom portal. There is no instant district signup.
How a school or district starts
Setup is a working session with the Causey team. Before students join, we review the school’s devices, email access, staff roles, and agreement.
Step 1
We set up your school or district
Start with one school or its actual operating district or network. Causey checks the institution and hands its workspace to the administrator you name.
Step 2
Staff invite their own people
Coaches and school administrators share join links with students, families, and staff. No shared passwords, no district-wide access to student accounts.
Step 3
Coaches run the events
Post a tournament to a team, see who can go, track who still needs to register with the organizer, and mark attendance on the day.
Step 4
The district sees the totals
District reports show participation and attendance counts by school. Authorized district administrators can also review connected-school rosters; class operations stay with school staff.
Who sees what, before anything else.
Reports, roster access, and classroom work have separate permissions. Public listings never include private student records.
Causey
Moves events, RSVPs, and totals between the right people. Stores the minimum.
District office
- Aggregate reports by school
- Authorized connected-school roster review
School staff
- Their own school only
- Roster, RSVPs, attendance
Public
- Public listings only
- No accounts, no students
Student browsing history
Not shared with school or district staff. Reports do not show what a student searched.
Three questions, answered without a spreadsheet.
“Which schools actually played this semester?”
Coaches mark attendance on the day; the office total updates itself.
No spreadsheet to maintain and no end-of-season email chain.
“Did families finish registering?”
Each event shows who is going and who still has registration open.
Families record when they finish the organizer’s registration. That is their confirmation, not an imported payment receipt.
“What do we hand the board at season’s end?”
One exported file with participation and attendance totals by school.
Named attendance, places, and awards stay in the school’s authorized reports.
Illustrative preview of the district workspace. Schools and totals are wireframe, not real data.
The preview cycles through three wireframe views of the Causey district workspace: participation totals by school, a district-wide tournament with schools marked going, and an exportable season report. It uses no real school data.
What we have not finished
This is a pilot, not a finished procurement package.
- Privacy, retention, and securityNot settled
- Privacy, how long data is kept, and security still have to be settled with the district.
- Email at school volumeIn pilot
- Causey has to prove its email delivery at school volume.
- Independent clubsSeparate path
- Independent clubs use a separate self-serve workspace. This is a pilot, not a finished procurement package.
- Beyond chessLater
- The pilot runs chess. Other types can be hosted; their public indexes are still thin.
Bring Causey to your district.
Names stay off this page. Districts join the pilot after legal review, and live email verification comes before any student rollout. A conversation is the first step, not a commitment.