Resolving Schedule Mismatches When Clients Extend Coverage

The Extended Coverage Request

For this hypothetical job, a client accepted a quotation for a wedding on October 14, 2026. The accepted quote lists two crew roles—one lead photographer and one second photographer—scheduled from 2:00 PM to 10:00 PM for a hypothetical total of $4,000 USD. Two weeks before the event, the client asks to extend coverage to 11:00 PM. You agree to a hypothetical $250 USD fee for the extra hour.

The decision is whether to issue a supplementary invoice or update the primary project records. Generating an invoice handles the payment, but it leaves the event calendar untouched. If your project scheduling and invoicing remain separate, the schedule will not show the 11:00 PM finish.

Identifying the Record Mismatch

Compare the newly generated invoice against the active project record. The invoice might read One Additional Hour, while the project schedule still lists a 10:00 PM end time. This creates a mismatch. The record shows the role of the second photographer ending at 10:00 PM. The owner still has to brief the people involved, and conflicting records make that briefing harder to track.

Resolving this mismatch requires editing the event time in your project management tool. You manually change the end time to 11:00 PM for both the lead and second photographer roles. This update aligns the project file with the financial agreement, providing a consistent reference for the crew.

Structuring Quotes and Dates

Studio Ninja offers Pick & Choose quote templates and Fixed quote templates. The fixed type presents a fixed list of packages and products.^[1]

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.^[2]

If your software limits edits to the original quote document, you can maintain the event timeline in the separate project date fields to keep the scheduled day accurate.

Implications for Deliverables

Event dates also influence post-production timelines. When a project schedule is not updated, derived deadlines may fall out of alignment. If the coverage extension pushes the final event date past midnight into a new calendar day, an automated due date relying on that event date will shift.

Project deliverable due dates in RevePod Post Production are derived from the configured delivery-day value for that deliverable type and the latest scheduled project event date. RevePod projects record events, crew roles and deliverables. If either the event date or the delivery-day value is missing, no derived due date is shown.

You can test this workflow with a sample job in RevePod. Create a new project without a prefilled quotation. Add an event scheduled for October 14, 2026, and assign a deliverable with a 30-day delivery value. Check the Post Production tab to see the derived due date. Then, edit the event to end on October 15, 2026, and observe how the deliverable timeline changes.

When an Invoice is Adequate

A separate invoice without a project schedule update is adequate when the scope change does not alter the event hours or crew roles.

If the same hypothetical client adds an engagement album order after the quote is signed, the event dates and crew times remain exactly the same. In that condition, logging the $250 USD hypothetical payment on a supplementary invoice is sufficient. There is no mismatch to resolve in the event schedule.

Record Checks for Extended Hours

Use these specific checks to audit your project files when adding coverage hours to an accepted quote.

• Check the accepted quote to confirm the originally stated start and end times.
• Review the supplemental invoice to verify the exact quantity of added hours.
• Open the project schedule and confirm the new end time matches the invoice.
• Review the crew role quantities and verify they cover the new duration.
• Check the derived post-production due dates if the time extension crosses midnight.