Photo Delivery for University and Student Events
TIME&SPACE · Organiser's Playbook
Universities run more events per year than almost any other organisation and deliver photographs worse than almost any other, mostly because the team changes every June.
Photo Delivery for University and Student Events
In short: The hard part is not any single event, it is that the people running them turn over completely every year. Whatever you set up has to survive a committee that has never met the last one.
A university runs an extraordinary number of events. Welcome week, society nights, sports fixtures, balls, conferences, graduation, open days. More events per year than most festivals, spread across dozens of small teams.
The photographs are usually taken. They are rarely delivered well, and the reasons are structural rather than anyone's fault.
The turnover problem
The society committee that ran last year's ball has graduated. The new one inherits a Facebook page they cannot log into, a Google Drive owned by someone who left, and no idea where last year's photographs went.
This is the defining constraint. Any system that depends on institutional memory will fail within twelve months, because there is no institutional memory.
What survives turnover:
- Accounts owned by the institution, not by a person. A society email address rather than a student's personal one.
- One documented place things go. Written down somewhere the next committee will actually be handed.
- A process short enough to explain in one message. If handover takes an hour of explanation, it will not happen.
Consent is not simpler because they are students
There is a tendency to treat student events as informal. The obligations are the same.
Two things make this sharper rather than softer. Some attendees are under eighteen, particularly at open days and welcome events, which changes what you can do. And students are a population who will, quite reasonably, care a lot in five years about what is publicly findable from their first year.
The practical position: keep galleries unlisted rather than publicly indexed unless there is a specific reason, get explicit consent for face processing separately from a general photography notice, and make removal genuinely easy. The GDPR guide for organisers covers the shape of it.
Graduation is a different job
Everything above assumes a social event. Graduation is not one.
The photographs matter more, to more people, for longer. Families who were not there want them. They will be looked at in twenty years. Getting them right is worth a different level of care than a society night.
The practical difference is findability. A graduation gallery of three thousand photographs where families cannot locate their own person is a failure regardless of how good the photography was. The specifics are in graduation photo delivery for schools.
What actually works across the year
One system for every society, not one per society. Fifteen committees each choosing their own approach produces fifteen dead Google Drives. A single route that the union or the institution provides survives.
Deliver during the event where possible. Students share immediately or not at all. Photographs that arrive on Thursday from a Saturday event have missed their entire window.
Assume phones and bad wifi. Campus venues are basements and sports halls. Whatever the delivery mechanism is, it has to work on a poor connection.
Keep the address stable. The same link works next year for the next committee, which is the single biggest handover win available.
The short version
The problem is not photography, it is continuity. Build for a team that changes annually: institution-owned accounts, one route rather than fifteen, a process explainable in a message, and a stable address. Then treat graduation as a separate and more serious job than everything else on the calendar.
Founder, TIME&SPACE