Hours with an event behind them.
Every service org eventually has to produce the same number, for a national office, a scholarship, an honor requirement or a re-registration form. It's also the number most likely to be wrong, because it usually lives in a spreadsheet somebody types into at the end of the term. Here it's summed from participation, and the evidence stays attached.
A month of projects, and what carries each part
Service orgs run on two loops at once: getting bodies to a Saturday build, and keeping a defensible record of who was there.
Every project
Who showed, and for how long
Participation is recorded against the event. A member's hours total is the sum of those records — you never edit the total directly, which is exactly why it can be trusted later.
Every month
The member who's sure they did more
Open their record and the events are right there with dates. The conversation stops being about memory and starts being about a list.
Recruiting for Saturday
Getting the ask in front of people
A pinned announcement sits at the top of everyone's dashboard, and tasks can be assigned to a role rather than a person — so the Service chair's list follows the seat when it changes hands.
Fundraisers
Money in, money out, and who's asking
Income and expenses on one ledger with the term's budget beside it, exportable to CSV when your advisor or your national wants the books.
Three weeks before the deadline
Who is going to miss the requirement
The hours goal has an at-risk band under it, so the people who need one more Saturday show up in the attention queue while there are still Saturdays left.
What it builds you
The service template keeps almost everything and drops parties. It's the widest of the six because these orgs genuinely run meetings, projects, money and comms at the same time.
Hours are a consequence, not a column
Because the total is derived from participation records, it can't drift from reality and it can't be nudged. If someone questions a number, the answer is a list of events, not an argument.
A goal, and a band under it
Set the hours goal for the term and the roster flags who's short automatically. The same threshold drives the dashboard's attention queue, so the two never disagree about who needs a nudge.
The chair's work follows the seat
Tasks assigned to a role resolve to whoever holds it at the time you look. Hand the Service chair role to someone new and the open items go with it — you don't reassign twelve tasks by hand.
Pages
Parties is the only page off by default, and it stays one toggle away.
Words your org uses
The only rename the template ships. Everything else already reads correctly for a volunteer org.
Seats
Tracked per member
GPA is off — a service org rarely gates membership on it, and an unused column that holds a grade is a liability rather than a feature.
Timeline categories
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 it signed out
At /create, name service events, fundraising and dues as things that happen in a normal month. Anything you leave unnamed stays off.
Open the term, then set the hours goal
The goal is the number the whole page is organized around. Set it in Settings before the first project rather than at the end when it decides who failed.
Seed the roster and invite
Names first, then one link with an expiry. Every redemption is recorded, so you can see exactly who joined through which link and when.
Log your first project the same week it happens
Not at the end of term. The record is only worth what its timeliness is worth, and a month-old memory of who came is the thing this replaces.
Export the ledger once, early
So you know what your treasurer will hand over in April, and so nobody discovers the format the week the report is due.
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 hours with three weeks left?
Compares each member's summed participation against the goal you set.
Ask Chapt ⌘K
how many hours did we log at the food bank this term?
Totals the participation records for those events, not a hand-kept tally.
Ask Chapt ⌘K
what did the fall fundraiser actually net?
Income minus expenses off the ledger, with the rows it used.
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 supervisor sign-off
Hours are recorded by an officer. Nothing here is counter-signed by the site lead, and there's no signature field. If your national requires one, this isn't that.
The hours report isn't a button yet
The roster and the ledger export to CSV from the app. A per-member hours export is a request to us today — we'll produce it, but it isn't self-service.
Nothing syncs outward
No integration with a national office's portal, a scholarship system, or a campus service-hour tracker. What leaves here leaves as a CSV you send.
It doesn't email volunteers
There's no mail-sending capability at all. Announcements are pinned inside the app; getting people to read them is still your job.
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.