Do you actually know how many editing hours your studio has left this week?
On Monday, the schedule looks fine. One editor has 2 projects, another has 3, and a third only has a small urgent revision. Then Thursday arrives and the whole post-production plan starts slipping.
One video comes back with heavier notes than expected. Another client asks for one more campaign version. A third project is waiting on sound, but the editor still has to keep it in mind. The producer opens the calendar and sees not capacity, but a set of optimistic promises. The issue is not that the team is lazy. The issue is that the studio is counting projects instead of editing capacity.
That mistake is more expensive now. Clients want more video, more versions, faster cuts, and more test formats. AI speeds up rough tasks, but it does not remove editorial judgment, review, revisions, or final quality control.
Why editor workload often looks healthier than it is
Capacity rarely breaks because of one huge mistake. It usually breaks through small assumptions that nobody challenges.
- A project is treated as one task - in reality it contains rough edit, graphics, captions, audio, export, upload, comments, and another quality check.
- Revision time is not reserved - the team plans the first cut, then hopes client notes will be light.
- Client waiting time is mistaken for free time - while a video is in review, the editor starts another project, but the revision round will still return to the calendar.
- Urgency beats priority - a fresh client request steals time from a project that was closer to delivery.
- Freelancers are treated like infinite overflow - the studio calls them only once the schedule is already too tight for a clean handoff.
This creates a management illusion. The calendar has days available, but production has no usable slots.
How to plan editing capacity
Good planning does not require watching every click in the edit suite. It requires a clear view of work types, buffers, and return points.
1. Split projects into editing states
If a project only sits in a broad "editing" status, workload is hard to manage. One project may be in first assembly, another on final export, and a third paused while the client reviews it.
A practical post-production pipeline can use these states:
- Assets ready - the editor can start without searching for source files or answers.
- Rough cut - the main editorial work is active.
- Internal review - a producer, director, or lead checks it before the client sees it.
- Client review - the team waits for notes but keeps future revision capacity in view.
- Revisions active - comments are sorted and work is back with the editor.
- Finishing and export - audio, captions, graphics, file checks, and upload.
- Delivered - no active slot is held except an agreed warranty or support window.
This changes the planning conversation. Instead of asking "who is free?", the producer asks: "where is active work, where are we waiting, and where will work return?".
What to do: use the same editing states across all post-production projects. Do not let tasks sit for weeks in a vague "in progress" bucket.
2. Plan attention blocks, not just projects
Editing is not measured only in hours. A complex cut needs a long quiet block. A revision may need 40 minutes, but it still takes context.
Separate editing work into 3 types:
- deep assembly - story logic, pacing, structure, and creative problem-solving;
- operational revisions - titles, replacements, local changes, and short exports;
- final quality control - version checks, audio, captions, safe zones, and delivery.
Each type has a different switching cost. If an editor’s day gets chopped into small requests, deep assembly will slow down even when the total hours look reasonable.
What to do: schedule the kind of attention needed. For example, protect 3 morning hours for a rough cut, then use afternoon blocks for revisions and exports.
3. Hold a buffer for returning revisions
A project in client review does not fully release the team. Without reserved space for its return, every revision round lands inside someone else’s day.
Small studios can use a simple rule: every project sent for review gets a reserved revision slot. The size depends on the client and the complexity of the video.
For example:
- short corporate video - 2-3 hours per round;
- ad with motion graphics - half a day or a full day;
- series or multi-format package - a separate branch in the plan;
- new client with unclear feedback habits - a larger buffer than usual.
You may not use the whole buffer every time. That is fine. The point is to avoid selling the same hour twice.
What to do: when you send a cut for review, immediately place an "expected revisions" slot in the editor or post-production schedule.
4. Assign an owner for the queue, not a supervisor
Micromanagement often appears when nobody trusts the workload picture. A producer keeps asking "where are we?" because they cannot see status, risk, or next steps.
The studio needs one owner for the post-production queue. It can be a producer, post-production coordinator, or lead editor. Their job is to maintain one shared view:
- who is working on what now;
- which projects are waiting for review;
- where revision buffers are reserved;
- which tasks are at deadline risk;
- where freelance help or a deadline change is needed;
- which client requests change the scope.
A PMS like Basalt helps keep project status, deadlines, comments, and responsibility in one operating view instead of rebuilding workload from memory and private messages.
What to do: in a short daily sync, discuss only 3 things: blockers, returning revisions, and scope changes.
5. Separate urgency from production priority
Every studio has a client who writes louder than everyone else. If every urgent request becomes first in line, the post-production plan will keep collapsing.
Use a simple priority filter:
- Fixed external deadline - campaign launch, event, broadcast, or publication date.
- Distance to final delivery - a nearly finished project should not stall because of a minor task.
- Cost of waiting - crew, talent, rental, contractors, or the client’s team depends on the next decision.
- Commercial impact - the request affects payment, upsell, retention, or reputational risk.
This lets the studio respond calmly: "Today we are closing the project with the fixed launch date, and your revision is in tomorrow’s slot."
What to do: decide who is allowed to change priority in the editing queue. If everyone can do it, there is no real plan.
6. Bring in freelance help before the team overheats
A freelance editor helps only when they have context, assets, and a clean task. If you call them during a fire, their first job is understanding the project.
Freelance support works best for predictable blocks: first-pass selects, technical cutdowns from an approved master, captioned or clean versions, deliverables packaging, and simple recurring formats for a known client.
Keep sensitive story decisions and complex client revisions inside the core team.
What to do: keep a list of tasks that can safely move outside the studio, and prepare a handoff package in advance: brief, assets, approved master, naming rules, and definition of done.
A minimum process for the next week
If workload lives in chats and the producer’s head, start with one workweek.
- List every active project and its editing state.
- Add the responsible editor or external contractor.
- Mark projects that are in client review.
- Add buffers for expected revisions.
- Protect deep assembly blocks that cannot be broken by small tasks.
- Assign one owner for the post-production queue.
- At the end of the week, compare the plan with reality and note where capacity was overestimated.
After 2-3 weeks, you will have your own benchmarks for first cuts, revisions, freelance fit, and risky clients.
Checklist: is editor capacity under control?
- Every project has a clear editing state
- Projects in review are not treated as fully free
- Revision buffers exist in the schedule
- Deep assembly time is protected from constant switching
- One person owns the post-production queue
- Urgent requests pass through priority rules
- Freelance help starts before the team overheats
- The team sees work types, not only deadlines
- Each week, plan and reality are compared
If 3 or more boxes stay unchecked, the studio is probably managing workload reactively. That is not an editor problem. It is a signal that post-production needs a more honest production plan.
Frequently Asked Questions
Should we track every editor hour?
No. Hour-level tracking can create a false sense of control. Large work blocks, project state, revision buffers, and switching risk matter more.
How do we know we need another editor?
Look beyond project count. If rough cuts keep moving because revisions and small requests absorb the day, the team is already above sustainable capacity.
Who should own the post-production queue?
Usually a producer or post-production coordinator. In a small studio it may be the owner or lead editor, but the role has to be explicit.
Related Reading
- AI Post-Production Workflow: Keep Control of Every Cut - faster drafts still need control over versions and revisions
- How Social Cutdowns Quietly Kill Studio Margins - extra versions require real team capacity
- 5 Signs Your Studio Has Outgrown Spreadsheets and Chats - workload eventually outgrows scattered files
Summary
Editor workload does not break only because the team has a lot to do. It breaks when the studio cannot see what is promised, what will return after review, and what needs a quiet block of attention.
Start with one practical move: map every active project into an editing state for the next week and reserve buffers for expected revisions. That will show where your studio has real capacity, and where it only has hope.