Athon Management · the event-day operations layer
It is 8am. The course is taped, the water table is half set up, and forty parents are standing in the middle of the gym waiting to be told what to do. The pledges are handled somewhere else. The projector is somebody else’s job. What is missing is the clipboard: the run of show, the count, and the board that says which volunteer stands where. Athon Management is that clipboard — the operations layer of the athon family, built for the person actually running the event on the day it happens.
This is the operations home — the clipboard, the counter, and the board. It is not the money (that is athon.software) and it is not the screen in the gym (that is tv.athon.software). Where those siblings do the work, this page says so plainly and does not claim it here.
3
instruments on one clipboard — the run of show, the unit counter, and the station board
1
seam to the money — a count is handed off to athon.software, and nothing else crosses that line
0
dollars moved and 0 minors named on this surface — the counter is a tally, not a charge, and the board holds volunteers, not children
Every number above is a structural fact about what this surface is and refuses, not a claim about how many schools use it. No operations backend is provisioned at this address today; the instruments below are the blueprint being built.
What is on the clipboard
An a-thon on event day is three jobs that people usually cobble together from a paper printout, a stack of clickers, and a group text. Athon Management is those three jobs as one instrument, built for the person holding the clipboard. Each is described below as the blueprint being built.
Instrument 1
The minute-by-minute plan for the day: wave stagger, who blows the whistle, when counters hand off, and what happens if the weather calls a hold. One page the whole team reads from, so nobody is improvising at lap fourteen.
Instrument 2
The tally instrument. One tap is one unit — a lap, a minute read, a book, a mile, or the unit the school names — with a double-count guard at the hand-off and per-lane totals that reconcile against each other.
Instrument 3
Who stands where. Stations, captains, check-in, and a backfill role for the no-show that always happens. It shows a coverage gap before it becomes a station with no adult at it — and it holds volunteers, never a child’s record.
Instrument 1 · the run of show Blueprint
A run of show is not a wish. It is the ordered list of what happens, when, and who is responsible — the thing you read out at the volunteer huddle so the day runs itself instead of running you. Below is a worked morning jog-a-thon, shown as the shape the clipboard is being built to hold. The times are relative to the first wave, not a promise about any one school’s schedule.
Station leads arrive, radios go out, and each lead walks their station before a single student is on the course. The clipboard holds the who-is-where so a lead who is running late shows as a coverage gap on the board, not a surprise at the whistle.
The captains read the day back to the volunteers: which wave counts on which lane, where the water is, who calls a heat hold, and the two call signs everyone uses on the radio. One page, read out loud, so nobody is improvising at lap fourteen.
The first grade band steps off. Counters stand at the lap line; each completed lap is a tap. Waves are staggered so a single lane is never counting two grade bands at once — the schedule stagger is the thing that keeps a tally honest under a crowd.
A counter who has stood at the line for twenty-five minutes hands the count to a fresh volunteer. The hand-off is the moment a tally is most often dropped or double-added, so it is a named step with a named procedure, not an ad-hoc swap.
The final band finishes, counters freeze their totals, and the station board flips each lane to closed. Nothing reopens a closed lane without a lead marking why — a reopened lane is exactly how a double-count gets in after the fact.
The frozen per-lane totals are reconciled against each other and handed to the pledge side. athon.management stops at the count; what the count becomes in dollars is athon.software's job, on athon.software's own timeline and status.
Two things make a run of show hold up under a crowd: the wave stagger that keeps one lane from counting two grade bands at once, and the named hand-off at the half. Both are in the blueprint because both are where a real event-day tally comes apart. Contingency lives here too — a heat hold or a rain call is a named branch with a named caller on the radio, not a decision made in a panic at the water table.
Instrument 2 · the unit counter Blueprint
The count is the whole event. It is the number a pledge resolves against, the number on the projector, the number a school reports at the end. Get it wrong and every dollar downstream is wrong. So the counter is being built around one idea: a tally is only as good as its weakest moment, and its weakest moments are known — the hand-off and the reopened lane. The counter is designed to make those moments loud, not silent.
A lap in a fun run, a minute in a read-a-thon, a book, a mile, or a unit the school names. The counter is built to speak the same unit vocabulary the rest of the family uses, so a count means the same thing on the clipboard, on the projector, and on the pledge side.
A tally is most fragile at a counter hand-off and at a lane that closed and reopened. The instrument is being built to make both a named, logged step: a hand-off transfers a running total to a named volunteer, and a reopened lane records who reopened it and why, so an extra count cannot slip in silently after a lane was closed.
Each lane holds its own running total. At the end, the lane totals are reconciled — they are meant to sum to the event total, and a lane that does not close cleanly is flagged for a lead rather than folded into a headline that hides it. The count is enumerated per lane, not reconciled from a single total that one busy lane can distort.
The counter produces one thing: how many units each participant completed. It does not know a pledge rate and it does not move a dollar. Turning a count into an amount is athon.software’s job, and it happens after the count is handed off — the boundary is deliberate, so an event-day tally can never accidentally trigger a charge.
The boundary is the important part. The counter produces a count and stops. It does not know a pledge rate, and it does not move money — money is honest-off across the platform, and turning a count into an amount is athon.software’s job, after the count is handed off. That seam is deliberate: an event-day tally can never accidentally trigger a charge, because the tally and the charge live on two different surfaces with a hand-off between them.
Instrument 3 · the station & volunteer board Blueprint
On event day the question is never whether a volunteer drops — it is who covers. The station board is being built to answer that before it becomes a problem: every station, every captain, every coverage gap in one view, with a backfill role that exists precisely because the no-show always happens. The roles below are how the board is organized. Each role sees what it needs and nothing more.
Event chair
Holds the whole board: every station, every captain, every coverage gap in one view. The chair is the person the run-of-show is written for, and the board is built to show them a gap before it becomes a station with no adult standing at it.
Station lead
Owns one station — the lap line, the water table, the check-in tent, the finish. A lead checks their volunteers in, calls a gap up to the chair, and marks their station open or closed. A lead sees their own station in full and the board’s call signs, not a roster of children.
Lap counter
Stands at the line and taps. A counter is assigned to a lane and a wave, is handed a fresh count at the half, and hands theirs off in turn. The board tracks which counter holds which lane so a hand-off is to a named person, not to whoever happened to be standing there.
Floater / backfill
Unassigned on purpose. When a lead calls a gap — a no-show, a counter who had to step away — the board is built to surface the nearest floater to fill it. A backfill is a planned role, because on event day the question is never whether someone drops, only who covers.
The board operates on volunteers, stations, lanes, and group totals — never on a child’s individual record. A lead sees their station and the radio call signs, not a roster of students. Where the wider platform’s consent-gated roster is involved at all, that is an existing platform capability behind its own privacy wall — not a new thing this page exposes, and not something a volunteer sees.
Where this sits in the athon family
The athon family is deliberately split so no one surface tries to be everything. The money, the operations, the broadcast, and the gear are four different jobs for four different people, and they meet at named seams rather than blurring into one tool that does all of them badly. Athon Management owns the operations. It hands a count to the money and, once built, a running total to the broadcast — and it stays out of both.
The pledge and payout engine: promise-per-unit, the exact amount a donor sees before any charge, the FLOOR that keeps the school whole. Athon Management hands it a count; what the count becomes in dollars is athon.software’s job, on its own timeline and its own honest status.
This surface: the run-of-show clipboard, the unit counter, and the station board. The two hours in the gym. It produces a count and a plan — it does not move money and it is not the screen on the wall.
The gym-facing leaderboard and goal thermometer — the thing on the projector that the whole gym watches. A separate, already-built surface with its own timeline. Athon Management is the staff clipboard behind it, not the screen itself.
The event-gear catalog — participant shirts, finisher medals, spirit gear. What a school orders around the event, browsed and quoted on its own sibling surface. Money is honest-off there too.
What is built and what is a blueprint
Athon Management is a blueprint today. The three instruments on this page are described so an event chair can see the shape of what is being built — they are not tools that record a live event right now, and nothing on this page stores event data or moves a dollar. We name each piece where it actually stands: blueprint, honest-off, or a sibling’s surface. We never present a planned piece as if it shipped, and we never borrow a sibling’s built capability and wear it as our own.
The ordered day, the wave stagger, the named hand-offs, and the contingency branches are designed. No backend records or runs a live run of show at this address today.
The tally instrument — one tap per unit, the double-count guard, per-lane reconciliation — is designed. It does not record a live event today, and it never touches money.
The stations, captains, check-in, and backfill logic are designed. No backend tracks a live roster of volunteers at this address today.
Money is honest-off across the platform. No price, no checkout, and no charge runs from this page. The counter is a tally, not a charge.
Not this surface. The pledge engine is athon.software, and it carries its own honest status (its a-thon execution surface is early access). This page does not claim it as its own or as live here.
Not this surface. The projector is a separate built surface with its own timeline. The pipe that would feed it a count from the counter is part of what Athon Management is being built to provide and does not carry live data today.
Straight answers
athon.software is the pledge and payout engine — the promise-per-unit, the exact amount a donor sees, the money. athon.management is the operations layer for the day the event runs: the run-of-show clipboard, the lap / unit counter, and the station and volunteer board. One is the money and the weeks around it; the other is the two hours in the gym. They meet at exactly one seam: athon.management hands off a count, athon.software turns it into an amount.
No. There is no operations backend provisioned at this address today. The run-of-show, the counter, and the station board on this page are the blueprint of what is being built — described so an event chair can see the shape of it — not tools that record a live event right now. Nothing on this page stores event data or moves money.
No. The counter produces one thing: how many units each participant completed. It does not know a pledge rate and it does not move a dollar. Money is honest-off across the platform, and turning a count into an amount is athon.software’s job on its own timeline — the boundary is deliberate so an event-day tally can never trigger a charge.
The gym-facing leaderboard and goal thermometer are tv.athon.software, a separate surface with its own timeline. athon.management is the staff clipboard, not the thing on the screen. The pipe that would feed a running count from the counter to that projector is part of what athon.management is being built to provide; it does not carry live data at this address today.
No. The station board and the counter work on volunteers, stations, lanes, and group totals — not on a child’s record. A minor is never named, pictured, or listed individually on this surface. Where the wider platform’s consent-gated roster is involved, that is an existing platform capability behind its own privacy wall, not something this page exposes.
A hand-off is the moment a tally is most often dropped or double-added, so it is a named step, not an ad-hoc swap. The instrument is being built so a counter who has stood at the line transfers a running total to a named fresh volunteer, and the board records the hand-off — who held the lane and who holds it now — so a count is never orphaned mid-event.
Yes, by design. The unit is the school’s word — a lap, a minute read, a book, a mile, a problem, or a unit the school names — and the counter, the run-of-show, and the board are built to speak whichever unit the event uses. The operations shape is the same whether students are running laps or logging minutes.
Email [email protected] — a person reads it and replies. Nothing on this page is automated, and there is no sign-up that provisions anything today. Tell us the event you are running and we will tell you honestly where the operations layer stands.
Tell us the event — the grade bands, the unit, the volunteers you expect — and we will tell you honestly where the operations layer stands and how it would fit your day. A person reads it and replies. Nothing on this page provisions anything or takes a payment.