Review submissions and request changes

Use submission review to confirm that a creator’s work meets the campaign’s non-negotiable requirements. It is not a tool for directing a creator’s personal style, tone, or editorial choices when those choices remain within the brief and its mandatory rules.

Studios can review submissions from a campaign’s Videos tab or from the studio-wide video queue. A new submission creates a notification; notification delivery can be adjusted by the recipient in their notification preferences.

Understand the submission states

State	What it means	What happens next
Needs review	A creator has attached a review video and the studio must decide.	Approve it or request changes tied to mandatory rules.
Changes requested	The studio identified one or more mandatory rules that are not met.	The creator replaces the review video and submits it again.
Approved	The review is complete.	The creator can publish and attach the public video from a connected account.
Published	A public video has been selected for the approved submission.	Ripple can track the campaign performance and payout eligibility.
Escalated to Ripple	A second review request was required after a resubmission (shown on the video detail page with the Handled by Ripple support panel).	Ripple receives a support ticket and reviews the compliance issue.

Open the review queue

1. Open the relevant campaign from Campaigns and select Videos, or open the studio-wide video queue.
2. Use the filters to focus on videos that need review.
3. Open the submission and review the attached video against the campaign’s brief and mandatory rules.

Check the deliverable, required platform, embargo timing, disclosure, required hashtags, and each mandatory rule. Constraints can guide production, but mandatory rules are the basis for a review decision.

Approve compliant work

Approve a submission when the attached review video meets the campaign’s mandatory rules and is ready for publication.

1. Open the submission.
2. Confirm the video complies with each mandatory requirement.
3. Select Approve video.
4. Confirm the decision if prompted.

Approval is final. This includes automatic approval: if a campaign uses an automatic approval setting, once Ripple marks the submission approved, the studio cannot later request changes through the normal review flow.

Do not approve a video in the hope that it can be adjusted later. If a mandatory rule is not met, request changes before approval.

Request changes only for mandatory-rule issues

Use Request changes when the video fails one or more mandatory rules. There is no free-text creative-feedback field in this flow. Instead, select the specific mandatory rule or rules that are not respected.

This protects both sides:

• the creator receives concrete, campaign-defined feedback;
• the studio records the factual compliance issue;
• personal taste does not become an arbitrary reason to delay or refuse a compliant submission.

Do not use Request changes merely because you would have preferred another editing style, tone, thumbnail, or creative angle if the creator has respected the mandatory rules.

1. Open the submission in Needs review.
2. Select Request changes.
3. Select every mandatory rule that is not respected.
4. Confirm the request.

The creator is notified of the selected rule or rules. The submission becomes Changes requested.

What happens after a change request

The creator can make a corrected video and attach it to the same submission. Ripple replaces the existing review video rather than creating a separate submission, then returns the submission to Needs review.

Review the corrected version again against the same mandatory rules. A request for changes is not a rejection, and the creator gets a genuine opportunity to remedy the identified issue.

A second non-compliant review

If the studio requests changes again after the creator has resubmitted, Ripple does not automatically make the submission payout-ineligible. Instead, the video detail page shows Escalated to Ripple (with the Handled by Ripple support panel) and Ripple opens a support ticket containing the selected compliance issues.

Ripple then reviews the situation. This escalation prevents a repeated compliance decision from being resolved unilaterally through endless change requests or an automatic financial penalty.

Publication after approval

After approval, the creator publishes the video on an allowed platform while respecting the campaign schedule and any embargo. Then they return to Ripple and select the matching public video from videos detected on their connected social accounts.

One submission represents one piece of content and can hold up to one published video per allowed platform. Attaching a public, eligible video from one allowed platform is enough for the submission to become Published; additional allowed platforms remain optional on the same submission. Ripple does not assume that every detected video belongs to the campaign.

If a public video is published before the campaign embargo, Ripple automatically records the embargo violation and marks the submission not eligible for payout. The studio does not need to use the normal review flow to trigger this outcome.

Review responsibly

Keep your review decisions consistent and timely:

• use only mandatory rules as the basis for a change request;
• review before any configured auto-approval deadline expires;
• approve only work that is ready to publish;
• treat a second compliance issue as an escalation to Ripple, not as a personal dispute;
• keep embargoes and required hashtags in view before publication.

For a campaign-wide view of timing and results, continue with Monitor a live campaign.