Video production for telecommunications
Half a telco film happens somewhere nobody may simply walk into: up a mast, inside an exchange, or in a customer's living room.
What this is about
The imagery a telecom brand wants is exactly the imagery that is hardest to access. Mast and rooftop work means height safety: only certified climbers go up, camera operators need the same qualification or the shot comes from a drone, and the rigger's schedule beats the light. Exchanges, data centres and network operation centres count as protected infrastructure, with visitor registration, escorted movement and rules about what may be legible on a screen. In private homes, the installation shoot needs the resident's agreement as well as the technician's. Meanwhile the claims side moves fast — coverage and speed statements are tied to a date and a footnote, so a film that quotes a number ages the day the number changes.
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
In planning terms, that means:
- Mast, tower and rooftop shots require certified height workers; an unqualified camera operator stays on the ground and the angle comes from a drone or a rigged mount
- Exchanges, data centres and operation centres are access-controlled: names are registered days ahead, movement is escorted, and screens showing live network state are off limits
- Coverage and speed statements carry a validity date and a footnote — a scene built on a specific figure has a shorter shelf life than the film around it
- Home installation scenes need consent from the residents as well as the employer, and the flat has to be dressed so no neighbour's data or door name is readable
- Field technicians work to dispatch schedules: the shoot follows their route for the day, and an emergency callout removes your protagonist without notice
What the plan has to deliver
A production plan is useful to this role when it provides the following:
- A height-work plan naming who climbs, who is certified, and what the drone alternative delivers if the weather closes the climb
- Site registrations for every secured location, submitted with names and identity details before the deadline the operator sets
- Claim wording tied to a source and a date, agreed with legal before the voiceover is recorded
Common pitfalls
What most often goes wrong in practice:
- Storyboarding a climb the camera team is not certified to join
- Quoting a network figure in the voiceover that changes with the next quarterly update
- Filming a technician's day without asking the household whose hallway ends up in the film
With TillyGen
TillyGen splits the briefing into scenes carrying their access type, qualification requirement and claim status, so the mast day, the secured site and the customer visit each arrive with the paperwork they need.
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 our camera operator climb the mast?
Only with valid height-safety qualification and the operator's approval. Otherwise plan the height perspective as a drone shot, a rigged action camera worn by a certified climber, or a ground-based long lens.
How far ahead do secured sites need notice?
Days at least, sometimes longer, and always with full names and identity details for everyone entering. Send the equipment list too, because recording devices are often reviewed separately from people.
How should the film handle network claims?
Anchor every figure to a source and a date, keep the footnote legible, and prefer statements that stay true after the next update. Where a number is essential, plan a graphic that can be re-rendered without a reshoot.
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.