# Timed scene board

Filmsers · Proof-of-concept pack · Worksheet v1

Test whether the concept reads in sequence before a full production commitment by assigning provisional durations and checking the handoff between shots.

## How to use

1. Give each shot a starting duration based on the action it must communicate.

2. Read the sequence aloud and note where the audience needs more time or a cleaner cut.

3. Keep timing provisional until the board has been reviewed by the story owner.

## Fictional worked example — The Last Signal

An original teaching example, not a customer result. Any referenced media or approvals are illustrative and not included.

### Target runtime

00:26 for the proof scene: enough time to establish the valley, show the choice and hold the answer without presenting a finished edit.

### Timed rows

CS1A 6s / valley darkens / storm rumble; CS1B 5s / Mara reaches radio / hiss carries; CS1C 4s / she decides / cut on glance; CS1D 3s / selector clicks; CS1E 8s / light answers / hold.

### Readability check

After CS1A: the valley is at risk. After CS1C: Mara chooses others. After CS1E: the warning had a consequence.

### Timing risks

CS1D needs readable switch labels. CS1E may need the light to arrive late enough to feel earned.

### Review decision

Director to test CS1C at 4s and 6s in board v2. Producer confirms the 26s target after review.

## Blank worksheet

Project: ____________________
Version: ____________________
Prepared by: ____________________
Approval status / reviewer / date: ____________________

### Target runtime

Set the intended scene or sizzle duration and explain why it is the right size.

Your notes:

____________________

### Timed rows

Record shot ID, duration, action and the cut or sound handoff.

Your notes:

____________________

### Readability check

Write what a first-time viewer should understand after each beat.

Your notes:

____________________

### Timing risks

Name any shot whose meaning depends on more time, sound or a missing reference.

Your notes:

____________________

### Review decision

Record the requested change, owner and next version.

Your notes:

____________________

## Review before handoff

- [ ] Each duration supports a readable action rather than padding a runtime.

- [ ] The board names uncertainty where a still cannot prove motion or sound.

- [ ] A requested change has an owner and version.

## Handoff

Save a versioned copy with the pitch materials. These notes do not create footage, sync to the shared demo or replace production, legal or editorial approval.