Separating Internal Tasks from Client Timelines

When you assign a wedding edit to an external contractor, you must decide whether to record their delivery deadline using the same field as the client's final project due date, or to create a separate internal task record. If you record the contractor's deadline in the main project delivery field, the studio and the client share a single recorded timeline. If you create a separate manual task for the contractor, you establish an internal schedule distinct from the contractual one. This recommendation to separate the dates applies when you need a recorded window to review the work, request changes, and handle delays before the final client delivery date.

For a hypothetical job, consider a wedding event recorded on October 4. The studio's project record lists a final delivery due date for a Highlight Film on November 28. You assign this film edit to an external contractor. Setting an internal due date provides a buffer that you can manage in your studio records.

Comparing Internal Dates and Final Deadlines

In this hypothetical scenario, you create a manual task for the contractor with an internal due date of November 14. On November 10, the contractor notifies you they need a five-day extension. You open the post-production records to evaluate the request.

You compare the current internal task and the main project record. The manual task lists a target of November 14. Adding five days moves the internal task due date to November 19. You then look at the project's derived delivery date of November 28. Because the revised task date of November 19 still leaves nine days before the client's November 28 deadline, you can decide to approve the extension in your task management tool. If the extension pushed the internal task past November 28, you would face a visible mismatch. That mismatch requires a decision about whether to cut your review window or ask the client to accept a revised delivery schedule.

Tracking Progress Without Dedicated Dates

Tracking these phases requires your studio software to support either separate tasks or custom project stages. If your current tool allows you to rename stages without assigning specific dates, that existing structure may be adequate for basic tracking. For instance, moving an item to a custom status indicates that the contractor has finished their portion.

Dubsado divides customizable project statuses into Leads and Jobs.[2]

Frame.io documents replies to asset comments, marking feedback complete and copying a link to a comment.[1]

Using these features allows a studio owner to track an editor's progress through stage names or comment replies rather than relying exclusively on a calendar view.

Testing Distinct Task Records in RevePod

If you are exploring a dedicated post-production dashboard, a modest next step is testing this dual-record approach using a sample job in RevePod. RevePod Post Production collects deliverables across projects with an assignee, status and delivery link.

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. If either is missing, no derived due date is shown. This derived date represents the deliverable's deadline within the project record.

To handle the contractor's internal timeline, 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. Manual tasks use their own due-date field. By linking a manual task to the project and setting its due date to November 14, you keep the internal contractor deadline separate from the derived project timeline.

RevePod Post Production has four built-in statuses: Not Started, In Progress, For Review and Done. A studio can rename and reorder these and add custom statuses; a custom status may be marked completed. If a delay occurs, you update the manual task due date and verify it does not conflict with the derived deliverable date.

Record Checks for a Deadline Extension

When an editor requests a deadline extension, check your records systematically before approving the change. Use this checklist to verify that your internal and client-facing timelines remain compatible.

  • Open the project record and locate the final client delivery date for the specific asset.
  • Open the internal post-production task record and locate the current assignee due date.
  • Add the requested extension days to the current internal task due date.
  • Compare the revised internal date to the final project delivery date.
  • Verify that the remaining days between the two dates accommodate your studio's required review time.
  • Update the manual task due date if the extension is approved.
  • Update the post-production task status to indicate the delay, if your system uses customizable statuses.

Sources & further reading

  1. Comments Panel Overview | Frame.io V4 Knowledge Center
  2. Project statuses | Dubsado Help 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