How to collect photos from a company offsite (without a WhatsApp group)

By Andrew Tjong · Published 13 August 2026 · Updated 13 August 2026

You planned the offsite, everyone took photos, and three weeks later you have eleven of them in a WhatsApp group. The fix is structural: photos have to flow into one album while they are being taken, not be collected afterwards. Here is what goes wrong with the usual methods, and a playbook that gets you every photo in one album by the bus ride home.

Why the usual methods fail

The WhatsApp group

The default, and the worst of the three. WhatsApp compresses images by default, so what you collect are degraded copies of the originals. People take 40 photos and share 3, usually the ones they look good in; the other 37 die on their phones. The "album" is a chat scroll: to keep anything you export it phone by phone, and whoever missed the group never sees any of it.

And there is zero control. You cannot remove an unflattering photo from thirty camera rolls, and if HR ever needs a photo taken down, there is no mechanism at all. For EU companies that is also a genuine data protection problem, not just an awkward one.

The shared drive folder

Google Drive, SharePoint, Dropbox: better storage, worse collection. The folder link goes out in a follow-up email, and uploading requires people to find the link, sign in, sometimes request access, then batch-upload from a phone gallery through an interface designed for desktop files. Every step loses people. Typical result: two conscientious colleagues upload everything, everyone else means to. The folder also arrives after the event, so it captures leftovers, not the moment, and access management becomes your job for weeks.

The hired photographer

Great for what it does: a professional will get the polished group shot and the branded banner photo. But a photographer is one person on a schedule. They leave at 21:00, and the best material happens at 23:30. They shoot the plenary, not the kayak that flipped. Delivery takes one to three weeks, by which time momentum is gone, and professional coverage of a 60-person offsite is a real line item. A photographer is a complement, not a collection strategy: 200 excellent photos of 10 percent of the moments.

The pattern across all three: collection that relies on people doing homework after the fun is over does not work.

The playbook

Before the offsite (30 minutes, a week out)

1. Pick the single destination. One album, one owner (you). Decide now, so no well-meaning colleague creates the WhatsApp group first. Announce it in the logistics email: "All photos go here, do not start a photo thread."
2. Set up a guest camera album. This is the pattern built for exactly this job: you create an album, it generates a QR code, and anyone who scans it can take photos straight into the album from their phone browser. No app install, no accounts, no access requests. (This is what we built Kept to do: guests join by name so you always know who shot what, and the host controls and can delete everything.)
3. Print the QR code. A5 or A4, three to five copies: registration desk, dinner table, bar, bus. One line of copy: "Scan, type your name, shoot."
4. Handle the privacy line. Add a sentence to the logistics email: photos go into one company-controlled album, tell the organiser if you would rather not be photographed, anything can be removed on request. Two minutes of work that saves real trouble.
5. If you have a photographer, brief them. They cover the set pieces; the guest album covers everything else. Agree their edited set gets added to the same album afterwards.

During the offsite (five minutes of nudging)

1. Demo it once, live. At kickoff, scan the code on screen, take a photo of the room, show it landing in the album. A ten-second demo converts better than any email.
2. Nudge at the right moments. Photos happen during activities and dinner. One verbal reminder at each is enough.
3. Deputise two natural photographers. Every team has them. Named requests work, broadcasts do not.
4. Watch the album, not the phones. You see photos arriving live; if the afternoon produced nothing, nudge at dinner.

After the offsite (15 minutes, within 48 hours)

1. Sweep the album same week. Remove duplicates, blurry shots, and anything a colleague would not want their manager scrolling past. One place to review means one review.
2. Share the link while it is warm. Monday morning, one message: "312 photos from the offsite, here is the album." A link three weeks later gets a fraction of the views.
3. Fold in the photographer's set when it arrives, into the same album.
4. Pick ten for the internal recap. Newsletter, all-hands slide, intranet. Get a quick OK from anyone identifiable before using photos on public channels like LinkedIn.
5. Set a deletion date. Decide how long the album lives (a year is typical), note it, and actually delete it then.

Why the guest-camera pattern wins

The structural difference is when collection happens. WhatsApp, drives, and photographers all collect after the moment: someone must remember, select, and upload. A guest camera collects during the moment: the phone's camera is pointed through the album, so taking the photo and submitting it are the same action. Nothing to chase, nothing to export, nothing compressed, no app to install.

And because everything lands in one host-controlled place, the awkward parts of company photos (the unflattering shot, the colleague who opted out, the deletion request months later) become a ten-second delete instead of an impossible group-chat archaeology project. If you want the pattern ready-made, here is how Kept works for company events.

Common questions