Before the game

Set up in this order Both products

Both of these are shared configuration — build them once and they are there on the desktop and in the browser, on whichever machine you end up working from.

1
Your code replacement file

The shortcuts that turn h30 into a full caption. Generate it from the two rosters, or bring your own. Do this first. It isn't only a typing convenience — it is the vocabulary that audio transcription is matched against, so it has to exist before your images land, not after you notice the captions are wrong.

2
Your XMP templates

Credit, copyright, location, the agency-specific field sets — the metadata that should be true of every frame from this game. Set the template before the game starts and it is applied as you work, rather than being something you retrofit to four hundred frames afterwards.

Delivery destinations and filename recipes matter too — but those are standing configuration rather than per-game prep. Set them up once and they're waiting for you every Saturday.

Building the code file from the roster

Pick the matchup and Deadline generates a shortcut for every player and head coach on both benches — home prefixed h, visitors v, followed by the jersey number. Roughly a minute's work for a full game.

Generated from a two-team roster
Type thisYou get
eventLakeview Riverside St. basketball
hRiverside State Ravens
h30Riverside State guard Marcus Vale (30)
h4Riverside State center Dominic Boyle (4)
v11Lakeview forward Andre Whitfield (11)
hhcRiverside State Head Coach Teresa Nunn
vhcLakeview Head Coach Bill Ackerman
AP style or Getty style, chosen when you generate. The same roster produces Riverside State guard Marcus Vale (30) for AP-style captions, or Marcus Vale (30) of the Riverside State Ravens, guard for Getty. Jersey numbers render as (30), #30, or not at all.
During the game

How the frames arrive

This is the one place the two products genuinely differ. Everything after it is the same work in the same shape.

FTP from camera
DeadlineFTP

The camera sends frames as you shoot them. They land in the gallery seconds later with thumbnails already made, ready to caption from a phone or a laptop — or by someone else entirely, back at the desk.

Ingest cards
Deadline Editor

Pull the card and ingest to the desktop, with the full-resolution originals in front of you. The usual choice when the edit matters more than the first ten seconds.

Or sync down from DeadlineFTP. Frames that came off the camera by FTP can be pulled into the Editor for a proper pass — transmit early, finish properly.
From here the two paths are the same work: caption, edit, deliver.
Same on both

Caption Both products

Three keystrokes for a full caption — or none at all, if your hands are busy.

Typed

h30, v11, hhc. Each shortcut carries a long form, a short form and the bare name, so one code can fill a full caption, a credit line, or just a name field.

Spoken

Record a voice memo naming the play. The transcript is matched against your code file and the codes expand into the same full caption text.

What you say → what the caption reads
“h30 pulls up for three over v11 late in the second half”
“Riverside State guard Marcus Vale (30) pulls up for three over Lakeview forward Andre Whitfield (11) late in the second half”

This is why step one is step one. Your codes and team names are fed to the transcription as vocabulary before it runs — without them, h30 comes back as “hay thirty” and nothing matches. A code that isn't on today's roster is left exactly as spoken rather than guessed at.

Same on both

Edit, then deliver Both products

Cull, tone, finish the metadata, send it. The XMP template you set this morning is already applied, so this is a check rather than a chore.

See it set up on your own fixture

Thirty minutes, screen shared. Bring a matchup you're shooting this week and we'll build the code file and the XMP template live, then send a captioned frame end to end.

Book a demo
Or read the side-by-side comparison of the two products first.