This chapter runs its teams, its attendance and its Cup out of one page. This is the tour — what each tab does, who can see it, and what you are expected to do with it.
A chapter with a hundred members has a problem that a chapter with fifteen does not: nobody can hold the whole roster in their head. Who is new, who competes, who has turned up to nothing since September. This page exists to answer that without a spreadsheet nobody wants to maintain.
It does three things. It drafts the chapter into balanced teams — Orgs — instead of letting them form by friend group. It tracks participation, so showing up is visible and counts for something. And it runs the Org Cup, which is the season-long competition between those Orgs that makes the first two matter.
Everything else on the page is in service of one of those three.
Sign in with the Google account your chapter knows you by, or with a username and password if an officer made you one. What you can see depends entirely on the role your officers gave you — not on anything you can set yourself.
The draft balances four things: team size, which division you lean toward, how long you have been in the chapter, and — if your chapter uses them — personality types. Every one of those comes from the form. A blank answer does not make you neutral; it makes you a coin flip.
Roles are set by officers and checked on the server every time anything is saved. Hiding a button is not what keeps things safe — the sheet refuses writes it should not accept, whatever the page happens to be showing.
| Can they… | Member | Org Lead | Admin | Master |
|---|---|---|---|---|
| See standings and their own Org | Yes | Yes | Yes | Yes |
| See their own points and type | Yes | Yes | Yes | Yes |
| See another member's points or type | No | No | Yes | Yes |
| Rename their own Org | No | Yes | Yes | Yes |
| Run the draft, log attendance, set points | No | No | Yes | Yes |
| Read private notes on members | No | No | Yes | Yes |
| Remove accounts, edit the sign-up form | No | No | Yes | Yes |
| Create chapters, grant roles | No | No | No | Yes |
Org Lead is not a separate account type — it is a member the draft marked as a leader. It carries one power: naming the Org you lead. Everything else about running it still goes through an officer.
The tabs across the top run roughly left to right in the order a semester uses them. Several are officer-only and simply will not appear for members.
Where the chapter is configured and where the roster comes in. Set what a team is called, how the chapter divides, what the ranks are — the whole page adopts your words. Then load the roster from the response sheet, a CSV, or a paste.
Everyone holding an account in this chapter, however they signed in. It fills itself as people join. Click anyone to see their card. This is also where the sign-up form's links live and where its questions are edited.
The Orgs themselves, as cards. Officers run and re-run the draft here and can move people by hand. Members see the teams and who is on them — ordinary chapter knowledge — but not each other's types or points.
One Org at a time, in depth: its roster, its division split, its type composition, its standing in the Cup. This is the page an Org Lead lives on.
Pick the event, check off who showed up, log it. It writes to the same points log as the Cup, so standings move the moment you save.
Two pages behind one dropdown. Standings is what everyone opens it for. What earns points is the scoring catalog — every action, what it is worth, and what kind of thing it is.
Suggested swaps that improve type balance without disturbing anything else, plus per-Org advice. Every proposal trades two people of the same year, division and leader status, so applying one cannot unbalance the draft.
Your page. Your points and where they came from, your sign-up answers, your recognitions, and your own name and picture.
The chapter's own form, filled in without leaving the page. Appears until you have completed it. Your answers are saved to your account as soon as you send it.
Who can do what, which chapters exist on the system, join codes, and every account that has ever signed up.
The draft is not random and it is not a popularity contest. It sorts the chapter into Orgs that are as alike as possible along four axes at once:
If your chapter uses personality types, a fifth axis is added: the sorter tries to avoid an Org that is nine of one type and nothing else. That is what the balance score on the Draft tab measures — lower is better.
These are the flexible pieces, and they are the reason a lopsided chapter can still come out even. If you genuinely do not mind which division you end up in, saying so is more useful than guessing.
Officers can move anyone by hand afterwards. The draft is a starting point, not a verdict.
Every Org accumulates points across the semester. The catalog of what earns them is set by your officers and is meant to be edited — it should describe what your chapter actually does.
Points are grouped by kind, each with its own colour: meetings, competition, service, social, leadership and recruiting. That grouping is what lets you see at a glance that an Org is winning on attendance but has done no service.
An Org with eleven people would beat an Org with nine on raw totals every time, regardless of effort. Ranking on points per member means the Cup measures participation rather than headcount.
The Profile tab is the only page written for you rather than for an officer. It shows:
Another member's type and points are theirs. Officers see them because running the draft and the Cup requires it; other members do not.
What officers actually do, in order.
Set the chapter upName the divisions and ranks under Intake, decide whether you are using personality types, and create the sign-up form. Hand out the join code.
Collect sign-upsMembers join, fill in the form, and appear on the Roster on their own. Chase the people who have not — a partial roster produces a lopsided draft.
Run the draftLoad the roster, pick how many Orgs, run it. Look at the flags, take the Assistant's swaps if they help, hand-adjust anyone with a note. Then tell everyone.
Log attendanceAfter every meeting, workshop and competition. This is the whole job — five minutes an event, and the Cup runs itself. Skip it for three weeks and the standings stop meaning anything.
Hand it overExport a save file and give it to whoever runs the Cup next. Then clear the chapter's data for a new semester — accounts and setup stay, roster and points go.
The browser copy is a convenience, not a backup. It disappears if the cache is cleared or the officer changes laptops. Export a save file at the end of each semester, and do not rely on one person's browser holding the only copy of anything.
Everything lives in your chapter's own Google Sheet, owned by your chapter. There is no separate database and no third party holding your roster.
Chapters are separate from one another: separate roster, separate teams, separate points, separate officers. Nothing crosses between them.
Full detail is in the privacy policy and the terms.