How to Write a Shot List with AI in 2026
A practical walkthrough for writing photography shot lists with AI — the right structure, what to never let AI fabricate, and the free tool that handles it. For wedding, portrait, event, and commercial photographers.
A strong photography shot list does three things: it makes sure you don't forget the must-have shots the client specifically wants, it sequences the shots realistically against the day's timeline so you're not chasing the moment after it's gone, and it gives the second shooter and the assistant the clarity they need to operate without checking in every five minutes. Writing them by hand for every shoot is repetitive structured work that's also where forgetting one critical shot (the grandmother who flew in from out of state, the CEO's headshot before they leave at noon) creates the kind of post-shoot conversation no photographer wants. AI is excellent at producing comprehensive structured shot lists in three minutes. The client-specific must-haves, the venue knowledge, and the timing judgment — those are yours.
This is a practical walkthrough for writing a shot list with AI that covers what the client expects without padding the day with shots nobody asked for.
What a strong shot list contains
Before you can use AI well, you need to know what good looks like:
- Shoot context block — shoot type, date, location(s), key timing milestones, photographer + second shooter assignments
- Must-have shots — the specific shots the client explicitly requested (these come first; nothing else gets prioritized over these)
- Standard coverage by phase — for weddings: getting ready, ceremony, family formals, couple portraits, reception; for events: arrivals, keynote, audience reaction, networking, sponsor signage; for portraits: setup, primary, variations, candids
- Family/group formals list — for weddings or family shoots, the specific combinations of people (with names so you can call them out by name on the day)
- Timing notes — when each cluster of shots happens, golden hour timing if applicable, hard time constraints
- Location notes — backup indoor locations for weather, sun position considerations, no-go areas at the venue
- Equipment notes — second body, lens swaps, lighting changes per phase
- Special instructions — sensitive situations (recent loss, divorced parents, accessibility needs), no-photo requests, surprise moments
Photographers whose shot lists serve them on the day are the ones whose lists prioritize must-haves at the top, sequence realistically against the timeline, and surface the special-situation notes that AI templates miss. AI handles the comprehensive coverage and structural layer; you provide the client-specific must-haves and the day-of judgment.
The right prompt structure
The mistake most photographers make on first try is asking for "a wedding shot list" with no context. The prompt that actually works gives the AI the shoot specifics, the must-haves, and the timeline:
<task>Generate a shot list for a wedding.</task>
<context>
Wedding date: September 12, 2026
Couple: Sarah & Mike (first names only)
Venue: Backyard ceremony at couple's home + reception at local restaurant
Guest count: ~50
Shoot coverage: 6.75 hours, single photographer (no second shooter)
Timeline:
- 2:30 PM — Getting ready (1 hour, just the couple, at their home)
- 3:30 PM — Ceremony (1 hour, backyard)
- 4:30 PM — Family + couple portraits (45 min, backyard then short walk to nearby park)
- 5:15 PM — Cocktail hour at restaurant
- 5:30 PM — Reception begins, dinner, toasts, first dance
- 9:00 PM — Coverage ends
Client must-have shots (verbatim from inquiry conversation):
- Sarah's grandmother (Helen) — flew in from Vermont; first family event
in 3 years; must capture her with both Sarah and Mike together
- Mike's late father's ring — being worn by Mike's brother as best man;
detail shot during ceremony
- The couple's dog (Bruno) — will be at the ceremony with a flower collar;
shots with the couple
- A candid of the couple's expressions during their vows (no posed
re-enactment)
- Sarah's mother helping her get ready (specifically the moment of putting
on her grandmother's earrings)
Family formals list (couple-provided):
1. Sarah + parents
2. Sarah + grandmother Helen
3. Sarah + parents + grandmother Helen
4. Mike + mother
5. Mike + brothers (3 of them)
6. Mike + immediate family
7. Combined immediate families (both sides)
8. Wedding party + couple
9. All grandparents present + couple
Sensitive situations:
- Sarah's parents divorced 2 years ago; civil but separate photos preferred
except in the "combined immediate families" shot
- One guest (Mike's uncle) declined photo opt-in (per couple's
pre-event note)
- Surprise: Sarah's brother flying in last-minute from London;
reveal at cocktail hour
Style preference (from client inquiry):
"Candid documentary feel; we want photos that show how the day actually
was — not posed for hours. We're especially into your work because of
how you capture the candid moments between people."
Equipment context:
- 24-70mm + 70-200mm + 35mm prime; one body + one backup
- No external lighting beyond a small on-camera flash for reception
- Ceremony is golden-hour-adjacent; reception is indoor
</context>
<instructions>
- Structure: must-have shots first (top of list), then standard wedding coverage
by phase, then family formals list, then sensitive-situations notes
- Sequence by timeline — don't put cocktail-hour shots before ceremony shots
- Family formals list verbatim from client; do not reorder or add combinations
- Sensitive situations as a clearly-labeled section at the top so the
photographer reads them first
- For the candid-documentary style, note where candid coverage is preferred
over posed (vows, first dance, toasts, reactions)
- 600 words maximum
</instructions>
<avoid>
- Generic wedding shot list padding (bouquet on table, ring shots if not requested,
shoes detail if not requested) — the couple prefers candid over staged
- Adding "while we're at it" shots not tied to client preferences
- Reordering the family formals list (couple provided their preferred order)
- Forgetting the must-haves (must-haves are non-negotiable)
- Posed re-enactment language (client explicitly didn't want that)
</avoid>The structure: shoot specifics, must-haves verbatim from the client, family formals from client, sensitive notes, and explicit instructions about what NOT to invent or reorder. The AI produces the structured list; you provide the client-specific content.
What to never let AI do
Invent must-have shots. If the client said "capture Sarah's grandmother specifically because of X," that's the must-have. AI will sometimes add plausible-sounding must-haves ("a shot of the venue at sunset") that the client didn't ask for. Generic adds become padding; client-specific asks are the actual work.
Reorder the family formals list. The order the couple provided is usually based on who's flying out early, who's mobility-limited, who's most important to whom. Don't let AI reorder for "logical flow."
Drop the sensitive-situations notes. Divorced parents, accessibility needs, photo opt-outs, surprise moments — these are the items that, when missed, cause the biggest post-shoot conversations. AI sometimes trims these for word count. Don't let it.
Add posed shots when the client wants candid. Style preferences matter. A client who said "no posed re-enactment of the vows" doesn't want a re-enactment shot listed.
Promise specific shots the day might not deliver. "Golden hour shot of the couple by the willow tree" is a planning intent. Whether it actually happens depends on weather, timing, and what's happening with the couple. AI can list intended shots; you adjust on the day.
Common mistakes
Generic shot list padding. "Bouquet detail" and "rings on lace" and "venue at sunset" if the couple didn't ask for them. Style-mismatched shots in the list cost time on the day.
No timing alignment. Shot list grouped by category instead of phase creates the situation where the photographer is looking for "couple's first look" at 5:30 PM when first look was at 3:00. Group by phase + timeline.
Family formals without names. "Sarah's family + Mike's family" doesn't tell the photographer who to call. Use names (with relationships if needed): "Sarah, Helen (grandmother), [parents' names]; Mike, [mother's name], [brothers' names]."
No backup location notes. Outdoor ceremony in summer means weather backup needed. Sun position notes for harsh-light timing. Indoor venue with reflective floor for the ceremony. These notes prevent in-the-moment scrambling.
Forgetting the must-haves. The single biggest post-shoot complaint photographers get is "you didn't capture the grandmother shot." Lead with must-haves; nothing else goes ahead of them.
What to never put on a public-facing shot list
- Sensitive personal details that should stay between the photographer and the couple (recent loss, family conflict, photo opt-outs)
- Surprise reveals (someone flying in, secret proposal, surprise gift) — the shot list goes to the photographer's team, not to the couple or vendors
The full shot list is for the photographer and second shooter. A simplified version (without sensitive notes and surprises) can go to the couple for review and to the wedding planner for timeline coordination.
The free tool that handles this for you
If you don't want to engineer the prompt every time, the Shot List Generator on AI Career Lab is pre-configured for the structure that covers what clients expect without padding. It produces shot lists with the elements above, in a format that sequences against the timeline and surfaces sensitive notes at the top.
Pair it with the Client Proposal Generator for the upstream booking and the Album Description Generator for post-shoot deliverables.
Free with an AI Career Lab account, capped at five runs per day on the free tier.
Want the whole system?
The Photographer AI Cowork Vault ($9, one-time) ships pre-built skills for client proposals, shot lists, album descriptions, marketing emails, inquiry responses, and pricing conversations. Works on Claude Cowork and Microsoft 365 Copilot Cowork.
Try it on your next shoot
Pick your next wedding or event. Gather the must-haves from the client, the family formals list, the timeline, and the style preferences. Run the inputs through the tool above. Use the output as the working shot list for the day — note how much more confident you feel about coverage when must-haves are at the top and sensitive situations are explicit.
Create your free AI Career Lab account and try the photographer tools today. No credit card.
This article is general guidance for working photographers. AI-generated shot lists are starting drafts requiring photographer review for client-specific must-haves, timing realism, sensitive-situation awareness, and venue-specific logistics. The shot list is a planning artifact; day-of judgment about what to actually capture remains the photographer's.
Save hours every week with the Photographer AI Cowork Vault
50 skills with AI-edit-aware contracts for inquiries, gallery delivery, and vendor pitches.
Related Guides
How to Write a Photographer Client Proposal with AI in 2026
A practical walkthrough for writing photography client proposals with AI — the right structure, what to never let AI invent, and the free tool that handles it. For wedding, portrait, commercial, and event photographers.
How to Install the Photographer Claude Plugin (Cowork & Code)
Step-by-step installation guide for the Photographer Claude plugin from The AI Career Lab — works in both Claude Cowork (chat) and Claude Code (terminal). What you get, how to install, and your first run.
AI Tools for Photographer Outreach and Client Acquisition in 2026
The AI tools photographers are actually using to win clients in 2026 — inquiry replies, vendor pitches, past-client outreach, and the social workflow that fills a calendar without burning the editing afternoon.