Projects
Each project has its own record, including the owner and the current status.
Work OS & Operations
We build the system your kind of work needs: a production, a studio, a practice. Projects, people, schedules and files stay together with the job they belong to.
The problem
Projects, files and schedules are kept in separate tools. People spend time asking where something is instead of doing the work.
What you get
Projects, people, schedules and files on one record, shaped to your kind of work.
Each project has its own record, including the owner and the current status.
Each project lists what has been delivered and what is still outstanding.
Shoot days, deadlines and who is booked on each are kept with the project they belong to.
The team can see who is assigned to each project and what is waiting on them.
Who does what
An example
Productions, crew, shoot days and deliverables in one place.
Each production gets its own record: the title, the dates, the locations and the roles to fill.
Sample: Short film, 4 shoot days, 2 locations
People are assigned to roles and shoot days, with availability checked against your calendar when it is connected.
Sample: Camera operator confirmed for days 1 to 3
A call sheet is prepared from the shoot day, with times, locations and contacts, for you to review before it goes to anyone.
Sample: Day 2 call sheet drafted for review
Shot lists, footage, cuts and deliverables are kept with the production, with the version and what is approved.
Sample: Rough cut v2 approved, colour pending
Engagements, deliverables and reviews, with who owns what.
An engagement is opened One record per client job. Each piece of client work gets a record with the brief, the dates and the people involved. Sample: Brand film, brief attached, due 12 Dec
Work is split into deliverables Each with an owner and a date. The job is broken into deliverables. Each has an owner, a date and a status, so nothing depends on memory. Sample: Storyboard. Owner: Priya. Due Friday.
Files and reviews stay together The latest version, and what was said. Files, versions and feedback are kept on the deliverable, so you know which version is current and what was asked for. Sample: Version 3 current, two notes outstanding
Late work is flagged, and a weekly summary sent The week at a glance. Work past its date is flagged to its owner and to you. A short summary of what is delivered and what is open goes out each week, by email or Slack. Sample: Friday summary sent to Slack
Connects to
Common examples of what it can be connected to. If a tool has an inbox or an API, we can usually connect it.
What changes
Late work and spare capacity are visible without a meeting.
Project details, files and schedules are kept together.
You can see which work is late and who has capacity, without holding a meeting to find out.
How it works
One session on your projects, then a system in your Airtable account.
We start with one working session on your projects, your deliverables, and what the team needs to see each morning.
We build the system in Airtable, in your account. You can export the data.
If you want the system maintained, we meet once a week to review what the team could not find and adjust it so they can.
It lives in Airtable, in your account. You can export the data.
We connect the tools you already use. You do not have to rename your work to fit a template.
Pairs well with
Each service works alone. These are the ones that make it work better.
Book a call or send us a message, and we will come back to you.