Two days after the offsite, the communications manager posts on Teams: "Can someone send me the photos? We need to write the recap." Forty-eight hours later she has received 11 expired WeTransfers, 6 personal Dropbox albums, 3 HEIC files Windows cannot open, and a Google Photos link that says "access denied". The professional photographer has delivered 80 tidy but soulless shots. Not a single photo of the team session or the informal dinner.
That is the standard scenario. And if you opened this article, you are probably living it right now.
The problem: 200 photos across 50 smartphones, and an overloaded IT team saying no
An offsite with 50 to 100 people easily generates 300 to 500 photos. They sit on attendees' phones, possibly in a few people's Instagram stories, and in the personal cloud of whoever had the right reflex. Nobody thought about a shared collection point. Or if someone did, the timing was wrong.
The "logical" solution: ask IT to create a shared folder on the company SharePoint, or open up Drive access. Classic problem: the ticket takes three working days, access is refused for data policy reasons, or the proposed solution only works internally with no guest access. IT is not being obstructive, it is overloaded and cautious, which is its job.
The result: the recap goes out with four blurry photos, management asks "where are the real ones", and everyone spends an hour digging through their personal camera roll two weeks later.
4 methods you have probably already tried (and why they break)
An internal shared Drive
Reflex number one. Create a folder on the company Drive, share the link, ask people to upload. In theory it works. In practice:
- External attendees (clients, contractors, speakers) have no company account
- Access rights are managed person by person, and nobody does that during the event
- HEIC photos from iPhones will not open on every Windows machine
- The share link expires or gets blocked by security policy
And then there is this question: who owns the folder? If the person who created it leaves the company, the folder goes with them.
A Slack or Teams photo channel
"Let's create a #offsite-photos channel and everyone posts there." It does create some atmosphere, that is true. But it is not a gallery, it is a chronological feed where photos drown in comments. Finding a specific photo three weeks later is archaeology. And downloading 200 photos one by one from Teams is half a day's work.
Email attachments
The option for people in a hurry. It always ends the same way: 25 MB emails rejected by the server, images compressed into illegibility, and an inbox that overflows. Not to mention the person who sends 80 photos as individual attachments to the whole team.
A USB stick going round the room
The last-resort option, reserved for people who lived through the 2000s. It takes 45 minutes to circulate, some people have MacBooks with no USB-A port, and the stick ends up in someone's bag, forgotten in their car. And you still do not have the photos from the freelance photographer who was there.
The pattern that works: an external event gallery with a QR code
The idea is simple: do not depend on internal IT infrastructure for a temporary photo gallery. Use an external service built specifically for it, reachable by QR code from any smartphone.
The principle: before the event, you create an online gallery tied to your offsite. You print a QR code, or display it on the tables, at the entrance, on the welcome screen. Attendees scan it and upload their photos straight from their phone, without creating an account. Photos land in the gallery in real time. Within 48 hours everything is centralised.
No IT ticket. No access rights to manage. No file format or size problems. You send the gallery link to management the next morning.
Evokly for companies is built for exactly this use case (offsites, team building, conventions) with an interface designed so that even the least digitally comfortable person understands how to upload in 30 seconds.
The real advantage over improvised methods: the gallery can be shared with external guests, it keeps high-resolution originals, and you can download it in bulk (ZIP) whenever you need it for the recap or internal communications.
GDPR compliance on the company side (EU data, retention, right to erasure)
This point deserves to be taken seriously, because the DPO will ask questions, and rightly so.
Data hosting. Uploaded photos must be hosted in the European Union to stay within the GDPR framework without a transfer to a third country. A service running on AWS us-east or GCP us-central moves data outside the EU, which requires additional safeguards (SCCs and so on). Check the hosting region before choosing a tool.
Retention period. Offsite photos should not be kept indefinitely. Set a retention period consistent with your internal policy (6 months to 1 year is common for this kind of content). The tool you pick must let you delete the gallery and all associated data at the deadline. For recommended durations by use case (offsite, wedding, public conference) and the documentation to produce, see our GDPR guide on how long to keep event photos.
Right to erasure. If an attendee asks for their photos to be deleted (GDPR article 17), you have to be able to honour that request. That means either the system lets an administrator delete individual photos, or the attendee can do it themselves.
Facial recognition. Some tools offer facial recognition to tag attendees. Biometric data is sensitive data under GDPR article 9; processing it requires explicit consent from each attendee, a defined retention period and an impact assessment (DPIA). Require the tool to record consent (timestamp, version of the text), encrypt the data and delete it automatically at the deadline. Without that DPIA, do not use the feature.
The Evokly GDPR compliance page details the architecture choices on these points: EU hosting, configurable retention, individual deletion, and facial recognition subject to explicit recorded consent with automatic deletion of fingerprints when the event expires.
An illustrative example: an 80-person offsite, from announcement to recap
Here is an illustrative example, built to show the method step by step: it is not a customer story, and its figures are starting assumptions, not measurements.
Context: 80 attendees, two days at a country venue. A mix of employees, managers and about ten external contractors. No professional photographer, but a few people who regularly take good photos with their phone. At this size you need the Event plan (unlimited photos and contributors): the free plan stops at 10 contributors and 100 photos.
Before the event, the communications manager creates the gallery and prints its QR code several times: one per table at dinner, two in the corridors, one at the entrance. She also prepares a 30-second announcement for the opening address.
During the event, the announcement is made on the first morning. It is what triggers the first uploads: without it, the QR code is just another piece of paper on the table. Attendees then pass the link to each other, and external contractors add their photos like everyone else, with no company account.
After everyone gets back, she sends the link again the next morning with a reminder. That is when the evening's photos arrive, as people find them in their camera roll. Everything lands in the same gallery, at original quality.
For the recap, she picks about twenty photos from the gallery and downloads the rest as one archive. Her work comes down to four steps: create the gallery, make the announcement, send the reminder, pick the photos.
That is the whole gap between this example and the opening scenario. The same offsite, organised differently. No IT ticket, no chasing, no lost files.
Once the photos are centralised, many organisations under-use what they collected. Our article on 12 team building photo ideas covers how to turn a post-event gallery into a lasting employee engagement lever.
If you want to see what it costs for your organisation, the plans are on the pricing page. There is a per-event option if you do not want to commit to an annual subscription before trying it.
