Redefining the project phase

When a couple accepts a bespoke wedding proposal, the studio's administrative focus shifts from sales to fulfillment. This transition requires moving the project through different phases of the business flow. In client management systems, project statuses are customizable categories reflecting these distinct phases. For instance, Dubsado divides project statuses into Lead statuses—representing the early stages of a client relationship—and Job statuses, which represent active work or completed projects.[1]

Moving a project from a Lead status to a Job status helps the studio track progress. However, updating a status label from a pending proposal to an active project is merely the categorization step. The studio must also map the specific tasks required to fulfill the newly agreed-upon scope.[1]

A workflow acts as a task list applied to every created job. As a job progresses through its three main stages—the lead stage, the production stage, and the post-production stage—specific tasks must be checked off to verify nothing is forgotten. If the final details of the accepted quote are not transferred accurately to this task list, the post-production pipeline risks falling short of the client's documented expectations.[2]

The risk of manual transcription

A vulnerability in the onboarding workflow exists during the handover from sales to operations. If a proposal undergoes revisions, additions, or subtractions before booking, the final accepted package represents a customized agreement. The studio must transfer this exact agreement into the post-production tracker to verify the work is delivered.

Consider a hypothetical scenario: A hypothetical client upgrades their package to include an extra parent album during the final quote review. The studio owner updates the final invoice and the client signs the agreement, but the owner forgets to manually add the parent album task to the post-production list. Six months later, the main gallery is delivered, but the parent album is entirely forgotten until the client asks for it, causing a delayed delivery.

If the photographer relies primarily on the active editing backlog and task lists, rather than cross-referencing the original signed contract for every editing session, manual data entry between these two systems creates an operational gap.

Balancing automation with manual review

Manually creating the project allows the studio owner to review the scope and assign resources thoughtfully. This review period is a necessary operational step. A studio owner must look at the final agreed deliverables, verify that the required second shooters are available, and ensure that the editing timeline aligns with the current backlog.

However, relying entirely on manual data entry to recreate the deliverable list line-by-line requires repetitive transcription. Separating the act of transcription from the act of review allows the studio to handle bespoke requests methodically without introducing clerical errors.

Software records still need accurate information and human decisions. A system can carry data over automatically, but the owner must confirm that the migrated data reflects a viable, realistic production plan before finalizing the project.

Establishing deliverables in the project record

Connecting the initial quotation directly to the active project record reduces the risk of dropped deliverables. In a studio's initial phase, RevePod Enquiries records the inquiry source, status, and remarks. When presenting the initial scope, RevePod features a native quotation builder for events, crew role quantities, and deliverables. A share link lets the client view, accept, or request changes without logging in.

When creating a project from an inquiry with an accepted quotation, RevePod can prefill the schedule, deliverables, payment total, and quote details. The owner reviews the prefill before saving. This workflow enforces the necessary manual review step while eliminating the initial data entry.

Once the project is created and saved, RevePod projects record the events, crew roles, and deliverables. Furthermore, RevePod Post Production collects these deliverables across projects, displaying an assignee, status, and delivery link. The RevePod client portal can then show the project schedule and shared project information, subject to visibility settings and plan access.

A procedural checklist for the booking handoff

To standardize the transition from an accepted quote to a fully populated editing backlog, a studio can follow a structured onboarding procedure. When setting up tasks in a management system like Studio Ninja, workflow options allow the creation of to-do tasks with assigned due dates. A task flagged with a red indicator when overdue can keep the post-production stage on track. Use the following checklist to audit or build your handoff process.[2]

  • Verify that the signed quote matches the bespoke deliverables discussed during the final consultation.
  • Update the system categorizations from a Lead status to an active Job status to reflect the booking.
  • Convert the quotation to generate the project record, allowing the software to prefill the agreed deliverables.
  • Manually review the prefilled schedule, crew roles, and deliverables against any custom notes left in the inquiry remarks.
  • Assign an owner to each deliverable task in the post-production workflow.

Sources & further reading

  1. Project statuses | Dubsado Help Center
  2. Workflows | Welcome to the Ninja Academy
  3. Comments Panel Overview | Frame.io V4 Knowledge Center
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

Track these deliverables in RevePod

RevePod's Post Production view brings deliverables from your studio's projects into one list. Each can have an assignee, a status and a delivery link. You can also configure delivery timelines in your services catalog.

  1. Open Post Production and find the project's deliverables.
  2. Assign each item and use Not Started, In Progress, For Review or Done, or a custom status.
  3. Check the delivery link and its client visibility before sharing it.

RevePod tracks the work; your team still edits in its usual photo and video tools. Configured delivery dates depend on the project's last scheduled event and the deliverable's catalog timeline.

Check current plans · What RevePod does