TV broadcast graphics are a live visual system: lower thirds, tickers, bugs, full-screen information graphics, idents, openers, scoreboards and data cards all need to behave coherently on air. The design problem is therefore operational as well as visual. A strong package anticipates text variation, live data, safe areas, timing, editor controls and the constraints of the playout workflow.
A broadcast package has to solve brand, information and operation together
A polished lower third is not a broadcast system by itself. The typography used in that lower third has to relate to tickers, scoreboards and full-screen graphics; the animation language has to match idents and transitions; and the package has to survive real names, live data and operator changes.
| Layer | What it controls | Typical decisions |
|---|---|---|
| Brand language | How the channel looks and moves | Colour, type, shape, transition, motion curves |
| Information hierarchy | What the audience reads first | Name vs role, score vs team, headline vs source |
| Runtime behaviour | How graphics work on air | Editable fields, states, duration, loops, data and fallback |
Lower thirds are a family of information states, not one name strap
The lower third is one of the most visible components of television graphics, but it can represent several jobs: name and role, location, source attribution, quote, headline, score or breaking-news information. A robust package defines these as related states rather than redesigning the banner for every programme.
The design should be tested with realistic extremes. A short placeholder name hides problems that appear when a presenter has a long title, an organisation name wraps, or a two-line headline arrives seconds before transmission.
Tickers and crawls are continuous information products
A ticker or crawl can carry headlines, financial data, sports results, weather information or service messages. The operational questions include item separation, scroll speed, fixed modules, category states and what happens when the incoming data is longer or shorter than expected.
- Separate fixed modules from moving content.
- Make item boundaries obvious without creating visual noise.
- Test reading speed with real copy, not lorem ipsum.
- Design width changes and missing values as explicit states.
- Check the combined screen when ticker, lower third and bug are all present.
Bugs, idents and persistent channel identity solve different jobs
A channel bug is persistent or semi-persistent identity: logo, live indicator, clock, programme mark or another small status surface. An ident/opening sequence, by contrast, is a larger brand moment. Treating them with the same visual DNA but different intensity prevents the bug from fighting the programme while keeping the channel recognisable.
Persistent graphics benefit from defined states: normal, live, special event, sponsored programme, temporary campaign or other operational conditions. The system should state which elements may change and which brand constraints remain fixed.
Full-screen and data graphics need information design before animation
Election results, market tables, weather, fixtures and explainer graphics can contain far more information than a lower third. The first design problem is therefore grid, alignment, type hierarchy and semantic colour. Motion should support the reading order instead of competing with it.
Adobe’s current data-driven Motion Graphics template workflow shows one useful model: text, colour and numeric data can be mapped into reusable templates. A television graphics engine may use a different technology, but the systems principle transfers well—separate data from presentation so repeated graphics do not depend on manual layout edits.
Safe areas and simultaneous graphics have to be tested as a screen, not as isolated comps
Broadcaster delivery specifications traditionally require on-screen text to stay legible and within defined safe areas, including after conversion. Even when modern displays reduce some legacy overscan concerns, the correct rule is still to test against the actual broadcaster or playout specification rather than assuming edge-to-edge design is always safe.
| Test | Question |
|---|---|
| Lower third + captions | Do critical texts collide? |
| Ticker + lower third + bug | Is hierarchy still obvious? |
| Long copy | Does the template wrap or shrink predictably? |
| Downscale / alternate output | Does type remain legible? |
| Bright/dark programme footage | Does persistent identity keep sufficient contrast? |
Reusable controls are part of the design
The designer should define the boundary between creative control and operator control. Adobe Motion Graphics templates illustrate this well: an After Effects author can expose the text, colour, media or choice controls that an editor needs while retaining the rest of the visual system. Essential Properties can also create multiple instances from one source composition without duplicating the design.
Responsive Design - Time is particularly relevant to lower thirds and straps. Protected intro/outro regions can retain their timing while the middle duration stretches to fit the edit, reducing the temptation to duplicate and retime every graphic manually.
What a professional broadcast graphics handoff should include
- A visual system guide
Define type, colour, spacing, motion, safe-area and state rules.
- Real templates or source projects
Deliver the assets in the format the editing or playout workflow actually uses.
- State coverage
Document normal, live, breaking, sponsored and event-specific variants where relevant.
- Data/control map
List every editable field, its expected data type and reasonable limits.
- Operator reference
Include preview videos and short notes explaining trigger, duration, fallback and incompatible combinations.
- QC evidence
Test long/empty values, simultaneous graphics and the real target output before sign-off.