A Simple Given–When–Then Brief for Multi-Step Video Scenes

In a fictional parcel-return scene, the locker opens before the phone reaches the scanner. In another draft, the phone disappears halfway through.

The setting looks right, but the action does not make sense.

This often happens when a brief spends more time describing style than sequence. Words such as “cinematic,” “smooth,” and “realistic” say little about what must happen first.

For a scene built around several connected actions, a simple Given / When / Then structure can make the order clearer.

Write the Order First

Start with the situation, the trigger, and the expected result:

Given a customer is standing beside a closed parcel locker
And the parcel is in the customer's left hand

When the customer holds the phone near the scanner

Then the scanner light turns green
And the locker door opens
And the customer places the parcel inside

This is a planning note, not an executable test or API specification.

• Given describes the starting point.
• When identifies the action that starts the sequence.
• Then lists what should follow.

If the door opens before the scan, the first broken step is easy to find.

Turn It Into a Short Brief

Once the order is clear, add only the details needed to understand the scene.

Create a short fictional parcel-return scene outside an apartment building.

Keep the same customer, phone, parcel, and locker throughout.

Action order:
1. The customer stands beside the closed locker.
2. The customer raises the phone toward the scanner.
3. The scanner light turns green.
4. The locker door opens.
5. The customer places the parcel inside.
6. The door closes.

Use one steady medium shot.
Keep the locker controls visible.
Do not add other people, logos, captions, or extra objects.

The brief does not describe every detail of the customer’s clothes or the building. Those details can be added later if they matter. The action order comes first.

The same format can support a draft made with Seedance 2.5, a storyboard, or footage assembled in an editor. Check the current interface and usage terms before uploading any reference material.

Record the First Failure

Watch the draft once from beginning to end. Instead of writing down every strange frame, find the first point where the planned sequence breaks.

Ask:

1. Is the starting situation correct?
2. Does the trigger happen?
3. Do the following actions appear in the right order?
4. Do the important people and objects remain consistent?
5. Has anything unnecessary been added?

Keep the failure note short:

draft: parcel-return-04

first_failure:
  time: 6s
  expected: "Phone reaches the scanner before the door opens"
  observed: "Door begins opening too early"

next_change:
  - "Keep the door closed until the scanner turns green"

One early mistake can create several later problems. If the door opens too soon, the customer may move early, the parcel may change position, and the camera may lose the main action. Correcting each symptom separately would miss the original failure.

Use a timeline editor when the scene works but a cut, pause, caption, or sound cue needs adjustment. Create another draft when the main action, subject identity, or event order has broken.

Remove Real Data Before Testing

A fictional workflow can still expose real information if the references are not checked.

Before uploading or publishing:

• Remove names, addresses, tracking numbers, access codes, and working QR codes.
• Confirm that images, voices, logos, and footage may be uploaded, processed, and reused for the intended purpose.
• Label the scene as illustrative when it could be mistaken for a real demonstration. Generated footage is not proof of safety, reliability, or product performance.

Real operating instructions should come from approved documentation, not from the generated scene.

Where This Method Helps

Given / When / Then works well when order carries meaning:

• Scanning a ticket before entering a station
• Buckling a helmet before riding a bicycle
• Adding recipe ingredients in sequence
• Showing a checkout or booking flow
• Assembling a simple object

It is less useful for abstract backgrounds or mood clips with no fixed action order.

A useful brief does not need to describe everything. For a multi-step scene, it needs to answer one practical question:

What must happen first?