← Back to Lumeny

How to Manage Client Information in One Place as a Photographer

Here's a question: where is the location for your next client shoot?

If the answer requires you to think — "WhatsApp, I think, or maybe the email thread, or I wrote it in the calendar note" — you don't have a system. You have scattered information that happens to be findable most of the time.

Most photographers manage client information across 5+ different places:

  • WhatsApp — location details, last-minute questions, day-of logistics
  • Email — booking confirmation, contract, brief, delivery message
  • Google Drive — the photos themselves
  • Spreadsheet — shoot date, status, notes
  • Calendar — time and location (sometimes duplicated from email)

None of these are wrong individually. Together, they create a retrieval problem. Every time you need information about a shoot, you're searching across multiple systems.

The Real Cost of Scattered Client Info

The direct cost is search time — 2–5 minutes per lookup, multiplied across 30 active and past shoots. That adds up.

The indirect cost is higher: uncertainty. When client information is in multiple places, you're never sure you have the complete picture. Did they send an updated location in WhatsApp after the email? Was there a special request buried in the thread you haven't revisited?

This uncertainty creates a low-level anxiety about every shoot. Not dramatic, but persistent. And entirely avoidable.

What "One Place" Actually Means for Photographers

One centralized place for client info doesn't mean abandoning email or WhatsApp — clients will always contact you through whatever channel is convenient for them. It means one place that holds the canonical reference information for each shoot:

  • Client name and contact
  • Shoot date, time, location
  • Shoot status (Booked / Briefed / Shot / Editing / Delivered)
  • Briefing details (moodboard, shot list, prep notes)
  • Gallery link (once delivered)
  • Notes (anything specific to this client)

When this information lives in one place, you open one thing before a shoot — not four.

How to Build This System

Option 1: Notion or Airtable

These work well for solo photographers who are comfortable with customization. Build a database with one row per shoot, columns for all the relevant fields, and a kanban view for status tracking.

Pros: flexible, free tier available, shareable. Cons: requires setup, doesn't integrate with your gallery delivery or briefing tools.

Option 2: A photography-specific platform

Lumeny is designed around this model. Each shoot has a dedicated page within your booking overview — date, client, status, briefing link, gallery link. The briefing tool connects directly to the shoot. The gallery delivery connects directly to the shoot.

You don't need to copy a gallery link into a separate system after delivery because the delivery is already in the system. Everything is connected by design, not workaround.

See: how to keep track of photography bookings

What to Do With Client Communication (WhatsApp, Email)

Don't try to centralize every message. That's a losing battle. Instead, extract the key information from any channel and put it in your canonical system.

When a client messages you on WhatsApp with the meeting point for the shoot, paste that into your shoot's location note. Then you don't need to search WhatsApp on shoot day — you open your shoot page.

This takes 30 seconds at the time of the message. It saves 3 minutes of searching later, and more importantly, it means you're confident you have the right information.

The Minimum Viable Client Info System

If you're starting from scratch or migrating from a spreadsheet, here's the simplest version that works:

  1. One row per shoot (spreadsheet, Notion, or photography platform)
  2. Status column updated after every major step
  3. Location field — pasted in from wherever the client sent it
  4. Briefing status — sent / not sent
  5. Gallery link — pasted in after delivery

That's five fields. Everything else is optional complexity you can add later.

Frequently Asked Questions

Do I need to centralize every client communication, or just key info? Just key info. Trying to centralize every WhatsApp message and email thread is a project management problem, not a photography workflow problem. Pull the essentials (location, special requests, confirmed dates) into your system and leave the rest in its native channel.

What's the difference between a CRM and a booking overview? A CRM manages relationships and sales pipelines at scale — tracking leads, contacts, and long-term relationships. A booking overview tracks active projects: who, when, status, what's outstanding. Most solo photographers need the second, not the first.

What if a client uses multiple channels to communicate? Redirect them, gently. "I'll keep all the shoot details in our briefing link — feel free to contact me here, but I'll make sure the final details are there." Most clients are fine with one canonical reference point.

Can I use my phone's notes app as a central client info system? You can — and many photographers do. The limitation is search, status visibility, and linking to galleries and briefings. A notes app holds information but doesn't make it actionable.

One place for every shoot, every client

Lumeny connects your briefings, galleries, and booking status in one platform. No more searching across four apps before a shoot.

Start Free Trial

Written by Christian Bauer, founder of Lumeny and photographer with 10+ years of experience.