When the clip has a set

Some judges take custom requests with a setting, an outfit or a prop, and many do not. Where they do, these are production elements rather than small extras: they turn a straight read into a constructed scene, and a request that treats them that way is one a judge can plan and quote for.

What counts as a setting element

A costume piece, a backdrop, an object used as part of the scenario, a lighting choice that signals a mood rather than just illuminating the shot: all of these are things a judge decides to include, source or arrange before recording starts. None of it is decoration for its own sake. In a scenario review, the setting is doing narrative work the same way a prop does in any short piece of performance - it establishes where the clip is happening and what kind of moment it is.

Why it changes what gets delivered

A straight read responds to your material and your brief with nothing else in the frame. Add a setting or a costume and the clip becomes a small constructed scene, which changes its content in ways worth being clear-eyed about before you ask: the judge is now performing a role inside a place, not just addressing you directly. Sustaining a role is work in its own right: Grandey (2000) describes emotional labour as managing emotions when a work role demands certain expressions be shown to customers, and a scene adds a character to manage on top of the register. Custom scenario reviews already cover the content side of that shift in more depth than this post needs to repeat.

What is worth adding here is the practical side: a request with a setting or prop attached is a request with more moving parts, and a judge reading it needs to know roughly what you have in mind, not just that you want "something with a bit of a scene to it." Vague scenario requests carry more of the guessing a judge has to price against than vague straight-read requests do, simply because there is more to guess.

Where the line sits

Not every judge takes prop or costume requests, and plenty who do only work within a narrow set of options they already have on hand. This is a boundary like any other: asking whether something is possible before writing the full brief is the polite move and saves both sides a wasted round. A judge declining a specific setting request is not declining you, and it is worth reading as ordinary rather than as a rejection.

What this is not

None of this is about anything explicit, and it is not a request that gets scoped or written on this site beyond the fact that it exists as a category. It is also not where the pricing conversation lives - that belongs with how a human read is priced against an automated one, since setup and props are exactly the kind of extra labour a judge weighs when she sets what she charges, and Rate Cock's own guide is the right place to compare the two before you commit to either.

An automated tool has no equivalent to any of this: it responds to what is uploaded and nothing else, with none of the setup, wardrobe or scene-building a human scenario involves. That is a fair trade for speed, and it is also exactly why a setting or a prop is not something you can ask an algorithm for at any price. If what you actually want out of the request is a number rather than a scene, an automated score is built for that and a human scenario is not. Neither is a measurement: if a stated figure is meant to be part of the scene, take it properly first and hand the judge the number rather than a guess.

What buyers get wrong about it

The most common mistake is treating a prop or setting as a small add-on to a straight read, priced the same way a sticker is priced onto an order. It is not a sticker. It changes what kind of clip is being made, and asking for it in the same breath as a simple two-line request ("could you also wear X and mention Y prop") usually gets read as underscoping a bigger job rather than as a minor extra.

The second mistake is arriving with a full scene already written, props, dialogue and all, and expecting the judge to execute it exactly. A scenario brief works better as direction than as a script - name the setting, the role and what matters to you about it, then let the judge decide how to build it, since that judgement is most of what is being paid for. A request that reads like a shot list rather than a brief tends to get declined or quoted high, not because the idea is unreasonable but because it leaves no room for the judge to actually do their job.

Briefing it well

Say what setting or prop you have in mind, ask whether it is something the judge does, and be ready for the quote to reflect the extra planning rather than just the extra minutes on screen. Writing the brief clearly is the cheapest lever you have over the result in any custom request, and it matters more here than in a straight read, because there is more for the judge to build.