How Continuity Photos Should Link to Shots and Takes
A continuity photo becomes useful when it can be traced back to the production event that created it. In SlateX, evidence media is related to a take, a shot, and a production element: the photo belongs to a specific take, the take sits in a specific shot, and the element is a separate relationship. That lets a receiver answer “which take and shot did this image come from?” before asking “which element is this evidence about?”
The first value of a continuity photo is traceability: know which take produced it before deciding what the image says about continuity.
Keep the take–shot relationship separate from the element relationship
A photo placed in a general album has very little production context on its own. A stronger record attaches the photo to a specific take and preserves the shot it belongs to. That gives the image a production origin. The production element answers a different question: what element is this evidence tracking? It does not replace the take or shot relationship; it provides a second way to gather related evidence across records.
During review, do not treat “find by element” and “trace back to the take” as the same operation. The element can group related media. The take and shot tell you which recorded event produced a particular image. Keeping both relationships means a receiver can move from a subject-oriented group back to the production record that created each piece of evidence.
When one element has several photos, the representative image is a starting point
A production element can accumulate media from several takes. SlateX groups an element's media by shot and selects one representative image for each group. The current order starts with take status: Circle before Keep, then Hold, then N/G. When the status is the same, the selection next considers take number and record time, favoring the later record for display.
That rule answers “which image should I see first?” It does not answer “which image is the correct continuity state?” The representative image is navigation. It gives the reviewer a useful place to begin, but a person still has to judge whether wardrobe, props, placement, action, or other visual relationships actually continue from one take to another.
When a photo enters the record, bring the relationships back with it
Capturing a photo should not leave behind a file with no record context. After the media is stored, it needs to return to the current form so that its take, shot, and element relationships remain intact. That is what allows a later reviewer to move from the continuity library back to the production record instead of being left with only a timestamp and filename.
When the desktop device has no camera, a phone can capture continuity media for the desktop workflow and return it to the current form; a transfer that has not been confirmed keeps a retry record. The purpose of that nearby path is not merely to move an image between devices. It is to put the media back into the record being edited. It is not a memory-card ingest path or a general backup system.
Candidate grouping can bring images together, but it can mispair them
In the comparison workspace, unlabeled images can be grouped as candidates based on visual similarity so that material from different takes can be reviewed together. The current grouping strategy has no absolute rejection threshold for a candidate that is simply too far away. If another unused image remains available, an unsuitable pairing can still be formed. The result should therefore be read as “a candidate worth checking,” not as an automatic continuity decision.
The same boundary applies to switching, flashing, and aligning photos in the comparison workspace. Those tools help a person inspect evidence. They can organize the material and put likely comparisons next to each other, but they do not decide which image represents the correct continuity state.
A photo is evidence, not a verdict; candidate grouping can be wrong, and the final continuity judgment remains human.
A stored relationship does not mean every search dimension exists
Although evidence media carries take, shot, and element relationships, direct filtering in the current continuity library is still limited. The present entry points mainly use category plus name and note text. Direct retrieval by scene, shot, take, time or performer is not implemented. There is one more concrete trap: categories are stored as language-dependent display values, so switching the interface language can make existing categories return nothing — category search should not be read as consistent across languages. Because of this, “the photo is bound to a specific take” must not be widened into “any on-set dimension can be retrieved later”.
This is also why preserving the relationships matters even when the current search surface is narrower. Today's search interface is not the same thing as the underlying record structure. Linking media back to the take, shot, and element preserves a clear origin, while the current version still requires the reviewer to use the available filters and record context to find that evidence.
A practical order for recording continuity photos
Start by establishing the current take and shot. Return the photo or video to that record. If the media belongs to a production element, add the element relationship as a separate link. When one element has several pieces of media, treat the representative image as the first item to inspect rather than as the answer. When you need to compare takes, move into candidate grouping and photo comparison, and use human judgment to resolve a mismatch or a bad pairing.
What we cannot do today is let a photo automatically prove which continuity state is correct. The current library also does not provide direct search across every production dimension such as scene, performer, or time. Continuity evidence can be stored with structure and traced back to its production context, but interpreting that evidence, deciding whether a candidate pairing is valid, and choosing what should continue are still human decisions.
FAQ
What should a continuity photo be linked to?
Evidence media is related to a take, a shot, and a production element; use the take and shot to identify which production event created the image, then use the element relationship to gather media for the same production element.
Which image should appear first when one element has several photos?
The representative image is ordered first by take status—Circle, Keep, Hold, then N/G—and then by take number and record time, but that display order does not mean the selected image has been judged to be the correct continuity state.
How can continuity media return to the current record when the desktop device has no camera?
A phone can capture continuity media for the desktop workflow and return it to the current form; an unconfirmed transfer keeps a retry record, so the intended destination remains the current take, shot, and element relationship rather than an unstructured album.
Can candidate grouping decide whether continuity is correct?
Candidate grouping only places potentially related photos together for review; the current strategy can mispair images, so a person must confirm the grouping against the photos and the production record.
Axiom One LLC — SlateX. Figures current as of 24 September 2026.