If you are a studio shooting 5 to 10 weddings a month, you are probably running the following system: each event has a WhatsApp group with the family, a Google Drive folder with the raw images, another folder for the edited set, a payment reminder thread, and a spreadsheet where you track who has paid and who has not. By the time you are juggling six simultaneous albums, the spreadsheet has 12 rows, five WhatsApp chats are asking for updates, one client's payment has slipped through the cracks, and you are spending Monday morning reconstructing where every album stands instead of editing.
Right now, the default workflow in most Indian studios looks like this: dump images into a Drive folder, paste the link into WhatsApp, track payments in a spreadsheet. It works — until it doesn't. If you are still doing the full deliver-then-chase cycle, see how to deliver wedding photos to clients in India for the stage-by-stage breakdown.
The fix is not a better spreadsheet. It is a single delivery ledger — a view that shows every album you are working on and its current stage at a glance: uploaded, shared, awaiting selection, payment pending, paid, delivered. No separate WhatsApp hunting. No reconciliation against a spreadsheet. One place that tells you what needs your attention right now.
Who this is for: growing Indian wedding and event studios — 2 to 8 shooters, 20 to 50 weddings a year — where the bottleneck has shifted from shooting capacity to delivery management.
The real problem is not organisation — it is attention
A spreadsheet is perfectly capable of tracking 10 albums. The problem is that a spreadsheet does not tell you anything unless you open it, update it, and cross-reference it against your WhatsApp chats, your Drive folders, and your bank statement. The work of keeping the spreadsheet accurate is separate from the work of actually moving albums through the pipeline, which means the spreadsheet is always slightly behind reality.
The real operational cost is context-switching: every time you need to figure out where an album stands, you spend 5 minutes checking three different sources. Multiply that by 10 albums and multiple check-ins per album, and you have lost an hour a day to the simple act of figuring out what needs to happen next.
A delivery ledger solves this by being the single source of truth that updates itself as you and your clients take actions: when the client selects their photos, the ledger shows selection complete. When they pay, the ledger shows payment received. You do not update the ledger — the workflow does.
What a delivery ledger looks like in practice
Imagine opening a single page that shows:
| Event | Date | Stage | Days since upload | Action |
|---|---|---|---|---|
| Sharma wedding | 2 Jun | Selection in progress | 5 | — |
| Verma wedding | 28 May | Payment pending | 12 | Send reminder |
| Patel engagement | 15 May | Delivered | — | Complete |
| Iyer wedding | 10 Jun | Upload in progress | 1 | — |
The column that matters most is Stage. You scan for anything in "payment pending" or "selection in progress" that has been there for more than a few days, and those are the albums that need your attention today. Everything else is on track.
This replaces:
- The spreadsheet where you manually update payment status
- The WhatsApp search for "did they ever send the selections"
- The mental tally of "who still owes how much"
- The Monday-morning reconciliation ritual
The Indian studio reality that makes this harder
Indian wedding albums are not straightforward because of three factors that every studio deals with and no spreadsheet can fully capture:
Joint-family decisions. The bride selects some photos. The mother wants to add more. The groom's sister has her own list. Selections arrive from multiple WhatsApp numbers over several days. A delivery ledger captures this naturally — it shows "selections in progress" until the studio marks it complete, regardless of how many family members contributed.
Multiple events per booking. A single wedding client may have a mehendi, a sangeet, a ceremony, and a reception — each its own album, each on its own timeline, but all belonging to one booking. A good delivery platform groups them under one client while keeping each event's stage separate.
Payment spread across multiple transactions. The advance was paid at booking. The balance is due on delivery. Sometimes there are add-on purchases (extra prints, additional edited photos). A ledger that tracks total paid vs. total due for each album stops you from having to remember who has paid what across five different UPI transactions.
Why this becomes critical past 5 albums per month
At 3 albums a month, your mental model is enough. At 10, it is not — and the cost shows up in specific ways:
- Payment leakage. You forget to follow up on one balance of ₹15,000. It sits for three weeks. The client eventually pays after a reminder, but the delay happened because you simply did not see it. (The structural fix for this is collecting payment before delivery — a ledger shows you which albums are stuck, and a payment gate ensures they do not stay stuck.)
- Resend requests. A client says they cannot find the link. You dig through a chat from two weeks ago. This happens 3–4 times per album cycle.
- Status embarrassment. A client asks "where are our photos?" and you have to check three sources before answering. Each time, the client's confidence drops a little.
A delivery ledger eliminates all three because the information is always in front of you, always current, and always accessible from your phone.
Where the spreadsheet still makes sense
Spreadsheets are excellent for things a delivery ledger is not designed to handle: tax calculations, annual revenue tracking, invoice generation, and long-term business planning. The point is not to eliminate the spreadsheet — it is to stop using it for the one job it is worst at: tracking real-time operational status across multiple simultaneous workflows.
How PhotoSelect approaches this
PhotoSelect's studio dashboard includes exactly this kind of delivery ledger. Each event gets its own album, and the studio sees every album they are working on in a single view: which are uploaded, which have been shared via a WhatsApp-ready link, which are awaiting client selections, which have payment pending, and which are fully delivered. The stage updates automatically as the client interacts — selecting photos, making a payment — so the studio never has to manually reconcile a spreadsheet against WhatsApp messages and bank notifications.
The result is that a studio shooting 10 weddings a month can see, in 10 seconds, exactly where every album stands — without opening a single chat thread.
(PhotoSelect charges a flat studio plan and takes zero commission on client payments — the gateway fee is the only deduction. The delivery ledger is part of the studio dashboard, not a separate add-on.)