All guides →

How to Organize Client Photos for Social Media (Without Chasing Anyone)

For social media managers, VAs and content photographers · 7 min read

Every social media manager knows the ritual. You need photos for next week's client content. You text them. Nothing. You text again. Eventually a WhatsApp dump arrives at 11 PM: 47 screenshots, three recipes, a blurry shot of a storefront taken through a moving car window, and one genuinely great photo of their team — compressed into pixel soup by the app.

You are not the bottleneck. The handoff is. Here's the intake-and-selection system that fixes it in one billing cycle, whether you manage three clients or ten.

Step 1: One intake link, forever

Stop receiving photos through chat apps. Compression destroys them, and chat history is where photos go to die. Set up a single, permanent intake channel per client — a Google Drive folder with "upload" permission, a Dropbox file request, or any dedicated upload link — and put it in three places:

Clients won't remember the link because they're running a business, not your workflow. That's fine — you're not trying to change them, you're giving every photo exactly one place to land.

Step 2: The folder structure that survives ten clients

Per client: ClientName / 2026-09 / raw and ClientName / 2026-09 / selected. Nothing else. No "misc", no "final_final_v2". The month folder is the archive; when October comes, September is closed — leftovers roll forward or die, but they don't haunt the active folder.

Rename nothing at intake. Filenames like IMG_4821.HEIC cost you minutes per client per month and buy nothing. Selection happens later; intake is purely about landing files in the right month.

Step 3: The 90-second triage

Once a week, per client, open the raw folder and make three passes — this takes longer to read than to do:

  1. Quality pass (30s): delete anything blurry, dark beyond rescue, or screenshot-of-a-screenshot. If a client's phone habitually produces bad photos, that's a coaching moment for your next call, not a daily emergency.
  2. Duplicate pass (30s): clients send five versions of the same shot "just in case." Keep the best of each burst, drop the rest without ceremony.
  3. Consent pass (30s): any photo with a recognizable customer face or a minor needs a consent flag before it goes anywhere. Keep a one-line note per photo ("signed May 12", "verbal OK"). This is the step that protects your client relationship and your invoice.

What survives triage moves to selected. That folder is your content inventory — and looking at it tells you instantly whether this client has a posting month or a drought.

Step 4: Selection is a content decision, not a filing decision

Don't pick photos one post at a time. Pick them in sets, matched to the platforms you're feeding: a 4–6 shot carousel group, a vertical frame for stories, a cover image, a lifestyle shot for filler days. Two rules make this fast:

Step 5: Make the handoff visible to the client

The chase happens because clients think photos are your problem until the moment you ask. Make the pipeline visible: in your monthly report, add one line — "Content published from your 14 photos: 6 posts. Photos still needed: team headshots, storefront exterior." Suddenly the intake link isn't your nagging; it's their to-do list attached to results.

Where to automate first

If you run this system by hand, it costs roughly an hour per client per month — real money at ten clients. The triage pass (quality, duplicates, consent flags) is the most mechanical part, and it's the first thing worth handing to software. PostSet takes the raw folder as-is, keeps the keepers, flags duplicates and consent issues, and drafts the actual post sets — carousels, stories, covers with captions — for your review. You keep the editorial call; the machine does the sorting. For a multi-client operator, that hour per client is the margin.

The system above works with nothing but Drive and discipline. Start there. Automate when the hours start billing against you.