Team update video template

Turn a weekly status note into a short video with progress, priorities and clear asks. Give colleagues the context they need before the next meeting.

See it in action with GNOME’s weekly Concessio update.

From this input to this video

GNOME’s public weekly report becomes a short update that separates completed work, work in progress and a request for contributors.

Create a 40-second update from the GNOME community, summarized from its public weekly report for GNOME contributors and users, covering October 2–9, 2026. Use this source material: https://thisweek.gnome.org/posts/2026/10/twig-269/. Open with the main takeaway: Concessio joined GNOME Circle and shipped version 1.0, with further permissions work underway. Cover completed work: Concessio 1.0 was released, the app joined GNOME Circle, and the release improved file opening, drag-and-drop support, permission editing with undo, and accessibility. Then explain work in progress: Ronnie Nissan is working on Vala bindings for libacl to support access control lists in Concessio later. State these decisions or requests, with the responsible owner and next date: Ronnie Nissan invites contributors experienced in writing bindings to get in touch; no deadline is supplied in the report. Use only dates and metrics supplied in the source. Clearly label completed, in-progress and planned work. End with Read the October 9 GNOME update and contact the maintainer through the linked project if you can help. Tone: clear and collegial. Voiceover language: English.

What you start with
What you get
Drag to compare
Read the exact input

Prompt

Create a 40-second update from the GNOME community, summarized from its public weekly report for GNOME contributors and users, covering October 2–9, 2026. Use this source material: https://thisweek.gnome.org/posts/2026/10/twig-269/. Open with the main takeaway: Concessio joined GNOME Circle and shipped version 1.0, with further permissions work underway. Cover completed work: Concessio 1.0 was released, the app joined GNOME Circle, and the release improved file opening, drag-and-drop support, permission editing with undo, and accessibility. Then explain work in progress: Ronnie Nissan is working on Vala bindings for libacl to support access control lists in Concessio later. State these decisions or requests, with the responsible owner and next date: Ronnie Nissan invites contributors experienced in writing bindings to get in touch; no deadline is supplied in the report. Use only dates and metrics supplied in the source. Clearly label completed, in-progress and planned work. End with Read the October 9 GNOME update and contact the maintainer through the linked project if you can help. Tone: clear and collegial. Voiceover language: English.

Selected style

Editorial

Read the video transcript

This week in GNOME, October second to ninth: Concessio joined GNOME Circle and shipped version 1.0, and more permissions work is already underway. Completed: Concessio 1.0 is out, and the app is now part of GNOME Circle. The release redesigns file opening, adds drag-and-drop, lets you change file permissions with undo, and improves accessibility throughout. In progress: maintainer Ronnie Nissan is writing Vala bindings for libacl. Planned: support for access control lists in Concessio, later on. A request from Ronnie: if you have experience writing bindings, please get in touch. The report sets no deadline. Read the October 9 GNOME update, and contact the maintainer through the linked project if you can help.

Make it yours

Fill in your details here, or continue and finish your brief in ngram.

Help filling in your brief
[duration]
Duration.
[team-name]
Team name.
[audience]
Audience.
[reporting-period]
Reporting period.
[source]
Source.
[headline]
Headline.
[completed-work]
Completed work.
[in-progress]
In progress.
[asks]
Asks.
[next-step]
Next step.
[tone]
Tone.
[vo-language]
Vo language.

Trusted by teams at

HubSpotDeelZapierITVVeevaDP WorldGenpactSafetyCulture

When to use this template

Turn a weekly status note into a short video with progress, priorities and clear asks. Give colleagues the context they need before the next meeting.

job: team update
Scene structure

A clear story to start from

Review the proposed plan to set the final scenes and pacing.

  1. 1

    Main takeaway

    Lead with the point colleagues should remember.

  2. 2

    Progress and priorities

    Separate finished work from work still under way.

  3. 3

    Decisions and asks

    Name each action, its owner and the next check-in.

How it works

Create your video

1

Bring the source

Use the material you want the video to explain and fill in the brief for your audience.

2

Make it yours

Choose your style, add your sources and select a Brand Kit if you want to use one.

3

Approve the plan

Review the proposed plan containing the script, approve it and watch the resulting video.

Start with your source

Turn your existing material into a video

Frequently asked questions

Can this become an investor update?

Yes. Set the audience to investors, supply the approved reporting period and metrics, and focus the asks on the decisions or introductions you need.

What should go into the source?

Use an approved status note, report or project update. Include the dates and owners you want repeated in the video.

What happens when I choose Use this template?

Your brief, selected style, aspect ratio and length carry into ngram through sign-in. Fill in the bracketed details here or in the app, add your own sources, and approve the plan containing the script when you are ready.

Can I make another version for a different channel?

Yes. After the first video is ready, ask ngram for another version and choose the new length and aspect ratio. Make each version from the same brief and source material.

Create your next team update video

Talk to sales