Dues, attendance, hours and standing — in one record the next exec inherits.
A chapter carries more operational load than any other org on campus: a meeting every week with a roll behind it, a hundred dues balances, service requirements that decide standing, parties with money at the door, and an exec board that turns over every year. This is the shape it starts in.
A month in the chapter, and what carries each part of it
Nothing below is a feature list — it's the five things that actually recur, in the order they hit, and the surface that already handles each one.
Every week
Chapter, and the roll behind it
Take attendance on the meeting itself. Percentages are computed from those records rather than typed anywhere, and they feed standing directly. Minutes get an AI summary with the decisions and action items pulled out of them.
First two weeks
Dues go out, and then the chasing starts
Every member carries a balance. A payment is a request a treasurer approves, and the balance and the ledger entry move together or neither moves — so "did she pay?" and "is it in the books?" can never disagree.
All semester
Service hours nobody wrote down
Hours are summed from who actually showed at each service event. A member's total always has an event list behind it, which is the difference between a number you can defend and a spreadsheet cell.
Two or three weekends
A party with cash at the door
Parties carry their own door revenue, expenses and wrap-up notes, on the same books as everything else — so the social budget isn't a second, private ledger in someone's Notes app.
Every spring
Turnover
Seats are roles, not logins. Reassign Treasurer and the whole record — every transaction, approval and roll — stays exactly where it is, with the old treasurer's name still on what they did.
What it builds you, before you invite anyone
The interview asks what your chapter does in a normal month and drafts this sheet from the answers. Every line is editable here, and again in Settings next semester when the chapter has changed its mind.
Standing is computed, not decided
On track / watch / at risk falls out of the four measures against thresholds you control. Move the attendance floor and every badge in the chapter moves with it — nobody is flagged because an officer felt like flagging them.
The books can't be quietly rewritten
Deleting a ledger entry marks it deleted and keeps the history, and removing someone from the roster never erases the record that they paid. An audit finds the correction, not a hole.
Rank stops a chair promoting themselves
An officer can only grant or edit roles ranked strictly below their own. The Social chair can hand out a committee seat; they cannot make themselves Treasurer.
Pages
Tasks and Announcements start off on purpose — the chapter group chat already does both, and a page nobody opens is worse than no page. Both are one toggle in Settings the week exec outgrows the chat.
Words your org uses
A sorority gets the same template with Sister instead of Brother.
Seats
Tracked per member
All four, because a chapter's standing rules usually reference all four. Each carries its own threshold — 70% attendance, a 2.5 GPA floor, an hours goal — and those are yours to set.
Timeline categories
Seeded editable, alongside the built-in Chapter, Party, Service and Deadline types.
First term
Fall 2026 · Aug 24 – Dec 18
Every line is editable on this sheet before anything is built — and again in Settings next term, when the org has changed its mind.
Do these five things, in this order.
Each one is cheap now and expensive later — that's the whole reason they're in this order.
Build the whole thing signed out
The interview at /create runs before you have an account — describe the chapter, edit the sheet, then sign in with Google at the last step. Your answers survive the round trip.
Open the semester first
Nothing works without an active term, and the first screen after creation says so. Confirm the dates the interview suggested; attendance, dues and budgets all hang off that record.
Seed the roster, then send one invite link
Paste the names in first so people claim their own row. Set the link to expire, revoke it after rush, and check the redemption list — an invite link is a door code, and anyone holding it can get in until it dies.
Set your thresholds before the first roll, not after
Attendance floors, the GPA cutoffs, the service-hours goal. Set them while nobody is failing them yet and the standing badges will never look political.
Take one real roll and post one real dues charge
The dashboard is honest about having no data. One meeting and one dues cycle is the point where the health dial, the KPI strip and the attention queue start telling you something you didn't already know.
Three questions an org like yours actually types.
The assistant reads your real records and cites the rows it used. It drafts changes; a person with the right seat is what makes one happen.
Ask Chapt ⌘K
who's short on service hours with three weeks left?
Reads the participation records behind each event — not a column somebody typed.
Ask Chapt ⌘K
who owes more than $100 in dues?
Named rows with balances, and every figure links back to the record it came from.
Ask Chapt ⌘K
what did we decide about formal at chapter last week?
Meeting notes are part of the record; the summary is the part with the action items.
Every draft is checked against your own seat before you see it. Without the permission the card is blocked rather than routed onward — and it names who does hold that authority.
What it won't do for you.
The section worth reading twice. Everything below is a real limit today, not a roadmap item dressed up as one — you should find this out here rather than in week three.
No payments, ever
Dues are records of money that moved through Venmo, cash or a check. There's no processor integrated, no card details anywhere, and nobody pays through this.
Polls are not secret ballots
Every vote records who cast it. That's fine for picking a formal venue. It is the wrong tool for bids, for judicial, or for anything a member would expect to be anonymous.
GPA is typed in by you
No registrar, no student information system, no integration that could. Read what not to put here before you add anything else sensitive as a custom field.
It doesn't message anybody
There is no mail-sending capability in the product. Announcements are a page inside the app; your group chat is still your group chat.
Removing a member with history needs us
The attendance records that depend on them block the delete, deliberately, so history can't be silently destroyed. Ask and we'll complete it by hand and tell you what was kept.
Not sure this fits your org?
Describe what you run in a normal month and we'll tell you plainly whether this is the right tool — including when it isn't. One person reads these, and they'd rather say no early.