I kept running into the same problem while researching how wedding photographers and videographers prepare for a wedding day.
Everyone seems to agree that a shot list can be useful. In practice, many wedding professionals either do not make one, make one very late, or end up with a document that is too long to use during the actual wedding.
The information is usually there. It is just spread across emails, questionnaires, Google Docs, spreadsheets, WhatsApp messages, notes and screenshots on a phone.
The couple has mentioned the important family groups somewhere. A first look was discussed in another message. There is a note about golden hour. Someone should be photographed early. Two family members should not be placed together. The cake cutting may happen, but nobody knows exactly when.
Then the wedding shooter still has to turn all of that into a shot list and somehow connect that shot list to a timeline.
That is the part I have been trying to solve.
Not by automatically generating a supposedly perfect wedding plan. I do not think that would be realistic. Every wedding is different, and software should not quietly make decisions that belong to the person actually shooting the day.
The goal is simpler: reduce the amount of manual translation between what the couple tells you and the plan you eventually use.
Starting with a more useful intake
The intake in Wedding Desk is becoming more structured.
Instead of only asking broad questions, it can collect information that is directly useful later in the planning process.
The People & group photos section lets the couple describe important people, relationships, family sides and requested photo combinations. It can also include practical details such as someone who should be photographed early or people who should not be grouped together.
There is also a Moments & priorities section.
The couple can indicate whether they are planning a first look, private vows or letters, wedding-party portraits, golden-hour portraits, parent dances, cake cutting, a grand exit and several other common wedding moments.
They can also add something less predictable. A cultural or religious moment. A tradition. An object, person or detail that absolutely should not be missed.
This is still an intake. It is information from the couple, not a finished production plan.
That distinction matters.
Turning answers into Shot List suggestions
This is where the system starts becoming genuinely useful.
When the couple submits the intake, Wedding Desk can turn the relevant answers into Shot List suggestions.
Requested family groups can appear as suggestions. Selected moments can appear as suggestions. A must-not-miss note can become a high-priority request. The system can also suggest common family combinations based on the people the couple entered.
Nothing is added automatically.
The wedding photographer or videographer reviews every suggestion and decides whether to accept or ignore it. Once accepted, it becomes a normal Shot List item that can be edited, reprioritised or removed.
Automation should remove repetitive work. It should not remove professional judgement.
That may sound like a small distinction, but it solves an important problem.
I do not want Wedding Desk to silently fill a shot list with fifty items because an algorithm thinks they might be useful. I want it to prepare the material, show where it came from and let the shooter decide what belongs in the actual plan.
What happens when the couple changes something
Another problem with intake-based planning is that answers can change.
A family group is removed. A first look is cancelled. A special moment is added. The couple changes the people included in a requested photo.
The easy technical solution would be to overwrite the Shot List item.
That would also be a terrible solution.
The wedding shooter may already have edited the title, priority, notes or placement. Those decisions should not disappear because the couple submitted a newer answer.
The current system therefore treats changes as something to review.
Wedding Desk can show that the Intake has changed and ask whether the new information should be applied. They can keep the current item, apply the Intake update, remove the item or restore something that was previously removed.
Again, it is not fully automatic.
It is controlled automation, which is a far more useful version of it for this kind of work.
Connecting the Shot List to the Timeline
A shot list on its own is only half the solution.
A list of twenty important shots is not very helpful if you still have to work out when each one should happen.
The Shot List and Timeline are therefore becoming more closely connected.
A family group can be linked to the Family photos moment. Golden-hour portraits can be connected to an existing golden-hour block. A first look can be linked to the first-look moment in the Timeline.
When a suitable moment already exists, Wedding Desk can suggest that connection. When several moments could work, the shooter chooses one. When the moment does not exist yet, the system can offer to add it to the Timeline.
That action is always explicit.
Selecting golden-hour portraits in the Intake does not suddenly schedule golden-hour portraits at a random time. The Timeline still needs an actual time, location and professional review.
The system helps connect the information. It does not pretend to know the wedding better than the person planning it.
Building the first Timeline
I also wanted to improve the other side of the same problem: where do you start when the Timeline is still empty?
Wedding Desk now has several built-in Timeline templates for common wedding structures, including full days with or without a first look, church ceremonies, civil ceremonies, shorter coverage and weddings with multiple locations.
These are not just fixed example schedules.
Instead, they are built around anchors such as coverage start, ceremony start, reception start and coverage end. When Wedding Desk already knows some of those times from the Intake, it can use them as the starting point.
The remaining moments are placed around those anchors.
Anything that cannot be calculated safely remains unresolved and needs confirmation. Travel time, for example, should not be invented just because the software wants to produce a complete-looking Timeline.
The result is a much faster first draft, but still clearly a draft.
Presets and Wedding starters
There are now two additional shortcuts for wedding shooters who often use similar workflows.
Moments presets let you save a common starting selection for Moments & priorities. For example, a preset for a full-day wedding with a first look, wedding-party portraits, golden hour and parent dances.
Timeline templates let you reuse a day structure.
A Wedding starter combines one Moments preset with one Timeline template.
When creating a new project, you can select that Wedding starter. Wedding Desk then prepares the Intake starting choices and preselects the relevant Timeline template.
It still does not submit the Intake for you. Shot List suggestions are not accepted on your behalf, and no final Timeline appears without review.
It simply removes several repetitive setup steps.
That is exactly what I want this system to do.
Timing family photos more realistically
Family photos are one of the clearest examples of why these connections matter.
A Timeline may contain a twenty-minute Family photos block. The Shot List may contain twelve accepted family groups.
Those two pieces of information should not live in isolation.
Wedding Desk can now compare the number of linked family groups with the planned duration and show whether the available time looks realistic, tight or clearly too short.
It does not change the Timeline automatically. It does not guarantee that every group can be photographed within a specific number of minutes.
It is simply a warning that the current plan may not match the amount of work.
That warning is far more useful than discovering the problem while standing outside the ceremony venue with twelve groups waiting and dinner already starting.
Where this is heading
This is what I have now, and it seems to work well.
But, as will probably become a recurring theme throughout this project, it is not yet in its final form. The connection between Intake, Shot List and Timeline may still develop in different directions, but I am happy with the foundation that is now in place.
The actual On The Day experience also can still take several forms. It needs to work fully on both phones and tablets, and it will eventually become a dedicated app.
What is becoming clear is the full path.
The couple provides the information once. Wedding Desk turns the relevant parts into suggestions. The shooter reviews them. Accepted shots connect to the Timeline. The Timeline becomes the structure for the wedding day. On The Day can then show the right shots, notes, people and practical details at the moment they matter.
No separate Google Doc. No spreadsheet beside the Timeline. No collection of phone screenshots. No digging through old messages to remember which family groups were requested.
One workspace, with the information moving through it in a controlled way.
I am not claiming that I have completely solved wedding-day planning. I do think this is starting to solve one of its more frustrating parts: turning information that's all over the place into a plan that is actually usable while shooting the wedding.
