Video production for media and publishing
A publisher shoots two kinds of video with one crew: editorial work that must stay independent, and commercial work that must be labelled as such.
What this is about
The wall between editorial and commercial output runs straight through the production plan. A branded format needs visible labelling and cannot borrow the credibility of the newsroom's own reporting, while an editorial piece cannot accept client input at all — which means separate briefings, approval routes and often separate shoot days in one building. The newsroom itself is a difficult location: monitors show unpublished stories, contact lists and source names, so screens are switched and desks cleared before the crew enters. Archive material carries licences with territory and term limits that a social cutdown quietly violates. And formats are series, so the plan has to make episode twelve producible in a fraction of the time episode one took.
Sector routine beats general experience: knowing the field's approval paths and constraints produces more realistic plans than more shoot days without that context.
What runs differently here
Where this differs from the general case:
- Branded content and editorial video follow different rules for labelling, client involvement and approval, and mixing them in one shoot day confuses both
- Newsroom screens carry unpublished stories and source contacts; every monitor in frame is switched to a prepared view before the camera is set
- Archive and agency footage comes with territory, term and platform limits — a clip cleared for the site is not automatically cleared for social
- Reporters on camera may not reveal sources, locations or ongoing investigations, so interview questions are agreed with the desk beforehand
- Series formats live on repeatability: a documented setup, a fixed episode structure and a template shot list decide whether episode twelve is affordable
What the plan has to deliver
A production plan is useful to this role when it provides the following:
- A clear declaration per piece: editorial or commercial, with the labelling and the approval route written next to it
- A screen and desk plan for newsroom scenes, prepared by the desk editor rather than improvised on the day
- A rights sheet for every archive clip listing territory, term and permitted platforms
Common pitfalls
What most often goes wrong in practice:
- Letting a commercial partner sit in on an editorial interview because both were on the same call sheet
- Filming a wide shot of the desk with a source name legible on a second monitor
- Building a format whose first episode took three days and whose budget assumed one
With TillyGen
TillyGen keeps each piece typed as editorial or commercial with its approval route and rights notes on the scenes, and turns a format into a reusable template so later episodes plan themselves.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
Can editorial and branded shoots share a day?
Better not. Different rules on client presence, labelling and approval apply, and a shared call sheet blurs them in front of the people you filmed. Separate the days, or at minimum separate the blocks with different contacts.
How do we film in a working newsroom?
Prepare it. The desk editor switches monitors to a cleared view, clears paper from the frame line and briefs who may be filmed. Anything about an ongoing investigation stays out of shot and out of the interview.
What do we need to check on archive footage?
Territory, term, platform and whether the licence covers social cutdowns and thumbnails. A clip cleared for one publication in one country is a rights problem the moment the format is syndicated.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.