Delivery SOP · v1.0

Master File Delivery — Standard Operating Procedure

How every Twyn capture session's heavy files (audio masters, AIM onboard video & telemetry, scan data) get to the client — safely, verifiably, every time.

Home\nLeads\nVehicles\nLicensing\nAudio\n3D Scan\nPhysics\nSOP

1 · The principle

The Twyn apps carry the paperwork (runsheets, reports, approval packs). Google Drive carries the masters. Every app has a "delivery folder link" field — the link is the thread that ties the record to the files. A session is not "delivered" until the folder link is in the runsheet and the checkboxes are ticked.

2 · Folder taxonomy (create once per session)

All deliveries live in one Google Shared Drive (not "My Drive" — Shared Drives survive staff changes and have proper access control) named Twyn Deliveries. Inside it, one folder per client, one per session:

Twyn Deliveries/
└─ {Client}/
   └─ {YYYY-MM-DD}_{Vehicle}/          e.g. 2026-08-04_Ferrari_F40
      ├─ 01_Audio_Masters/             multitrack WAVs, exactly as slated
      ├─ 02_Onboard_Video/             AIM camera exports, full length
      ├─ 03_Telemetry/                 AIM data files (.xrk/.drk + CSV export)
      ├─ 04_Scan_Data/                 scan deliverables per client spec
      └─ 05_Docs/                      exported runsheet, physics approval pack, photos

Naming: date first (sorts chronologically), vehicle with underscores, no spaces. File names inside must match the run log slates — the client's audio team navigates by slate.
05_Docs always gets: the exported Audio Runsheet HTML, the Physics approval file, and nothing else — it's the session's self-describing index.

3 · Upload procedure

Install Google Drive for desktop on the capture laptop. Sign in with the Octane account. This is mandatory — desktop sync survives dropped connections and handles 100 GB+ files; browser upload does not.
Copy the session's files into the local synced session folder in the structure above. Copy, don't move — the originals stay on the capture SSD until step 6.
Let it sync. Check progress in the Drive desktop menu — do not close the laptop until it shows complete.
Spot-verify in the browser: open 2–3 of the largest files' preview, check sizes match the local copies.
In the relevant Twyn app: paste the session folder link, tick the delivery boxes, export the client file into 05_Docs.
Only after the client confirms receipt: the capture SSD becomes the retained local backup (kept minimum 90 days, labelled with the session name).

4 · Sharing policy

Never use "Anyone with the link". This is unreleased-game material under NDA. Studios treat leaks as contract-ending. Share the session folder (not the whole drive, not the client folder) with the client's named recipients' email addresses only, as Viewer. If their IT blocks external Google access, fall back to MASV (below) — never to a public link.

Recipients are named in the booking email; if in doubt, ask the client producer who should receive.
Access is removed 30 days after the client confirms they've pulled the files.
Internally, the Shared Drive is restricted to the Twyn delivery team.

5 · Fallback — MASV

If a client can't access Drive, use MASV (media-industry large-file delivery, pay-per-GB, resumable, delivery receipts). Same folder structure zipped per subfolder; paste the MASV package link into the app instead. Drive remains the archive of record either way.

6 · Who does what

Recording engineer: steps 1–4 on the day or same evening.
Session lead (Will): step 5, plus the client notification email with the folder link.
Anyone: if the "Stale — re-verify" or missing-checkbox state persists 48h after a session, chase it. An unticked box means an undelivered session.

Definition of done: masters synced ✓ · spot-verified ✓ · folder shared to named recipients ✓ · link + ticks in the app ✓ · exported record in 05_Docs ✓ · client confirmed ✓ · SSD labelled and shelved ✓

Octane Twyn · Octane Sports Entertainment FZCO · internal SOP — do not distribute outside the delivery team.