Deciding when a wedding inquiry officially becomes a studio project

The risk of merging leads with active workloads

For the hypothetical studio in this guide, two prospective couples have requested dates but neither has accepted a quotation. A third couple has accepted a quotation, and the owner is preparing an internal project record. The owner wants to decide which of these three records to put into the active production view. The sample contains two tentative inquiries and one accepted quotation; those are the states being compared here.

The owner can keep the two tentative inquiries in an inquiry list and use a production view for the accepted quotation's project. Another option is to display all three records in one view with an explicit status on each. In either arrangement, the sample still has one accepted quotation and two tentative inquiries. Before assigning people or committing to a production schedule in this example, the owner can separately check staff availability and the scope the client has actually accepted.

Defining the boundary in your current software

Before choosing where to record the two tentative inquiries in the sample, check which record types and statuses your tool provides. One arrangement to test is a single list that contains both tentative inquiries and the accepted quotation's project, with a status on each row. A second is separate inquiry and production views. Compare the sample's three records in whichever arrangement is available in the tool you are evaluating.

Other systems utilize a comprehensive folder structure. A tool might require you to manually add a job, which acts as a centralized folder containing the initial client information, outgoing quotes, and eventual contracts, regardless of whether the date is formally secured.^[2]

If your current software seamlessly blends these stages, you will need to establish strict internal rules about what constitutes a confirmed booking. Without a structural boundary, the studio owner carries the administrative burden of remembering which scheduled shoots are real commitments and which are merely hopeful conversations.

A procedure for elevating inquiries to active jobs

To maintain an accurate operational dashboard, establish a formal, multi-step transition procedure. Step one is isolating the inquiry. A prospect should remain classified strictly as an inquiry while you verify their date, discuss budgets, and negotiate the initial scope. During this phase, avoid adding the event to the studio's primary production calendar. You are only tracking preliminary details.

Step two is defining the proposed scope. Once you have enough information, build a formal quotation outlining the required crew, the timeline, and the expected deliverables. In a hypothetical scenario, if a couple mentions that their initial budget of 5,000 USD was provisional, the studio can adjust the quotation at this stage before any production data is finalized. This allows the potential project to be accurately scaled before it ever enters the production queue.

Step three is securing the client's formal acceptance. The quotation is sent for review. As long as the quotation is pending, the client remains an inquiry. Step four is the conversion. Only when the client formally accepts the quotation does the status shift. At this precise moment, the studio begins producing, migrating the accepted details into the active project calendar.

• Maintain the prospect as an inquiry while verifying dates and provisional budgets.
• Build a formal quotation outlining the required crew, timeline, and deliverables.
• Verify the client has formally accepted a specific quotation before changing their status.
• Confirm the event date is no longer tentative.
• Migrate the accepted details into the active project calendar.

Executing the segmented transition in RevePod

A hypothetical studio maintains a lean Projects dashboard in RevePod by only transitioning leads from Enquiries after a quotation is formally accepted and reviewed. RevePod Enquiries records the inquiry source, status, and remarks. When you are ready to propose a scope, you use the native quotation builder for events, crew role quantities, and deliverables. A share link lets the client view, accept, or request changes to the proposal without logging in.

Once the client accepts the proposal, the transition to an active job begins. When creating a project from an inquiry with an accepted quotation, RevePod can prefill the schedule, deliverables, payment total, and quote details. The studio owner reviews this prefill before saving the new project.

While the software manages this data transfer, it is subject to standard operational limits. Quotation acceptance in RevePod is simply an operational state indicating agreement on scope; it is not evidence of legal enforceability or proof of a processed payment. Software records still require accurate information and human decisions regarding tax compliance, payment collection, and contract signatures. To begin clarifying your own workload, audit your current project list and remove any non-committed tentative dates.