Activity rosters
A participant list with a season attached, maintained by the person who knows
It is a smaller idea than it sounds and it does most of the work on this site. A roster that knows when as well as who is what turns a folder of images into a record, and it is the difference between captioning a sport page and reconstructing one.
What an activity roster actually holds
- An activity. A team, a production, a club, a trip. It is a thing with a name that a school already recognises, not a folder somebody created.
- A season. The period the membership applies to. Without this a roster is a snapshot of now, and an image from three months ago has nothing correct to resolve against.
- A membership held over time. Who joined, who left, and when — not a list that is edited until it is right today.
- A link to the student record. Which is where the permission state lives, and which is why nothing on this page needs a permission of its own.
None of those four is a photography feature. That is deliberate: the imagery benefit is a consequence of the school keeping a decent record of its own activities, which it usually wants for a dozen other reasons anyway.
Three consequences worth spelling out
These are the things that stop being somebody’s job. Each reads as a small convenience and each is the difference between a record that holds and one that holds until the coach changes.
A season is not a date range somebody typed. It is the thing that makes “who was on this team” a question with an answer, and it is why an image taken in November resolves against November’s membership rather than today’s. Without it, every roster is a snapshot of the present pretending to be a record of the past.
Membership is held over time, not overwritten. When a student joins in October and leaves in February, both facts are held. The alternative — a list that is simply edited — means the November photographs quietly become unattributable the moment somebody leaves the club.
Permission is resolved at use, not at capture. The membership tells you who was there. The permission state tells you what may be done about it now. Keeping those separate is what allows a family to change its mind in March about a photograph taken in November without anybody having to rewrite history.
A roster against a folder, as arrangements
This compares two ways of ending up with the same photographs, not two products. The left column is what a school has by default, because it is what happens when nobody decides anything.
| The question in May | A folder per team | Held on the activity roster |
|---|---|---|
| Who is in this photograph? | Somebody remembers, or nobody does | The season's membership at the time |
| A student left mid-season. Now what? | The folder is still named for the team | Membership held over time; images still resolve |
| May this be published? | A separate question nobody can answer from a folder | Per-student state, resolved at the point of use |
| Who can update the list? | Whoever has the drive | The person running the activity |
| What happens at the end of the year? | The folder stays, unowned, indefinitely | The season closes and the record stays attached to it |
The season boundary, which is where this usually breaks
Almost every system that gets activity photography wrong gets it wrong at a boundary. A season ends and the roster is edited for next year; an image from March now resolves against a list that describes September. Nobody did anything careless, and the record is gone.
Holding membership over time rather than overwriting it is the fix, and it is unglamorous enough that it usually loses to a simpler data model. The cost of the simpler model is not visible in the first year, which is precisely why it wins the argument and then fails in the third.
The same reasoning applies to an activity that changes shape: a team that merges with another, a club that renames itself, a production that is remounted. The activity is the continuing thing and the season is the instance; keeping them distinct means a rename does not orphan four years of photographs.
Questions about rosters
Is an activity roster the same thing as a class roster?
No, and conflating them is the usual mistake. A class roster is stable for a year and is maintained by the office. An activity roster changes mid-season, is maintained by a coach or a director, and frequently includes students from several year groups at once. They share a student list underneath; they are different memberships over it.
What happens to images when a student joins or leaves mid-season?
Images resolve against the membership at the time they were taken rather than the membership now. A student who left in February is still in the November photographs, because that is a fact about November. What changes with them is the permission state, which is resolved at the point of use rather than frozen at capture.
Who maintains these lists?
Whoever runs the activity, which is the point. A roster that only the office can edit is a roster that is wrong for most of the season, because the person who knows a student stopped coming is the coach, not the office.
Does an image have to belong to exactly one activity?
No. A photograph from a combined event can be held against more than one activity, and it resolves against each of their memberships. Forcing a single owner is how images from anything cross-programme end up in a personal folder instead.
Who is usually holding the camera, and what that implies, is on volunteers. What the school may actually do with the result is on what may be posted.