Writing a shot list

How to write a shot list for a photoshoot

What actually belongs on a shot list, why choosing between a group and a tag decides whether your list reads like a day, and a worked example showing both at once.

What actually belongs on a shot list

A shot list is not a shooting script, and it is not a mood board. Its job is to tell anyone reading it cold exactly what to capture and in what order. For stills work, that means genuinely photographic specification rather than a scene description: size and angle, orientation, focal length and aperture where they matter, the camera body if more than one is in use, the kind of lighting, and whatever wardrobe, prop or styling note applies to that exact shot. There is deliberately nothing about frame rate, camera movement or sound on that list — a stills shot list, done properly, has no motion-picture fields at all, because none of them describe a photograph.

Two more fields pull more weight than they look like they should. A priority — must-have against nice-to-have — so you have an honest answer ready for what gets dropped if the day runs long. And an estimated duration, so your list can become a schedule rather than staying a list. Neither is decoration; both are what the rest of the day is worked out from.

Two ways to cut the list, and they are not interchangeable

Almost every shot list that goes wrong goes wrong here, by treating groups and tags as the same kind of thing. They answer different questions.

A group is the shape of the day

A group holds a shot once and once only — a shot is in one group or none — and the groups run in the sequence you actually intend to shoot them. "Feed room," then "stable," then "prep," then "ridden" is not a way of filing things, it is the day, written down. Because the sequence is stored and the letter, count and running time for each group are worked out from the shots inside it, reordering the groups relabels and retimes the whole sheet for free — nobody goes back and renumbers section C to section B by hand.

A tag is a second, independent cut across the same shots

A tag carries nothing but its own name, and a shot can wear several. Where a group asks "what order do we shoot in," a tag asks a different question entirely, after the fact — "which folder does this belong in for delivery," "which product line is this," "which images does this specific client see." A shot tagged "hero" and "SS26 knitwear" can sit wherever its place in the day puts it, and still turn up in the right place when the list is re-sorted by tag for the edit or the client hand-off.

Muddling the two produces a shot list that is either an unordered pile with labels, or an ordered list that cannot be re-cut for delivery without physically moving rows. Keep them separate and the same list does both jobs.

A worked example

Below is a shortened but real shot list for a small commercial product-and-lifestyle shoot — three groups, tags cutting across them, and a duration on every row. This is the level of detail worth aiming for: enough that someone who was not in the brief meeting could run the day from it.

#	Group	Shot	Size	Angle	Priority	Tags	Est.
1	A — Flat lays	Full product range, laid out	WS	Overhead	Must-have	Catalogue	20m
2	A — Flat lays	Hero product, detail on stitching	DET	Overhead	Must-have	Catalogue, Hero	15m
3	A — Flat lays	Packaging, closed and open	MCU	Eye level	Nice-to-have	Catalogue	10m
4	B — Studio hero	Hero product on set, key light	MS	Eye level	Must-have	Hero, Website	30m
5	B — Studio hero	Hero product, three-quarter angle	MS	High	Must-have	Hero, Website	15m
6	B — Studio hero	Texture close-up	ECU	Eye level	Nice-to-have	Hero	10m
7	C — Model, lifestyle	Full outfit, walking	WS	Eye level	Must-have	Lifestyle, Website	25m
8	C — Model, lifestyle	Product in use, hands	MCU	Low	Must-have	Lifestyle, Hero	20m
9	C — Model, lifestyle	Candid, laughing	MS	Eye level	Nice-to-have	Lifestyle, Social	15m
—	Ungrouped	Behind-the-scenes for socials	—	—	Nice-to-have	Social	10m

Read the tag column sideways and the delivery cut appears without moving a single row: everything tagged "Hero" is shots 2, 4, 5, 6 and 8, whichever group they sit in; everything tagged "Website" is 4, 5 and 7. Read the group column top to bottom and the shoot day appears instead: flat lays first while the studio is lit for the hero set, the hero set second, the model last once hair and makeup have had the whole morning. That is two cuts of the same nine rows, and neither one required touching the other.

Latentshoot’s shot list. Lettered groups — A Outerwear, B Knitwear & layering, C Rooftop — each showing a shot count, a running time and a small “Derived” tag, with a note under the group heading and rows underneath showing status, size, angle, lens, light, location, look and estimated duration. — The group heading’s shot count and running time are marked as worked out rather than typed, because nobody typed them — they are read off the rows underneath, which is also why dragging a shot into a different group re-totals both groups for free.

How much detail is too much

The acronyms in the size column — WS, MCU, DET and the rest — are there to keep a dense list scannable, not to look professional. The test for any one row is whether someone competent who missed the brief could shoot it without asking you a question. Add detail until that is true, then stop. A shot carrying more than a handful of tags has usually stopped tagging and started narrating — cap it, and let the group and the priority flag carry the rest of the context.

Building it once, not every time

Setting a shot list up this way is genuinely more work the first time than a plain checklist in a notes app, and there is no honest way around that. What it buys back is on every shoot after the first: the same groups and tags come round again job after job, and a photographer who shoots the same kind of job repeatedly stops re-inventing the structure and starts filling it in. See how long does a photoshoot take for how the estimate column gets easier to fill in over time too.

Turning the list into the rest of the day

Get this structure right and you never have to build anything after it by hand. The running order, the daylight band, the gear list and the call sheet are all read off the shot list rather than kept as documents of their own — change a duration or drag a shot into a different group and everything that follows from it is already correct. See how the schedule is built from the shot list and how the call sheet follows from it.

The groups, tags, priority flags and durations above are the actual fields on Latentshoot’s shot list — not a template to copy into a spreadsheet by hand.

Write your shot list in Latentshoot

Frequently asked

What is the difference between a shot list and a call sheet?

A shot list is the plan for what to capture, in what order. A call sheet is the document built from it for the day itself — call times, location and the running order — so the two should never be kept as separate, hand-maintained documents.

How many tags should one shot carry?

As few as answer a real question about delivery or categorisation — a product line, a client folder, a social flag. Once a shot carries more than four or five tags it has usually stopped tagging and started narrating, and that detail belongs in a note instead.

Do groups have to match physical locations?

No — a group is whatever shares one lighting setup and one continuous stretch of the day, which is often a location but is just as often one set within a single studio, or one model in one outfit.

Write your shot list in Latentshoot See the shot list feature

No card. The schedule, the gear list and the call sheet all follow from this one list, on the free plan too.