Where a Note Is Written Determines Which Handoff Column Receives It

Before writing a “note” on set, distinguish at least three places: take-level notes, camera-level notes, and scene-level summary or description. The first two are different fields within a take record, while the third place is on the script side: a scene’s summary plus the description and notes of the shot the take belongs to; where the text is entered determines which handoff column receives it and where the receiver can find it.

Take-level notes and camera-level notes are two different fields with two different column destinations, while scene-side text belongs to another layer rather than to the same note box.

Where take-level notes and camera-level notes go

Take-level notes enter the handoff’s general note columns: ALE uses SlateX Comments, CSV uses Notes, and PDF has a note position as well. Camera-level notes go to Camera Notes-type columns and are emitted with the camera record; the PDF body has no such column. If one of these fields is empty, the other field does not fall back into its place.

One gate on that road has to be known: the ALE folds its free-text columns to ASCII (accents, typographic quotes, dashes and full-width punctuation are folded), and whatever is still non-Latin ships as an empty cell there, verbatim in the CSV and the PDF. Source-index cells — card number, scene number, file name, path — are not folded at all, so a non-ASCII value there simply ships empty. A note written in Chinese should be checked in those two files, not looked for in the ALE.

A note written at the wrong level may therefore be absent from the column the receiver expects to read. A statement about the take belongs in the take-level note, while a statement about a particular camera belongs in the camera-level note. What a Take Record Needs for Handoff provides the broader record context for these fields.

How scene-side text enters Description

The scene summary, the shot description and the shot notes are joined with a fixed separator into one SlateX Description cell in the ALE and one Description cell in the CSV. That source is different from take-level SlateX Comments and camera-level Camera Notes, so Description should not be treated as a backup note field for an individual take. Scene-level, shot-level, take-level and camera-level text have to remain separate during receiving.

When one source has no content, the handoff represents the gap according to that format’s missing-value rules. Missing Values in a Handoff: What Each Blank Means explains the difference between empty values, placeholders and generated defaults; the boundary here is simply the destination of each note source. Identify the column source before interpreting how an empty value appears.

Correct placement matters more than merely seeing a column with text, because SlateX Description, SlateX Comments, and Camera Notes correspond to different record layers.

Status changes do not write text into notes

Changing a take status does not inject status text into take-level or camera-level notes. Changing the status leaves the note fields unchanged, so choosing a status should not be interpreted as adding another line to a note field. When the receiver sees note text, it should be read as content actually stored in that note field.

The note fields themselves have no content validation and may be left empty. An empty note does not cause another note column to take over its role, and it does not cause status information to be inserted. The layers remain take-level note, camera-level note, and the scene-and-shot side.

Why an imported summary should not be read as a plot synopsis

When an external script file is imported, note-like paragraphs are not created as separate records; they are folded into the scene summary. There is another important boundary: when the summary is still empty, the earliest action paragraph can be stored there in full. The field called “summary” can therefore contain action description text rather than a manually prepared plot synopsis.

That is why the summary should not be described as a machine-generated synopsis, and its semantic quality should not be inferred from the field name. What an Exported FDX Does Not Bring Back explains other places where import and export do not make a symmetric round trip. When the receiver needs to understand the summary’s source, the actual imported content should be inspected.

Why PDF and machine-readable files still need separate checks

Take-level notes can appear in the PDF note area, but the Daily Log layout uses fixed column widths, so overlong text may not be displayed in full. The PDF should therefore not be promised as a place where the complete note text is always visible. Full-field verification should return to the machine-readable handoff or source record.

Before delivery, the receiver should verify which note source is carried by each column: SlateX Description in the ALE and Description in the CSV for the combined scene summary, shot description and shot notes, SlateX Comments or Notes for take-level notes, and Camera Notes for camera-level notes. These locations do not fall back into one another. Once the source is identified, the receiver can distinguish between text that was never entered, text entered at another level, and text clipped by page layout. Whether these texts are found by global search is covered in What On-set Global Search Actually Looks In.

FAQ

Are take-level notes and camera-level notes merged together?

No. Take-level notes go to SlateX Comments or Notes-type columns, while camera-level notes go to Camera Notes-type columns.

Does choosing a status add status text to a note?

Updating a status does not inject text into the note fields. Note content should be interpreted as the text actually stored in the corresponding note field.

Is a scene summary necessarily a plot synopsis?

No, during external script import, note-like paragraphs can be folded into the summary, and the earliest action paragraph can also be stored there in full. The field name alone does not establish that the content is a synopsis.

What should be checked before delivery?

The receiver should verify the source layers for SlateX Description or Description, SlateX Comments or Notes, and Camera Notes. If the PDF does not show the full text, the machine-readable file or source record should be used for verification.

Axiom One LLC — SlateX