Why lower third templates should store a saved person
Somewhere in the series, the same executive's name is spelled two different ways. It was typed by hand both times, by two people, from memory.
Quick Answer: Lower third templates are the reusable name and title graphics that identify a speaker on screen. When the template stores a text field, every appearance of a familiar speaker becomes fresh typing. When it stores a saved person, with name, role and company, that typing turns into a selection.
What should lower third templates store instead of a line of text?
A person. Name, role, company and whatever else the graphic shows, saved once and referenced from then on.
A text field has no memory. It cannot tell you that this name has appeared before, or that the spelling in one of those videos is wrong, or that the title on the whole set is now out of date. It holds characters and asks no questions.
Storing the person changes the unit of work. Adding a familiar speaker to a new video stops being an act of typing and becomes an act of choosing, which is the same move a motion design system makes for the rest of your brand furniture.
Why do teams duplicate finished videos instead of reusing lower third templates?
Because duplicating the video is the only way to keep the setup. Someone asked us for starter templates and described the workaround in the same breath.
"Capsule.Video starter templates would be an awesome idea because I remember like obviously, now I just duplicate videos"
A marketer at a travel advertising technology company
A finished video, with its edit and its exports and its old title text, ends up serving as the container for a saved identity. The video becomes the storage medium because nothing else in the workflow offers to remember a person.
It works right up until the copy diverges from the original and nobody can say which duplicate is the good one, which is the state version control for video templates exists to clean up.
What do lower third templates cost you when a title changes?
Here is the same set of jobs, run through a template that stores text and a template that stores a person.
| Job | Template stores text | Template stores a person |
|---|---|---|
| Add a speaker who has appeared before | Type name, type role, type company, check spelling | Pick them from a list |
| Same speaker, third video this month | Third round of typing | Third selection |
| A speaker's title changes | New title typed into every future video | Update the record once |
| Find every video showing the old title | Open project files and read the text layers | Look up where the person is used |
| Hand the series to a new editor | They copy from whichever old video they can find | They select the saved person |
Take a monthly interview show with twelve episodes and the same four executives rotating through. One of them gets promoted in the spring, so the title on their card changes.
Every episode already published still carries the old title. Nobody is going to reopen eight projects to fix a role line, so the archive stays wrong and the team agrees to fix it going forward only. Two months later a new editor takes over, duplicates the most recent episode to inherit the setup, and pulls the title from the one video that had already been corrected. Now the archive is wrong in two directions.
Capsule's published figures put 30% of creative time into tedious tasks. Retyping a name the system already saw last week is a small, very repeatable piece of that number.
Why does the lower third templates problem rarely reach a product roadmap?
The friction is invisible to everyone except the person doing it. Typing a name is a few seconds of work, and nobody escalates a few seconds.
Buyers evaluate a template system by looking at output. They watch a video, the lower third looks right, the brand holds, the evaluation passes. The typing starts after the purchase, daily, for the two or three people who live in the tool.
So the request arrives sideways, in the shape of a workaround somebody already built. Duplicating a finished video to keep the setup is one of those, and it points at exactly where the memory should have been.
Give the lower third a record to point at instead of a field to fill in, and let the record be the thing people update when a title changes.
FAQ
What are lower third templates?
Lower third templates are reusable graphics that display a speaker's name, role and company in the lower part of the frame. When they store editable text fields, the same speaker information gets entered again for every video that speaker appears in.
How do you reuse a lower third for the same speaker across videos?
Save the speaker as a record the template references, then select that record in each new video. Where the tool cannot store a person, the workaround is duplicating a finished video to inherit the setup, which is how archives drift.
What happens to old videos when a speaker's job title changes?
They keep the old title. A template holding typed text has no link back to the videos it produced, so every past episode carries whatever was typed on the day, and finding them means opening project files one at a time.
Why do lower third templates cause so much repetitive work?
Each appearance is treated as new information rather than a reference to something already known. The template asks for name, role and company every time, and the person filling it in is the only one who ever sees the cost.