From Inquiry to Final Edit: How to Track Special Creative Requests

When a 'Yes' in Sales Becomes a Problem in Post-Production

Imagine a prospective client is on a call with your sales lead. They love your studio’s portfolio but have a specific vision: they want their final gallery to lean heavily into a moody, high-contrast, black-and-white style. To secure the booking, your salesperson enthusiastically agrees. The couple signs, and the project is filed away until the wedding date. Months later, your editor receives the raw files. With no special instructions attached to the project, they apply your studio's standard, light-and-airy presets. The client receives a beautiful gallery that is completely at odds with what they were promised.

This scenario is not a failure of memory or talent; it is a failure of information transfer. The creative promise made during the inquiry was lost in the handoff between sales and post-production. The editor did their job correctly based on the information they had. The problem is that the most important information—the client's specific request—never made it into the project record.

Where Creative Requests Get Lost

In many studios, the journey from lead to active project is tracked using statuses. This is a common feature in studio management software, which often divides the workflow into stages like 'Lead' and 'Job' to help organize the sales pipeline. For example, a project might move from 'Inquiry' to 'Consultation Booked' to 'Proposal Sent.'^[2]

According to Dubsado’s documentation, these statuses reflect the different phases of a business flow. While excellent for tracking the commercial progress of a project, these high-level statuses do not inherently carry the specific creative details needed by your production team. A 'Booked' status confirms a contract has been signed, but it says nothing about the promise of extra black-and-white edits.^[2]

Similarly, workflow-based systems often use stages like 'Lead,' 'Production,' and 'Post-Production' with automated tasks. Studio Ninja's workflow, for instance, can trigger emails and questionnaires at set times. However, if a unique client request is not manually added as a specific 'to-do' task within that workflow, it can be overlooked. The system automates the standard process, but the non-standard promise is what requires a deliberate, manual entry.^[3]

A Procedure for Connecting Sales to Editing

To prevent these gaps, special requests must be treated as formal deliverables from the moment they are made. This requires a clear procedure that makes the information visible at every stage. You can establish this by formalizing the handoff of client information from the very first point of contact.

• During the inquiry, record the special request in a permanent notes field.
• When building the quotation, add the request as a specific line-item deliverable.
• When converting the accepted quote into a project, verify the deliverable carried over.
• In post-production, assign and track this deliverable as a distinct task.

Step 1: Record the Request in the Inquiry

The first point of failure is often the first point of contact. Notes from a sales call can end up in a private notebook, a miscellaneous CRM field, or an email thread, disconnected from the eventual project. Instead, the person handling the inquiry should log the request directly in your central system. In RevePod, this means adding a remark to the Enquiry record. The note must be specific and actionable. For example: 'Client requests 20 additional B&W edits, high-contrast, moody style. See their shared Pinterest board for examples.'

Step 2: Add it to the Quotation as a Deliverable

A note is a good start, but a deliverable is a commitment. The next step is to translate the request from an informal remark into a formal part of the agreement. When you build the quotation, add the special request as a distinct line item. This makes the commitment explicit to both the client and your internal team before anyone signs. RevePod’s quotation builder allows you to list all deliverables, crew roles, and events. You can add a line for 'Advanced B&W Edit Selection (20 Images).' This can be a zero-cost item if it’s a stylistic choice you’re happy to accommodate, or a priced add-on if it represents significant extra work. Either way, it is now on the record.

Step 3: Carry the Deliverable into the Project

Once the client accepts the quote, that explicit commitment must be carried into the project plan. A manual process—copying and pasting notes—is prone to error. A better approach is to use a system where accepting a quote helps generate the project. When creating a project from an accepted quotation in RevePod, the system can prefill the schedule, payment details, and, crucially, the list of deliverables. The studio owner reviews the prefilled project before saving it, ensuring the 'Advanced B&W Edit Selection' becomes a permanent part of the project record.

Step 4: Assign and Track in Post-Production

With the request now attached to the project, the final step is to make it visible to the post-production team. Instead of a generic 'Edit Photos' task, the editor should see a specific list of what needs to be delivered. RevePod's Post Production workspace collects all deliverables across projects, showing each item with an assignee and a status. The editor assigned to the project will now see 'Advanced B&W Edit Selection (20 Images)' as a required task, right alongside 'Main Gallery Delivery.' This ensures the promise made months earlier, during a sales call, is seen and acted upon by the person responsible for the final product.

This level of task-specific tracking is essential for complex creative work. In a video review tool like Frame.io, for instance, collaborators can mark individual comments or pieces of feedback as complete. This provides clarity and ensures every note is addressed. Applying the same principle to your photography deliverables—tracking each promised component to completion—serves the same purpose.^[1]

What If the Request Is Vague?

This procedure works best for specific, actionable requests. But what if a client simply says they like 'moody' photos or want a 'photojournalistic' feel? These are stylistic preferences, not measurable deliverables. Forcing them into a line item might create more confusion. In these cases, the best approach is different. The conversation with the client should be used to set expectations about your studio's existing style and range. A note should still be attached to the project, but it will be advisory rather than prescriptive: 'Client prefers moodier tones; consider during selection and initial color grading.' This acknowledges the client's preference and guides the editor's judgment without promising a specific outcome that might be impossible to deliver. The decision of whether a request is a deliverable or a note is a judgment call for the studio owner.

Checklist: Is Your Handoff Missing Information?

Use these questions to evaluate your own studio's process for capturing and retaining client requests. A 'no' to any of these questions may indicate a gap where important information could be getting lost.

• Does your inquiry form have a dedicated field for special creative requests?
• Where are notes from your initial sales calls and emails currently stored?
• When you build a quote, can you add custom, non-standard deliverables?
• Does your project record automatically inherit notes and deliverables from the inquiry and quote?
• Does your post-production task list show specific creative deliverables, or just a single 'Edit Photos' task?
• How does an editor formally confirm they have completed a special request?