Your team has several launches coming through a China production partner. The subscription upgrade offers more simultaneous projects. That sounds useful, until every new edit reaches the same product reviewer and waits. More work has started, but the next launch still has no approved files.
Before purchasing additional concurrency, ask which part of the process can finish more work. ONCE’s proposed three-number worksheet connects that question to procurement. This is an evergreen analysis based on current public guidance, not a claim that a new industry-wide service model launched today.
What a delivery promise actually covers
Superside’s current project-workflow help page distinguishes production using existing assets from original creative development. It says timelines depend on scope, complexity and capacity, with fast-turnaround support limited to certain tasks and plans. Checked November 3, 2026, the page does not show a verifiable absolute update date.
Those are one provider’s descriptions of its service. They do not establish a market standard. The useful question for any proposal is whether its additional project slots increase entry into the process or the supply of completed, usable work.
ONCE’s three-number worksheet
Scrum.org’s January 2021 Kanban Guide distinguishes work in progress, throughput, cycle time and work-item age. It describes how more average work in progress at a given throughput generally corresponds to longer average completion time. Atlassian also presents WIP limits as a way to expose bottlenecks. ONCE applies those established concepts to content purchasing below; the underlying flow theory is not an ONCE invention.
| Number | Suggested content-team definition | Question to answer |
|---|---|---|
| Open work | Comparable items committed to production but not finished, with active, waiting and blocked status visible | Are unfinished commitments accumulating? |
| Completed work | Comparable items meeting the agreed completion standard in the same reporting period | Did additional capacity produce usable delivery? |
| Age of unfinished work | Elapsed time since each open item started, with its next action and current obstacle | Which old commitments are hidden by the completed-work report? |
Keep original concepts, translation updates and edits from approved footage in separate groups. A count combining them cannot tell you how many original videos a team can produce next month. Log scope changes rather than quietly treating a newly commissioned shoot as the same small edit request.
Agree on the start and finish before comparing vendors
A submitted request and a commitment to begin production are different events. Record both. For this worksheet, work enters the open count when the agreed inputs are ready and the parties commit to starting. Time spent waiting for that commitment still belongs in the customer’s overall experience; it should not disappear because the production clock starts later.
The finish must match what you purchased. A first draft may complete a review stage, while an approved set of delivery files completes a different obligation. If your in-house team controls publication, record that as a separate step rather than asking a supplier to guarantee an action outside its control.
For overseas teams, specify business or calendar days, time zone and reporting cutoff. A Friday handover from Shenzhen awaiting Monday review in the US creates elapsed time without necessarily creating equivalent production labor. Track elapsed time and actual work separately.
A hypothetical launch queue
Suppose a brand consistently finishes four comparable edit requests per week, while open work rises from four to eight. These numbers are illustrative, not ONCE results or an industry benchmark.
If most unfinished items await confirmation of product facts, assign a qualified product owner to resolve them. If conflicting feedback is the obstacle, consolidate the decisions. Another editor might otherwise produce more drafts for the same congested review stage.
If inputs and review are timely, and unfinished work concentrates in a specialist production step, investigate additional capacity for that step. Buy the relevant skill or resource and then observe whether more items actually finish. Adding a general project slot is not evidence that the constrained step can handle more work.
Do not divide eight items by four per week and promise every video in two weeks. Average flow relationships require consistent definitions and a sufficiently stable, comparable process. Individual requests still vary in dependencies and complexity, and dates need a project-specific plan.
A paused project should remain visible
When a product decision is unresolved, both teams can agree to pause production and release an active slot. Keep the original start date, pause reason and cumulative elapsed time in the record. Show active and paused work separately. Moving slow items out of the active queue must not make the end-to-end history look faster.
Likewise, customer approval time should not be reported as supplier labor, and internal supplier queues should not be relabeled as customer delay. Give each stalled item a next action, responsible person and agreed response point. That makes a decision to resume, rescope or reschedule concrete.
Try a limit before buying a larger allowance
Select one comparable work group and agree on a temporary limit to committed open work. Set the number from actual resources and needs; there is no universal optimum in this article. At the limit, prioritize finishing or unblocking existing work. If a fixed launch must interrupt, name the item that will be paused or moved rather than silently exceeding the limit.
Watch completed volume, unfinished age and the required quality checks. If output falls, investigate whether the limit is too restrictive, tasks are bundled too broadly or a key resource is being left idle. A WIP limit is an experiment, not a guarantee. If output holds while old unfinished items decline, use that evidence to discuss the next capacity agreement, allowing for simultaneous changes in scope or staffing.
A useful purchasing schedule separately describes accepted work, concurrency, production and review responses, pause and restart rules, and the finish standard. Avoid one undefined phrase such as “more capacity” covering all of them.
Scale the ability to finish
For ONCE, a recurring service should turn agreed commitments into usable content consistently. More open projects can create coordination work before they create additional value. The worksheet helps identify where incremental spending belongs, but it does not prove a margin improvement without actual cost and delivery records.
Start your next review with one task group and its definitions. Use the video production planning resources to connect the resulting capacity conversation to a real brief, inputs and delivery scope. Preserve each period’s observations so that a changing board does not replace the record used to make the purchasing decision.
Sources and limits
Checked November 3, 2026: Superside Help Center, Superside project workflow (no verifiable absolute update date shown); Scrum.org, The Kanban Guide for Scrum Teams (January 2021); and Atlassian, Working with WIP limits for kanban (no explicit update date shown).
The content-task definitions, procurement approach and trial design are ONCE recommendations. The queue example is hypothetical. This article does not claim to have measured a client’s workflow or verified a supplier’s actual delivery performance.
