Creator Content Intake That Doesn't Lose Cuts

Ask a creator ops manager about their worst campaign moment and you'll rarely hear about a video that failed review. You'll hear about the one that went live without being reviewed at all, because it arrived as a DM on a Friday and the person who saw it assumed someone else had it.

Intake is the least interesting stage of the approval workflow and the one that produces the most expensive failures, because everything downstream is conditional on a cut being in the system. A rigorous review process applied to 90% of the content is not a rigorous review process.

The failure isn't sloppiness, it's the number of doors

Content arrives however each creator prefers: email attachments, WeTransfer links, Google Drive folders, Instagram DMs, a Slack channel someone set up for one campaign and kept using, a text message to whoever they met at the shoot.

Every door is reasonable in isolation. Collectively they produce four specific problems:

• No single queue, so "what's outstanding right now" is a question nobody can answer without asking four people.
• No arrival time, so you can't tell whether a creator is late or you are.
• Silent drops. A DM read on a phone and mentally filed is indistinguishable from one that was actioned.
• Ambiguous versions. final_v2_REAL.mp4 in a Drive folder next to final_v2.mp4 is a coin flip.

The fix isn't a better tool necessarily. It's a decision: one door, and content that arrives any other way gets redirected rather than reviewed. That second half is the part teams skip, and it's what makes the rule hold. If DMs still get reviewed, DMs are still an intake channel.

What a cut has to carry to be reviewable

A file on its own isn't enough to review. The intake step exists to attach the context that makes the review possible, and if it doesn't capture these, someone reconstructs them by hand later:

• Which creator, and which upload link or contract it belongs to
• Which deliverable it satisfies, specifically. Not "a video for the summer campaign"
• Which version it is of that deliverable
• Which surfaces it's cut for, since a Reel and a Short from the same master are two reviews
• The rules in force for that deliverable at the moment it arrived
• Arrival timestamp, which starts the turnaround clock

That fifth one is the one people miss. Campaign rules change mid-flight, and a cut delivered on the 3rd was made against the brief as it stood on the 3rd. If your intake doesn't record which version of the rules applied, a reviewer three weeks later is judging a video against a standard the creator never saw. That's also why the brief has to travel with the video.

Versions belong to the deliverable, not the creator

This sounds pedantic and it's the thing that most often corrupts a queue.

A creator contracted for three videos will deliver a v1 of each, then a v2 of whichever ones came back with notes. If your numbering is per creator, their second video's first cut becomes "v4," which is meaningless, and the revision history of any single video is impossible to read.

Number per deliverable. Creator A, video 2, version 1. Their second video starts at v1 again, because it's a different video and not a revision of the first. Every deliverable then has a clean history you can read top to bottom: what was submitted, what came back, what changed.

The related rule: each deliverable occupies its own row in the queue. A creator who owes three videos and has delivered two should appear as two items awaiting review and one outstanding, not as one line item that hides the rest.

Make the creator's side easy or they'll route around it

Intake discipline fails when the official channel is worse than a DM. Creators are working from a phone, often on a deadline, and often for several brands at once. If your door requires an account, a password reset, a VPN, or a form with eleven fields, they'll send a Drive link instead and you'll accept it, because the alternative is not having the video.

What keeps a single door intact:

• No account for the creator. A link that identifies them is enough, and one fewer credential is one fewer support conversation.
• Works on a phone, including the upload of a multi-gigabyte file over a mediocre connection.
• Shows them the brief and their last round's notes at the moment of upload, which is when it's actually useful rather than a week earlier in an email.
• Confirms receipt immediately, so nobody sends a "did you get it?" message.
• Accepts the file they have, rather than demanding a specific codec or aspect ratio they'd need a laptop to produce.

The confirmation matters more than it looks. A large fraction of creator ops messaging is people checking whether a thing arrived, and each one costs both sides a context switch.

Intake is where the clock starts

Once every cut has an arrival timestamp, turnaround becomes measurable, and the whole review function gets a number: time from upload to decision.

That single metric surfaces problems no quality review will. A backlog is visible before anyone complains. A creator waiting nine days shows up as a nine-day-old row rather than as a relationship that quietly cools. And the escalation path has something objective to trigger on, which is what makes the ownership split in who should own creator content approval enforceable instead of aspirational.

It also changes the argument about capacity. "We're behind" is a feeling. "The median cut waits 3.5 days and the oldest is 11" is a staffing case.

Doing it without buying anything

If you're not ready to change tooling, most of the value is available from a shared sheet, as long as it's genuinely the only door:

1. One folder or form where everything lands, and a stated rule that anything arriving elsewhere gets redirected to it.
2. A row per deliverable, not per creator, with version, arrival date, status, and decision.
3. The brief version recorded against each row.
4. A weekly look at the oldest open row.

That's a worse product than a real system and it's dramatically better than four doors. The failure mode this prevents isn't inefficiency, it's the video that went live unreviewed, which is the only intake failure that ever becomes a real problem. The rest of the stages are in the approval workflow guide.