How to Keep an On-Set Take and Continuity Log for UGC

01

What production context must the log preserve?

The log must preserve decisions and changes that cannot be inferred reliably from the footage alone.

An editor can inspect the picture and sound, but may not know whether an improvised line was intentional, whether an opened package must match a later demonstration, or whether an incomplete-looking clip contains the preferred hook. Filenames identify files; they do not usually explain production intent.

Record whether the creator preferred the performance, whether a technical problem limits its use, and whether a claim or disclosure needs review. Also capture transient physical states: a seal has been removed, a liquid level has dropped, the creator changed hands, or a prop moved. These details determine which modular clips can be combined without visible continuity errors.

Create the log during capture rather than reconstructing it later. Immediate logging reduces reliance on memory and lets the team record why a take changed while that decision is still clear.

02

How should you assign stable IDs to hooks, claims, demos, and CTAs?

Give every script module a permanent ID before recording, then append a sequential take number to each attempt.

A module is a self-contained creative unit that can be selected or rearranged in an edit. Recommended prefixes are H01 for a hook, CL01 for a claim, D01 for a demonstration, B01 for a bridge or body line, P01 for proof or testimonial material, CTA01 for a call to action, SAFE01 for a neutral safety line, and BR01 for B-roll.

Append the attempt number to produce take IDs such as H01-T01, H01-T02, D02-T04, and CTA01-T03. Do not renumber existing modules once filming starts. If the creator improvises a new hook after H03, assign H04 rather than changing earlier IDs. Stable IDs let the script, take log, continuity photographs, filenames, and editor notes refer to the same unit.

Plan the modular structure before the shoot when possible. The related Creator Modular Ad Footage Shoot guide explains how to divide a script into independently usable capture units.

03

What fields belong in the copyable UGC take-log template?

Use one row per take and controlled terms wherever possible. Copy the following header into a spreadsheet, database, or CSV file.

Copyable header: Shoot ID | Capture date | Module ID | Take | Module type | Script version | Filename | Source position | Framing | Performance | Technical status | Wording delta | Audio disclosure | Visual disclosure | Disclosure timing or issue | Claim status | Wardrobe state | Prop state | Product state | Continuity change | Select status | Usable range | Continuity photo | Editor note

Enter dates as YYYY-MM-DD. Use the exact camera filename after the device finishes writing the clip. Under source position, enter source timecode when available. Otherwise, combine the filename with a clip-relative range, such as IMG_1842.MOV, 00:12–00:21.

Keep performance and technical status separate. A take can have strong delivery but clipped audio, or clean sound but flat delivery. Use concise performance terms such as STRONG, CLEAN, FLAT, RUSHED, or PARTIAL. Technical terms might include CLEAN, SOFT FOCUS, AUDIO ISSUE, INTERRUPTED, or EXPOSURE SHIFT.

Standardize select status as PREFERRED, USABLE, SAFETY, HOLD, or NO. PREFERRED is the first editorial choice. SAFETY is an acceptable alternative with different pacing or lower creative risk. HOLD means the footage must not be used until a question—commonly a claim or disclosure issue—is resolved. NO means the take has no intended use.

Example completed row: D02 | T04 | IMG_1842.MOV | 00:12–00:21 | 9:16 overhead close-up | wording: “Twist twice” instead of “twist until locked” | product: open, seal removed, approximately 80% full | continuity: label rotated toward camera | performance: clean hands and pacing | technical: focus clean, refrigerator noise | claim: approved | disclosure: not required in this module | select: PREFERRED | editor note: use action from 00:12 and cut before creator looks off-camera.

For a broader planning document around this log, use the UGC Production Workflow Template.

04

How do you maintain the log while the camera is rolling?

Use a short call-record-log routine after every attempt, rather than stopping later to reconstruct a batch of takes.

The logger can be the creator, producer, or another person on set. If the creator is working alone, keep the spreadsheet or notes app beside the camera and record only the information that changed. Do not let detailed prose slow down capture; controlled statuses and short deltas are faster and easier to search.

If the camera does not provide useful source timecode, the exact filename is the primary link between the row and the media. For a long clip containing several attempts, record clip-relative start and end positions for each useful passage. Adobe Premiere supports clip metadata, log notes, original filenames, and timecode-related fields; markers can also hold comments at specific moments. A portable spreadsheet remains useful because some project metadata can stay inside the editing project unless it is linked to file-based XMP metadata.

1. Call the module and take aloud before the performance: “Hook two, take three.”
2. Record the take, including a brief pause at the beginning and end when practical.
3. Log the result immediately. Do not wait until several more attempts have been recorded.
4. Record only the meaningful delta, such as: Changed “three days” to “a few days.”
5. Assign performance and technical statuses separately.
6. Mark one PREFERRED take and one SAFETY take before changing framing, lighting, wardrobe, or product state.
7. Reconcile the log with the exact filename after the camera finishes writing the file.
8. Photograph the setup before moving props, wardrobe, lighting, or the product. Reference that image in the log.

05

How should wording, claims, and disclosures be recorded?

Write the exact meaningful deviation and place unresolved claim or disclosure problems on hold.

Avoid notes such as “said it differently” or “disclosure problem.” Use specific entries: Verbatim; dropped “paid partnership” disclosure; said “cures” instead of the approved wording; changed “I use this daily” to “I’ve been testing this”; CTA omitted discount code; or visual disclosure cropped out in the close-up.

The log should flag review questions rather than decide them. Use HOLD—CLAIM REVIEW when a creator departs from approved claim language. FTC endorsement guidance states that endorsements must reflect honest opinions and experiences, and endorsers should not make representations the advertiser could not make directly. That makes wording deviations important production information, not merely performance notes.

When a material-connection disclosure is required, record its components separately: Audio: yes or no; visual: yes or no; timing; wording; and visibility problem. FTC guidance says video disclosures should appear in the video rather than only in the description and explains that audio and visual presentation can improve the likelihood that viewers notice them. It also warns against assuming a platform disclosure tool is necessarily sufficient. Brand or legal reviewers should determine the final requirement for the specific endorsement.

06

Which continuity details matter most in modular UGC?

Track any state that affects whether one hook, claim, demonstration, or CTA can be cut beside another.

Prioritize camera position, crop, lens or zoom setting, eyeline, microphone placement, hair, sleeves, jewelry, makeup, prop orientation, product label direction, package condition, consumable level, device screen, app page, hand choice, background objects, and practical lights. For demonstrations, note whether the result has already occurred.

Log a change on the first affected take. For example: “Product now open; cannot intercut before D02-T03 as unopened,” or “Right sleeve rolled after H02-T04.” If a continuity change is intentional, say so. An unexplained mismatch and a deliberate alternate setup can look identical to an editor.

Product condition deserves its own field rather than being buried in notes. Useful states include SEALED, OPENED, ASSEMBLED, USED, WET, DAMAGED, and an estimated amount remaining. Reference a continuity photograph whenever visual description alone could be ambiguous.

07

What should you verify before dismantling the set?

Run a reconciliation pass while reshoots are still possible, then preserve the capture-time log as the original production record.

Confirm that every planned module has at least one usable take, every preferred take has an exact filename, and every partial take has a usable range. Check that claim changes and disclosure mistakes are flagged, continuity photographs are referenced, and preferred or safety labels do not conflict.

Export or duplicate the log before handing off footage. Do not overwrite the capture-time record with later editor notes; add separate columns or a new version instead. Adobe’s Text-Based Editing can generate searchable, timecoded transcripts, but a transcript does not explain whether a deviation was approved, intentional, preferred, or blocked from use.

The next production stage is raw-footage organization and editor handoff. Use the Organize Raw UGC Footage for Editors guide to move from the capture log into folders, proxies, manifests, and delivery notes.

ATIYO can preserve the roadmap, brief, brand context, assets, iterations, and reusable learnings connected to these modules. Media performance remains in the ad platform and ATIYO preserves creative context and learnings. ATIYO does not connect to ad accounts, buy media, calculate ROAS, or know performance unless a user records it.

1. Verify module coverage and identify any missing safety take.
2. Match every PREFERRED, USABLE, and SAFETY entry to a filename.
3. Review all HOLD rows before approving footage for editorial use.
4. Check source positions and usable ranges for partial clips.
5. Reference and back up continuity photographs.
6. Export a portable CSV or spreadsheet and retain the original version.