How do I send a change request to a Creator?

When a Creator submits content, you can ask them for changes without leaving Cohley. Change requests are sent from the asset itself, while the content is still in Content to Review — before you accept it.

Which briefs have change requests

Change requests are part of the manual content-review step, so they exist on the brief types that have one: UGC, Influencer Partnership and Professional briefs. You review each submission in Content to Review and can send changes before you accept it.

Seeding and Product Review briefs have no change requests. In a Seeding brief, content is cleared to post automatically once it passes AI Asset Analysis, so there is no review step to send feedback from — you can still see what was flagged (What is a Seeding Brief?). Product Review briefs have no change-request step either. If you need approval over what gets posted, run a UGC or Influencer Partnership brief.

Where change requests happen

Open the asset and click into the Full Asset View. This is where you review a submission and send feedback on it. You'll see several sections:

• Caption — if the Creator provided one (Influencer briefs only)
• Transcript — a timestamped transcript of the video's audio; click a timestamp to jump to that moment
• Collaboration Comments — notes your team left on the asset via the Collaborate feature
• AI Asset Analysis — automated scan results, flagged at the first timestamp where the issue appears
• Asset Change Request — the running list of change requests you've already sent to the Creator

Two ways to send a change request

1. Send a flagged requirement straight to the Creator

In the AI Asset Analysis section, each flagged requirement has a Send Change Request button. Click it to send that specific flag to the Creator — no copy-and-paste needed. Once sent, the flag is marked Sent to Creator and the request appears in the Asset Change Request section below.

2. Write your own request

To ask for something that isn't tied to a flagged requirement, use the text box below the asset. For videos, you can attach your request to an exact timestamp, or use 00:00 for changes that apply throughout the video.

Caption edits work the same way — send them as an Asset change request, or leave the feedback in the chat. See Where can I view the caption for approval?

Before you send: reshoot or edit?

The two are treated differently, and the distinction sets the timeline you owe the Creator.

A few rules that apply to both:

• Send feedback within 5 days of the content due date. If content was due on the 20th, your feedback needs to go out by the 25th.
• Always give the Creator a deadline in the chat section.
• Consolidate your team's feedback into one message. Several separate requests for the same asset are harder for the Creator to act on, and the edit round is meant to be one round.
• When building an Influencer brief, leave one to two weeks between the content due date and the post live date so there's room for a round of feedback.

For the full policy, message templates you can copy, and worked examples, see Reshoot/Edit Guidelines.

What the Creator sees

The Creator gets an automated email — "[Brand Name] has sent you a change request" — with each affected asset linked in the chat. Opening the link shows them your specific instructions on the asset.

Creators are instructed not to make edits until they receive a change request or a direct message from you, so a submission sitting in Content to Review won't change on its own while your team is still deciding.

If the content still isn't right

If you've sent a change request and the resubmitted content still doesn't meet the brief, reach out to your Customer Success Manager for next steps rather than sending repeated rounds. See also Handling Creator Issues.

Can I delete a change request after I’ve sent it?

No. Once a change request is sent it stays on the asset — there is no way to delete or withdraw it, and the Creator has already been notified. It remains in the Asset Change Request list as part of the record of what was asked for.

If you sent one by mistake, or changed your mind about what you need, send a second request that supersedes it and say so plainly — for example “Please ignore my previous request about the lighting; the only change we need is the logo placement.” You can also message the Creator in the brief chat to explain. Creators see the requests in order, so a clear correction is easier to follow than a silent change.

This is worth a moment’s care before you click send: consolidating your feedback into one request is better for the Creator than several, and it is the only way to keep the list clean.

Related

• Reshoot/Edit Guidelines — the policy, timelines, and request templates
• AI Asset Analysis Process — how flags are generated and reviewed
• Downloading Content to Review — why the review preview looks compressed, and when you're cleared to use an asset