What the Daily Log Is for and How It Differs from an ALE or CSV
In SlateX, the Daily Log is a shoot-day PDF summary for script supervisors, assistant script supervisors, and post-production receivers to read. It gives a quick view of which Takes were recorded and what on-set context was noted, but it is not a field-by-field handoff: an ALE primarily carries identity and time clues, while a CSV carries finer shooting and camera detail.
Who reads the Daily Log and what it shows
On set, the Daily Log helps the script supervisor and assistant script supervisor communicate what happened during the Shoot Day. In the edit room, receivers can first scan a readable account of the day instead of starting with machine-readable tables. It summarizes the work; it does not package the picture or sound media for delivery.
The header provides context such as the Shoot Day, call time, first shot, wrap, and meals. The table lets readers follow Scene and Take identity, rolls, selected camera information, ratings, and visible notes. What fits on the page should not be mistaken for the full contents of every on-set record.
How its job differs from an ALE and a CSV
An ALE is an exchange list for a receiving workflow. Its main purpose is to supply checkable clues about material identity, time positions, Scene, and Take. Even populated fields must be checked against the on-set record and actual media; see What an ALE File Is Actually For for its scope and limits.
A CSV is a tabular detail sheet for column-by-column review, covering finer camera, optical, composition, and shooting-state information. It is better suited to checking individual fields, but it is not a verified media manifest either; see What a CSV Handoff Carries That an ALE Does Not for the differences. The Daily Log helps people understand the day first; the ALE and CSV pass checkable details into later work.
Why the Daily Log cannot be checked cell by cell
The Daily Log summarizes by Take, while machine-readable handoffs such as ALE and CSV expand records by camera. A multicamera Take stays on the same Daily Log row but can correspond to separate camera rows in the machine-readable files. Row numbers, row counts, and visible fields therefore cannot be matched directly across these outputs.
Even if a roll, rating, or note appears in the Daily Log, that does not mean the underlying field has been verified. Cross-file checks should first align Scene, Take, and Camera ID, then inspect the relevant machine-readable fields and on-set records. A note may also be only partly visible on the page; for layout limits, see How Many Takes Fit on a Daily Log Page and Why Text Gets Clipped.
Why media paths and sound timecode are absent
The Daily Log does not provide a path that locates the actual media, and it has no sound start timecode field. Even when a sound roll appears in its table, that identifier is not a sound time position. A browsable PDF cannot replace verification of media location or sync references.
ALE and CSV can carry source filenames, path text, and sound start timecode transcribed on set, but that text does not automatically locate media on the receiver's machine, and an unentered field may remain empty. For the distinction between a sound roll and sound timecode, see Why Sound Roll Does Not Mean Sound Timecode Is Present.
When to select the Daily Log separately at export
If the receiver needs a shoot-day PDF that can be read directly, select Daily Log (PDF) separately during export. Selecting ALE or CSV prepares those respective machine-readable handoffs; it should not be treated as also exporting the Daily Log. Whether to include the PDF depends on the receiver's reading and verification needs.
At handoff, the receiver can use the Daily Log to get an overview of the Shoot Day, then return to ALE, CSV, and on-set records to verify individual fields. For where exported deliverables are stored and how to check retention, see Where Handoff Files Live After Export—and How Long They Last; do not infer those details from the report page.
FAQ
Can the Daily Log replace an ALE or CSV for post-production checks?
No. The Daily Log is a shoot-day summary for people to read. Field-level verification of media identity, time positions, or camera detail still belongs in the appropriate machine-readable handoff, checked against its source records.
Does a multicamera Take from the same Shoot Day become multiple Daily Log rows?
No. The Daily Log uses a row per Take. When a Take has several cameras, its camera-related cells use the camera whose letter sorts earliest; other cameras do not become additional PDF rows. Use ALE or CSV for camera-by-camera review.
Does a sound roll in the Daily Log reveal sound start timecode?
No. A sound roll is an identity clue, not sound start timecode, and the Daily Log does not deliver sound timecode. Check the corresponding machine-readable field and on-set sound record when that value is needed.
Must the Daily Log be selected separately when exporting ALE or CSV?
If the receiver also needs the Daily Log PDF, select Daily Log (PDF) separately. When only machine-readable details are needed, select ALE or CSV according to the handoff requirements rather than treating the Daily Log as mandatory.
Axiom One LLC — SlateX