---
name: film-conference-presentations
description: "Film a talk with the host’s go-ahead. Save the files and clear notes for the next person."
category: Content Factory — Produce
stage: Produce
definitive_article: GAP — to be written
status: needs-work
---

# Film conference presentations

A talk can hold lessons worth sharing after the event. This guide helps a speaker save the talk and the questions that follow. First, check what the event allows and who will run the camera.

**The path:** Event permission → Talk and allowed Q&A → Files and notes → Editor.

**Use this when:** You or a client has a confirmed speaking slot and permission to capture it.

## Inputs
- A confirmed event, speaker, session time, and the organizer’s recording and reuse terms.
- A camera operator or agreed fixed setup, charged phone, stand, storage, and a clear view.
- An audio plan. If a venue feed or official recording is available, ask how it may be received and used; do not assume it is included.
- The raw folder, tracker access, and named speaker/editor contacts. Get the session title and any allowed slide source.

## First-run prompt

> Use the confirmed event and rights I provide to prepare a recording checklist. Then turn the actual files and time notes into an intake index. Identify missing ranges, allowed questions, and the next editor. Keep speaking evidence precise; do not invent an endorsement or claim a full recording if a part is missing.

## Steps
1. Confirm recording and later use with the organizer before the event. Ask about official footage and audience questions. Use a personal backup only if it is allowed; an official recording does not grant extra recording rights.
2. Assign the operator and test the view and audio input before the room fills. Choose a stable position without blocking attendees. Check power and storage against the planned session length.
3. Capture the host’s introduction if permitted. Save the wording and context as proof of that introduction; it does not by itself prove every expertise or endorsement claim.
4. Record the talk from start to finish when allowed. If recording stops, write the missing time range. Do not label a partial recording as the full talk.
5. Record the permitted questions and answers. If an audience member is not cleared to appear, follow the event’s method for keeping them out or omit that segment. Transcribe only the questions you may use.
6. Capture approved stills and supporting shots of the speaker and event. Keep the source date and event name with each. Avoid badges, private screens, or attendees who are not cleared.
7. Save the originals as YYYY-MM-DD-eventname-talk with part numbers where needed. Upload video, separate audio if any, and photos. Note the intro range, talk range, Q&A range, rights, and any gaps.
8. Add useful audience questions to the [Topic Wheel](https://blitzmetrics.com/topic-wheel/) topic queue with their event source. They may support a HOW topic or a story; they are not automatically the WHAT offer.
9. Send the indexed package to [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript). Let the editor choose supported teaching clips and keep the event rights attached to every derivative.

## Definition of done (QA checklist)

- [ ] The organizer’s allowed recording and reuse scope is recorded.
- [ ] The talk’s coverage is measured against the actual session; gaps are visible.
- [ ] Intro and allowed Q&A sections are indexed, without inflating an introduction into a wider endorsement.
- [ ] Usable pictures, sound-review evidence, and approved supporting images are present, or missing items are named.
- [ ] Files and allowed question notes are saved and handed to the editor.

## Example(s)

**Fictional teaching example — not a real event or speaking credit.** At the made-up Northside Shop Meetup, Alex gives a 20-minute talk called “Make Repair Quotes Clear.” The organizer allows the talk and host introduction to be reused, but asks that audience faces stay out of public clips.

The teaching index reads: introduction 00:00–00:45; talk 00:45–20:45; permitted speaker answers 20:45–24:30. The phone misses 11:10–11:40 after a battery change. The tracker therefore says “talk captured with a 30-second gap,” not “complete talk.”

A sample question, “How do you explain a changed quote?”, goes into the quotes topic queue with the event and time noted. It is a topic idea, not proof that a quote system improved sales. All names, times, permissions, and footage in this example are invented for teaching.

## Handoff and Content Factory context

The editor receives the event package through [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript). Short clips can follow through [Extract short clips](https://local-service-spotlight.github.io/task-library/?task=extract-15-60-second-clips-from-long-form-video#task-extract-15-60-second-clips-from-long-form-video). The speaker or event contact resolves rights questions before use.

This task serves **Produce** in the [Content Factory](https://blitzmetrics.com/content-factory/). Produce makes or prepares source material. Process edits it, Post puts approved work on a channel, and Promote helps it reach people. Only the steps and handoff above are part of this task.

## When this runs

Run for each confirmed, approved event. A recurring conference does not create permission to record or publish its next session.

## Run with an agent

The agent can prepare the plan, organize allowed files, and check the evidence it can actually access. A person records real stories, supplies permission, or resolves an account step when needed. Save the current state in the project files and tracker. A model name does not create memory, access, a scheduler, or permission to act.

For all agent media checks, keep the player muted and its volume at zero before playback. If that cannot be checked, use captions, metadata, or still frames. Do not claim sound quality was heard when it was not.

## Write up the real run

For every actual attempt, [write the run’s meta article](https://blitzmetrics.com/meta-article-prompt/). Link this exact task and its source revision. State the start, work done, evidence, result, gaps, and next owner. Keep failed, partial, and blocked work visible. Writing the record does not authorize publishing it.

Use one stable execution ID for this task’s actual run. Internal retries, checks, and new versions do not add runs. A separately scoped child task may have its own ID linked to the parent. A teaching example has no real execution ID and must not enter the run count. Follow the [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) for that distinction.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Produce
- **Importance:** 4/5 `●●●●○` — frequency 3, revenue 4, gating 2 (creates the asset ads amplify)
- **Suggested previous station:** `capture-client-stories-on-phone`
- **Suggested next station:** `record-screen-shares-of-real-audits`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Raw files in Content Library `01-Raw/` plus a tracker row (question, date, speaker). Next skill never needs the chat — it needs the files.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Dedicated canonical article: not mapped in the current task source. Use the owned teaching references below while that article gap is reviewed.
- Exact task: [Film conference presentations](https://local-service-spotlight.github.io/task-library/?task=film-conference-presentations#task-film-conference-presentations)
- Publishing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [One-minute video method](https://blitzmetrics.com/one-minute-video-guide/)
- [Topic Wheel: stories, topics, and offer](https://blitzmetrics.com/topic-wheel/)

## Review and evidence still needed

The contributor status in the source header is preserved. It is not a claim that this draft has been independently accepted or that a real run has passed. The worked example above is for teaching only.
- No dedicated canonical conference-capture article is mapped.
- Event-specific rights, exact coverage and sound evidence need a real event.