The Wave Effect: Why a Past Event's Photos Get Shared All at Once
TIME&SPACE · Business of Events
A live event's photos trickle in as guests scan all day. A past gallery's whole guest list learns at once, so claims and shares compress into 48 hours.
The Wave Effect: Why a Past Event's Photos Get Shared All at Once
In short: A live event's photos get claimed the way the event itself unfolds, a scan here, a scan there, spread across the day and the days after. A gallery built from an event that already happened does not have that rhythm, because there is no event still running to spread the news for you. Everyone on the guest list learns about it at the same moment, so claiming and sharing compress into the first 48 hours instead of trickling out over a week.
TIME&SPACE indexes photos from an event that already happened the same way it indexes a live upload: face recognition does not know or care how old a photo is. What is different is not the technology. It is the shape of what happens once that gallery goes live.
Why a live event trickles
At a live event, guests find out about photo delivery in staggered ways, a QR code on a screen someone notices an hour in, a friend who scanned already and mentions it, a sign at the exit on the way out. Claims spread across the whole event and into the following day or two, because the audience is discovering the gallery exists at different moments, not all together.
Why a past gallery does not
A gallery built from an old photo set has no event left to carry that word of mouth. The only way the guest list finds out is the organiser telling them, usually one email and one post, sent on the same day. There is no staggered discovery because there is nothing left to stagger it. Everybody who is going to find out, finds out within the same hour or two.
The shape it actually takes
That single moment of telling produces a predictable pattern rather than a flat response. Claims peak around the first day after the notification goes out. Sharing, people posting what they found rather than just opening it, peaks a day after that. From there the response tapers into a longer, quieter tail that runs for roughly two weeks as the notification gets forwarded, reposted, or opened late by someone who missed the first message. The bulk of it, though, happens in that first 48 hours.
What this means for timing the notification
Because the response is triggered by a single message rather than by an ongoing event, when and how that message goes out matters more than it would for a live gallery. Send it once the whole set has finished processing, not in batches, so nobody on the list claims early and tells people the gallery is only half ready. Send it across every channel you intend to use on the same day, the email and the social post together, rather than staggering them to spread out the work, because staggering the message is what flattens the wave that makes it work in the first place. And send it while the event is still something people remember clearly enough to want to see themselves in it again.
Where this fits
This applies to the past-gallery offer specifically: uploading the existing photo set from an event that already happened, at 50% off any standard plan, with the same 365-day guest access as a live event. A live event's photos are still worth getting into a recap email and a content calendar in the weeks after, which is a different kind of marketing work with a longer timeline of its own. A past gallery's first notification is the one moment that does most of the work, and it only happens once.
Founder, TIME&SPACE