The Early Deliverable Timeline
If a studio offers a comprehensive package, the agreement often includes a pre-wedding session alongside the primary coverage. For this explicitly hypothetical job, a client accepts a hypothetical $5,500 quote for a package that includes an engagement session and a physical guestbook album. The records show the engagement session occurs on May 15, the photo gallery is delivered in June, and the wedding day is scheduled for October 20.
The guestbook must be designed, proofed, printed, and shipped by September 1 so the couple has it for the wedding reception. The owner has to decide whether to track the engagement session as a distinct project record or list its deliverables within the main October wedding record. The choice dictates which project fields the production team reviews in June to initiate the guestbook design step.
Comparing Single and Separate Project Records
Using a single project record requires logging multiple event dates into one client file. The owner reviews the project screen to verify if the early session has its own distinct block or if it sits in a generic notes field.
HoneyBook project dates can represent an event, a final deliverable due date, a working period or project end date. Its documentation allows more than one project date.[1]
With one project, the owner compares the engagement date and the wedding date to see if the software calculates a single due date for all deliverables based on the final October event. If the system calculates a guestbook due date based on October 20, the June design task might not appear in the current production queue. The production manager would have to manually open the October project during the summer to check for pending intermediate deliverables.
Alternatively, splitting the package creates an "Engagement" project with a May 15 date and a "Wedding" project with an October 20 date. The engagement project holds only the session gallery and guestbook deliverables. This isolates the timeline, allowing a date calculation based strictly on the May event. The studio then manages two separate project records for the same client, which requires confirming that payments and contracts can be linked or tracked across split files.
Structuring the Initial Proposal
The workflow begins before the project is created. When drafting the initial proposal, the studio itemizes the engagement session, the photo gallery, and the guestbook alongside the primary wedding day coverage. Using standard templates makes this list reproducible.
Studio Ninja offers Pick & Choose quote templates and Fixed quote templates. The fixed type presents a fixed list of packages and products.[2]
If the accepted quote lists the engagement guestbook as a distinct line item, the owner can map that directly to a separate project or a specific manual task. If the quote lumps all physical goods into one generic "Wedding Album and Print Credit" line, the owner has to manually separate the guestbook and establish its earlier timeline during the project setup phase.
Testing a Setup in RevePod
In RevePod, project deliverable due dates in the Post Production tab are derived from the configured delivery-day value for that deliverable type and the latest scheduled project event date. If a single project contains both the May 15 engagement and the October 20 wedding, the latest scheduled event is October 20. A derived due date for the guestbook would reference October, not May.
To accommodate a single-project workflow, the owner relies on manual entries. RevePod Post Production can create a manual task, optionally linked to a project or kept under Other, with an assignee, status, due date, priority and notes. The owner assigns a manual task for the guestbook with a strict July 15 due date. This establishes a visible target for the editor without altering the October derivation for the main wedding gallery.
If the studio splits the booking into two separate RevePod projects, RevePod Post Production collects deliverables across projects with an assignee, status and delivery link. The production view displays the engagement project's guestbook with a derived due date based on the May 15 session. Once the guestbook ships, the engagement project is completed, leaving only the October wedding project in the active queue.
Record Checks for Multi-Part Packages
Before standardizing a process for early deliverables, run a test using a hypothetical multi-date project to verify how your system generates tasks and calculates deadlines.
- Review the software documentation to find whether deliverable due dates calculate from the first event date, the final event date, or creation date.
- Set up a test project using two event dates spaced at least four months apart.
- Add a physical deliverable to the test project and check the master production list to see which event date anchored the calculation.
- Test whether the system allows a manual due date override on a single deliverable without changing the main project dates.
- Create two separate test projects for a single hypothetical client to see if the platform allows shared invoicing across split project records.
- Compare the steps required to archive an early session's deliverables in a split setup versus a single combined record.
Sources & further reading
Check the agreed offer against one project
RevePod has a quotation builder for event coverage, crew, services and deliverables, with a client link and PDF. When creating a project from an enquiry with an accepted quotation, the offer can prefill event, deliverable and payment details. Check those records against the agreed scope.
- Build an example quotation from your services and packages.
- Inspect the client link and PDF before sharing the offer.
- After acceptance, create the project from the enquiry and review its event, deliverable and payment records.
Quotation access depends on your plan. Your team still confirms the agreed scope and checks project records; the software does not certify that every client commitment has been fulfilled.
