Clipping campaigns

A clipping campaign brief template editors can actually use

Write a clear brief for Reels and Shorts: source footage, editing rules, reward terms and a review checklist, with a worked podcast example.

By 6 min read
A campaign checklist beside source footage, a vertical storyboard and an approval card
Editorial illustration · Dashrize.
Share

“Make five clips from this episode. Keep them punchy.”

An editor can start from that message, but they have to guess almost everything: which moments matter, whether they can add music, where to publish, and what will get rejected. Those guesses become revisions after the work is already done.

A clipping campaign brief is the shared set of instructions for the source footage, intended audience, editing requirements, publication rules and reward conditions. A useful brief lets an editor check their own submission before sending it. It also gives the reviewer a reason for each approval or rejection.

This is a practical template for a brand or podcast team preparing Reels and Shorts. It is a planning aid, not a substitute for the platform’s terms or a rights agreement.

Start with the decision the viewer should make

Write the goal in one sentence before choosing a clip length. “Introduce this interview to people who manage a small shop” gives an editor a direction. “Go viral” does not explain which moment belongs in the cut.

Then choose one next step: watch the full interview, visit the profile, or learn a product feature. If you want someone to leave YouTube Shorts for a website, remember that ordinary description and comment URLs are not clickable. A call to action has to fit the placement. Source: YouTube’s clickable link guidance.

Copy this brief and fill the gaps

The bracketed values below are decisions for your team. They are not Dashrize defaults.

Brief field What to write
Intended viewer [Who this clip should help, and what they already know]
One next action [The single action the viewer should take]
Authorised footage [Source URL, asset folder, permitted timestamps, and who can answer access questions]
Editing boundaries [Target duration, framing, subtitle language, and any parts that must remain together]
Publication [Accepted platforms, permitted accounts, posting window, and whether cross-posts need separate submissions]
Caption requirements [Required hashtag, credit, disclosure instructions, and the intended link placement]
Claims and exclusions [Exact claims supported by the footage, and claims or edits that are not permitted]
Reward conditions [Rate and unit, qualifying metric, approval conditions, budget limits, and applicable platform terms]
Review evidence [Post URL, any requested screenshot, check time and reviewer contact]
Corrections [How to ask a question or respond to rejection; who approves changes before reposting]

If you cannot fill the source-access or reward-condition row, the campaign needs another conversation before it needs another editor.

Worked example: an independent shop-owner podcast

Imagine a podcast team promoting an interview about slow-moving stock. The following is a fictional example, not a customer case study or a live paid campaign.

  • Viewer: an owner who chooses inventory for a small retail shop.
  • Purpose: give the viewer one useful stock-check question, then invite them to watch the longer interview.
  • Source: the team’s authorised episode file, with a note pointing editors to the stock-ordering discussion.
  • Edit: one complete idea in a proposed 25–45 second cut. Keep the speaker’s condition attached to the recommendation; do not remove “if your margins allow it.”
  • Subtitles: readable on a phone, faithful to the spoken words, with any Hindi or English translation checked by someone fluent in that language.
  • Destination: the team’s channel profile, or an eligible related video where the publisher controls the YouTube channel. Editors should not imply they can attach another channel’s upload as their own related video.
  • Reward section: completed separately with the actual campaign’s rate, metric and review terms before recruitment opens.

Notice the constraint that does the most work: keep the condition attached to the recommendation. It prevents a misleading clip more clearly than “make sure it feels authentic.”

Turn vague feedback into checks an editor can pass

Instead of this Write this
Make the hook stronger The first sentence should identify the stock problem discussed in the clip
Add good captions Check the speaker’s name and product terms; preview subtitles on a phone
Stay on brand Use the supplied asset files and avoid the specific unsupported claims listed in the brief
Show proof Submit the published post URL and the named metric for the agreed reporting window

These are examples to adapt, not performance guarantees. An editor still needs room to choose a good moment and make the cut flow. Define the parts that affect accuracy and acceptance; leave room for judgment in the edit itself.

Put the brief into Dashrize’s campaign fields

Dashrize’s campaign setup supports a source link, instructions, allowed platforms, attachments or Drive links, and a required hashtag. Put the source in the source field and the review rules in the instructions. If you use a longer document, link it clearly and give it a version date so two editors do not unknowingly work from different rules.

Budget, expected views and platform reward settings belong in the campaign setup too. Check that the written brief agrees with what the campaign shows. Do not invent a separate payout promise in a document that contradicts the displayed terms. See how to run a clipping campaign for the surrounding setup.

Before recruiting broadly, ask one editor to read the brief and describe what they would submit. If their interpretation surprises you, change the instructions now. You have found a cheap problem to fix.

Questions brands and editors should settle early

Should every editor use the same opening sentence?

Only if exact wording is necessary. Otherwise, specify the audience and the accurate idea, and let editors try different openings. Requiring identical cuts makes it harder to learn which approach works.

Does a source link mean the footage and music are cleared?

No. Confirm that the team can authorise the intended footage, audio and uses. Being able to download a file is not permission to publish it. The brief should identify the approved assets and who can resolve rights questions; it should not tell editors to improvise permission.

What if a clip gets views but fails the brief?

Views do not erase the publication or review rules. State the review conditions before the work starts, explain a rejection against a written requirement, and clarify the correction process. Avoid changing the acceptance criteria after someone has edited to the agreed instructions.

Which view count belongs in the brief?

Name the actual metric and reporting source. “Views” is too loose when a public counter and private analytics measure different things. Our Shorts views versus engaged views guide explains why the distinction matters.

Prepared September 14, 2026. The template and podcast scenario are original illustrative examples; campaign terms must be completed for the actual offer.

Find these guides useful?

Add Dashrize as a preferred source on Google to see more of our creator-earnings guides in your Search results.

Keep reading