Setting up a scenario

Brief a custom scenario with three things - the setting, the role the judge plays, and two or three beats you want the clip to hit - plus a rough length. Leave out word-for-word dialogue and delivery directions: the more a brief resembles a finished script, the less room the judge has to perform.

Three things a scenario brief needs

The setting. Where this is happening and what role the judge is playing - a fitting room, a first date, a specific fantasy frame. One sentence is usually enough.

The role. Who the judge is being inside the scenario, stated plainly rather than implied through tone.

The beats you care about. Two or three moments you want the clip to hit - a reaction, a line of dialogue in spirit rather than in exact words, a turn near the end. Not a shot list, a short list of what should happen. Memory research suggests why a turn near the end earns its place: in Redelmeier and Kahneman's 1996 study, how 287 patients remembered two medical procedures tracked the most intense moment and the final three minutes, not the total length.

What not to include

Word-for-word dialogue. Stage directions for delivery - pacing, emphasis, how a line should land. A running order so detailed that the judge is reading it back to you rather than performing it. A fully scripted request tends to get declined or repriced as something other than a review, because reading a script is a different job from judging one, and most judges who took on the second do not want to do the first.

Why the direction-only version works better

A judge given setting, role and beats fills the space between them with judgement - timing, emphasis, the exact words - which is the skill you are commissioning. What a scenario review actually contains once it's shot is closer to a short piece of performance than to a verdict, and performance needs a performer with room to work, not a technician executing a plan.

How much setup is enough

A single sentence usually establishes the setting well enough for a judge to work with: where this is happening, who they are inside it, what the mood is. Buyers sometimes worry that a short setup will leave the judge guessing, but the opposite tends to be true - a short, clear setup gives a judge fewer constraints to reconcile, while a long one written like backstory for a novel often contradicts itself in ways that then have to be resolved on the fly during recording. If the scenario has one element that genuinely needs explaining - why the role exists, what led to this moment - explain that one thing and leave the rest implicit.

Revising a scenario brief after a first attempt

If an earlier scenario request did not land quite right, the fix is almost never more detail in the next brief. It is naming what specifically was off - the role read too gentle, the pacing rushed the ending - and leaving the judge to correct for it. Referencing a previous clip this way is its own small skill, and it produces a better second scenario than restating the whole brief with extra instructions bolted on.

Scope creep to watch for

Props, outfits or a specific setting change what is being asked for and usually change the quote too. Mention them as part of the initial brief rather than adding them after a price comes back, because that is exactly the kind of detail that determines whether a scenario is priced like a scenario or like something bigger.

A short brief, done properly

Setting, role, two or three beats, rough length. That is a complete scenario brief, and it is shorter than most buyers think it needs to be - the same four-line discipline that makes any request work applies here with one extra line for the beats.

If a scenario feels like more direction than you want to write, an automated read skips all of this entirely and returns a straightforward assessment instead - Rate Cock's guidance on choosing between the two is worth a look before you decide which you actually want, and an automated tool's own consistency is part of what you would be trading away. A scenario is also not the route to a number - a fixed score comes from a tool built to give one, not from a judge performing a role, and asking a scenario to also deliver a rating usually weakens both halves of the request.

If a measurement is genuinely part of the ask

Some scenarios brush against a stated figure - a role that references a size, say - and the honest way to handle that is to supply the number rather than let the judge estimate one inside the performance. Taking a proper measurement first and stating it in the brief removes a guess from a request that otherwise has enough moving parts already.