By Vellora Labs · Updated October 8, 2026
Fictional example: “Meeting Desk” below is an invented product for teaching the brief format. Its screens, workflow, and proposed claims are illustrative. No customer quotes, performance results, or live product capabilities are asserted.
Download the editable .txt template
1. Decision and audience
Decision: should the explainer lead with reviewing actions or sharing the meeting summary? Audience: product managers who recently followed up a cross-functional meeting. Context: decisions and action owners are spread across notes and messages. Confirm that context in actual research before using it in public copy.
2. One message
Proposed message: “Review suggested meeting actions, choose an owner, then share a confirmed summary.” Human review is part of the concept. Do not imply automatic assignment or sharing. Next action: open a clearly labeled sample workflow. Runtime: 45 seconds.
3. Source-to-scene map
| Source / status | Proposed scene | Claim boundary |
|---|---|---|
| S1: mock meeting notes, invented | 0–7s: a decision and action in separate notes | Show an example situation; do not call it a customer quote |
| S2: prototype action-review screen | 7–18s: review a suggested action | Label prototype; no accuracy or time-saving promise |
| S3: prototype owner selector | 18–34s: choose an owner, edit wording, confirm | Show user control; no implied automatic assignment |
| S4: sample summary screen | 34–45s: review the result and open the sample | Keep the CTA consistent with actual access |
4. Working script
- 0–7 seconds: “A meeting ends. The next actions are still scattered across your notes.”
- 7–18 seconds: “In this concept, Meeting Desk brings suggested actions into a review screen.”
- 18–34 seconds: “Check the wording, choose the owner, and confirm what should be shared.”
- 34–45 seconds: “Review the summary before it leaves your team. Explore the sample workflow.”
Read the script aloud at the planned pace. The scene timings are a starting budget, not a promise that the words will fit. Leave time for people to read labels and inspect the interaction. Keep a visible “concept demo” label wherever prototype screens appear.
5. Production and claims checklist
- Replace every fictional asset with material you have permission to use.
- Keep private names, meeting content, and identifiers out of screenshots.
- Verify that displayed controls and outputs match the current product.
- Provide captions and keep text readable at the actual viewing size.
- Remove unsupported speed, quality, accuracy, or adoption claims.
- Check that the final link delivers what the invitation promises.
6. Comprehension test
Show the video without coaching. Ask viewers what the product does, who chooses an owner, and when sharing happens. Record their unaided account before replaying any scene. Follow the full test protocol to separate missing detail from poor fit.
Decide in advance how you will handle a risky misunderstanding. For this fictional concept, an interpretation of automatic sharing would trigger review of the relevant scene. Do not report this example rule as a validated success threshold.
Adapt it to your product.
The download includes both this fictional example and blank fields for your own evidence. The brief builder creates an editable timed outline from your inputs. You can then use TapVid or your own video workflow; nothing transfers automatically.
Explore TapVid → · TapVid is a product from the team behind Vellora. This template is authored by Vellora and is not a testimonial or a report of a completed study.