# Capture one builder event without losing the field story

Builder event content capture runs on a shot log that ties every file to its intended use, its confirmed subject and its reviewer. Build the list from the event route, the plan set and the buyer questions. Record clean establishing views, field details and short explanations, then label permissions and facts before any footage reaches drafting, editing or publishing.

## What should the capture plan include before event day?

Start with the event's operating purpose. If the day explains a new community, the capture plan needs place, lot relationships and buyer orientation. If it opens a finished [spec home](/glossary/spec-home/), it needs circulation, selections, completed details and accurate availability language. If it is a trade gathering, the useful story may be the process questions people bring to the booth.

Walk the route with the event lead and the field contact. Mark where guests enter, where groups collect, which views contain private information and when trade or cleaning work will be finished. The best camera position is useless if it blocks a doorway or exposes material you cannot publish.

### Write a source-backed shot brief

| Capture item | Source to verify | Likely use |
| --- | --- | --- |
| Community or site orientation | Current map and field walk | Event recap or community page |
| Plan relationship | Approved plan sheet | Process explanation |
| Finish or fixture detail | Specification or selection record | Project page or short video |
| Builder explanation | Interview prompt and field fact | Captioned clip or article source |
| Visitor question | Approved note without private details | FAQ or follow-up content |
| Event activity | Permission and release status | Recap and future invitation |

For each sequence, the brief states the exact question it answers and the person who can verify it.

## How do you capture the house without disrupting the event?

Separate clean-house capture from guest activity where you can. Record the approach, the primary circulation and the key details before the doors open. Once visitors arrive, switch to controlled angles that do not interrupt tours or expose faces, screens, sign-in sheets and private conversations without permission.

Follow the same route guests follow. A wide exterior establishes the site. An entry movement shows the first decision point. Medium views explain room relationships. Tight details show the construction or selection point under discussion. Random clips of faucets and light fixtures explain nothing about the house.

### Capture in a repeatable sequence

1. Record exterior context, arrival and the event entrance before traffic builds.

2. Follow the main circulation with steady, unobstructed movements.

3. Capture the plan or lot feature tied to the day's central question.

4. Record details only after you confirm what they are and how to describe them.

5. Ask the builder for short answers to prepared field questions.

6. Collect room tone and quiet transitions for editing.

7. Log restricted footage, missing facts and required approvals before you leave.

For a finished model, coordinate the route with [model home marketing](/articles/events-and-showings/model-home-marketing/). For a busy public opening, the field planning in [Parade of Homes planning](/articles/events-and-showings/parade-of-homes-planning/) protects access and staff roles.

## Which questions produce useful builder interviews?

Ask about decisions visible at that property. "Tell us about your company" invites a speech. "What did this lot require you to change in the plan?" gives the builder a concrete place to start. The answer can point to the grade, the window placement, the garage approach or the circulation on camera.

Good prompts connect documents to built work. Ask which plan sheet matters, where an allowance became a selection, what the team checked before drywall, or how a punch item gets verified. Do not prompt a claim the file or the field condition cannot support.

Keep answers short enough to stand alone, but do not force a slogan. If the explanation needs context, record the context. The [builder video marketing guide](/guides/builder-video-marketing/) covers the wider publishing system, and the [Video stage](/process/video/) defines how capture, agent support and human approval work together.

## How should permissions and project facts be logged?

The shot log travels with the files. Record the project, event, location, construction phase, subject, speaker, usage limits and fact reviewer. Check appearance, property and document-use permissions with the relevant rights holder. Check release wording with your professional adviser. Hold uncertain clips for review.

Separate capture permission from factual approval. A person may agree to appear while the description of a finish, a plan change or a project status still needs review. A field fact may be correct while the footage shows a private address, a family photo or a document on the counter.

### Check permissions, facts, site context and ownership

| Review lane | Questions to answer |
| --- | --- |
| Permission | Can every visible person, property detail and document be published for this use? |
| Accuracy | Do the plan, the spec, the status and the spoken explanation match the approved source? |
| Site judgment | Does the footage show unsafe behavior, protected work or a misleading construction condition? |
| File ownership | Are originals, edits, logs and approvals stored in folders the builder controls? |

## How does raw event footage become durable content?

Ingest files under a project and event naming rule, then attach the shot log. Do not start by cutting a recap montage. First find the useful source units: a clean room sequence, a plan explanation, a lot observation, a repeated buyer question, a reviewed quote.

One unit can support several outputs when each version fits its context. A builder explanation becomes a short captioned [video](/process/video/), a quotation on a project page and source material for an FAQ. The words still need review in every format. Status language has to change when the event ends or the home changes condition.

Our Claude and Codex agents transcribe interviews, group clips, draft captions, build pages and check links. A person controls permissions, confirms field facts and approves every published output. The notes from [community events for builders](/articles/events-and-showings/community-events-for-builders/) feed this system when capture is planned before guests arrive.

Use the [events and showings library](/articles/events-and-showings/) to connect capture with invitation, sign-in, follow-up and measurement. Keep the shot log beside the originals so an editor can pull the approved source and its restrictions.

## What do builders ask about filming an event?

### Can one person host and capture the event?

One person can host and capture a small builder event if both tasks stay manageable. Assign separate roles when visitor access, sign-in or field explanations need active attention.

### Should we record every room?

Record the event route and the room details needed to answer your chosen buyer questions. Label each sequence with its project, subject and review status before editing.

### What happens when a fact is uncertain?

Hold event footage when a project fact is uncertain. Ask the responsible reviewer to check the plan, the spec or the current status before that detail is approved for publication.

### Who should own the original files?

Keep original event footage, approved edits, shot logs and permission records in storage the builder controls. Document access so you can retrieve the files when a production partner changes.