Event photo sharing for a birthday, not a wedding

Almost everything written about collecting photographs from a party assumes a wedding, and a wedding is the unusual case. It has a hundred guests, a paid photographer, a printed stationery budget and somebody with a microphone.

A sixtieth in a restaurant has none of that, and it has the same problem. Forty people take four hundred photographs, six of them arrive in a group chat, and the person the party was for sees almost nothing. The arithmetic behind that number is the same at any size of party. Below is what actually differs.

What event photo sharing changes at a birthday

Three things, and only one of them is a complication.

There is usually no photographer, which means the guest photographs are not a supplement to a professional set. They are the entire record. That raises the stakes and it also lowers the standard, because nobody is comparing them to anything. Blurred is fine. Blurred is all there is.

The event is often a surprise, or at least the person it is for is not organising it. So the person collecting is not the person the photographs are for, and the natural moment to hand them over is a few days later rather than the same night. That works in your favour. There is no rush and the gallery is a better present than a chat thread.

And it is smaller, which is the only genuine complication, because a smaller party is more forgiving of a bad system and so nobody builds one. At forty people you can plausibly chase everybody individually. You will not, and the photographs will scatter across four apps in three resolutions, which is exactly what happens.

The card is still the whole difference

The mechanism that works at a wedding works here for the same reason. A code on a table beats asking people, because asking people requires you to be near them at the moment they are willing to act.

What changes is the design, and it changes more than you would expect. A card set in wedding stationery on a table at a fortieth reads as somebody else's event. Melora asks which kind of event it is when you create one, and the answer picks the card you are shown first: rings for a wedding, balloons for a birthday, sparks for a party, a plain rule for anything corporate. The code itself is identical in every one of them and stays near-black on near-white, because that part is machine-readable and has one job.

For a restaurant party you usually need fewer cards than a wedding. One per table is still right, but there are four tables rather than fourteen, and a single sheet of four cards printed at home covers most sixtieths entirely.

Where the wedding advice stops applying

Four pieces of standard wedding guidance are wrong at a smaller event.

• Say it during the speeches. There are often no speeches. The equivalent is the moment the cake arrives, which is the one point in the evening where everybody is looking at the same thing and quiet.
• Print a card per table. At a house party there are no tables. Put one on the kitchen counter and one wherever the drinks are, which are the two places every guest visits.
• Turn on approval so nothing embarrassing appears. At a wedding that queue is worth the effort. At a birthday the photographs are going to one person who will look at all of them anyway, and a queue just means nobody sees anything during the party.
• Buy the storage for video. A wedding with a band produces video. A dinner for twenty mostly does not, and the free tier is genuinely enough for an evening of photographs from a small group.

The last one is worth being specific about. The free tier here is twenty megabytes and never expires, which is a handful of photographs rather than an evening. It is sized to let you see the whole thing working before you decide, not to run a party on.

A company party is a different animal

Everything above assumes people who know each other. An office event has two constraints a birthday does not, and both are about consent rather than logistics.

The first is that not everybody at a work event wants to be photographed, and unlike at a wedding they may not feel able to say so. Approval before anything appears is the right default here for exactly the reason it is the wrong one at a birthday. Say in advance that the gallery exists and that anybody can ask for a photograph to be removed.

The second is that a gallery of a company party is not a marketing asset by default, and treating it as one after the fact is how people end up on a careers page without being asked. Decide which it is before you print the card, and say which it is on the card.

What to do first

Set it up a week early rather than the day before. Not because it takes long, it takes about five minutes, but because printing at home always turns out to be a twenty-minute job at eleven at night and it is better done on a Tuesday.

Then leave the upload window open well past the event. The people who send the most photographs are the ones who do it the next morning, sitting down, going through what they took. The plans and what each window is are worth reading before you pick, and the step by step is here.

The rest of the advice on this blog is written about weddings and translates directly. Where to put the card is the one to read next, because placement is the whole game at any size of party.