# Feature: On-Set VFX Supervisor Shot Log ## Overview Add a new module to the existing VFX Review project called **Shot Logging** (working title: **VFX Supervisor Reports**). This is **not** simply a spreadsheet of takes. It is a production tool designed for VFX Supervisors to log every setup and take while on set using an iPad or phone. The design must fit naturally into the existing VFX Review architecture, coding standards, authentication system, permissions and database structure. This feature will later integrate with Shot Reports, Reviews, Assets and the VFX pipeline, so everything must be designed around reusable relationships instead of duplicated data. --- # Primary Goals The application must allow a supervisor to: * create a shoot day * create setups * create unlimited takes within a setup * quickly duplicate previous take information * review previous takes without leaving the current page * attach unlimited reference images * capture complete VFX metadata * work efficiently while standing on set with an iPad The workflow should require as few taps as possible. --- # Future Integration Design the database so this module can later connect to: * Shot Reports * Review Sessions * Final Shots * Assets * Camera Reports * Production Notes * Editorial * Deliverables For example: A Shot Report should later be able to display * every logged take * supervisor notes * all reference images * HDRI status * tracking marker notes * camera information without duplicating data. Avoid storing information twice. --- # UI Requirements This page is intended primarily for iPad landscape orientation. Requirements: * touch friendly controls * large tap targets * Apple Pencil friendly * responsive * works well on desktop * works on phones for quick edits The page should never feel like filling in a spreadsheet. Think of it as a digital clipboard. --- # Layout Use a split layout. LEFT SIDE A scrollable list of all takes. Example Setup A Take 1 Take 2 Take 3 Take 4 Each take should display: * take number * clip name * quality colour * notes indicator * image count * warning indicators Selecting a take loads it instantly. No page reload. --- RIGHT SIDE Displays the editable take. Changes should autosave. --- # Fast Navigation Allow: Previous Take Next Take Duplicate Previous Take New Take New Setup Keyboard shortcuts on desktop. Large touch buttons on iPad. --- # Smart Autofill The application should remember previous values during the current shoot. Examples Lens Cooke S4 50mm ↓ Suggest again Camera Alexa Mini LF ↓ Suggest again FPS ↓ 24 ISO ↓ 800 White Balance ↓ 5600 Filters ↓ reuse previous Clip names should intelligently suggest the next sequential clip name where possible. Changing only one or two fields between takes should be the normal workflow. --- # Required Fields General * Production * Shoot Day * Date * Unit * Scene * Shot * Setup * Take Camera * Camera Letter * Clip Name * Roll * Camera Model * Resolution * Codec * FPS * Shutter * ISO * White Balance * Colour Space Lens * Lens Set * Lens * T Stop * Filters * Anamorphic Tracking Checkboxes for * HDRI * Chrome Ball * Grey Ball * Macbeth Chart * Clean Plate * Survey * Lidar * Witness Camera * Lens Grid * Texture Photos * Photogrammetry Lighting * Weather * Sun Direction * Artificial Lights Supervisor * Notes * Continuity * VFX Requirements * Quality Rating --- # Unlimited Images Each take can contain unlimited images. Support: * drag and drop * upload * direct camera capture * iPad camera * phone camera Images should upload in the background. Do not block editing while uploads complete. Each image should store: * filename * timestamp * uploaded by * optional caption * optional category Suggested categories * Slate * Camera Position * Wide Reference * Lens * Lighting * HDRI * Tracking * Texture * Witness * Miscellaneous Images should appear as thumbnails. Selecting a thumbnail opens a gallery viewer. Allow deleting, renaming and reordering. --- # Previous Takes Panel One of the most important features. The supervisor should always be able to see previous takes while entering the current one. Provide: * previous take summary * compare current vs previous * highlight changed fields For example Lens 50mm ↓ 85mm highlighted ISO 800 ↓ 800 unchanged This makes continuity checking very fast. --- # Autosave Every field should autosave. No Save button. Unsaved changes should be visually indicated. --- # Offline Ready The architecture should support offline editing later. Design APIs and local state with synchronisation in mind. --- # Attachments Each take should later support attaching: * videos * HDRIs * LiDAR files * lens grids * PDFs * documents Design the database with generic attachment support rather than image-only support. --- # Database Design Normalise data appropriately. Suggested entities: ShootDay Setup Take TakeImage TakeAttachment Lens Camera Location Weather User Avoid storing repeated strings where practical. --- # API Design Create REST endpoints consistent with the existing VFX Review API. Support: Create Read Update Delete Autosave Bulk image upload Image deletion Pagination where appropriate. --- # UX Goals The application should feel fast enough that a supervisor can log an entire take in under 20 seconds. The interface should minimise typing. Prioritise: * autocomplete * remembered values * one-tap selections * large touch controls * quick navigation * minimal modal dialogs The supervisor should never lose context while moving between takes. --- # Future Enhancements Keep the architecture open for: * voice notes with speech-to-text * Apple Pencil annotations * drawing on reference images * GPS logging * barcode/QR scanning * camera metadata import * live camera feed integration * Shot Report generation * continuity checking * production analytics * completeness validation (HDRI missing, no clean plate, etc.) Build this as a first-class production module that integrates seamlessly with the existing VFX Review platform rather than as a standalone form.