If you shoot for a living — weddings, editorial, brand work, real estate, commercial — the work in front of the camera is maybe a third of the job. The rest is brief reading, shot planning, scouting, schedule wrangling, post-shoot logging, edit selection, client review, delivery, and invoicing. Each one of those generates documents, decisions, and follow-ups, and most of them live in different apps that don't talk to each other.
This guide is about consolidating the parts that benefit from being together — briefs, shot lists, location notes, post-production logs, client comms — into a single vault where you can find them later and where an agent can do the boring middle work.
What a photographer's notes have to hold
A working photographer's notes carry four loads. Each one fails in a particular way when it lives in the wrong place:
- Client briefs — usually delivered as a PDF, a long email, or both. They evaporate from working memory by the time you're at the location.
- Shoot planning — shot lists, location notes, lighting plans, gear lists, schedules. Lives in a notebook that's hard to share with assistants and a phone that runs out of battery.
- Post-shoot logs — what worked, what to reshoot, which frames are the keepers, edit notes for each selected image. Usually sits in your head, then degrades.
- Client communication — the back-and-forth around delivery, revisions, and approvals. Usually buried in email.
A vault holds all four together, in a form an agent can read across. Plain markdown for the text. PDFs auto-converted to searchable text. Audio (voice memos from the shoot, client briefing calls) transcribed automatically. Inline databases for the lists that want to be tabular. The same client-side shape — briefs, calls, deliverables, revisions — applies to any project work; see AI notes for client work for the broader freelancer-and-consultant version.
Briefs you actually remember
Most photography work starts with a brief. A brand wants four hero images, three lifestyle, ten product cutouts, in their style, by Friday. The brief arrives as a 12-page PDF or a long email, you read it once, and by the day of the shoot you're working from a half-remembered version of it.
The fix is to put the brief in a place the agent can read while you're planning the shoot. Drop the PDF onto a page in your vault — it's auto-converted to markdown via docstrange, so it becomes searchable text instead of an opaque file. Now you can ask: "Read the Acme brand brief. Pull the must-have shots, the brand color guidelines, and the technical specs for delivery." You get the relevant slices back in plain English, in seconds.
For client briefing calls, drop the recording onto the same page. It transcribes with speaker labels — useful for picking out exactly what the creative director said about mood versus what the marketing manager said about deliverables, three weeks later when you're re-reading. The brief and the call sit side by side, and the agent can quote from either.
Shot lists that survive contact with the location
Shot lists are notoriously aspirational. You write a 30-shot list at home, you get to the location, you adjust to the actual light and the actual subject, and the list barely resembles what you shoot. That's fine — the list's job isn't to dictate, it's to make sure nothing critical gets missed.
A shot list lives best as an inline database in a markdown page, embedded directly via the :::database::: directive. One row per shot. Columns for description, location/setup, subject, must-have flag, and a status (planned / shot / skipped / reshoot needed). On the day, you check off rows as you go.
The benefit of being in the vault, alongside the brief: when the brief changes mid-shoot ("can we also get a few horizontal versions?"), you don't have to leave the page. You add rows. After the shoot, you have a clean record of what was actually captured against what was planned.
For multi-day shoots or multi-location work, unlimited page nesting matters. A wedding shoot might have a parent page for the day, sub-pages for getting-ready, ceremony, portraits, reception — each with its own shot list. The structure can be as deep as the shoot demands.
Location and lighting notes that compound across shoots
Every photographer builds up location knowledge over time. The park where the late-afternoon light is great in October. The studio where the seamless paper roll is twelve feet wide. The venue where the chandelier kills the white balance. Most of this knowledge lives in your head and dies when you forget which venue had the chandelier problem.
A "Locations" sub-vault, with a page per place you've shot at, captures it. Notes on light, time of day that works, parking, power outlets, spaces to use as makeshift dressing rooms, the friendly contact at the front desk. Photos of the space if useful. Over a year of work, this becomes the kind of operational knowledge that distinguishes a photographer who's been around from one who's still learning.
Same shape works for gear setups you've used and want to remember. "Lighting setup — small product shoot with a key, fill, and rim — what worked in Studio B." Plain markdown, dated, recoverable next year when you have a similar brief.
Post-shoot logs and the brutal first edit
The selection pass is where most photographers lose time. You come back with 1,200 frames. You need to narrow to 80 for the client. The first pass is mechanical; the second is taste; the third is fixing the second pass.
The agent doesn't pick frames for you (and shouldn't — that's the work). But it helps with the surrounding admin. A "Post" page per shoot, with sections for: first impressions, frames flagged in-camera as keepers, the edit decisions that came up during selection, color and mood notes for the look you want.
After the first pass, type the edit decisions into the Post page. "Going for a slightly cooler grade than the brief asked for, with the brand-color tones held back for the hero shots." Six months later, when the same brand books a follow-up shoot, the agent can pull this and you don't re-derive the look from scratch.
For the actual file management — selects, edits, exports — that still lives in Lightroom or Capture One. The vault is for the thinking around the work, not the catalog itself.
Client revisions that don't drown you in email
Every photographer has been here. You deliver a gallery. The client comes back with notes — eight images need a different crop, three want a warmer grade, one needs the sign in the background removed. The notes arrive as an email with screenshots, or a Loom, or a meeting on Tuesday.
Capture the notes in a "Revisions" sub-page on the relevant shoot page, with one row per revision in an inline database: image filename, requested change, status, completed date. The page becomes the single source of truth for what was asked and what was done. When the client emails next week to ask "did you do all the revisions?", you can answer from a list instead of scrolling email.
If the revisions came over a recorded call, the transcript with speaker labels lives in the same page. Three weeks later when there's a question about whether they actually requested the crop change, you can ask the agent: "Find every time we discussed the crop on image 0214 in the revision call." The moments come back, in plain text. The same capture-and-quote pattern is the spine of how to capture action items so they actually get done.
Pricing, contracts, and the weekly review
Photographers carry a lot of pricing context — base rates, addons, travel surcharges, usage rights for editorial versus commercial. A "Business" sub-vault with a current rate sheet, a page of past quotes (one entry per quote, with brief, rate, and whether it closed), and standard contract clauses helps. When drafting a new quote: "Read my last five quotes for editorial work in the same range. Draft a quote for this new prospect referencing what I charged for similar scope, and include my standard editorial usage clause." You're not building a pricing tool — just putting your own pricing context where the agent can ground its draft in what you actually charge.
Once a week, skim active shoot pages. Anything that needs a delivery, revision, or follow-up email goes on a single follow-ups list. Update shoot statuses that moved. Add location or lighting notes that didn't get captured during the week. To shortcut: ask the agent first — "What deliverables are due in the next ten days, and what client revisions are still open?" Saturday morning becomes ten minutes of housekeeping instead of a guilty hour.
A useful boundary: the vault holds notes, briefs, transcripts, and decisions. It doesn't hold raw files, edited images, or your gallery delivery. Lightroom, Capture One, Pixieset, ShootProof — those still do their jobs. Same for booking and invoicing — if you have HoneyBook or Studio Ninja, keep it. The vault is the place the thinking lives. For the broader sales-side workflow that runs alongside client deliverables, our guide on drafting emails and proposals inside your notes app covers the next move.
A calmer way to run a shoot pipeline
Shooting is going to be intense whether your notes are good or not. But the cognitive load between shoots — remembering what the client asked for, finding the location notes from last year, tracking which revisions are still open — that part is fixable. Move it into a vault, let the agent handle the boring searches, and you stop spending the morning before each shoot reassembling context.
Try Docapybara free — sign up, drop in the brief PDF for your next shoot, your shot list, and one set of location notes, and ask the agent for a one-page shoot plan grounded in all three.