Seasonal Booking Workflow

This project started with a simple frustration: every autumn, the same flood of booking requests arrived through email, social media, and a contact form that nobody checked regularly. The client, a small studio with three photographers, was losing leads because responses took two or three days. The brief was not to build a fancy system, but to make the existing process predictable.

We mapped the current flow first. Requests came in, someone copied details into a spreadsheet, then sent a confirmation with availability. The spreadsheet had no calendar view, so double bookings happened twice in the first month of use. The client asked for something that would work on a phone, since most requests arrived while the team was on location.

What we changed

The new workflow uses a shared calendar with clear time blocks for each season. Instead of asking clients to wait for a reply, the system shows available slots immediately and holds them for 48 hours. If no payment follows, the slot opens again automatically. This removed the back-and-forth that used to take three emails per booking.

  • Replaced the spreadsheet with a visual calendar that shows seasonal availability at a glance
  • Added automatic reminders that go out 24 hours before a session, reducing no-shows by a noticeable margin
  • Created a simple intake form that collects location, session type, and preferred dates in one step
  • Set up a waiting list for weekends, which are booked out six weeks ahead during peak season

Tradeoffs and decisions

The hardest part was deciding how much automation to introduce. The client wanted to keep a personal touch, so we avoided fully automated confirmations. Instead, the system flags new bookings and sends a notification, but a human reviews each one before the client receives the final confirmation. This adds about fifteen minutes of work per day but keeps the tone warm and flexible.

We also had to account for the fact that the studio works with different session lengths depending on the season. Summer sessions run longer because of the light, while winter sessions are shorter and more contained. The calendar now supports variable slot lengths, which sounds simple but required rethinking how the availability was calculated in the first place.

The project took four weeks from first meeting to launch, including two weeks of testing with real bookings during the transition period. The client reported that response time dropped from two days to under four hours, and the double-booking issue disappeared entirely.

Cookie settings

We use cookies to keep the site reliable, remember basic choices, and understand which pages are useful. You can accept, reject, or review the settings before continuing.