Digital script supervision
Script coverage, per-take records,
and deliverables someone can check
Recorded on set, delivered to post.
SlateX is a digital script supervision app built natively for iPhone, iPad and Mac — for the person on set who is responsible for the day's record.
On-set recording and handoff method →
Whether a handoff file goes straight to the edit is for the receiving side to verify. We do not claim it conforms on their bench.
Script · coverage
Coverage follows the script's own structure
Import FDX and read each scene's length to the eighth of a page. On the script page the two tracks are Master and Coverage; double-tap a track cell and the coverage marks for a whole dialogue block change at once.
With numeric shot naming the right-hand track never appears.
Take · rating
Circle / Keep / Hold / N/G — the words the set actually uses
Rate each take as it happens; the take number is the highest number already in that shot, plus one.
We do not invent a fifth word.
Continuity · reference
Attach continuity references to the take they belong to
Continuity material is linked to a specific take; across takes it is grouped by shot, and a reference image is picked by rating and take number. After image alignment on the comparison screen you can flicker through the takes one by one.
Grouping only offers candidates — the judgement stays yours, and ordering is a starting point for finding things, not a continuity call.
On set · offline
Hand material to the right machine with no network
A Mac has no camera: start the take from the Mac, an iPhone shoots it and sends it back. The receiver only acknowledges once the file and its record are both stored, and anything unacknowledged is resent.
This path runs between iPhone and Mac only, and it does not resume interrupted transfers.
Handoff
Export a per-camera ALE, with reel and clip numbers auto-numbered by camera
Record on set. Generate FDX, ALE, CSV and PDF for handoff at wrap.
Per-camera detail stops at ALE and CSV — the PDF carries the first camera only. A receiving editor still checks the exchange file field by field.
Project → (Episode) → Scene → Shot → Take
├ camera
└ continuity refs
↓
FDX · ALE · CSV · PDFBefore wrap, you should be able to check it yourself
You do not have to take our word for it. The order is fixed: keep what was already recorded, place every object in an explicit relation, then make the deliverable checkable.
Grab a take without committing anything: it captures the current timecode and duration, and becomes a take only once you confirm. Close it and nothing happened. What you did record sits under your own account — we hold no key to it.
Coverage is anchored to the script lines, each take to a shot and its cameras, each continuity reference to a take — so the record does not collapse into one flat list.
Fields and naming all come from the same record, so the recipient can check it field by field.
Design positions
Four things we do not trade away
You can check all four against the app itself.
No dirty data
If it is not certain it does not become a take — stopping, rolling back, or quarantining beats half a record.
Fail rather than overwrite your setup
If a preset cannot be resolved, the whole import fails instead of quietly replacing it with empty values.
Quarantine rather than pretend it worked
A transfer that cannot finish is quarantined, never reported as delivered.
Export never touches the original
Every deliverable is a read-only copy of the record.
Data, timecode and the workspace
Two things we can state plainly: which account the data lives under, and how timecode is counted. Everything else is interface.
Ownership
Your material lives in your own private iCloud store under your Apple account; we hold no key to it. SlateX is just the read-write interface.
The part that is never gated
Cancel and you still own the log: open it, edit it, delete it, close the account.
Timecode
29.97 counted at 29.97, shown at 30. Bluetooth timecode hardware sync — one device at a time.
Mac workspace
A multi-window workflow rewritten natively for Mac: separate windows split by working role, not a phone layout enlarged.
What a set needs is not convenience. It is reliability.
One record chain: script coverage, takes and continuity references — and at wrap something a receiver can check.