The fastest way to kill a Request is to turn it into a multi-question interview. Contributors look at five vague questions, think "this is a lot," and put it off until they don't do it at all. The fix is two questions, in a specific structure, with the response type set up so contribution is as low-friction as possible.
Pro tip: Two questions, not five. One for the narrative, one for B-roll. The editor has everything they need; the contributor isn't overwhelmed.
Use two questions, not five
A Request with five questions looks like homework. A Request with two questions looks like a quick favor. Contributors are far more likely to actually open a two-question Request, and the clips you get back are tighter because the contributor wasn't trying to budget their energy across five prompts. Resist the urge to ask "everything you might want."
First question: the narrative spine
The first question gets the main content. The walk-through, the explanation, the story. This is the clip that will carry the video. Write it as a specific prompt, not a vague topic. "Walk us through how you set up the dashboard on the first day" is better than "tell us about onboarding." The narrower the prompt, the more usable the answer.
Second question: the supporting B-roll
The second question is for the B-roll layer. Visuals that go under the narrative spine. Screen captures, environment shots, document scans, anything that lets the editor cut away to keep the video visually moving. This is where you specify "send three screenshots of the dashboard" or "upload the final report PDF." The B-roll question isn't asking for performance, just material.
Preselect video as the response type and disable recording for B-roll
For the narrative spine question, preselect video as the response type. That removes the contributor's decision moment of "should I write or record this?" — they see the recording interface and answer accordingly. For the B-roll question, disable recording entirely so the field becomes a drag-and-drop upload. Configuration choices in the Request form save thirty seconds of contributor friction each, which is the difference between a yes and a postponed maybe.
Try it this week
Open your next Request in MarketScale and rewrite it to use exactly two questions. Make question one the narrative spine with video preselected. Make question two the B-roll, with recording disabled and drag-and-drop enabled. Send it and watch how much faster contributors complete it.