Wedding Photographer Timeline Template: A Day Schedule Built With AI

Build a template of fixed blocks with set buffers (getting ready, ceremony, family groups, drinks, golden-hour portraits, evening), have AI fill it from the couple's answers and the venue's times, then run clash checks against the venue's rules, the planner's schedule and the couple's group list. You supply the sunset and drive times yourself, because an assistant will guess them.

Sample wedding-day timelines are easy to come by. A timeline rarely fails because the order is wrong; it fails because it collides with something the photographer did not know: a dining room the venue resets at half past four, a speeches slot the planner placed in the golden hour, or fourteen family groups the couple forgot to mention. The checks are the part worth building.

Follow me on Instagram@sagnikteaches

Everything below follows one imaginary wedding. Each time and count is made up to show the method, so substitute your own.

Connect on LinkedInSagnik Bhattacharya

The template: fourteen blocks, each with a rule and an owner

Every block has a planning rule and an owner, the person who can say whether the block really fits. The rules are starting points, not standards, so replace them with yours. A block with no owner is a guess.

Subscribe on YouTube@sagnikteaches

Two rows carry most of the weight. Family groups are priced by count, not by feel: 12 groups at three minutes is 36 minutes before any buffer. And golden hour is tied to sunset, not to the clock, so it wanders through the day with the seasons. At a late-summer wedding it may sit in the middle of dinner; in midwinter it may land before the ceremony has finished.

Numbers you source yourself: sunset, drive times and group counts

An assistant is good at arranging blocks and poor at facts about the real world, so keep four numbers out of its hands.

• Sunset. Take it from a sunset table or a weather service for the venue's date and place, and type it into the prompt. An assistant will state a sunset time in a confident sentence and may be wrong by enough to matter. In this example sunset is 19:42, so golden-hour portraits start at 18:42 and run 25 minutes to 19:07.
• Drive times. Use Google Maps with the departure time set for the hour you will actually travel; Depart at works for one destination at a time. In the example the map says 22 minutes from the hotel to the venue, and the plan allows 30 with an 8-minute buffer.
• Family groups. Count them from the couple's list. The example list has 14: 14 x 3 minutes is 42, plus 10 buffer is 52, rounded to 55.
• Venue windows. The hours when rooms are open to you and when they are closed, in the venue's own words. In the example they arrive later, in the venue's reply shown further down: the dining room is open to photographers until 14:45 and closed from 16:30 to 17:30 for the reset.

Stage one: a draft that looks right and is not

Start with the lazy prompt, because it shows what goes wrong.

Build a wedding-day photography timeline for me from the details below, using my template. Include golden-hour portraits.

Details: getting ready at a hotel from 11:30; ceremony at 15:00 for 40 minutes at the venue; reception at the same venue; dinner is served in the evening; the couple have a long list of family groups; coverage ends at 21:30.

What comes back is tidy, complete and confident. Four of its lines are shown below (illustrative), with what the assistant silently assumed.

None of those four assumptions came from your details. Each is phrased so plausibly that a skim lets it through. The fix is a prompt that forbids estimating and forces a visible gap.

Build a wedding-day photography timeline from my template and the details below. Use ONLY times, counts and rules I supply. Where I have not supplied a sunset time, a drive time, a number of family groups or a venue window, write ASK in that row instead of estimating. Output a table: start, end, minutes, block, location, who confirms. Each block must start when the previous one ends, and the minutes must add up to the coverage length. Then list every assumption you made.

Template rules: [paste the rules table]
Couple: [paste their answers]
Venue: [paste the venue's times and rules]
Typed by me: sunset 19:42; hotel to venue 22 minutes by car at that hour; 14 family groups

With the three typed numbers supplied, the draft now puts golden hour at 18:42-19:07, allows 52 minutes for the groups and 22 minutes for the drive, and marks the dining-room details row ASK because no venue window has been supplied yet. In the example you fill that row with the slot that seems natural, 17:00-17:30, and move on to the checks. That is a guess, the very thing the ASK was there to stop, and the clash finder further down catches it. A prompt like this one is worth saving with your template; for more general prompts, the ChatGPT prompts for wedding photographers cover timelines, group lists and albums.

Stage two: the venue, the planner and the couple each get a say

The draft is only a proposal until the people who control the constraints have seen it. Each gets a short list, and the questions are the same for every wedding, so keep them in your template.

Eight questions for the venue

1. What is the earliest access for photographers, and for the dining room before guests?
2. When are rooms closed for resets, and when can I go back in?
3. Where is the ceremony, what is the indoor backup, and where may I stand?
4. What are the rules on flash, tripods, drones and no-photo areas?
5. Which area faces the sunset, and is it open in the evening?
6. Where can photographers park and unload, and is there room for a second shooter?
7. How are the lights set during speeches and the first dance?
8. Are there curfews or finish times that affect coverage?

Five asks of the planner

• The current version of the master timeline, and which version is final.
• Where dinner service, speeches and cake sit, and how fixed each is.
• The couple's transport times, and the wedding party's.
• Who decides if the day runs late, and how they will tell you.
• Whether suppliers get a meal break and when.

The planner's master timeline is the document the whole day runs on, so ask for it before you finalise yours; the wedding planner's AI workflow shows how it is built from enquiry to final timeline.

Six asks of the couple

• The family groups list, in order, with who gathers each group.
• Anyone who needs extra time, a chair or a quiet moment.
• Delicate family arrangements, asked privately and kept off any shared document.
• The five shots they would be upset to miss.
• Whether they want a first look.
• How they feel about leaving the party for 25 minutes of portraits.

Turning a venue's reply into windows you can plan around

Venues reply in friendly prose, and the constraints you need are buried inside it. This is where an assistant earns its place: it can pull every window and rule into a table, provided you stop it filling gaps. Here is an illustrative reply.

Hi! Photographers can come into the barn from 12:30 until 2:45 pm to photograph the room. After that the team start laying up, and the room is closed to everyone from half four to half five while we do the final reset. No flash during speeches please, and no drones anywhere on the estate. The terrace faces west and stays open until 10 pm. Parking is behind the stables, with unloading from 12:00.

Extract every time window and every rule from the venue's reply below into a table with three columns: item, what the reply says, and the time in 24-hour form. Where the reply does not mention something I have listed (ceremony flash, tripods, second shooter parking, lighting during speeches), write "not stated" instead of assuming it is allowed. List any ambiguity as a question.

Reply: [paste the reply]
Items to check: [paste your eight questions]

A good extraction gives you 12:30-14:45 for room access, a closed window of 16:30-17:30, no flash during speeches, no drones, a west-facing terrace open until 22:00 and parking behind the stables from 12:00. The failure to watch for runs the other way: a table that says "flash at the ceremony: allowed" because the reply was silent. Silence is not permission. Every "not stated" becomes a question back to the venue, and that is the cheapest way to learn about a no-tripod rule before you are standing in the aisle.

The family groups list: order it, count it, name a wrangler

Couples describe their groups in a sentence, and a sentence is hard to schedule. This is an illustrative one.

We'd like the usual family photos: everyone together, then each side's close family, each of us with our parents and grandparents, our extended families, then us with the wedding party, our friends from university and from work, the little ones, and both sets of parents together.

Turn the couple's paragraph into a numbered list of family groups, one line each, with the approximate number of people and who is in it. Put the largest groups first while everyone is still present, and keep each side's family together. Do not merge groups and do not add groups they did not name; if something is unclear, write ASK. Count the groups at the end.

[paste the paragraph]

The assistant's first ordering, with the headcounts you would confirm with the couple (illustrative):

That is 14 groups, so 14 x 3 = 42 minutes and 52 with the buffer, the figure the whole schedule rests on. Two edits are needed. The children are last, when they are least patient, so move them to third. And the grandparents are scattered through the list instead of being done early, when seating is easiest and they are fresh. The assistant ordered by size and family, not by people's patience or stamina, which only you can judge. Give one named person from each side the numbered list and a role: they gather the relatives, you shoot. Without a wrangler, the 3 minutes per group is the first number to fail. For turning a couple's brief into a shot list, the same-day quotes and shot lists tutorial goes further.

A clash-finder prompt and what it found

Paste the corrected timeline, the planner's version and the venue's rules, and ask for clashes only. Telling the assistant not to fix them keeps the decisions with you.

Compare my timeline with the planner's master timeline and the venue's rules below. List every clash: blocks that overlap, a block inside a window when a room is closed or I am not allowed in, a block shorter than its rule allows, and any block placed in a time I did not supply. For each clash say who must confirm it. Do not change the timeline; I will decide the fix.

My timeline: [paste]
Planner's timeline: [paste]
Venue rules: [paste]

Run against the example, the assistant reported three items.

1. Travel 13:35-13:57 is the 22-minute drive with no buffer, but the rule is map time plus 8 to 10 minutes. Confirm with you; allow 30.
2. Dining-room details 17:00-17:30 fall inside the venue's closed window of 16:30-17:30. Confirm with the venue, which says the room is open to photographers until 14:45.
3. Golden-hour portraits 18:42-19:07 overlap the planner's speeches at 18:45-19:15. Confirm with the planner.

The last item is the interesting one. In the lazy draft the golden-hour block sat at 19:10, after the speeches, so nothing looked wrong. Typing the real sunset moved the block to 18:42 and exposed the clash. The answer was a phone call: the planner agreed, after checking with the caterer, to move dessert and speeches 30 minutes later, so speeches now run 19:15-19:45. The room details moved to 14:05, before guests arrive, because the venue allows photographers in until 14:45.

Remember what the check cannot do. It compares the documents you paste, nothing more. If the venue's no-flash rule during speeches is not in the paste, the assistant will not know it exists. Read the venue's own event sheet yourself before you trust a list of "no clashes".

The timeline after the checks, minute by minute

This is the version the example wedding ends up with. The "basis" column shows where each number came from, which is what you will want when someone queries it.

Add the minutes: 125 + 30 + 20 + 35 + 40 + 10 + 55 + 50 + 10 + 57 + 25 + 8 + 30 + 30 + 5 + 70 is 600, which is the ten hours from 11:30 to 21:30. Make that sum a habit. Assistants misadd, and a timeline whose blocks do not add up to the coverage length has a hole in it somewhere. In a sheet, =B2+TIME(0,C2,0) will compute each end time from the start and the minutes.

Notice the "flex" notes in the basis column. Mark every block as fixed or flexible. The fixed ones are tied to something outside your control: sunset, the ceremony, the planner's speeches. The flexible ones have a minimum length and give time back when the day slips.

Rain, a late ceremony and extra family groups

Three changes are common enough to plan for in advance, and two of them can land on the same day.

• A late ceremony. If it starts 20 minutes late, everything after it shifts, but golden hour is fixed to sunset. The flexible blocks before it give time back: drinks candids shrink by 15 minutes and the reset by 5. The ceremony delay is absorbed without touching the portraits.
• Four more groups on the morning. The couple add relatives. Four groups at three minutes is 12 extra minutes, which the drinks candids block gives back.
• Both on the same day. Here the flex runs out. A 20-minute late start plus 12 minutes of extra groups needs 32 minutes, and the drinks candids (50 down to 30) and the reset (10 down to 5) can give back only 25. Decide in advance where the last 7 minutes come from: move the two extended-family groups to a quick shot during the evening, or accept missing the first minutes of guests taking their seats. Agree the choice with the couple when they send the group list, and write it in your private notes, so nobody has to negotiate it on the lawn.
• Rain. Write the alternative for each outdoor block now, with a decide-by time. Golden-hour portraits might move to the covered terrace and the barn's west-facing doors for the same 25 minutes, decided at 18:00. Family groups might move under the ceremony canopy, decided at 15:30. A plan B that is only thought of at 18:00 has no time left to be good.

Ask the assistant to draft each alternative as a second table, then run the clash finder on it as well. A rain timeline is a timeline too, and it collides with the same people.

Sending it, freezing it and learning from the day

Number every version and put the date on it: version 1 is the draft, version 2 follows the checks, version 3 is the one the couple and planner approved. Send the couple a clean version with times and names only, and keep your fixed and flexible notes for yourself and a second shooter. Send the planner, the venue contact and the DJ the parts that concern them; the DJ builds a run sheet from the same facts, as the wedding DJ questionnaire tutorial shows. Agree a freeze date, about ten days out, after which changes arrive through the planner, in writing.

After the day, record what actually happened beside what was planned.

This is an illustrative record, and a single wedding proves nothing. After ten weddings it becomes your own data: if ceremonies keep starting around ten minutes late, your default buffer should be ten minutes; if groups take less than three minutes each, change the rule. An assistant can work out the average difference per block from a pasted log, but check its arithmetic against a spreadsheet, as with any sum. Over a season the template stops being a guess and becomes a record of how your weddings actually run.

Wedding photography timeline questions

How long should family group photos take?

Work it out for each wedding: the number of groups times about three minutes, plus ten minutes of buffer. Fourteen groups need around 52 minutes. Ask the couple for the list in advance, shoot the largest groups first while everyone is present, and agree who will gather relatives so you are not hunting for people.

Can AI work out sunset and golden hour for a venue?

Do not rely on it. Take the sunset time from a sunset table or weather service for the venue's date and place, type it into the prompt, and let the assistant do only the subtraction. An assistant can state a sunset time in a confident sentence without having looked anything up.

How early should I send the timeline to the couple and planner?

Send a first draft once the ceremony and dinner times are known, ask for corrections within a week, and freeze it about ten days before the date. If a planner holds the master timeline, send yours to them first and align to theirs, because they will be the one calling changes on the day.

What if sunset falls during dinner?

Plan a 20 to 25 minute break from the meal, agree it with the couple and the planner, and tell the caterer so the main course is not served as they leave. Put it in the timeline as a fixed block, with a bad-weather alternative decided by a set time.

Further reads

• Zapier for Photographers: Automate Enquiries, Contracts and Reminders — Automate the reminders that go with a fixed timeline.
• How Photographers Can Handle Client Emails With AI — Keep timeline and reminder emails short and consistent.
• How to Price Photography Packages: A Cost-per-Shoot Model With AI — Price coverage hours so the timeline does not erode margin.
• HoneyBook or Dubsado for a Wedding Photographer? Costs and AI Compared — Client-management tools that can hold the timeline and reminders.
• Is AI Culling Worth Paying for as a Wedding Photographer? — Whether AI culling earns its fee once the day is shot.
• 7 ChatGPT Prompts for Makeup Artists: Quotes, Timelines and Kit Lists — Seven fill-in ChatGPT prompts for bridal quotes, day-of timelines and kit lists, each with a realistic sample output and what to correct.
• 8 ChatGPT Prompts for DJs: MC Scripts, Toasts and Announcements — Eight fill-in ChatGPT prompts for wedding and party DJs: entrances, toast introductions, announcements and a pronunciation sheet, with sample lines.
• Best AI Photo Editor for Photographers: Cull, Edit or Retouch First? — Choose an AI photo editor by workflow stage: time a paid gallery, find the slowest stage, and test one tool on the same wedding shoot.
• DJ Event Checklist: Gear, Timeline and Backup Plan Built With AI — Pre-event, load-in, set and pack-down lists for DJs, a ranked backup kit, a music failover table and the prompt that has AI build them for you.
• Wedding Catering Proposals: Tastings, Quotes and Follow-Ups With AI — A caterer's workflow for wedding proposals: tiered quotes you can check, tasting invites, guest dietary lists and follow-ups after the tasting, drafted with AI.
• Wedding Planner Client Questionnaire: Answers to a Brief With AI — Twenty discovery questions for wedding clients, how to send them to each partner, and an AI prompt that turns the answers into a one-page brief you can check.
• AI Tools for Filmmakers: Script Breakdowns, Shot Lists, Call Sheets — Assistants or production platforms for breakdowns, shot lists and call sheets on a small paid shoot, with worked examples and what to check by hand.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google Maps Help on departure times (checked October 2026).