The decision to archive or wait
For this hypothetical job, the accepted quote lists a $3,000 package for an October 12 wedding and a June 1 engagement session. The clients sign a cancellation agreement on August 15. The June 1 engagement session was photographed, but the raw files are currently in the post-production queue waiting for color correction.
The studio owner must decide how to handle the active project record. Archiving the project removes the October 12 wedding from the studio calendar. However, comparing the canceled wedding date field against the pending June 1 engagement deliverable status reveals a mismatch. The primary event is canceled, but the specific editing task remains an active obligation.
If the contract was canceled on May 15 before any photography occurred, using a system's native archive or cancel function is adequate to close the file. When early deliverables are partially complete, the owner has to decide how to keep the pending work visible to the editing team after removing the primary event from the calendar.
How overarching statuses affect workflows
Project software uses overarching statuses to organize timelines. When an owner changes the status of a primary job to canceled, the software applies that state to the entire file.
Dubsado divides customizable project statuses into Leads and Jobs. Dubsado lets users create, rename and reorder project statuses.[1]
Studio Ninja describes a workflow as a task list applied to a job. Studio Ninja documents several conditions that tick Job accepted, including quote acceptance, a contract signature, invoice payment, a newly created job and manual ticking.[2]
Moving a project out of an active job status stops subsequent workflow steps. If the overarching project is removed from the active board, attached tasks and workflow items tied to that job may no longer appear in the daily queue.
Resolving the tracking mismatch
To resolve the mismatch in the hypothetical $3,000 package, the studio needs a distinct record for the engagement edit that persists after the October 12 project is archived. One method is to leave the overarching project active until the engagement gallery is exported and sent. The studio changes the event date to indicate the cancellation but leaves the overarching project status unchanged. This keeps the editing task visible in the software's active list, though it requires the owner to manually bypass automated messages related to the wedding date.
Another method is to duplicate the pending deliverable as an independent record before archiving the parent project. The studio manager creates a new, separate task specifically for the June 1 engagement edit, assigns it to the editor, and then archives the October 12 wedding project. This allows the studio to clear the canceled wedding date from the calendar while retaining a visible line item for the post-production schedule.
Testing manual tasks for partial fulfillment
In RevePod, the Post Production tracker collects deliverables across projects with an assignee, status and delivery link. However, RevePod Post Production retains deliverable records for archived projects and places them in its Archived tab. The All, Active and Upcoming task views exclude archived-project rows.
If the studio owner archives the hypothetical October 12 project, the June 1 engagement edit moves to the Archived tab. To keep the edit in the active queue, 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.
As a modest next step, you can log into RevePod and test this on a sample job. Create a manual task under Other for an outstanding engagement edit, assign it a due date, and then archive the main project. Check the Active task view to confirm the manual editing task remains visible.
Record checks for canceled jobs
Before changing any active project to a canceled or archived state, review the records to verify whether any specific deliverables require completion.
- Compare the cancellation date against any scheduled early milestones.
- Check the post-production tracker for undelivered files associated with the project.
- Verify whether the remaining tasks are tied to the overarching project status.
- Create independent manual tasks for any outstanding deliverables.
- Assign a specific due date and assignee to the new manual tasks.
- Archive the primary project record.
- Confirm the manual tasks appear in the active editing queue.
Sources & further reading
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.
- Open Post Production and find the project's deliverables.
- Assign each item and use Not Started, In Progress, For Review or Done, or a custom status.
- 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.

