How do you photograph your first wedding, start to finish?

How to use this guide

Read it end to end once, a month or more before the wedding, following none of the links; the goal on the first pass is the shape of the whole day in your head. Then work through it again with the links, because every section here is the compressed version of a full chapter: this page is the map, and the chapters are the territory. In the final week, stop reading this and read only the chapters that scare you. And if you are holding a coffee and a phone with a wedding three days out, start with the quick version instead and come back here after.

The month before: where the day is actually won

By a month out the business layer should be finished: a signed contract, the retainer paid, and the balance scheduled to clear before the day, all covered in the business pillar and worth confirming now rather than discovering missing later. What remains is the photography planning, and it has three deliverables. First, the walkthrough and shot conversation: see the venues at the hour you will shoot them, read the light the way the natural light chapter teaches, and have the conversation that surfaces what this couple actually cares about. Second, the timeline, built backwards from sunset with real durations and buffers, because the schedule most couples draft has portraits at the wrong hour and zero slack. Third, the named family list: groupings with names, not descriptions, plus the appointed relative who can find people. Photographers who arrive with those three documents have already made most of the day’s decisions while calm.

The week before: the boring ritual that saves you

The final week is logistics, run as ritual rather than improvisation. Build the one page day sheet: every address, every contact number, arrival times, the timeline, the family list, sunset time, and the rain call plan. Confirm the timeline with whoever runs the day, planner, coordinator, or the most organized parent, and flag any gap you cannot work with now, not on the morning. Then run the physical ritual: charge everything, format cards in the cameras that will use them, fire every flash, pack to the packing list, and shoot ten test frames with both bodies the night before. If it rains that week, so much the better: read the rain playbook before you need it, since the 9am rain conversation goes better when you already know your answer.

Gear that survives the day

The honest capability floor is shorter than the internet suggests: two camera bodies, because a wedding is the one job where a dead camera cannot mean a pause; dual card slots writing duplicates, per the backup workflow; a fast prime or two and a working zoom; one flash you know cold, plus the beginnings of the two light kit; and double the batteries and cards your estimate says. Rent what you lack rather than buying in a panic, and spend the week’s practice time on the lighting pillar rather than on new equipment, because the dark reception at the end of the night is the only technical wall on the day that preparation genuinely cannot talk its way around.

The day, hour by hour

Arrival and establishing. Arrive early enough to walk the spaces before they fill. Shoot the venue, the room, the details, flowers, stationery, the dress and jackets, first: they are the frames with the most patience, and they disappear under people by noon. This is also when you take one test frame in each space and set your working exposures, so the first human moment does not double as a light meter.

Getting ready. Small rooms, mixed light, six people talking to you at once: the getting ready chapter covers the craft, and the summary is: find the window, clear what you can, work wide to tight, and let real moments finish before you improve them. The frames that matter here are hands, faces, and the people helping, not an inventory of the room.

First look, if there is one. It is a timeline decision as much as an emotional one: a first look moves couple portraits and often family formals before the ceremony, buying enormous slack later in the day. Photograph it from far enough away that the moment belongs to them, with the long lens, and resist directing it beyond placing them in good light.

The ceremony. The one segment with no second chances anywhere in it. The ceremony chapter covers positions and movement rules; the spine version: settle the movement rules with the officiant before guests arrive, protect the processional, the reaction at the top of the aisle, the vows, the rings, the kiss, and the recessional, and take the dependable frame before attempting the ambitious one. In a dark church with flash banned, the dark church chapter is the survival guide, and its first lesson is positioning over ISO.

Family formals. A logistics problem wearing a photography costume. The eleven minute system: largest grouping first, release people as groups shrink, the named list in your hand, the appointed relative fetching, two frames of every grouping. Run it with a calm, audible voice and it finishes on time; run it by consensus and it eats the portrait window.

Couple portraits. Whatever the timeline says, plan for the twenty minute version: a repeatable sequence of five setups you can run in any venue, prompts that produce movement rather than poses, and the discipline to stop at enough. If the light is golden, the golden hour chapter is the exposure mechanics; if it is noon, the same chapter’s shade rules save the set.

The reception. The running order, entrances, toasts, first dances, cake, open dancing, exit, each with different demands, is the reception chapter; the light that carries all of it is the reception flash cheat sheet, which is the single most useful page on this site to have memorized. Eat when the couple eats, because nothing photogenic happens during dinner and it is the only pause the day offers. Stay for the exit you promised, and confirm the send off time with the coordinator at dinner, not at midnight.

When it goes wrong, because something will

Every first wedding contains one failure: weather, a collapsed timeline, a dead camera, a missing relative at formals, a DJ who moved the first dance without telling you. The professional response is the same in every case: triage by irreplaceability, protect what happens once, and renegotiate the rest calmly with whoever owns the schedule. Rain has a complete playbook. Gear failure is why the backup workflow exists and why the second body is not optional. Shooting alone multiplies every failure mode, and the solo chapter is honestly about failure planning more than photography. What converts a bad moment into a bad reputation is almost never the failure itself; it is improvising a response you could have decided in advance.

After the day: where the job is actually finished

The night ends with the same night ingest: both card copies onto two separate drives before you sleep, cards untouched until delivery. Then the delivery arc: cull to the number your contract promised, covered with the deciding math in how many photos; edit consistently; ship a preview set inside the first week so the silence never gets heavy; and deliver the gallery on the date you promised, or say so before the date per the late photos scripts, which you will hopefully never need. Then send the invoice’s last paperwork, back up the delivered gallery, and write yourself the honest one page debrief, what ran long, what you missed, what you will pack differently, while it still stings. That page is the difference between shooting one wedding twelve times and getting twelve weddings better.