Deciding whether to track physical albums and digital edits in a single system

Comparing dates and deliverables on a split timeline

In this hypothetical job, the wedding event takes place on May 1. The accepted quotation lists two distinct deliverables: a digital photo gallery and a 10x10 leather album. The digital gallery has a turnaround time of 30 days, placing its due date at May 31. The album design and print order process requires 90 days, setting a target completion date of July 30. When reviewing the post-production schedule on May 25, the studio owner sees that the digital gallery is ready for export and the client link is generated.

At this stage, the owner must check the project records to see how the album is logged. If the studio uses a single project-level due date of May 31, marking the job as complete on May 25 clears the digital gallery from the editing queue. However, a mismatch occurs if the 10x10 leather album record is tied to that same overall project date rather than its own July 30 timeline. The owner must resolve this by either updating the album's specific due-date field or, if the software does not support line-item dates, moving the album record to a separate fulfillment list.

If the album layout cannot begin until the couple selects their images from the digital gallery, the July 30 target relies on a variable start date. The owner compares the date the gallery link was sent against the internal record for the client's selection deadline. If the client misses the selection date, the arithmetic for the July 30 deadline breaks down. The owner must decide whether to adjust the album's internal due date forward or hold the original timeline in the project tracker.

Managing vendor tools and status levels

Dubsado divides customizable project statuses into Leads and Jobs. Its documentation states that users can create, rename and reorder these project statuses.^[1]

A studio owner can use customizable project levels to manage the gap between digital delivery and physical fulfillment. If the May 1 wedding reaches the May 31 gallery deadline, the owner can change the project's overall status to a specific physical-production label rather than closing the job entirely. This record update keeps the job visible while the album designer prepares the layout for the July 30 deadline.

When dividing the post-production work, the owner must check the assignee fields for each deliverable. In this hypothetical job, the digital editing is assigned to an internal editor, while the album design is assigned to a separate print manager. The owner compares the active tasks for both assignees. If the system only displays one primary assignee for the entire May 1 project, the print manager might not see the album task in their queue until the editor manually transfers ownership. Checking this capability helps determine if separate tracking is necessary for multi-person teams.

Verifying tasks and conditions for integration

Studio Ninja describes a workflow as a task list applied to a job. Its documentation notes several conditions that tick Job accepted, including quote acceptance, a contract signature, invoice payment, a newly created job and manual ticking.^[2]

If a studio's current tool applies a workflow task list to the overall job, the owner can check if the album layout is listed as a distinct task with its own 90-day trigger. When the existing system supports assigning individual due dates to separate tasks within the same job, that tool is adequate for keeping physical and digital tracking together. The owner can assign the gallery export task to the editor and the album design task to the studio manager without conflicting deadlines.

A task list applied to a job provides a structured set of required steps. In our May 1 hypothetical wedding, the owner evaluates whether the active job view lists line items for ordering a USB drive, drafting the 10x10 album layout, and tracking the lab shipment. If these steps are missing from the primary digital sequence, the owner must decide whether to manually append them or rely on a secondary spreadsheet. By evaluating the project records, the owner confirms whether the required print-related tasks remain visible alongside the digital export tasks, establishing an accurate count of what physical items remain outstanding.

Testing a consolidated view in RevePod

To evaluate a consolidated approach, an owner can test a sample job in RevePod. RevePod Post Production collects deliverables across projects with an assignee, status and delivery link. The software 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.

For the May 1 wedding, the owner can verify how due dates are generated. 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.

If the derived date does not fit the album 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. The owner can add a manual task for the 10x10 album with a July 30 due date, assign it to a specific team member, and keep it linked to the May 1 project. The owner reviews this manual task record alongside the digital gallery deliverable to decide if this view accommodates both timelines.

• Check the quoted deliverable list for the 10x10 leather album to verify it transferred to the active project board.
• Compare the digital gallery's derived due date with the album's derived due date to spot any scheduling mismatches.
• Verify the project's overall event date (May 1) is populated so the derived delivery days can calculate correctly.
• Review the assignee field on the manual album task to confirm a specific team member is responsible for the print order.
• Check the status field on the album task after the digital gallery is marked Done to ensure it remains open.