Identify
Name the scene need, capture type, microphone position, and current noise state before recording.
Record each wild track as an editor-ready chain: identify the scene need, preserve the microphone and noise conditions, copy the real filename, and name the student owner and edit destination before leaving the location.
Write the project, shoot date, location, scene range, recorder, microphone, and student sound owner before the first wild recording. Give the session a short ID such as LIBRARY-D1 so every later filename and note points to the same place and day. Listen for the steady background that defines the room: ventilation, traffic, computers, birds, or crowd bleed. Record the starting noise state in plain words instead of calling the space quiet. The logger reads the header back while the recorder operator checks that the device, microphone, and media card match the written entry.
Keep the cast, crew, furniture, doors, lights, and powered equipment in the same state used for dialogue. Place the microphone where it was for the scene, set the same recording level, announce the session ID, then hold everyone still. Log the room-tone filename, microphone position, noise state, and exact recorded duration from the device. If a chair moves, a phone vibrates, or a door opens, mark the interruption and make another file rather than hiding it. Route the clean file to the scene dialogue bed so the editor knows which cuts it can bridge.
When ventilation starts, hallway traffic increases, rain begins, or a crowd enters, treat the new background as a separate state. Write what changed and the clock time, then record a new tone without overwriting or renaming the earlier file. Keep microphone model, direction, height, and level unchanged unless the log explains the difference. Mark which takes belong before and after the change. The editor receives two named beds instead of one misleading room-tone label and can match each part of the scene to the background that actually existed.
Identify the exact scene, shot, take, speaker, and line that needs replacement before recording. Note the reason, such as an airplane, clothing rustle, clipped word, or off-camera delivery, without diagnosing the whole take. Keep the performer at the original distance and direction from the same microphone when possible. Record three labeled versions with the same pace and intention, then copy the real filenames from the recorder. Mark the permission state for the voice and route the files to dialogue repair for that take, not to a vague audio folder.
For a voice heard from another room or outside the frame, log the cue that triggers it and the visible action it must support. Record the speaker name, line, distance, microphone position, and whether the delivery should sound near, far, blocked by a door, or open to the room. Make one neutral version and two performance variations. The logger names the scene and intended cut point before each file. Flag any unapproved name or personal information in the line as a hold, and assign the director to choose a file for the off-camera dialogue track.
Choose one visible action whose production sound is weak or covered: a zipper, book close, cup set-down, key turn, paper fold, or backpack latch. Write the prop, surface, action speed, scene, and take reference. Place the microphone close enough for a clean sound but keep the original action and material unchanged. Record three controlled repetitions, leaving silence between them, and note any background contamination. Copy each filename and route the preferred option to the exact picture action. The prop owner confirms that recording does not authorize damage, alteration, or unsafe handling.
Log the performer or shoe type, floor surface, pace, direction, step count, and scene action before recording. Capture one pass at the story pace and one safety pass with cleaner spacing. If the character crosses from tile to carpet or indoor to outdoor, make separate files and mark the transition rather than calling both footsteps. Count the usable steps during playback, copy the filenames, and assign the editor destination as entrance, exit, corridor pass, or under-dialogue movement. Stop if the route creates a safety or access problem; the log cannot grant location permission.
Separate the sound into handle or latch, movement, and close or stop so the editor can align each event. Log the door, room side, speed, force boundary, microphone distance, and scene reference. Record each part twice without slamming, locking, or changing the approved location state. Note squeaks, hallway voices, alarms, or access restrictions as observable conditions. Copy the six filenames or one clearly segmented filename and mark the desired picture frames for each part. Assign a location owner to confirm the door is left in its required final position.
Record the wider ambience that establishes the place, such as a playground, cafeteria, hallway, street edge, or quiet library zone. Log the microphone direction, height, fixed or moving position, dominant sound, interruptions, and the scene section that needs the bed. Do not record private conversation as useful texture; stop, move, or mark the file held for review when identifiable speech enters. Make one fixed perspective and one alternate perspective, then name the files from the device. Route them to the opening, transition, montage, or scene tail rather than merely writing ambience.
When a useful recording contains a horn, bell, chair scrape, handling bump, clipping, radio burst, or unexpected voice, record the file and time position instead of writing bad audio. State whether the wanted sound remains usable before, after, or underneath the problem. Keep the original file intact, make a clean retry when allowed, and link both filenames in one row. Assign one student to compare them on headphones and record the result. The editor destination becomes use clean retry, inspect original segment, or hold for supervisor review; the log does not authorize deletion.
Compare every written filename with the recorder file list before the device or card leaves the location. Confirm that each row names a capture type, scene need, duration, microphone position, noise state, owner, and edit destination. Mark voice or private-location permission as confirmed, held for review, or not applicable according to the project's authorized record; never infer consent from participation. Resolve duplicate labels and blank destinations while the responsible students are present. Count the logged files and held items, then have the logger and permission owner sign the handoff sheet.
Place copies of the approved audio files, not the only originals, in one project folder with the completed log. Preserve the recorder filenames and add folders only when the structure is written on the handoff sheet. The receiving editor checks the file count, opens one room tone, one wild line, and one isolated effect, and confirms that their rows point to real files. Record the storage location, backup location, receiving person, time, held items, and next review owner. The sender and receiver sign only after the package, log, and exceptions agree.
Name the scene need, capture type, microphone position, and current noise state before recording.
Copy the real filename, duration, fault state, consent boundary, and named student owner after recording.
Give every approved file an edit destination and reconcile the package with the receiving editor.
This classroom production record does not grant performer consent, permission to record private speech, location access, school approval, equipment access, account access, permission to delete original media, or permission to publish a film. A held file remains held until the authorized teacher, producer, owner, or supervisor resolves it under the project's rules.
The useful record is the whole chain: a stated scene need, matching conditions, real filename, measured duration, observable noise state, permission status, named owner, and edit destination. A generic sound report can list a file; this student log also makes the small crew prove who captured it, why the editor needs it, and where it may safely go.