The Video Production Operator

The Video Production Operator

Fifteen skills for the people who shoot real footage with real cameras at real locations, and then do the paperwork themselves at eleven at night. Built for videographers and small production shops, not for marketers.

Download Plugin

the-video-production-operator.plugin

⏱ 15 min read ● Beginner Version 0.1.0

Section 01

What this actually is

The technical side of video is finished and mostly free. Rendering, generation, transcription, captioning, clipping, reframing — all solved, all well funded, none of it where your money goes.

Your money goes somewhere else entirely. It goes in the round of revisions nobody defined. In the deliverable that turned out to be nine files. In the release that covered the website but not the ad campaign. In the version you made twice because the spec said "social cuts". In the drive on your desk that is the only copy of a wedding.

That is the operating layer, and nothing is built for it. This pack is fifteen skills for exactly that layer, and every one of them ships a document you can send rather than advice you have to act on.

🎬

Who it is for: freelance videographers and small production shops, roughly two to fifteen people. Wedding, corporate, event, branded content, commercial. One person with a camera, or a producer plus a shooter plus an editor. People who are good at the craft and were never taught the paperwork that protects the margin.

There is no assumption about your genre, your country, your currency, or what you edit in. It asks, and it remembers. Where it needs a number it does not have, you get a clearly marked blank rather than a plausible figure that ends up in a document a client accepts.

Section 02

Start here

One phrase. That is the whole onboarding.

Say this first, and nothing else: "set me up"

About ten minutes, once. It asks what you shoot, your three or four most common job types, whether you shoot alone or with a crew, what you cut in, your rates including the lines nobody quotes — overtime, travel, kit, second shooter — and where you actually film, which decides what it says about permits, releases, privacy and disclosure everywhere else.

It asks for one real message you have sent a client. Not "what tone would you like", because "professional" describes thousands of different writers and gives the rest of the pack nothing. A real message shows how you open, how you sign off, how long your sentences run, and what you would never write.

And it asks two questions almost nobody is asked. What do clients usually assume is included that isn't? That answer becomes the exclusions on every quote you send. How many copies of your last finished project exist right now? The answer is often one.

Then it does the part most tools skip. It tells you which of three stages is actually leaking money:

Winning the job Not enough work, or work won at prices that never made money in the first place. The leak is upstream of any shoot.

Running the shoot Days overrun and go unbilled, costs get absorbed, or footage comes back without the paperwork that makes it usable.

Getting out of post Revisions run past what was quoted, deliverables get made twice, projects sit for weeks waiting on feedback nobody chased.

Not enough evidence yet Where the answer is thin it says the verdict is provisional and names what would confirm it, rather than dressing a guess as a diagnosis.

Most operators arrive certain they need more enquiries. The most common honest finding is that they include two rounds of revisions, have nothing written down, and just do the extra work. No rate rise fixes that, and being told so in minute nine is worth the whole ten minutes.

Section 03

The fifteen skills

You never have to learn a skill name. Say what you need in your own words and the right one opens. The headings below are just so you know what is in the box.

Setup

Set me up The one-time interview, the production profile, and the project tracker every other skill reads and writes. Ends with the verdict on which stage is leaking.

Winning the work

The client wants a video Discovery, the creative brief, and the treatment where the job needs one. Turns "make it inspiring" into something testable by finding what the viewer believes now and what they would have to believe instead.

What should I charge The estimate with assumptions, exclusions and a validity window; the internal budget with your real margin; and the actualisation sheet that tells you whether the last job made anything.

What am I actually delivering Every file with its spec, destination and approver, plus the real count hiding behind "and some social cuts". Catches the four things forgotten on every project.

Who owns the video Term, territory and media priced as a grid rather than given away. Checks the licence against the music, stock and talent permissions underneath it before writing a word of it.

Planning the shoot

What shots do I need A shot list tested join by join, so the film can actually be assembled. Also an honest answer on whether this job needs a storyboard, which most do not.

Should I shoot this or generate it A route per shot — filmed, generated, licensed, rendered — priced on what it costs to change rather than what it costs to make. Records provenance as the route is chosen.

Write me the prompt for this shot Built from shot grammar rather than model-specific phrasing, so it survives the tool being replaced. Opens by asking whether the shot is describable at all.

I'm filming Tuesday Recce report, run of day and call sheet — plus the one unconfirmed thing that would kill the day, and who to phone about it today.

Do I need a release Talent, minors, locations, property, permits, insurance, drone work, filming identifiable people in public, and consent for synthetic replicas. Scoped to what the footage has to do.

Post and delivery

I've got the footage, now what The paper edit as an argument rather than a shortlist of good bits, and an assembly your editing software imports — or a written paper edit that works just as well if it doesn't.

The client sent notes One de-duplicated timecoded change list with conflicts flagged, every note classified, and the reply that offers "within this round, or this is a change order — your call".

I'm ready to deliver The checks that must happen before anything leaves, the masters, and the handover package: files, disclosure note, licence dossier, covering message.

Do I need to label this as AI A dated assessment of which regime applies and whether this specific video triggers it. Most do not, and saying so accurately is the product.

How do I back this up The shoot-day offload routine, the naming convention, and an archive plan that counts independent failures rather than drives — because three drives on one desk are one copy.

⚡

The part that makes these worth paying for: every skill forms a judgement before it writes. Is this job priced to survive its own revisions. Is this footage an asset or a liability. Does this need a storyboard, or just a shot list. Which of these deliverables will have to be made twice. A skill that only generates is a template with better manners.

Section 04

When it pays for itself

Not evenly. There are about six moments where this pack earns a year of itself in an afternoon, and they are worth knowing so you reach for it at the right time.

Before you quote a job you have done badly before. The quote skill gives every line a unit and a boundary. "Edit and grade" is not a quantity, so no amount of extra editing ever becomes billable. That one pass is usually the difference between a job that makes money and one that felt fine until the end.

The moment a client says the word "ads". A release signed for a website and organic social is functionally unsigned for a paid campaign. The signature exists, the paperwork looks complete, and the footage still cannot do what it is about to be asked to do. Catching that before the campaign costs one short addendum.

At kickoff, when nobody has counted the files. "The film and some social cuts" is routinely nine deliverables. Counting them at kickoff is free. Counting them at delivery is a change order you have to ask for after the goodwill has been spent.

The night before a shoot. Not for the call sheet template — you have one. For the list of promises other people have to keep, and which of them have been confirmed with the person who actually has to keep them rather than with whoever booked it.

When the third round of notes arrives from someone who was not in the first two. The reply that holds the line without damaging the relationship is the message most people cannot write in the moment, and it is where the margin actually is.

Any time you notice you have one copy of something. Every other failure in this pack is recoverable. That one is not.

It also works in the other direction. If you are already good at one part — plenty of shooters are excellent at planning and terrible at licensing — the setup verdict will tell you where to spend your attention rather than asking you to adopt fifteen new habits at once.

Section 05

How the skills work together

The setup creates a project tracker that every skill reads and writes. That is what stops you retyping things, and it is the difference between a system and a folder of prompts.

What happensWhat it feeds

The brief settles the goal and the structureThe quote prices against them, and the shot list is built from the structure

The quote names a deliverable countThe deliverables spec checks itself against it and flags anything beyond, instead of absorbing it

The quote defines what a round of changes isThe review-round manager can hold that line later — it can only enforce a boundary the quote wrote

A shot is routed to generation or stockProvenance is recorded at that moment, so the disclosure question is answerable at delivery without reconstruction

A release is signed, or isn'tDelivery blocks on it, and the licence skill treats its scope as a cap on what you can grant

A deliverable gets made twiceThe count feeds the leak verdict, so a pattern across three projects becomes a finding rather than three separate irritations

A project is deliveredThe actuals come back to the next quote — quoted days against days used, quoted rounds against rounds that happened

That last row is the one that compounds. A single job that ran over tells you almost nothing. Three of a kind tells you whether your day count is wrong, your round definition is wrong, or your rate is wrong — and those need completely different fixes.

🔗

You can enter anywhere. Each skill says what it needs, reads whatever already exists, and asks only for what is genuinely missing. Nothing insists you start at the beginning of a project you are already halfway through.

Section 06

Connecting tools is optional

Every skill produces the finished thing in chat and as a file, always. Connectors only ever save you a step.

That is not modesty, it is the design. Several things you might expect to connect simply do not exist, and we checked the directory rather than assuming.

If you connectWhat it saves you

Google Drive or DropboxDocuments filed beside the project's files instead of downloaded and moved by hand

GmailCovering notes — quote, call sheet, release request, delivery — drafted into your drafts. Nothing is ever sent for you

Google CalendarShoot days, call times and feedback deadlines in your calendar rather than only on the plan

Notion or AirtableThe project tracker mirrored somewhere you can see it outside the chat

CanvaWhere your titles, thumbnails or social versions already get made there

Riverside, Descript, TellaEditing and media tools that work on material already held in those platforms

HyperFrames by HeyGenComposing and rendering animated titles or diagram sequences from markup

What does not exist, so you do not go looking

There is no connector for the common video review platforms, and one of them removed the developer tokens that would have made one possible. The review-round manager is built copy-and-paste first for exactly that reason: paste the comments in from wherever they arrived and it consolidates them.

There is no video publishing connector, and the major platforms restrict uploads for unaudited applications anyway. Nothing in this pack publishes on your behalf — including applying an AI disclosure label, which is yours to apply on your own account. The delivery note tells the client which files need it.

Production management tools in this space mostly have no public interface at all. Use a document store or a database connector for the tracker instead.

And two directory entries have confusing names. One named for a well-known text-to-speech company is actually their agents platform, not voice. One named for a well-known video generation company is an unrelated mobile release-management product. Neither does what the name suggests.

🔑

Connect nothing and everything still works. You will copy and paste more, and file a few documents yourself. No skill mentions that something is missing, and none stops halfway because a tool is not there.

Section 07

What it refuses to do

This is the section worth reading properly, because it is where a pack like this differs most from a folder of prompts — and because several of these refusals are the reason it is safe to put its output in front of a client.

It will not invent a number

No day rates. No permit fees. No licence costs. No crew prices. No competitor quotes. No regulatory thresholds. Where a real figure is needed and unknown, you are asked, and if you genuinely cannot say, you get a blank in square brackets.

The reasoning is narrow and practical: a blank gets filled in before the document goes out. A plausible-looking number gets sent, accepted, and then quoted back at you.

It will not rule on the law of your country

Releases, minors, permits, drone operation, filming identifiable people, privacy and synthetic-media disclosure all vary enormously by jurisdiction, and they are moving right now. The pack reads your location from setup, tells you what category of requirement applies, says what to check and with whom, and states no jurisdiction's rules.

Anything involving minors, medical or clinical content, synthetic replicas, or a place you are unsure about is flagged as worth a lawyer — said plainly, not buried as boilerplate.

⚠️

It will never claim a licence is cleared, and it will never represent a document as signed that has not been. The licensing skill produces a decision framework and a record of what was checked and when. It tells you what to verify and where — it does not assert that a specific track, clip or font is cleared for a specific use.

It is willing to say no label is needed

A compliance skill that flags everything is useless, because it gets ignored on the day it matters. The disclosure skill separates platform labelling from platform monetisation from statutory transparency — three things with different triggers that get constantly conflated — and then tells you plainly when this specific video triggers none of them.

The assessment is dated, because these rules move, and it travels with delivery so the client knows what they were told and when.

It blocks a delivery sparingly, and only for three things

A skill that blocks on everything gets routed around, and then it blocks on nothing. Three things genuinely stop a delivery: an unsigned release on footage going out, a grant the licences underneath cannot support, and a deliverable that does not exist. Everything else is flagged in the covering message and the files go.

It will not send, publish, sign or upload anything

Every message is written for you to read and send yourself. Nothing contacts a client, a crew member, a contributor or a location on your behalf, and nothing represents anything as executed.

💬

Quotes, licences, releases and change-order language are commercial drafts, not legal advice. Every document says so on its face rather than in a footnote, and says that anything binding is worth review by a lawyer where you operate.

Section 08

It will tell you things you do not want to hear

This is deliberate. Every verdict in the pack is allowed to come back inconvenient, and a tool that only agrees with you is not worth paying for.

"The number's fine — it's above what you charged for the last two. The problem is that four of these lines can't be exceeded. 'Edit and grade' isn't a quantity, so there's no version of this where extra editing becomes billable."

"You've got three copies and one event. They're all in the same room, so a break-in or a burst pipe takes all three at once. You don't need a fourth drive — you need one of the three somewhere else."

"There's a film in this and it isn't the briefed one. Nobody says anything usable about scale. What they talk about, repeatedly and well, is how long people stay. That's a better film, and someone approved the other one."

"One thing would kill Tuesday and it isn't the weather. The workshop's booked through their marketing manager, and nobody has spoken to whoever actually runs it. That's a five-minute call today."

"You can't grant this as written. The track is under a subscription that covers your own channels, and they want it in paid advertising in three countries. This surfaces as a claim after it's live."

In every case you can overrule it. Say so, and it records the decision and the date, does it your way, and does not raise it again. The record exists so that a later question about what was known and when is answerable in one line — which protects you far more than the argument would have.

Section 09

Installing it

Drag the-video-production-operator.plugin into the plugin upload dialog. That is the only installable file.

Open a new chat and say "set me up".

Answer the setup questions. About ten minutes, and you only do it once.

Go where the verdict sends you.

After that, just describe what you need. Some phrasings that work, none of which require remembering a skill name:

"what should I charge for this job" "the client wants a two minute brand video" "do I need a release for this" "write me a call sheet, I'm filming Tuesday" "they've asked for a version I never quoted for" "I've got four hours of interview, where do I start" "the client sent notes and it's the third round" "can they use this in ads" "do I need to label this as AI" "I've only got one copy of this project"

If your rates change, you get a new camera, you switch editing software, or you start filming somewhere new, just say so. It updates only what you named and does not restart the interview. A change of location will also prompt a fresh look at permits and releases, because those are the defaults that location actually governs.

A note on what is inside the download. The .plugin file is the only installable one. Alongside it you may also have README.md and CONNECTORS.md, which are for reading rather than installing — the first is the same content as this page in plain text, the second lists every connector and what it saves. Nothing in the package needs configuring before use.