# Track every edit back to one approved job-site source

One builder video shoot can feed several distinct assets when the crew captures a complete source package: wide context, field details, a reviewed explanation, clean audio, stills, a transcript and permission notes. Plan each output before you film, keep one fact record, and cut each version for a specific buyer question instead of pasting one clip everywhere.

## What should one job-site shoot capture?

Capture enough context to explain the decision after everyone has left the site. A tight clip of blocking means little without the room, the plan reference and the reason it matters. Start with the wide condition, move to the detail, record the builder's explanation and gather clean supporting footage to cover edits in the interview.

The source package also needs non-[video](/process/video/) material. Take approved stills, record the exact project alias and phase, save the interview transcript and note any term that needs confirmation. Photograph the plan detail only when it is cleared for publication. The package is useful because every piece points back to the same verified story.

The [video and social library](/articles/video-and-social/) holds the channel and format guides that receive these source assets.

### Which source assets create editing options?

| Source asset | Primary use | Review need |
| --- | --- | --- |
| Wide site or room view | Establishes place and phase | Privacy and project status |
| Steady field details | Supports the spoken explanation | Condition and sequence accuracy |
| Builder interview | Provides judgment and terminology | Claims and commitments |
| Clean natural sound | Creates transitions and context | Private conversations |
| Approved still frames | Supports posts, pages and thumbnails | Crop and usage permission |
| Transcript | Supports captions and written drafts | Speaker correction |
| Shot and permission log | Controls later reuse | Current status |

## How should you plan outputs before filming?

Start with buyer questions, not a list of platforms. A framing visit might answer how a plan creates a long sight line, why blocking goes in at a future handrail, and what has to be coordinated before rough-ins. Those are three stories with related evidence. List the owned page and the likely format for each.

Then find the shared shots. The wide room view may serve all three stories, while the plan detail belongs only in the sight-line explanation. That keeps the field list short without forcing every output to use identical footage.

### What is the source-to-publish workflow?

1. **Choose the site questions.** Confirm what is visible, current and worth explaining.

2. **Map likely outputs.** Give each question an owned page and one or more formats.

3. **Build the shot matrix.** Mark shared context, unique details, speakers, stills and restrictions.

4. **Capture the source package.** Record complete answers and steady evidence. Do not edit in the camera.

5. **Write one fact sheet.** Store the phase, plan references, approved terminology and open questions.

6. **Produce distinct drafts.** Shape each asset around its reader and destination.

7. **Review every derivative.** Check facts, captions, permissions, links and changed context.

8. **Archive the chain.** Keep masters, approved exports and usage notes in storage you control.

## How does the same footage become different assets?

A short vertical post opens with the field problem and gives one conclusion. A longer video keeps the builder's reasoning, the plan context and the tradeoff. A website article organizes the transcript into a clear explanation with a table or checklist, and takes its place in your [topical map](/glossary/topical-map/). A follow-up email points to that article when a buyer asks the same question.

Give each derivative a job. Record the source passage behind each one so a later correction reaches every version.

Use [short vertical videos for builders](/articles/video-and-social/short-vertical-videos-for-builders/) for the concise version and [YouTube for custom builders](/articles/video-and-social/youtube-for-custom-builders/) for longer explanations. For capture choices, compare [builder photography vs video](/articles/video-and-social/builder-photo-vs-video/).

## What breaks when one clip is copied everywhere?

Aspect ratio is the obvious problem. Context is the expensive one. A caption written for people who already know the project confuses a new viewer. A temporary event reference goes stale on a permanent page. A short edit drops the qualification that made the builder's answer accurate.

Repeated publishing also creates maintenance. If the project status changes or a fact needs correcting, the team has to know every place the asset appears. Keep a derivative list tied to the master asset and the fact sheet.

### How should captions and accessibility fit?

Build captions from the reviewed transcript, then check names, construction terms and timing against the final edit. Do not let an automated transcript turn a material, room or plan term into a different claim. The finished asset should still make sense with the sound off.

### Where can AI agents speed up the workflow?

We run Claude and Codex agents that transcribe the interview, group clips by question, propose selects, draft captions, turn approved explanations into article outlines and check derivatives against the fact sheet. A person picks the story, corrects the transcript, verifies field conditions and approves every publication.

Agents are especially useful for consistency. They compare the short caption, the long description and the article draft for conflicting phase names or plan terms. They cannot decide that an unclear assembly is complete or that an unrecorded permission exists.

The [Video stage](/process/video/) sets up the active-house capture and builder interview system. The [builder video marketing guide](/guides/builder-video-marketing/) explains how those files connect to owned pages and buyer follow-up.

## How should the derivative record be organized?

Organize source files by project alias and capture date, then use subfolders or metadata for camera originals, audio, stills, transcripts, project facts, permissions, working edits and approved exports. File names should identify the subject without exposing private buyer information.

Give each derivative its own record: master filename, source passage, buyer question, crop, caption version, approved use, reviewer and destination. Note any recheck condition beside the approval. When a source fact changes, use this record to find every affected export and public placement before you prepare a replacement.

## What do builders ask about reusing one shoot?

### How many assets should one shoot create?

Let distinct, supported buyer questions decide how many assets a builder shoot produces. Do not split one weak explanation into repetitive posts.

### Can the transcript become an article?

A builder video transcript can become an article after speaker review and checks against plans, field notes, permissions and the current build process.

### Should every platform get the same edit?

Adapt a builder video edit to the reader and the destination. Keep the approved source facts while you change length, framing and context for each version.

### Who owns the source package?

The builder keeps original footage, audio, stills, transcripts, fact sheets, permissions and approved exports. Keep the derivative record beside that source package.