The real admin work starts when everyone gets home.
A week after a big event, the messages usually sound the same. "Can you send the photo where we are near the stage?" "Do you have one of my parents from the ceremony?" "Which folder has the team photo?" None of these are unreasonable requests. They are just expensive when every answer requires manual searching.
The problem is not the client. The problem is the delivery system. If guests receive one huge gallery or a Drive folder with thousands of files, they will use the photographer as the search bar. That works for one small event. It breaks when you are shooting every weekend.
Stop answering requests inside WhatsApp threads.
WhatsApp is useful for client communication, but it is a poor production system. Screenshots get compressed. Filenames disappear. Multiple relatives ask for the same thing. Assistants cannot easily track what has been solved. By the end, the studio has done hours of unpaid support work and still looks slow.
Move requests into the gallery wherever possible. If guests can search by face, like images, and download approved files from the same place, the thread becomes a notification channel instead of the workspace.
- Send one gallery link instead of individual files.
- Ask guests to use face search before requesting manual help.
- Use liked photos for album selection and retouching requests.
- Keep admin-only notes for special client requests.
- Export selected filenames instead of collecting screenshots.
Create three request lanes.
Every post-event request usually belongs to one of three lanes: find my photos, select these photos, or fix this photo. Keep those lanes separate. Finding is solved by search. Selection is solved by likes. Fixes need a smaller, paid or approved editing workflow.
This separation protects your time. It also makes communication calmer because the client can see where a request belongs.
- Find: guest uses QR or selfie search to discover matching photos.
- Select: client likes images for album, print, or retouching shortlist.
- Fix: studio reviews a specific filename and confirms scope before editing.
- Deliver: final downloads are sent through the gallery, not scattered links.
Use a simple reply script.
A good script should sound helpful without turning every message into a custom search job. Try this: "I have uploaded the event gallery here. Please open it and use the selfie search to find photos of yourself. If something important is missing, like a family group or stage moment, reply with the event name and I will check the archive."
For client selections: "Please tap the heart on every photo you want for the album or retouching list. That gives our editor the exact filenames, so nothing gets missed."
For out-of-scope edits: "Happy to handle that. This is outside the included color correction, so I will confirm the edit count and timeline before we start."
Be careful with face search promises.
Face search can save a huge amount of time, but it should be explained honestly. It works best with clear faces and enough event coverage. Heavy blur, sunglasses, side profiles, children running across a frame, and dark dance-floor light can reduce matches. Public evaluation programs like NIST FRTE are a useful reminder that face recognition is measured technology, not a guarantee.
The right promise is simple: the gallery helps guests find likely matches quickly, and the studio can still help with important misses. That sounds professional and sets the right expectation.
Bottom line
Post-event requests do not have to eat your week. Put discovery, selection, and fixes into separate lanes. Let the gallery do the repetitive work. Keep human attention for the requests that actually need a human.