The Operational Challenge of Multi-Day Bookings

A multi-day wedding booking often involves different crew requirements, distinct timelines, and specific deliverables for each day. For the studio, treating each day as a separate project can seem like a logical way to manage this complexity. By isolating the welcome dinner, the main wedding day, and the farewell brunch into individual files, the studio can attach entirely different crew rosters and generate separate invoices.

However, this internal separation directly impacts the client’s experience. Imagine a hypothetical US studio that books a three-day wedding and creates three separate projects, sending the client a different portal link for each event. When the couple attempts to check the start time for the welcome dinner or locate the deliverables list for the brunch, they must find the specific email containing the correct day's link. If they log into the Saturday portal to find Friday’s schedule, the information is not there.

Consolidating Dates Within a Single Framework

The alternative is to consolidate the entire weekend into a single project, giving the couple one reference point. Some studio management software is built for this. In HoneyBook, for example, a single project can support a primary date, an end date to create a range, and up to 10 additional dates to track separate events like a rehearsal dinner or ceremony without duplicating the project.[3]

When clients access a consolidated project, the portal interface defines what they can see. A HoneyBook client portal shows shared files, messages, and project details, while specific notes can remain visible only to the internal team. Studio Ninja uses a tabbed layout for quotes, contracts, and invoices, displaying overall job details on a side panel. In either case, a unified project structure means the client navigates one environment for all weekend details.[2][1]

Tradeoffs in Structuring a Multi-Day Wedding Booking
Decision FactorUnified Project SetupSeparate Project Setup
Client AccessSingle portal link for all events.Multiple links for the client to track.
Timeline DisplayChronological view of all dates and times.Siloed schedules, visible only within each project.
Deliverable TrackingCombined list of all photos and films for the weekend.Deliverables are split across distinct portals.
Studio AdministrationOne project to manage; may require more detail within.Easier to isolate billing or crew for a specific day.

Mapping the Weekend in RevePod

RevePod projects are designed to hold multiple events, crew roles, and deliverables within a single workspace. This structure allows you to build a comprehensive plan for a wedding weekend that the client can view through their portal. The client portal shows the project schedule and other shared information, with access and visibility controlled by your settings.

Before the booking is confirmed, you can use RevePod’s quotation builder to detail the events, crew role quantities, and deliverables for the entire multi-day package. When creating a project from an inquiry with an accepted quotation, RevePod can prefill the project with this information, including the schedule and payment total. The studio owner reviews the prefilled data before saving the project. It is important to note that prefilled crew quantities do not assign specific named people to those roles; that is a separate step in the studio's workflow.

Building a Reusable Multi-Day Template

If you decide to use a unified project portal, establishing a consistent data entry routine makes the schedule more legible for both your team and your client. Clear labels for each date and specific deliverable lists prevent the events from blurring together.

  • Confirm the primary wedding date is recorded in the main event field.
  • Add secondary dates for the welcome dinner, rehearsal, or brunch as separate events.
  • Define the start and end times for each distinct event block.
  • List the specific deliverables tied to each event day in the shared project information.
  • Check the client portal view to confirm internal team notes are not visible.
  • If different parties are paying for separate days, consider if your single-project workflow can accommodate that or if separate projects are necessary.

Sources & further reading

  1. Getting started with the client portal | Welcome to the Ninja Academy
  2. What clients can see and do in the client portal | Help Center | HoneyBook
  3. Start a project and set project dates | Help Center | HoneyBook
Published by RevePod Editorial. This article was prepared with AI assistance and published automatically from a saved draft. References are provided where available. Suggest a correction.
TRY THIS IN REVEPOD

Walk through the client side before inviting a couple

RevePod has a project client portal with schedule, contract and payment information, and deliverable links, subject to your plan and visibility settings. Use the demo to inspect the client experience, then set up a trial project.

  1. Review the project schedule and the information you intend to share.
  2. Check which contract, payment and delivery details are visible.
  3. Open the client link yourself before sending it to a client.

A client portal does not replace your editing application or establish that files are backed up. Custom portal domains are a Max-plan feature; check current pricing for plan access.

Check current plans · What RevePod does