How to Structure a 30–90 Second Expert Video

Use the CORE structure

C: Claim. Answer the audience's question in the first sentence. Make the claim as narrow as the evidence requires.

O: Origin. Name the situation, source, or problem that makes the claim relevant.

R: Reason. Give the mechanism, evidence, decision, or example that supports the claim.

E: Edge and exit. State the boundary, then give the audience a next step or deeper source.

CORE can fit 30, 60, or 90 seconds by changing the depth of each part, not by deleting the boundary.

The 30-second structure

Use 30 seconds for one distinction, rule, correction, or first action.

0–5 seconds: direct answer. Example: "A transcript does not make a video source-backed by itself."

5–18 seconds: mechanism or example. Example: "It makes the recording searchable. The source trail comes from keeping the clip connected to what the person said and the material that shaped the question."

18–25 seconds: boundary. Example: "That still does not mean the claim was independently fact-checked."

25–30 seconds: handoff. Example: "Review the source and attach the evidence before publishing."

Do not force an introduction or biography into this format. Put identity in the page, caption, or visual label.

The 60-second structure

Use 60 seconds for one decision, framework, objection, or simple mechanism.

0–8 seconds: answer. State the conclusion and audience.

8–20 seconds: context. Name the situation or misconception.

20–42 seconds: example or mechanism. Walk through one concrete case.

42–52 seconds: boundary. Explain when the lesson does not apply or what remains unknown.

52–60 seconds: handoff. Give a question, action, or source.

Example: "Founders should prepare examples for camera, not memorize scripts. A script makes the speaker track exact wording while also watching the lens and remembering the product. Instead, keep three anchors nearby: the user situation, the product decision, and the evidence. That approach is not right for legal or regulated statements that require approved language. For a normal product interview, start with one real customer question and answer it from those anchors."

The 90-second structure

Use 90 seconds when the idea needs a comparison, demonstration, or meaningful uncertainty.

0–10 seconds: direct answer.

10–25 seconds: problem and stakes.

25–60 seconds: mechanism, comparison, or demonstration.

60–75 seconds: evidence and boundary.

75–90 seconds: practical handoff and source.

A 90-second expert video can hold more nuance, but it should still answer one main question. If a second claim appears, mark it for another clip.

Prepare beats, not a word-perfect script

Write one line for each CORE beat. Use nouns and prompts rather than sentences.

Example: claim, demo one user threshold; origin, feature tours lose the job; reason, input → action → output; edge, demo is not outcome proof; exit, link documentation.

This preserves the speaker's natural syntax. If exact wording matters, use an approved statement and label the recording context appropriately.

Speaking pace varies. Time a real rehearsal rather than using a fixed word-count target. Clarity, pauses, accent, technical terms, and visual actions all affect duration.

Start from a question

A good short video answers something a real person might ask.

Useful prompts include: What is the difference between X and Y? Why does this workflow fail? What should I inspect first? What does this result not prove? Show one step. When should I not use this method? What changed your decision?

REC Content Studio researches supplied context, prepares tailored questions, guides a solo on-camera recording, transcribes the answers, and suggests grounded highlight candidates. The user selects and renders the final clips. The product does not guarantee a target duration or publish to social platforms.

Record long enough to edit fairly

Do not stop an answer at exactly 30 seconds while recording. Capture the complete thought, pause, then try a tighter version.

The editing pass should keep the setup required for meaning, the claim, the supporting example, the qualification that changes the decision, and the handoff.

Remove repeated phrasing and dead setup, not essential context.

Write a highlight rationale: what does the clip do, for whom, and what must remain? This keeps the shortest cut from automatically winning.

Use visuals only when they carry information

For screen demonstrations, let the action determine the pace. A user needs time to see the state change.

For charts, state the axes and comparison. For a framework, display the term only after explaining its function. For captions, keep lines readable rather than filling the screen with every spoken word.

W3C recommends accurate captions, transcripts, and description of essential visual information. Short duration does not reduce accessibility requirements.

Honest limitations

Thirty seconds is unsuitable for many research results, safety instructions, legal explanations, and complex decisions. A short video can introduce the issue and link to the source.

A well-structured expert clip is still the speaker's selected explanation. It does not prove the claim or represent every view.

Platform trends change. Do not redesign the core argument around a current hook convention. A complete answer remains reusable across channels.

Short-video checklist

Before recording: one real audience question, one narrow claim, one example or mechanism, one essential boundary, one next step, and source ready.

Before publishing: duration fits the idea, direct answer arrives early, no important context was cut, names and numbers verified, captions accurate, deeper source linked, and the clip has one editorial job.

A short expert video succeeds when the viewer can repeat the idea without repeating it incorrectly. Build the complete thought first; let duration shape the depth.