Wedding photography runs on details that are emotionally important and operationally easy to lose. The couple mentions a grandmother who needs a chair nearby. The planner changes the family portrait order. The venue has a quiet side entrance. Someone says the first look is private, then a cousin asks where to stand.
A client brief for a wedding photographer has to hold people, timing, locations, shot priorities, sensitivities, and post-production notes. Docapybara gives you one vault for the brief, calls, PDFs, questionnaires, timelines, and shot lists, with Capy available to search and summarize the material when the day gets close.
Make one page for the wedding
Create a parent page for each wedding. Put the couple's names, date, venue, package, planner contact, and the current state of the work at the top. Under that, link child pages for questionnaire, timeline, shot list, family portraits, vendor notes, location scouting, and post-production.
The page is not meant to replace your booking or gallery system. It is the working memory for the creative and logistical details. Contracts, invoices, and delivery can stay in the tools you already use. The vault holds the context you need to shoot attentively.
For the broader photography workflow, AI notes for photographers covers briefs, locations, revisions, and post-shoot logs beyond weddings.
Turn questionnaires into searchable context
Couples often answer questionnaires carefully, then the answers get buried in a form export or PDF. Upload the questionnaire or paste the answers into the wedding page. If it is a PDF, Docapybara converts it to markdown so Capy can read it as text.
Ask specific questions: "What family dynamics should I be careful about?" "Which moments matter most to the couple?" "Pull every named person who appears in the questionnaire." "What details should the second shooter know before arrival?"
The point is not to summarize away the couple's voice. It is to make the important details easier to find while preserving the original answers nearby.
Record planning calls when appropriate
Planning calls contain the details that do not fit neatly into forms. Tone, hesitation, priorities, worries, and small corrections. When recording is appropriate and everyone understands, keep the audio on the wedding page. The transcript with speaker labels gives you a readable record of who said what.
After the call, ask Capy to pull changes to the timeline, open questions, promised follow-ups, and emotionally important details. Review the result and turn it into a short client-facing recap if needed.
This workflow overlaps with notes during phone calls and action items that actually get done. The capture is useful because it becomes follow-through.
Build the shot list as a living table
A wedding shot list changes. Family portrait requests get added, the ceremony order shifts, rain moves portraits indoors, and the couple remembers one more heirloom detail. Use an inline database via the :::database::: directive for the shots that need tracking.
Helpful columns include moment, people, location, priority, timing, status, and notes. A row might be "bride with grandmother's locket," priority high, location getting-ready suite, timing before dress, status planned. Another might be "wide reception room before guests enter," timing cocktail hour, status pending.
Keep artistic flexibility outside the table. The database is for must-have commitments and logistical reminders, not every frame you might make.
Give family portraits their own page
Family portraits deserve their own page because the names and relationships matter. Write the grouping list in plain language, then add notes about mobility, divorced parents, children who need a snack nearby, and anyone who should not be placed together.
Capy can turn a messy list into a smoother order: "Reorder these family portraits to reduce movement for grandparents and keep immediate family first." You review it because only you know the human texture, but the agent can help with the mechanical arrangement.
For event-heavy work outside weddings, event planners: vendors and timelines is a useful cross-category companion.
Prepare the pre-wedding brief
A few days before the wedding, ask Capy for a one-page shooting brief grounded in the wedding page and linked notes. Include timeline, addresses, contact names, must-have images, family sensitivities, weather plan, gear reminders, and open questions.
This is where having the material in one vault helps. The brief can pull from the questionnaire, planning-call transcript, timeline PDF, venue notes, and shot-list database. You are not hunting through email on the morning of the event.
If you use assistants or second shooters, you can turn the brief into a clean handoff document. Keep private notes separate if they are not needed for the handoff.
Preserve post-wedding memory
After delivery, add a short post-wedding log. What went well, what ran late, which family grouping was tricky, which venue location worked, what edit notes matter if the couple orders an album, and what you would do differently at that venue.
These notes compound. The next time you shoot at the same venue, Capy can pull prior venue notes. The next time a couple has a similar timeline, you can reuse the lessons without trusting memory.
Try Docapybara free at signup. Create one wedding page, add the questionnaire and timeline, then ask Capy for the current must-have details before your next planning call.