Why 'Request Revision' Is Not Optional
Leaving a comment in Media Studio is not enough — you must click Request Revision to notify your editor. This walkthrough explains the full revision workflow.
Transcript
Hi, everyone. I wanna talk to you about the request revision button because if you are looking to make changes to your video and you are not clicking that button, your video is going nowhere. That is the only way to ensure that your video project will get back to an editor. So here's how you do it. So if I'm in Media Studio, I'd like to make some changes to the video. I might be thinking, okay, all I need to do is make a comment here. So I wanna cut out the first fifteen seconds of video. Please remove the first fifteen seconds of video. And that may be it. If that's the only thing that I need. And I'm thinking, you know what? Okay. That's good. And now I will get my video back with the first fifteen seconds of video deleted, but that's not how it works because if you don't hit the request revision button up here, it's hot pink when you hover over it. This information will never get to our editors. They don't even see it unless you hit that button. Now, another best practice tip to save you some time is to make sure that you have all of the changes that you'd like for the video submitted at the same time. That way you can send them all back in one fell swoop. So the editor only has to go through that project one time to make your changes and get that video back to you as soon as possible. So we've left that comment in there. But before I hit request revision, I want to ask myself, have I looked at the entire video? Is there anything else possibly that I would like changed at this time? And then I think, you know what? I'm going to go here at the end and say, please make this a blue background. Submit. So now that I have both of my changes there, now it's time to hit request revision. And then when I do that, it asks me, are you ready to proceed with the revisions? Please note that no additional comments can be made once you submit the edit request. So what do I do? No return to proofing or do I hit request editing? I might go back and say, you know what? I'm going to return to proofing just to make sure. What if I realize here that tip three was actually tip four, and I need to change it? So let me change that. Please change number three to number four. Let's submit. Now I've given this a once through again, and I realize that there are no additional changes that I would like for this video. I am ready to request revision. When I do that, am I ready to proceed with the revisions? Yes. Let's edit. Before I can officially go through, it's going to ask me to rate the quality of the video edit. It's important to point out here that the star rating is based solely on the editor's performance with this project. This is not you rating the project based on whether or not you're finished with it or if you may want changes or like to take things in a different creative direction or maybe add a new element. That's not how we use the star system. We use the star system to rate the quality of the edit that you've been given from our editing team. So I'm going to give this a five star rating because this was a great edit. These are just changes that I wanted and that I knew that I needed a correction on. And then why are you requesting a revision? Directions were not followed. That wasn't the case. Technical error. That's not the case. I have something new to add, which I don't have any new elements, so I'm not going to choose that one. Branding misuse, that is not in play here. Changing creative direction. That's essentially what I'm doing. I'm lopping off the beginning. I'm changing the color on the end, and I'm just correcting while we're at it. That number three to the number four. So I'm going to hit changing direction here, and then you can put any additional details if you'd like there. And then finally, this is the big moment when you're gonna hit request revision, and it will officially go back with the editor. So please remember, always hit that request revision button to make sure that all of your notes are seen by our editors so we can get your project back to you as soon as possible. And, again, best practice, put all of those changes in at one time so you can get your project back and get it posted as quickly as possible.
Overview
In this 4-minute screenshare walkthrough, contributor Michelle Dawn Mooney demonstrates the Request Revision button inside Media Studio and explains why it is a required step — not an optional one. The video covers how to batch feedback before submitting, what each revision reason category means, and how the star rating system works. By the end, contributors understand exactly how to communicate change requests in a way that actually reaches the editorial team.
What Is This?
The Request Revision workflow is the formal mechanism inside Media Studio that routes contributor feedback directly to an assigned editor — comments left outside this process are not surfaced to the editorial queue and will not trigger any action.
What You'll Learn
- Locate and use the Request Revision button inside Media Studio
- Understand why comments alone do not notify editors or trigger a revision
- Batch all requested changes into a single submission before clicking Request Revision
- Select the correct revision reason category to route feedback accurately
- Rate editor performance using the star rating system after a revision cycle
- Distinguish between rating editorial quality versus overall project satisfaction
Key Insights
- Clicking Request Revision is the only action that places a revision task in the editor's queue — comments are invisible to the editorial workflow without it.
- Batching all feedback before submitting a revision request reduces turnaround time and prevents editors from receiving fragmented or conflicting instructions.
- The star rating system is designed to evaluate editor performance specifically, not general satisfaction with the project outcome.
- Selecting an accurate revision reason category helps the editorial team prioritize and route requests efficiently across the platform.
Deep Dive
One of the most common workflow breakdowns on the MarketScale platform occurs when contributors leave feedback as comments but do not click Request Revision. It is an understandable assumption — comments feel communicative, and in many tools they are. Inside Media Studio, however, the editorial queue operates independently of the comment thread. An editor will not see a revision is needed unless the formal request is submitted through the designated button.
This distinction matters most under deadline pressure. When a contributor assumes their comment has triggered a revision and the editor assumes no changes are needed, content can move toward publication without the intended updates in place. The Request Revision button eliminates that ambiguity by creating a clear, trackable action in the system.
Best practice is to consolidate all feedback before initiating a revision request. Submitting multiple separate requests for a single piece of content fragments the editorial process and can create version conflicts. Taking a few extra minutes to compile every note — timing adjustments, graphic changes, script corrections — into one cohesive submission results in a cleaner, faster revision cycle for both contributor and editor.
After a revision is completed, contributors are prompted to submit a star rating. This rating is specifically tied to the editor's performance: responsiveness, accuracy, and the quality of the edit itself. It is not a measure of how the contributor feels about the final product or the broader project. Understanding that distinction helps contributors provide meaningful, actionable feedback that supports continuous improvement across the editorial team.
Frequently Asked Questions
What happens if I leave a comment in Media Studio without clicking Request Revision?
The comment will be saved in the platform but will not appear in the editor's task queue. Editors work from the revision queue, not the comment thread, so your feedback will not be acted on until you formally submit a Request Revision.
Can I submit more than one Request Revision for the same piece of content?
You can, but the recommended approach is to batch all of your feedback into a single revision request. Submitting multiple separate requests can create confusion around version order and may slow down the editorial turnaround time.
What should I consider when giving a star rating to my editor?
The star rating is intended to reflect the editor's individual performance — factors like responsiveness, accuracy, and the technical quality of the edit. It is not a rating of the overall project, the content strategy, or outcomes outside the editor's direct control.
Related Topics
Contributors who want to get more out of the revision process should also explore Media Studio navigation fundamentals and how publishing statuses work within the platform workflow. Understanding how content moves through each stage — from draft to editor review to publication — provides the full context needed to use Request Revision effectively and avoid delays.
#MediaStudio #PlatformWorkflow #RequestRevision #ContentProduction #EditorialWorkflow #MarketScale #PlatformNavigation #Publishing #ContentWorkflow #B2BMedia
Keep learning.
Explore more coaching sessions across all categories.
Ready to apply this
Want help putting these lessons to work for your team? Ask us anything.