Sheets = Database
One Google Sheets workbook holds your shots, assets, tasks, users, and schedule. It stays a normal spreadsheet — you can always open it, audit it, export it, or walk away with it.
MOTK has no servers of its own. It assembles three things your team's Google account already provides into a production tracker.
One Google Sheets workbook holds your shots, assets, tasks, users, and schedule. It stays a normal spreadsheet — you can always open it, audit it, export it, or walk away with it.
Originals and review proxies live in Drive folders owned by your team, organized per record. Backups work with the Google tools you already know.
The MOTK interface — tables, detail pages, schedule, dashboard — is an Apps Script web app deployed from your own Google account, with your own IDs. No third party in the loop.
The workbook, the media, the deployment — all of it belongs to your team's account. If MOTK development stopped tomorrow, your production data would still be sitting in your own spreadsheet and your own Drive, fully readable.
Sheets, Drive, and Apps Script are part of a standard Google account. There is no server to rent and no per-seat license — the practical cost of running MOTK is your existing Google storage.
Heavy camera originals are slow to review in a browser. MOTK's upload flow files originals into the record's folder and queues a proxy job; a worker transcodes lightweight review copies, and a scheduled audit scans for anything missing a proxy so gaps get caught, not discovered in review.