How to Organise Photos After a Photoshoot: A Folder System That Scales

You shot 1,800 frames last weekend. They are sitting on a memory card, on a desktop folder called "Import 2", and possibly in a second copy that you cannot quite remember the location of. In six months, when the client emails asking for "that one shot near the window", you will need to find it in under five minutes. Will you?

Most photographers learn photo organisation the hard way — by losing a shoot. A drive fails, a card gets reformatted too early, or a folder structure made sense in 2024 but is unintelligible in 2026. The fix is not more storage or a better app. It is a system you follow every time, without thinking, that turns a chaotic post-shoot dump into something you can search, share, and archive in a few hours.

This guide covers the full organisation lifecycle: folder hierarchy, file naming, culling and ratings, backups, and — the part most articles skip — what belongs in a shared workspace versus your local archive. By the end you will have a template you can copy, paste, and reuse for every shoot you do.

Why Organisation Falls Apart

Disorganisation rarely starts with bad intent. It starts with shortcuts. The card import goes into "Desktop/New Folder" because you are tired. The keepers get exported into the same folder as the RAWs because you are in a hurry. The client gets a Google Drive link to a folder called "edits-final-FINAL-v2".

Each shortcut is small. The compounding effect is what kills you. After a year of shortcuts, you have:

• Shoots you cannot find without scrolling through thumbnails
• Files with names like _DSC4382.ARW that tell you nothing about who, what, or when
• Three copies of the same shoot in three different drives, none of them complete
• No idea which version of an edit was the one the client approved

A repeatable system prevents this. The system below is not the only one that works, but it is one that scales from 5 shoots a year to 5 shoots a week without breaking.

Folder Hierarchy That Works

A good folder structure is chronological at the top, descriptive in the middle, and functional at the bottom. The pattern that scales:

Photography/
  2026/
    2026-05-02_Anna_Portrait/
      01_RAW/
      02_Selects/
      03_Edits/
      04_Exports/
      05_Delivery/
    2026-05-08_Mara_Editorial/
      01_RAW/
      02_Selects/
      ...

Three principles to notice.

Year first, then date. Year folders make archiving and backup trivial — you can move "2024" to cold storage as one operation. Date-prefixed shoot folders sort chronologically in every file browser without any extra effort.

ISO date format (YYYY-MM-DD). Never use 15-05-2026 or May 15 2026. ISO dates sort correctly. European dates do not. American dates confuse everyone. Pick the format that the operating system can sort and stick with it.

Numbered subfolders. Prefixing with 01_, 02_ keeps the working stages in workflow order rather than alphabetical order. RAW comes before Selects, Selects before Edits, Edits before Delivery — exactly the order you walk through them.

When a Shoot Has Multiple Locations or Looks

For longer shoots with distinct setups, add a layer inside the RAW and Edits folders:

2026-05-02_Anna_Portrait/
  01_RAW/
    look-1-window/
    look-2-studio/
    look-3-rooftop/
  03_Edits/
    look-1-window/
    look-2-studio/
    ...

Resist the urge to add this layer for every shoot. A standard portrait session does not need it. A full-day editorial with five looks does. Add structure when the shoot demands it, not pre-emptively.

File Naming Conventions

Camera-generated filenames are useless six months later. _DSC4382.ARW does not tell you whose shoot it was, when it was, or what it was. Renaming on import takes ten seconds and makes everything searchable.

The pattern that works for most photographers:

YYYYMMDD_ClientName_001.ARW
20260502_Anna_001.ARW
20260502_Anna_002.ARW

Lightroom, Capture One, and Photo Mechanic all support this rename pattern as a one-click import option. Set it up once, save it as a template, and apply it to every import.

Rules for File Names

• Lowercase with underscores or hyphens — never spaces. Spaces break URLs and some scripts.
• Three-digit sequence numbers — 001, not 1. Ensures correct sorting up to 999 frames.
• Avoid special characters — no &, ', (), accented letters in filenames. Keep them in folder names if you must.
• Do not put version numbers in raw files — RAWs are the source of truth and never change. Version numbers belong on edited exports: 20260502_Anna_001_v2.jpg.

What About the Selects?

When you export keepers from RAW into the Selects folder, keep the original sequence number so you can trace any select back to its RAW. A select named 20260502_Anna_047.jpg always corresponds to 20260502_Anna_047.ARW. This trivial rule saves hours when a client asks for a re-edit and you need the original file.

Lightroom Catalog Versus Folder System

A common confusion: do you organise inside Lightroom (catalogs, collections, smart collections) or outside it (folder structure on disk)?

The answer is both, and the disk wins ties.

The folder structure on disk is your source of truth. It survives Lightroom reinstalls, catalog corruption, and switching to a different editor. Anyone — including future you — should be able to navigate the folders without any software.

Lightroom catalogs add a working layer on top. Use one catalog per year, or one master catalog if you stay under ~50,000 images. Inside the catalog, use Collections for grouping selects, and Smart Collections for things like "all 5-star images from 2026". But do not rely on the catalog for organisation that should live in folders.

If your folder structure depends on Lightroom to make sense, the structure is broken. Folders should be readable from Finder, Explorer, or the terminal — without any application open.

Star, Flag, and Colour Ratings

Lightroom (and most editors) give you three rating systems. Most photographers use them inconsistently or not at all. Pick a convention and apply it the same way every time.

A simple system that works:

• Flag (P) — keepers — anything technically usable, your first-pass survivors.
• 1 star — sent to client/model for review.
• 2 stars — client/model selected this for editing.
• 3 stars — final, edited, ready for delivery.
• Rejects (X) — to be deleted after the shoot is delivered.

Colour labels are optional but useful for status tracking: red for "needs retouching", yellow for "in progress", green for "done". Do not stack too many systems — one or two layers of metadata is enough.

The point is not the specific letters or numbers. It is that "2 stars" means the same thing in every shoot you have ever done.

Local and Cloud Backup: The 3-2-1 Rule

If you are not following the 3-2-1 backup rule, you are gambling. The rule, as widely documented by backup providers like Backblaze:

• 3 copies of every file
• On 2 different types of media
• With 1 copy offsite

For a working photographer, that translates to:

• Copy 1 — the working drive (internal SSD or fast external)
• Copy 2 — a local backup drive (external HDD or NAS)
• Copy 3 — a cloud backup service (Backblaze, Arq to S3, iDrive)

The card itself is not a backup. The moment you reformat the card, that copy disappears. Treat the card as a one-way delivery mechanism.

When to Format the Card

Never format until both backups are confirmed. "Confirmed" means you have actually opened the backup folders and verified the file counts match. A copy that ran in the background and reported success is not the same as a copy you have visually verified. Trust, but verify.

What Belongs in a Shared Workspace

This is where most organisation guides stop — and where the modern photo workflow really starts. Folder structure and Lightroom catalogs solve the photographer's local problem. They do not solve the shared problem: the moodboard the model needs to see, the selects the client should review, the comments on individual frames, the final delivery.

A shared workspace is not a duplicate of your local archive. It is a curated subset of one shoot, organised around collaboration rather than storage.

For each shoot, the shared workspace should contain:

• The brief and moodboard — creative direction, references, colour palette
• The agenda and logistics — date, location, schedule for the shoot day
• The proofs for review — your curated selects, not the full RAW set
• Comments and selections — feedback tied to specific images
• Final deliverables — edited photos ready for download

This is exactly the gap Cullengo is built for. A shoot in Cullengo is one workspace that holds the moodboard, planning details, photo galleries, comments, and final delivery — all attached to one shoot. The galleries are separated from generic photo storage, so the shoot's review set does not get mixed with your archive of personal work or unrelated shoots. Per-gallery visibility lets you keep the moodboard private to your team while sharing the proofs gallery with the model.

The shared workspace should not try to replace your local folder structure. They serve different purposes: the local archive is for the photographer, the shared workspace is for the collaboration. Both can — and should — exist in parallel.

For more on the collaborative side, see our guides on the photographer-model collaboration workflow and how to share photos with a model after a shoot.

Archiving Old Shoots

Shoots are not finished when you deliver them. They need a graceful exit from your active drive. After delivery, run an archive routine:

1. Confirm delivery and approval. The client has the files and has confirmed receipt. No outstanding revisions.

2. Delete the rejects. Files marked with the reject flag (X) can go. So can intermediate exports — Lightroom can regenerate JPEGs from RAWs at any time.

3. Keep the working files. RAWs, the catalog, the final edited files, and the delivery folder. That is what you might need later.

4. Move to archive storage. A slower, cheaper drive — or a cold cloud tier like Backblaze B1, S3 Glacier, or an offline drive in a fireproof safe.

5. Update the year folder. Once a shoot is archived, the local working drive only holds the current year. Last year's shoots live on archive media, indexed by the same 2025-MM-DD_ClientName structure.

How long to keep RAWs is a personal call. The legal minimum in most jurisdictions is none — a delivery is a delivery, and you are not contractually obliged to retain raw files unless you have agreed to. Practically, most photographers keep RAWs for at least 12 months after delivery in case a re-edit is requested. After that, it is a storage cost decision. Some keep everything forever. Some delete everything older than two years. Pick a policy and apply it consistently.

Common Mistakes

A few patterns that show up again and again in photographers' archives:

• No naming convention — every shoot folder named differently. Searchable only by memory.
• Editing before culling — investing 30 minutes per image in retouching before the client has confirmed selections.
• Using the card as a backup — leaving images on the card until the next shoot, "just in case". The card is not a backup, it is a single point of failure.
• Mixing personal and client work — one undifferentiated dump of every photo ever taken. Separate at the top level: Photography/Clients/ and Photography/Personal/.
• Versioned filenames as a system — final.jpg, final-v2.jpg, final-FINAL.jpg. Use folders for stages, not filenames. Filenames should describe the image, not its status.
• No archive routine — old shoots stay on the working drive forever, slowly consuming space until you panic-delete in a hurry.

For an end-to-end view of how organisation fits into the rest of your process, see our guide on photography workflow management and the photo shoot planning checklist that sets up a shoot before you ever press the shutter.

A Quick Setup Checklist

If you are starting from scratch — or rebuilding after a year of chaos — here is the order to do it in:

1. Create a top-level Photography/ folder.
2. Create year subfolders for the years you have shoots from.
3. Define your shoot-folder template (YYYY-MM-DD_ClientName_ShootType/) and the subfolder template (01_RAW/, 02_Selects/, etc.).
4. Set up a Lightroom import preset that applies your file rename pattern and copyright metadata.
5. Configure two backup destinations: a local external and a cloud service.
6. Decide on your rating convention and write it down so you do not drift.
7. For collaborative shoots, set up a shared workspace — moodboards, proofs, and delivery in one place per shoot.

The first time through takes an afternoon. Every shoot afterwards costs you nothing — the system runs on autopilot, and finding a six-month-old image takes seconds.

For tips on the delivery end of this pipeline, see the best way to deliver photos to clients and our getting started with shoot planning guide for new collaborators.

FAQ

Q: How long should you keep client photos?

A: There is no legal requirement to keep RAW files after delivery, unless you have contractually agreed to. The practical minimum most working photographers follow is 12 months after the shoot — long enough to handle re-edit requests, reprints, or the client losing their delivery files. Beyond that, it is a storage cost decision. Many photographers keep RAWs indefinitely on cold storage; others delete after two or three years. Pick a policy, write it into your contract, and apply it consistently so clients know what to expect.

Q: What is the 3-2-1 backup rule for photographers?

A: The 3-2-1 rule means keeping 3 total copies of every file, on 2 different types of media, with 1 copy stored offsite. For photographers that usually means: a working drive, a local external backup, and a cloud backup service. The point is redundancy across failure modes — a fire that destroys your studio also destroys both local copies, but the cloud copy survives. The original card is not one of the three copies, because you will reformat it before the next shoot.

Q: Should you organise photos by date or by client?

A: Date first, client second. Date-based folders sort chronologically in every file browser, scale infinitely, and survive client name changes (companies rebrand, models change names). Embed the client name in the folder title (2026-05-02_Anna_Portrait) so search still works, and use Lightroom keywords or metadata for cross-cutting searches like "all of Anna's shoots". Pure client-based folders work for photographers with a small number of recurring clients, but break down once the volume grows.

Q: What is the best file naming convention for photo shoots?

A: YYYYMMDD_ClientName_001.ARW is the convention most working photographers settle on. It sorts chronologically, includes enough context to identify the shoot from the filename alone, and the three-digit sequence number scales up to 999 frames per shoot (use four digits if you regularly shoot more). Keep it lowercase, use underscores instead of spaces, and avoid special characters. Set this as your import rename preset in Lightroom or Capture One so it applies automatically to every shoot.

Q: Where should you store photos for client review?

A: Not in a generic Google Drive folder, and not in your local Lightroom catalog. Client review needs a visual gallery with selection and comment tools — a workspace where the client can see proofs, mark favourites, and leave feedback tied to specific images. Cullengo is built around per-shoot workspaces that hold the moodboard, proofs, comments, and final delivery in one place, separated from your local archive. See Cullengo's use cases for examples of shoot-based collaborative review.