---
name: film-casual-team-conversations
description: "Film a real team talk that helps others learn. Mark parts to cut before you pass the file on."
category: Content Factory — Produce
stage: Produce
definitive_article: GAP — to be written
status: needs-work
---

# Film casual team conversations

Your team solves useful problems each day. A real talk can help others learn how you think. This guide shows you how to record the talk, mark private parts, and give the best moments to an editor.

**The path:** Agree on limits → Record real work → Mark useful moments → Editor.

**Use this when:** A real work discussion has a useful lesson and everyone involved agrees to the recording and planned use.

## Inputs
- A real planned team talk, such as a project review or a discussion of a problem.
- Agreement from everyone recorded and a list of facts, names, or screens that must stay private.
- A phone or the team’s approved recorder, enough storage, and a position that captures all speakers.
- The raw folder, tracker access, and the editor who will review highlights and private sections.

## First-run prompt

> Use our real discussion brief to make a short recording plan. After the talk, turn my time notes into an editor’s cut list. Keep proposals separate from measured results. List the exact private sections, permission gaps, and the next owner. Do not stage the conversation or publish it.

## Steps
1. Explain why the talk may become content. Confirm who agrees and what stays private. If someone does not agree, leave them out of the recording or keep the discussion unrecorded.
2. Set the camera where it can show the group and capture each voice. A wide shot may suit a table discussion. Run a short test; change the setup if a speaker is off-screen or the input is weak.
3. Record the real talk. Start with a short statement of the problem so the editor has context. Do not stage disagreement, invent a client issue, or repeat a conversation as if it were the first event.
4. Let each person finish their point. Keep the recording running through useful context, but pause when private material or a new person enters. Record the gap so later viewers are not misled by a cut.
5. While the discussion is fresh, note the strongest two or three moments with time ranges. For each, write the question, the useful idea, and any decision. A lively clip without enough context may need a longer cut.
6. Make a separate list of private sections with start/end times and what must be removed. Do not rely on “blur sensitive things” as the only instruction.
7. Save the original unchanged. Name it YYYY-MM-DD-topic-team-convo. Upload it to the approved raw folder, then add the link, speaker names, permission state, highlights, and edit limits to the tracker.
8. Hand off 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). Use “Raw — needs private-content review” if redactions remain; the source file being uploaded does not make it safe to post.

## Definition of done (QA checklist)

- [ ] The recording captures real work with agreement from the recorded people.
- [ ] Each speaker can be identified and understood; any missing sound review is explicit.
- [ ] Two or three useful moments have time ranges and enough context for an editor.
- [ ] Private segments have specific edit instructions and a named reviewer.
- [ ] The original and tracker row are saved and accessible to the editor.

## Example(s)

**Fictional teaching example — not a recorded meeting.** Maple Cycle’s team talks about missed repair pickups. The sample 12-minute conversation has these edit notes:

| Time | What happens | Editor’s instruction |
| --- | --- | --- |
| 00:20–01:10 | The team defines the pickup problem | Keep as context |
| 03:10–04:05 | A staff member suggests asking the customer to choose a pickup day | Candidate teaching clip; label it as a proposal |
| 06:02–06:30 | A sample customer’s contact details appear | Remove the whole section before public use |
| 09:00–10:10 | The team chooses a small test | Keep the decision; do not claim the test worked |

The sample handoff teaches the difference between an idea, a decision, and a measured result. It supplies no real permission, recording, or outcome evidence.

## Handoff and Content Factory context

The editor receives the source and cut list 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). [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) may follow once the private-content review has cleared the candidate sections.

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 when a suitable real discussion happens. Do not create meetings or automatic recordings just to fill a content quota.

## 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:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** `record-screen-shares-of-real-audits`
- **Suggested next station:** `create-a-3-minute-why-video`
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 casual team conversations](https://local-service-spotlight.github.io/task-library/?task=film-casual-team-conversations#task-film-casual-team-conversations)
- Publishing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [One-minute video method](https://blitzmetrics.com/one-minute-video-guide/)

## 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 team-conversation guide is mapped.
- A real recording, participant permission, and reviewed cuts are required for an execution.