Async video status update: a 60-second script and template
A status video replaces a status meeting only if it is shorter than the meeting’s first agenda item. This page gives you a 60-second script with timings, the three-line summary to post with it, a full example for a project that has slipped, and a table of what to change for your team, your manager, executives, and clients.
7-day trial · $49 once · no subscription · Apple Silicon · macOS 14+The short answer
A good async video status update runs 60 to 120 seconds and covers four things in order: the status in one sentence, what changed since the last update (shown on screen), the main risk with its owner and date, and the one decision you need. Post it with a three-line written summary so people who skip the video still get the status.
Record a video when…
Progress is something people can see, or the status changed and the reason needs 30 seconds.
- There is a prototype, a dashboard, or a before-and-after to show.
- The status moved from on track to at risk and people will ask why.
- The audience is spread across time zones and the weekly call suits nobody.
- You are replacing a 30-minute status meeting where most people only listen.
Write it or call instead when…
There is nothing to show, or the situation needs a conversation.
- Nothing changed. Write “on track, no changes” and stop.
- The update is a number or a date. One line in the channel is faster.
- It is an incident. Page people; do not make them watch a video.
- The decision needs three or more people to argue it out. Book the meeting, and send the video beforehand as context.
60-second status update script, with timings
Open the thing you will show (the build, the board, the chart) before you start. Close everything else. Then say these four parts in order.
- 0:00–0:10 · Status and reason. “Checkout redesign is at risk. Tax calculation is waiting on the provider’s test account.”
- 0:10–0:30 · What changed, on screen. Show one or two finished things. “Since Monday: the address step is done, and here is the new order summary.”
- 0:30–0:45 · Risk, owner, date. “If we don’t have the test account by Wednesday, launch moves from the 14th to the 21st. Priya is chasing it.”
- 0:45–0:55 · The ask. One decision or one favor, addressed to a named person. “Marcus, can you escalate with the provider today?”
- 0:55–1:00 · Where to reply. “Answer in the project thread. Next update Friday.”
Written summary template to post with the video
Half your audience will read this and not press play. That is fine: the summary carries the status, and the video carries the evidence. Keep it to these lines.
- Status: On track / At risk / Blocked, plus the reason in one clause.
- Changed since last update: one or two items.
- Risk: what, who owns it, and the date it starts to cost you.
- Ask: @name, the decision or help needed, by when.
- Video: link and length, for example (1:05).
- Source: link to the board, plan, or dashboard shown in the video.
Worked example: a checkout project in week 6
The project: an eight-week checkout redesign with a launch date of the 14th. In week 6 the tax integration is stuck. The video is 1:05 long and shows two screens: the working address step in the staging build, and the project board with the tax ticket in Blocked. The post in the project thread reads:
“Status: At risk. Tax calculation is blocked on the provider’s test account. Changed: address step done; new order summary in staging. Risk: without the test account by Wed, launch moves from the 14th to the 21st (owner: Priya). Ask: @Marcus, please escalate with the provider today. Video (1:05): link. Board: link.”
What makes it work: the status is the first word, the date slip is a number, and exactly one person is asked for exactly one thing. Everything else on the board stays off the video.
What to include in a status update, by audience
The four parts stay the same. The length and the opening line change with who is watching.
| Audience | Length | Lead with | Leave out |
|---|---|---|---|
| Your own team | 60–90 seconds | What is blocked and who can unblock it | Background they already know |
| Your manager | 60–120 seconds | Status, then the decision you need | Task-level detail |
| Executives | 45–60 seconds | Date, budget, and the one risk | How the work was done |
| A client | 90–120 seconds | What they can see or try now | Internal names and tools |
Recording a status update on a Mac with Qreata
Status updates have a specific failure: one wrong fact. At 0:35 you say “the 14th” when you meant “the 21st.” A date error in a status update is worse than no update, and re-recording the full minute invites a different slip. The screen is right and one word is wrong, so in Qreata you select 0:33–0:38 on the timeline and choose Record voiceover · keep video in the Segment menu: you say the right date over the same picture, and recording stops at the end of the range. If the screen was wrong as well, Replace Take (the Rerecord tool in the editor) re-records picture and sound together. The remaining 55 seconds stay untouched.
To get from a rambling 1:40 to a tight 1:05, use the local transcript. Remove silences takes out the pauses, Remove filler words takes out “um” and “uh”, and you cut a false start or a repeated sentence by deleting its words, so tightening does not mean dragging trim handles.
When the evidence is one number on a dashboard, add a zoom on it by hand, or turn on Auto-zoom on clicks and click the number, so it is readable in a chat preview. Captions in video burns the words into the picture for people who watch the preview muted. And because recording and editing run locally with no account, an unannounced roadmap or revenue chart stays on your Mac unless you press an upload button.
What Qreata does not do: it does not post to your chat tool, notify anyone, or collect replies. You export the file, or get a link by pressing the Google Drive button or through the separate paid Qreata Cloud, and paste it yourself. For a ten-minute test in the 7-day trial, record this week’s update with the script above, then change one date with Record voiceover · keep video and listen to the join.
Common mistakes in async status videos
Each of these sends people back to asking for a meeting.
- Narrating chronologically (“on Monday we…, on Tuesday we…”). Lead with the status.
- Hiding the bad news at 2:40 of a three-minute video.
- An ask addressed to “the team.” Name one person.
- Scrolling through the whole board. Show the two tickets that matter.
- No written summary, so the status cannot be searched next month.
- Recording every week out of habit when nothing changed.
- Quietly replacing a video after people watched it. If a fact changed, post a correction in the thread.
Questions worth asking
How long should an async status update video be?
60 to 120 seconds. One minute is enough for status, change, risk, and ask. Go to two minutes only when you have something on screen that needs explaining.
What should a weekly status update include?
Four things, in this order: the status with its reason, what changed since last week, the main risk with an owner and a date, and the one decision or help you need.
How often should I send an async status update?
Once a week for an active project, on the same day each week. Skip the video and write one line in weeks when nothing changed.
Can async video updates replace status meetings?
Yes for the part of the meeting where people report progress. No for decisions that need discussion; keep a shorter meeting for those and send the video the day before.
Does Qreata post the video to Slack or notify my team?
No. Qreata exports an MP4 and can upload it to Google Drive or the paid Qreata Cloud for a link. You paste the file or link into your channel yourself.