How to run album selection when both families want a say

In many Indian weddings the album is not chosen by the couple alone. The bride's family wants their relatives in it, the groom's family wants theirs, and sometimes there are two albums, one for each side. The studio ends up in the middle, receiving two lists that overlap, contradict each other and arrive weeks apart.

The fix is to decide the rules before selection starts, and to collect both families' picks in one place where the studio can separate them.

The short answer

Agree at booking whether there is one album or two, who gives the final yes for each, and how many photos each side gets. Then let both families like photos in the same gallery, tell the system which side each person is from, and filter by side when you shortlist.

Step 1: settle the album structure at booking

Ask three questions while the booking is being confirmed, not after the wedding:

• One album or two? Many families order one album per side, or one main album plus a smaller one.
• Who decides for each album? One person per side gives the final yes. Everyone else suggests.
• How many photos per album, and by when? A clear target and a closing date stop selection from dragging on.

Write the answers in the booking message, so nobody remembers them differently later.

Step 2: decide which functions belong to whom

Some functions belong mostly to one side, such as a Haldi at the bride's home. Others are shared, such as the pheras and the reception. Tell each family which functions they choose from, and keep the shared functions for the couple to decide together.

Step 3: collect picks in one place, labelled by side

The hard part is not the choosing. It is keeping track of who chose what. When both families send separate WhatsApp lists, the studio has to merge them by hand.

A better setup is one gallery where everyone likes photos, and each person says which side they are from. Some galleries ask guests "Which team are you in?" when they first open the gallery, so every like is already labelled. The studio can then filter: only the bride's side, only the groom's side, only the couple's own picks, or the most liked photos overall. On Vyavasth this happens in Smart Selects.

Step 4: shortlist, then send one list per decision maker

From the filtered likes, the studio makes a shortlist for each album and sends it to the one person who decides for that album. One yes per album, not a group discussion.

Step 5: handle overlaps

The same photo often appears on both sides' lists, such as a group photo at the reception. Decide upfront that shared photos can appear in both albums, and count them toward each album's total.

Mistakes to avoid

• Collecting lists separately on WhatsApp. You will spend days merging them.
• No single decision maker. Selection becomes a family debate that never closes.
• Not agreeing photo counts per album. Each side picks far more than the album holds.
• Starting selection before the rules are agreed. Changing rules halfway restarts the whole process.

For more on getting selection finished, see why album selection takes months.

Frequently asked questions

Should there be separate albums for the bride's and groom's families?

It depends on the families. Many Indian weddings have one album per side, or one main album plus a smaller one. Agree it at booking so selection starts with a clear structure.

How do I stop both families from changing the selection again and again?

Name one decision maker for each album and agree a closing date. Everyone else can suggest photos, but only the decision maker sends the final yes.

How do I know which family selected which photo?

Collect selections in one gallery where each person says which side they are from. The studio can then filter the likes by the bride's side or the groom's side instead of merging separate lists.

What about photos both families want?

Let shared photos appear in both albums and count them toward each album's total. Agree this rule before selection starts.