Creator Workload Calculator: Can You Deliver This Content Package?

“Can you make eight Reels?” is incomplete as a workload question. Eight edits from organized footage are different from eight researched, filmed, captioned, revised and published demonstrations.

Use the calculator on this page to estimate one defined content package. It adds your production stages, shared administration and contingency, then compares the result with the hours you actually have available. It is a planning aid, not a promise of productivity or a recommended posting frequency.

Define one item before entering numbers

Write a short unit definition: “One vertical product demonstration, filmed by me, with reviewed captions, one consolidated revision round and publication.” That definition determines what each estimate includes.

If half the package is simple recuts and half is location filming, calculate them separately and combine the workloads. An average that mixes very different jobs can conceal the item that causes the delay.

List exclusions too: sourcing products, travel, translation, additional formats, complex animation, unplanned reshoots or community management. Excluded work does not disappear. It needs its own estimate or an explicit agreement that it is outside the package.

The broader principle is matching demand with available time and skills, rather than counting deliverables alone. Asana's capacity-planning guide describes that distinction; the calculations here use your inputs and do not borrow a generic creator productivity benchmark.

Enter hours for each production stage

Use decimal hours consistently: 15 minutes is 0.25 hours, 30 minutes is 0.5 and 90 minutes is 1.5. Do not enter 30 when you mean half an hour.

The field names are deliberately simple. You can include another genuine production task in the appropriate stage, but note the choice so the estimate remains interpretable later.

If you film a batch in one session, divide that filming time across the items or count it as shared work with a clear note. Do not do both. Shared administration is a once-per-package input in this calculator.

Understand the formula

The calculation is transparent:

Per-item hours =
  research + filming + editing + revisions + publishing

Base workload =
  (number of items × per-item hours) + shared administration

Contingency hours =
  base workload × (contingency percent ÷ 100)

Planned workload =
  base workload + contingency hours

Hours remaining =
  available hours − planned workload

Contingency adds time to the workload. It does not increase your available hours and is not a claim that you should be busy for a particular percentage of the week.

Enter a whole number of items and non-negative hour estimates. A zero may be appropriate when another person supplies a completed stage, but describe that dependency. Zero editing time is not realistic simply because you intend to use a faster tool.

Try a fictional six-Reel package

Suppose you estimate the following for each Reel: research 0.5 hours, filming 0.75, editing 1.5, revisions 0.5 and publishing 0.25. These are invented planning inputs, not measured averages or recommended delivery times.

The per-item total is 3.5 hours. Six items require 21 hours. Add 3 shared administration hours and the base workload is 24 hours. A chosen 20% contingency adds 4.8 hours, giving 28.8 planned hours.

With 30 hours genuinely available, the remaining capacity is 1.2 hours. That is a narrow margin in this scenario, not permission to add another full deliverable.

Adding two items is not “just a couple more posts.” Under these assumptions, it changes the package from fitting to exceeding available time. You can use the difference to discuss scope, deadline or support before committing.

Make available hours honest

Choose the same planning window for both workload and capacity. A monthly package cannot be compared with one week's available hours.

Start from your actual schedule. Remove existing commitments, leave, recurring responsibilities and time you do not intend to allocate to this package. Do not count all waking hours as capacity.

For a team, avoid treating everyone's time as interchangeable. An editor's free afternoon does not automatically solve a filming bottleneck. Run separate checks for constrained roles or stages.

Calendar time also matters. A package may require 20 working hours spread across two weeks because products arrive late or an approver is unavailable. The calculator measures effort, not those dependencies. Record the shoot date, review window and publication deadline alongside it.

Replace guesses with your own completed-work records

For a new format, label the first estimate provisional. After each completed item, record actual time by the same stages. Note what changed: missing assets, a difficult caption pass, unexpected export checks or a second decision-maker.

The distinction between estimated and actual time is also explicit in Asana's time-tracking documentation. You do not need that product to use the idea; a private timer log or the text worksheet below can be sufficient.

Compare like with like. Do not use a simple talking-head edit to predict a scripted product demonstration without accounting for the different work.

Keep waiting time separate from active working time. Waiting for approval affects the schedule; reviewing the returned notes affects workload. Both matter, but adding the entire waiting period to editing hours makes the effort estimate misleading.

Decide what to change when the package does not fit

First check for double counting or an unclear scope. If the workload is still too high, change a real constraint: reduce the number of items, simplify the agreed format, move the deadline or add someone with the relevant skill and availability.

Do not remove the revision estimate merely to make the result turn green. Agree a workable review process using the timecoded feedback template. If support is added, allow time for the project handoff.

Finally, save the assumptions with the package proposal. “Six demonstrations with one consolidated review round fit this window under these estimates” is a useful planning statement. “I can always make six videos a week” is an unsupported generalization.

CONTENT-PACKAGE WORKLOAD WORKSHEET
Planning window:
Package / client:
One item means:
Included review scope:
Excluded work:
Dependencies / approver availability:

INPUTS — DECIMAL HOURS
Number of items:
Research per item:
Filming per item:
Editing per item:
Revisions per item:
Publishing per item:
Shared administration, counted once:
Available hours in this same window:
Contingency percent:
Source of estimates: measured / provisional / mixed
Batch-work allocation notes:

CALCULATION
Per-item total:
Items × per-item total:
Base workload including shared administration:
Contingency = base × percent / 100:
Planned workload = base + contingency:
Remaining = available − planned:
If negative, required change:

FICTIONAL EXAMPLE — NOT A BENCHMARK
6 items
Research 0.5 + filming 0.75 + editing 1.5 + revisions 0.5 + publishing 0.25 = 3.5 hours per item
6 × 3.5 = 21 hours
Shared administration = 3 hours
Base = 24 hours
Chosen contingency = 20%, adding 4.8 hours
Planned workload = 28.8 hours
Available = 30 hours
Remaining = 1.2 hours

ACTUAL-TIME LOG — duplicate per item
Item ID:
Research:
Filming:
Editing:
Revisions:
Publishing:
Unexpected work and reason:
Waiting / calendar delay, recorded separately:
What should change in the next estimate?:

DECISION
Package fits effort capacity?:
Shoot / approval / publication dates also fit?:
Constrained role or dependency?:
Scope, timing or support adjustment:
Confirmed assumptions and date: