From an empty week to a show that ran.

01 · The production

Put the week in one calendar.

Dates, venue and the shape of the production, next to every other production you have on. The clash you would otherwise find in an email thread shows up while there is still time to move something. It also publishes as a subscription feed, so the dates land in the calendar the rest of the company already uses.

LiveRun production calendar: a month view with six productions across September and October — CalendarSix productions, September into October

02 · The day

Build it in blocks, rig to strike.

Not just the show window. Rig, load-in, soundcheck, blocking, rehearsal, doors, transmission, strike — each block with its own window, the departments called into it and the people on site. Move one block and everything after it cascades. Pin the transmission block and it holds at 19:00 while the rehearsal runs long.

LiveRun production day: blocks from rig and load-in through soundcheck to strike, each with the departments called and their team leads — Production daySeven blocks · six departmentsTransmission pinned

03 · The people

Name the team leaders.
They bring their own crews.

A producer typing in thirty names is a producer doing somebody else’s job. Name one lead per department and they staff their own department, and only their own — that limit is in the database, not in a convention. Everyone is inside the production from the first week, not on the morning of the show.

LiveRun teams tab: six departments, each with its team lead, phone, e-mail, on-site window and invitation progress — Departments and leads17 people · 15 confirmed

04 · The rundown

Write the show, or start from one you have run before.

Segments with durations, sources, video, audio, graphics, location and notes, adding up against the block window as you type. Columns are yours: switch them on, reorder them, pin the ones that never move — and the order you set is the order the operator scans in the console. Lock a duration that is not yours to change. Turn on time anchors for sport. Save the result as a template, or pull a running order straight out of a production you ran before.

LiveRun rundown editor: the transmission block from 19:00 to 20:30 with fifteen segments in sections, each carrying source, video, audio, graphics, location and duration, and a counter for the free time left in the block — Rundown editor1:03:00 written into a 1:30:00 block27:00 free

05 · The show

Send the links, then run it.

The crew get their links by e-mail, each one its own — the panel shows who has not had theirs yet rather than a wall of confirmations. Then the transmission block opens: the console takes the clock, the wallboard goes up in the green room, and the phones on the floor follow the same rundown the gallery is reading.

LiveRun live console on air: wall clock, transmission clock, time in segment with drift, time to next, the current segment panel, the next two segments and the full segment timeline — Live consoleSegment 6 of 15On air

Your first hour, by role.

Producer

You build the day.

Create the production and its days
Lay out the blocks and pin the transmission window
Name one lead per department
Set the notification lead time for the production
Send the crew their links

Show director

You drive the show.

Open the rundown and write or import it
Set the columns you scan by
Lock the durations that are not yours to change
At the transmission block, take the console

Team leader

You staff one department and write its notes.

Accept the invitation by e-mail
Add your own crew and their call times
Write your department’s notes onto the segments that need them
Nobody outside your department reads them

Crew

You open a link.

Open the link from your producer
Add it to the home screen
Read your call time and the day around it
On air, read the segment and the note written for you

What this does not do.

Not playout

It does not play a single frame, drive automation or touch a router. It tells the people who do those things what is next, and when.

Not the project tracker

Keep the tracker your office runs on. It was not built for the week the set goes up, and it is no use with minutes to air.

Not the company messenger

Keep that too. The channels here exist because the roster exists, and they disappear with the production.

Not a newsroom system

There is no wire, no story pool and no scripting workflow for a daily bulletin. This is built for a production day with a transmission window at the end of it.