How to Track Client Requests Without Losing Details

Client requests scatter across channels: a WhatsApp message here, an email there, a verbal comment on shoot day, a follow-up DM a week later. Every scattered piece of information is a potential gap in your service. This page covers how to centralize client requests and what to do when they come in after delivery.

The Challenge: The WhatsApp and Email Scatter Problem

Most photographers manage client communication reactively. A client sends a message; you respond. A detail comes in; you try to remember it. This works — barely — until you have 6 active projects running simultaneously and start confusing details between clients, forgetting requests, or delivering something that doesn't match what was asked.

The scatter problem compounds at three points:

1. Pre-shoot: requests and preferences coming in from multiple channels
2. On shoot day: verbal requests made in the moment that don't get written down
3. Post-delivery: edit requests or questions that don't have a clear paper trail

How to Centralize Pre-Shoot Requests

The briefing is your primary tool here. Instead of letting client preferences accumulate in email threads, route them through a structured briefing:

1. Send the briefing 3–7 days before the shoot
2. The briefing's prep question section collects client requests in a structured way
3. Their responses live in the briefing, not scattered across your inbox
4. Before the shoot, you read the briefing — not hunt through email

This doesn't mean clients won't email you. They will. But when they do, you have a place to record the important information: add it to the relevant field in the briefing, or note it in the project record.

How to Handle Shoot-Day Requests

When a client makes a specific request on shoot day ("can we get a shot by that oak tree?"), note it immediately. Options:

• A quick note in the shoot briefing
• A note in your phone that you can reference when culling
• A brief voice memo

The key: don't rely on memory across the post-production period. If a specific shot was requested and you captured it, note where it is during culling so you can confirm it's in the delivered gallery.

How to Handle Post-Delivery Edit Requests

Post-delivery requests are a different category. These need:

• A clear record of what was requested and when
• Scope assessment: is this within your contract's revision policy?
• A response that confirms what you'll do and when

When a client messages you after delivery, reply with a confirmation email (not just a WhatsApp ack): "Got it — you'd like [specific edit] on the couple portrait from [section]. I'll have that to you by [date]." This creates a paper trail and manages expectations.

Client Request Tracking Checklist

• Pre-shoot requests funneled through structured briefing
• Shoot-day verbal requests noted immediately
• Post-delivery requests confirmed in writing
• Scope checked against contract for all edit requests
• Follow-up sent when changes are delivered

Frequently Asked Questions

What's the simplest way to stop losing client requests? One structural change makes the biggest difference: send a briefing with a prep questions section and record client responses there rather than leaving them in email. Centralizing collection is more important than any individual note-taking habit.

How do I handle a client who sends requests across multiple channels? Acknowledge in their channel, then record in your central system. "Thanks — I've made a note of that!" Then actually make the note somewhere structured.

What should I do when a client makes a request that's outside my contract scope? Acknowledge the request, confirm what's included in the contract, and offer a path forward: "Retouching individual images isn't in the standard package, but I can offer that as an add-on — here's what that would look like."

Is there a way to prevent most post-delivery requests? Yes — by being thorough before delivery. Review the briefing and confirm key requests are addressed before sending the gallery. A quick delivery message note ("I've included the oak tree shot you mentioned on the day") shows attentiveness and often pre-empts follow-ups.

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