Why nothing is moving on your video
A stalled edit needs a named next action. Check the production work, missing inputs and review decisions before guessing where the delay sits.
You sent the footage. Since then there has been one message, and it did not contain a date. You have reread your own last email to check whether you sounded annoyed, which is the point at which this has started costing you something other than money.
Before the chasing email, one question is worth more than any other, and it works on both sides: whose turn is it. Not when will it be ready. Who is holding it right now, and what are they waiting for.
The answer will land in one of two halves. Both are common, and only one of them gets written about.
The supplier's side
Four failures, in roughly the order they happen.
No acknowledgement. A message arrives and is not answered that working day. Not answered properly, just acknowledged: received, looking at it, back to you by Thursday. A supplier who lets messages sit unacknowledged has taught you that sending them achieves nothing, so you start sending more of them, which makes everything worse for everybody.
A shared inbox still needs an accountable owner for each project. Name the contact and the cover arrangement so the next reply can build on what has already been agreed.
No visible queue. You cannot tell whether your video is next or behind four others. Waiting is tolerable when you know what you are waiting behind. Waiting with no information is what turns a reasonable timescale into a grievance.
Silence treated as an acceptable state. The underlying belief is that no news is fine until there is news. It is not fine, because you have a launch, a series, a person expecting something, and you cannot plan around a gap. A delay you are told about early is an inconvenience. The same delay discovered late is a broken promise.
Your side
This half is worth checking before the email goes.
The footage arrived late, or incomplete. A slot booked for the week beginning Monday does not survive the material turning up on Thursday. It goes back into the queue, and by then the queue has somebody else in it.
Notes arriving in several batches can repeat setup and review work. Consolidate them where practical, and flag a late correction promptly if it changes something important.
An approval has been sitting unread. Somewhere in your inbox is a link that has been waiting for you since last week. From your side nothing is happening. From theirs, they are waiting for you, and they may have stopped chasing you for it because chasing a partner feels rude.
A decision nobody made. A question was asked in the middle of a long message and never answered, so the work stopped at that point. Both sides now believe they are waiting for the other, and that state can last a fortnight without anybody being at fault in a way they would recognise.
The reason your own delays are invisible to you is structural. Your part of the work finishes the moment you press send. Theirs starts when they open it. Nothing on your screen changes state, so nothing reminds you that it is still your turn.
What fixes both halves at once?
One shared place where the current state of every video is visible, and a rule that whoever holds it says so.
A shared status record makes the next action visible. It will not solve every capacity or decision problem, but it makes the conversation about them more concrete.
The record also reduces reconstruction: what was sent, what was decided and what is waiting. Use it to unblock the work, rather than to keep score against each other.
What does that look like if you have no software?
A single shared document, one row per video.
The name of the video, what state it is in, who is holding it, since when, and what it is waiting for. Updated when something changes hands, not on a weekly schedule, because the whole value is that it is true at the moment somebody looks at it.
You can build that this afternoon and share it with whoever is doing the work. If they will not keep it up, you have learned something concrete about how the next few months are going to go, and you learned it in a week.
What should you say when you have heard nothing?
Not any update on this? That invites a reply saying it is coming along.
Ask three things instead: where is it now, who is holding it, and what are you waiting for from me. The last one does the work. It is disarming, it is genuine, and often enough what comes back is an approval you never sent.
Agree working hours, response times, the named contact and how schedule changes will be communicated. Apply the published service commitment where one exists.
One row per video, and a column saying who is holding it right now. That is the whole apparatus, and it works without a supplier: somebody editing their own videos gets the same sheet, and the column stops being who and becomes what state is this in. Filmed. Cut. Waiting on a decision I keep not making. The last row is the one that explains most stalled channels.
Whichever half your current silence belongs to, the useful move is the same, and it is not the chasing email. It is deciding whether you are willing to keep the record straight on your own side, because somebody who cannot see when you are the delay has no way to tell you, and that is as true when the somebody is you.
Sources and evidence
Our method. Acknowledging every message the same working day, naming one person responsible for a video, and keeping one row per video showing who is currently holding it, is how this studio keeps a production queue visible. It is a working practice, not an external rule.
Keep reading
Where this becomes a system.
See how we apply this in our work.
Start with the Free Audit
Send a link to your work.
Your audit usually arrives within three working days. We use your details only to reply to your enquiry.
What you will get
What is working, what could improve and whether we can help.
Two or three priorities, with the reason for each.
A recommended next step, even if that step is not us.
There is no obligation to continue. We only arrange a call if you ask for one.