Three couples, one Saturday in August
A couple from a video call last week asked you to hold the second Saturday in August while they visit their venue again. Another couple emailed about the same date two days later, and you told them it was pencilled in and you would let them know. Then a third couple, a referral from a venue coordinator you like working with, asked about it this morning.
You think the first hold was until Friday. Or was it the Friday after? The note is in a message thread somewhere. The couple have gone quiet, you do not want to be pushy, and you also do not want to turn away two other couples for a date that may end up empty.
Holds live outside the diary
Most photographers keep confirmed weddings in their calendar and studio management software, but provisional holds are treated differently. They are informal promises, so they get written on a sticky note, typed in a phone note or left in the email thread where they were agreed.
- A hold has no expiry date written anywhere, only a vague 'I'll hold it for a week'.
- Nobody reminds the couple that the hold is about to lapse, so it drifts.
- The calendar shows the date as free, so another enquiry gets an 'available' reply.
- When a second couple is waiting, there is no record of who asked first.
Because the holds are invisible to the rest of your system, every conflict turns into a memory test.
The cost of holds that nobody tracks
The most expensive outcome is an empty peak Saturday. You turned down later couples because of a hold, the first couple never booked, and by the time you noticed it was too late to fill the date.
The opposite happens too. You forget a hold, tell another couple the date is free, and then have to make an awkward phone call to one of them. Both situations are uncomfortable, and in a business built on recommendations, word about how you handled it travels.
How we build a holds list that manages itself
- Each hold is created from the enquiry with one tap: couple, date, venue and an expiry date that defaults to your usual hold period.
- The hold is written to your calendar as a provisional entry in a different colour, so the date never shows as simply free.
- Two days before the hold expires, the couple receive a friendly nudge written in your words, with the booking link.
- If another couple enquires about a held date, the draft reply says it is currently held and offers to let them know, and they join a waiting list for that date in order of enquiry.
- When a hold expires or is released, the next couple on the waiting list is flagged for you to contact.
- When the couple books, the hold turns into a confirmed wedding in your studio management system without retyping.
| Situation | Before | After |
|---|---|---|
| Couple asks you to hold a date | Note in your phone | Hold with expiry on the calendar |
| Hold about to lapse | Nobody notices | Couple gets a reminder, you see it too |
| Second couple asks for the date | Guess who asked first | Waiting list in enquiry order |
| Hold released | Date may sit empty | Next couple flagged for you |
The rules are yours: how long a hold lasts, whether a hold needs a phone call first, and whether peak Saturdays get shorter holds than a midweek winter wedding.
A normal week with holds under control
When you open your calendar you can see every Saturday in the season: booked, held until a date, or free. A glance at a held date shows who is holding it, until when, and who else has asked. The reminders go without you having to write them, which takes the awkwardness out of following up.
When a couple lets a hold lapse, you find out on the day it happens rather than weeks later, while there is still time to offer the date to someone else.
Is this happening in your diary?
- You keep provisional holds anywhere other than your calendar.
- You are not sure how many dates next season are held rather than booked.
- You have turned couples away for a date that ended up empty.
- You have told a couple a date was free when it was already held.
- Following up on a hold feels awkward, so it gets put off.