A wedding photography questionnaire template that actually gets answered

TL;DR — Most of what goes wrong on a wedding day is an information problem, not a photography problem: a ceremony that started 20 minutes early, a family list that arrived by text at 4pm, a stepfather nobody warned you about. One form sent six weeks out prevents nearly all of it. Below is the whole thing — 17 questions, in order, with what each one is actually protecting you from. Copy it into whatever you use.

There is a version of the wedding day where you spend the morning reconstructing a timeline from a forwarded email chain, and a version where you arrive already knowing that the ceremony is outdoors at 4pm, the couple isn’t doing a first look, and the bride’s parents are divorced and shouldn’t be grouped together.

The difference between those two days is a form, sent once, several weeks in advance.

This one is the template we ship as a starter form in ApertureBook, reproduced in full so you can use it anywhere — a Google Form, a PDF, an email. The value isn’t the list; anyone can write a list. It’s the reasoning behind each question, which is what tells you whether to keep it, cut it, or add one of your own.

What is the form actually for?

Two things, and being clear about which is which keeps the form short.

1. Facts you will act on during the day. Times, addresses, names, groupings. If an answer won’t change what you do between 9am and midnight, it doesn’t belong on this form.
2. Context that changes how you behave. Family dynamics, someone recently bereaved, a couple who hates being posed. This is the part that gets skipped, and it’s the part that separates a photographer who handled the day gracefully from one who didn’t.

Everything else — package details, payment, image rights — belongs in the contract or the invoice, not here. A questionnaire that doubles as a sales document gets abandoned halfway through.

Their details: ask for confirmation, not for typing

The form opens with the contact block, and there’s a specific way to get it wrong: making a couple retype information you already have.

• Your full name
• Best email
• Best phone number — in case we need to reach you on the day
• Partner’s full name
• Partner’s phone number

You already know at least the first two from the booking. The right pattern is to pre-fill what you have and ask the couple to correct anything that’s changed, which turns five fields into a two-second glance. In ApertureBook the first three are tagged to the client record and arrive already filled in; the partner’s details are the only ones typed from scratch.

The partner’s phone number is the one people cut. Don’t. On the wedding morning the person you most need to reach is in a different building, and the phone you have on file is being held by a bridesmaid.

The day: six questions that build the timeline

• Wedding date
• Ceremony venue (address)
• Ceremony start time
• Reception venue (address) — leave blank if the reception is at the ceremony venue
• What time would you like coverage to start?
• What time would you like coverage to end?

The two coverage questions are separate from the ceremony time on purpose, and it’s the single most useful distinction on the form. Couples routinely assume that “eight hours of coverage” begins when they start getting ready, which may be three hours before you’d planned to arrive. Asking them to state a start and end time in their own words surfaces that mismatch weeks early, while it’s still a conversation about the timeline rather than an argument on the day.

Ask for the reception venue as a full address, not a name. “The barn” is not a navigable destination at dusk, and the venue’s own website will list the postal address of an office three miles away more often than you’d think.

Coverage: what they actually want photographed

• Which moments matter most to you? — getting ready, first look, ceremony, family portraits, wedding party portraits, couple portraits, reception details, speeches, first dance, cake cutting, sparkler exit
• Are you planning a first look?

The multi-select is doing something subtler than it looks. You’re not going to skip the ceremony because they didn’t tick it — you’re finding out what they’ll be disappointed about. A couple who ticks reception details and not wedding party portraits is telling you where to spend the light.

The first look question is a timeline question wearing a coverage question’s clothes. A first look moves the entire portrait block before the ceremony and buys you an hour of daylight; no first look means family portraits are compressed into the gap between ceremony and reception, and you need the list ready in advance. One yes/no reshapes the whole afternoon.

The family photo list: give them a format

• Family photo list — list the groupings you’d like, e.g. “Bride + parents”, “Both families”

Placeholder text matters more here than on any other question:

Bride + parents
Groom + parents
Both families together

Ask an open question and you get “just the usual family ones.” Show the format and you get a list you can read aloud. That’s the whole trick — the person calling out names in 20 minutes of chaos is you, and the list has to be readable at a glance, not decoded.

Two things worth telling the couple when you send this: keep it under about 15 groupings (each one costs roughly two minutes, and 25 groupings is an hour of daylight), and nominate a family member who knows everyone to round people up.

The question most photographers don’t ask

• Anything sensitive we should know? — divorced parents, a recent loss, someone who shouldn’t be photographed together — it helps us handle the day gracefully

This is the most important question on the form and the easiest to leave off, because it feels intrusive to ask.

It isn’t, if you say why you’re asking. The help text is not decoration — it gives permission to answer, and names the categories so the couple doesn’t have to decide what counts. What comes back is the thing you could not have guessed and could not recover from: the father who died in March and whose photograph will be on a chair, the two siblings who cannot be in the same frame, the parent who is not invited.

Nobody tells you this in an email chain about timings. They will write it in a form field that asks.

Vendors: one name, one number

• Wedding planner or day-of coordinator — name and phone number, if you have one

On a well-staffed wedding, the coordinator is the person who knows where the couple actually is, and having their number means you never have to interrupt the couple to ask a logistics question.

If they have no planner, the blank answer is itself information: you are the person who will be asked what happens next. Plan for that.

Anything else

• Anything else we should know?

Leave it open, put it last, and read the answers. It is where you find out about the surprise bagpiper, the ring-bearer dog, and the grandmother who can’t manage stairs.

The whole template, in order

Questions worth adding, depending on how you shoot

The 17 above are the ones that apply to nearly every wedding. These are situational — add them when they’re relevant to your work, and resist adding all of them:

• Getting-ready addresses, if you cover the morning. Two more locations, often nowhere near the venue.
• Videographer’s name and contact, if there is one. Ten minutes of coordination the day before is worth more than any amount of politeness on the day.
• Is there a meal for vendors, and when? Your one chance to eat is usually during the couple’s dinner, and it needs to be on the timeline rather than improvised.
• Exit plan — sparklers, confetti, a car. It’s a lighting setup, and it’s the last shot of the night.
• Anything you’d rather we didn’t photograph. A gentler companion to the sensitive question; some couples answer this one instead.

What not to add: anything you can look up, anything the contract already covers, and “describe your style in three words.” A form that takes 25 minutes gets abandoned at question nine.

When to send it, and how to get it back

Timing is most of the response rate.

• Send at 6–8 weeks out. Earlier and half the answers are “we don’t know yet”; later and you’re competing with seating charts and final headcounts.
• Send a reminder if it’s not back in a few days. This is dull, mechanical work that is nonetheless the difference between a 50% and a 90% return rate. Automate it if your tools can, and cap it at two — a third reminder reads as nagging.
• Set a due date about two weeks before the wedding, so there’s room to ask follow-up questions about whatever the answers reveal.
• Read it in front of them. The most valuable ten minutes in the run-up is a phone call that starts “I read your form — tell me more about the family portraits.”

Then print it, or keep it on your phone in something that works without signal. Rural venues have no bars, and a family list living in a browser tab is a family list you don’t have.

Where this template lives

Everything above is the Wedding day details starter form in ApertureBook, one of six we ship (wedding, portrait, newborn, senior, post-session feedback, new inquiry) so nobody has to start from a blank builder. Using it there rather than as a document changes a few things:

• Contact fields and the wedding date arrive pre-filled from the client record, so the couple confirms instead of retyping.
• Clients fill it in the app, or from a link in a browser with no login at all — no account, no password, nothing to remember.
• Answers autosave as they go, so a form abandoned at question nine can be picked up that evening rather than restarted.
• Reminders send themselves: at most two — one three days after sending, one two days before the due date — and they stop the moment the form comes back.
• You get an email when it’s submitted, and the answers export to a PDF to carry on the day itself.
• A few answers — phone, address, notes — fill in blanks on the client record. Only blanks: a form submitted months later never overwrites something you already have.
• A submitted form locks, so the answers you shot from can’t quietly change; you can reopen it if the couple needs to amend something.
• It deliberately doesn’t take file uploads. Forms collect session details, not documents — a shot list is text, and text is what you can read one-handed at a reception.
• The form sits on the same client record as their gallery, invoice and contract, rather than in a separate tool.

Copy the questions regardless. The list is the useful part, and it works in any tool you already have.

ApertureBook is client gallery software for photographers — private galleries on the web and in a native app your clients install, with forms, invoicing, contracts and e-signatures alongside them. Start free, or see the rest of the platform.