How to brief a walkthrough in one sentence

We ask for one product and one task in a sentence. That sounds like a formality, but it is the single biggest predictor of how fast a sample comes back, and of whether the finished video is the one you wanted.

The pattern

A brief that works has three parts: the thing being operated, the task in a verb phrase, and the result that would settle the question.

[product]  +  [one task, as a verb]  +  [the result that proves it]

Briefs that worked

• "Alert me when any product drops below 20 in stock" — and the proof is the alert arriving.
• "Restore a single file from last night's backup" — and the proof is the restored file matching the original.
• "Invite a teammate with read-only access" — and the proof is the teammate seeing the dashboard and not the settings.
• "Connect the billing integration and issue one refund" — and the proof is the refund appearing on both sides.

Briefs that need a second round

Three shapes cost a day or two while we come back with questions.

• A feature, not a task. "Show the reporting module" has no finish line, so there is nothing to verify.
• Several tasks at once. "Set up the account, import data and build a dashboard" is three videos; picking which one matters is your call, not ours.
• A claim rather than an action. "Show how fast it is" needs a number, a method and a comparison before anyone can film it.

What we confirm back

In one reply we confirm the scope, the access we need, and the environment. Access is always a trial or a demo tenant, never production. If the task needs data to exist first, we say so, because seeding it is part of the run and belongs in the log.

One more thing worth naming

Tell us the language or languages you want at the same time. Narration is written per language rather than machine-translated line by line, and knowing up front means one recording serves all of them instead of a second run later.