I have, in my downloads folder, sixteen volunteer-hour spreadsheets from sixteen different parent organizations. Catholic K–8s, public elementary PTOs, independent K–12 parents’ associations, a Jewish day school, two charter networks. They are nearly identical.

Tab one is the family roster, surname-first, with a column for “annual hour requirement” that is either 20, 30, or 40 — never anything else. Tab two is the master event log, color-coded by category. Tab three is the running ledger, one row per hour-credit event. Tab four is “buyouts” — the dollar amount families paid in lieu of serving. Tab five is the reconciliation tab, and it is broken.

The reconciliation tab is broken in subtly different ways at every school. But the shape of the breakage is so consistent that you start to suspect something structural. After enough conversations, it became clear: this isn’t sixteen independent spreadsheets. It’s one Platonic spreadsheet, badly approximated sixteen times by sixteen volunteer treasurers who have never met each other.

The Platonic spreadsheet

The work a parent-organization treasurer is doing — when she opens that spreadsheet on a Sunday morning in late April with a cup of coffee and a vague feeling of dread — is reconciliation. Specifically, four-way reconciliation, between:

  1. The roster of families who owe hours. Some are exempt. Some have multiple kids and only owe one set of hours. Some joined mid-year and owe a prorated amount.
  2. The events where hours could be earned. Each with a category, a date, a slot count, and an internally-debated point value.
  3. The actual sign-ups and attendance. Sometimes from SignUpGenius, sometimes from a paper sheet, sometimes from an email thread that has been forwarded twice.
  4. The buyout payments and fundraising credits. Often in a separate Stripe or Square or Venmo log, with the family name spelled differently in each system.

The treasurer’s job, every May, is to merge these four sources into a single statement-per-family that the board can review and the school can countersign. Theoretically, the spreadsheet does this for her. Practically, it doesn’t, because spreadsheets are not databases — they are flat-file simulations of databases — and four-way joins on a flat file held together by VLOOKUP are exactly as fragile as that sentence makes them sound.

Look at any May reconciliation tab and you’ll see structural problems leaking into the spreadsheet — exemptions, prorated requirements, conversion ratios, half-hours that nobody can explain. Every single one of these is a database concept being faked with conditional formatting.

Consider the fundraising committee chair. The committee chair is exempt from the standard hour requirement at this school — but the spreadsheet has no concept of exemption, only a single “required hours” column. So the treasurer types a note in the status cell, in italics, in a slightly different shade of red than the actual conflicts. Next year, the next treasurer won’t know that note exists. The family will get a “you’re 12 hours short” letter. The chair will reply, justifiably annoyed, and the new treasurer will spend a Saturday morning excavating her predecessor’s email archive to find the precedent.

This is the actual problem we’re solving. Not “tracking volunteer hours” — that’s the surface of the problem. The actual problem is that the operating reality of a parent organization has a half-dozen first-class concepts that don’t fit into a flat spreadsheet, and so they get implemented as italicized notes in the wrong color of red, and they don’t survive the annual board turnover.

The first-class concepts the spreadsheet can’t represent

From the sixteen spreadsheets, here are the concepts that consistently show up as italicized notes — meaning every parent organization is independently rediscovering them, and every spreadsheet is independently failing to model them:

1. Exemption with a reason

Committee chairs are often exempt. Board members sometimes are. Families with a recent bereavement, a serious illness, or active military deployment may be exempt for a year or for a quarter. The spreadsheet records this as a note. A real system needs to record the exemption as a typed entity with a reason, an approver, an effective range, and an audit trail.

2. Proration

A family that joins in February doesn’t owe a full year’s hours. A family that withdraws in March shouldn’t be billed for May. Every school has rules for this — usually unwritten, usually different from the rules at the school across town — and the spreadsheet doesn’t represent them at all. The “required hours” column gets manually overwritten, with a note next to it.

3. Conversion between currencies

Most parent organizations let families convert between dollars and hours. The conversion ratio is rarely stable — it might be $30/hour for buyouts but $25/hour-equivalent for fundraising sponsorships, with a different ratio still for in-kind donations. A flat spreadsheet has one column of dollars and one column of hours, and the conversion lives in a comment cell.

Why this matters: The reason every parent organization eventually has the May reconciliation argument is that the rules of the conversion live in the treasurer’s head, and when the treasurer turns over annually — and at most parent organizations she does — the rules turn over with her.

4. Lineage of adjustments

Hours get adjusted. Someone signed up but didn’t show, so they get pulled. Someone showed up unscheduled and put in three hours, so they get added. Someone disputed a missed credit, the dispute was reviewed at the May board meeting, and three hours were added with a note explaining why.

In the spreadsheet, all of these adjustments overwrite the prior value. The audit trail is the email thread. If the spreadsheet is the source of truth, the audit trail is unfindable. If the email thread is the source of truth, the spreadsheet is wrong by construction.

5. Membership scope of an event

Some events earn hours toward the school-wide requirement. Some only earn hours toward a class-specific requirement (e.g., the room parent’s auxiliary program at the lower school). Some earn hours that are restricted to a specific committee’s bylaws. The spreadsheet has one column called “hours” and a comment that says “but only counts toward the carnival committee,” and you can guess how that ages.

Why software hasn’t solved this yet

You might reasonably ask: this is a database problem. Hasn’t somebody built the database?

The answer is: yes, kind of, and not exactly. There are tools that handle volunteer scheduling (SignUpGenius, MobileServe), tools that handle fundraising (DonorPerfect, Givebutter), and tools that handle parent communication (Konstella, Parent Square). Each one has a notion of “hours” or “points” or “contributions” — but only inside its own bounded context. The reconciliation problem the treasurer faces in May is precisely the problem of stitching those bounded contexts together, and that’s what the spreadsheet is for.

So she keeps the spreadsheet. The spreadsheet keeps having the same five problems. Every May, she reconciles by hand. In June, she sends out the year-end statements, fields the disputes, and updates her notes. In July, her term ends, and she hands the spreadsheet to her successor.

“I told the board I’d do one year as treasurer. That was three years ago. I keep saying I’ll hand it off but I can’t find anyone who will inherit the spreadsheet.” — PTO treasurer at a 380-family Catholic K–8, in our discovery interviews

What the right shape of solution looks like

If you accept that the underlying object is a commitment ledger — a typed, append-only record of obligations and credits between families and the parent organization — then the right shape of the solution drops out almost mechanically.

The ledger needs:

  • Typed entries, not free-text. Each entry is one of: requirement, credit (volunteer-attended), credit (buyout), credit (fundraising), exemption, adjustment.
  • Lineage. Adjustments don’t overwrite prior entries; they supersede them. The prior entry is preserved in superseded state with a pointer to its replacement.
  • Reasons. Every adjustment, exemption, and conversion has a structured reason field — not free-text — so the next treasurer can read the why without an archaeology project.
  • Scope. Each entry is scoped to a specific commitment program (school-wide, committee, class), so a single family can have multiple parallel ledgers without the rules getting tangled.
  • Conversion as policy, not arithmetic. The dollars-to-hours ratio is stored as a versioned policy, not hard-coded into a cell formula. Change the ratio mid-year? The change is dated. Old entries keep their old conversion. The audit holds.

None of this is conceptually hard. What’s hard — what’s apparently been hard enough that nobody has done it for the parent-organization market — is taking it seriously enough to actually build it. The volunteer-organization software market is dominated by tools designed for nonprofits, where the assumption is that you have a paid executive director, a development office, and a CRM. Parent organizations have none of those. They have a treasurer with a day job and a spreadsheet.

The handoff problem

The other piece — and this is the piece that’s harder to convey to people building “tracking software” — is that the system has to survive a complete leadership turnover every year. Most software is built on the assumption that the people configuring it have continuity. Parent-org software cannot make that assumption.

Concretely, this means:

  • The configuration of the commitment program (rates, deadlines, exemption rules) needs to be visible and editable in the product, not buried in the implementation team’s email.
  • Audit trails need to be human-readable by the next treasurer, not just by an auditor.
  • Onboarding documentation needs to assume the reader has never seen the product before, because every July she hasn’t.

A lot of products say things like “easy onboarding” or “intuitive UX.” For parent-org software, this is not a marketing claim — it is a structural requirement. If the new treasurer can’t run the system on day one, the system gets abandoned by August.

What we’re building

Lumicura’s Commitment dashboard is the most visible artifact of all of this. Underneath, it’s a typed append-only ledger with all of the properties above. Above it, it looks like the spreadsheet — because the spreadsheet’s shape has been honed by sixteen treasurers, and the shape they converged on is, to a first approximation, correct.

What’s different is what happens at the edges. When a buyout comes in via Stripe, it lands in the ledger. When a volunteer event closes, attendance auto-credits the ledger. When the treasurer needs to mark a committee chair exempt, that exemption is a typed entry with an effective range, and next year’s treasurer sees it before she sends the “you’re 12 hours short” letter.

The May reconciliation panic is not solved by a better spreadsheet. It’s solved by recognizing that the spreadsheet was never the right tool — that the underlying object is a ledger, and that the year-end statement is a derived view, not a hand-stitched artifact. We’ve spent the last six months building exactly that, and the early signal from our pilot schools is what we hoped: the May meeting is just shorter.

If you’re a parent-org treasurer reading this with a spreadsheet open in another tab — we’d genuinely like to talk to you. Not as a sales call. As a discovery conversation. We’ve done twenty-two of these now and each one has shifted what we’re building. Email hello@lumicura.com.

Filed under: Commitment programs. If you'd like one of these in your inbox monthly, subscribe to Field notes.