Streamlining Deliverables and Data I.O. in Post-Production

0:00 Hey everyone, Pete from Service AI here. I’m excited to show you a small part of the post-production ecosystem that focuses on deliverables and Data I/O. Deliverables are always quite complex — lots of scheduling, specs, iterations, and team members involved. The simpler we can make this, the better — it’ll be more effective and easier for you to track what’s going on.

0:21 Let’s jump right in. We’ve got the “All Deliverables” view with a few widgets up top to track what’s happening based on studio and status. Below that, the view is organized by producer.

0:42 We can organize this in many ways, but for now, I’ve got it set up to show our current deliverables.

0:46 Here we can monitor everything — tech specs, deliverable types, statuses — and this stage field even shows progress visually when you hover over it.

1:02 It helps you see how things are moving along in the delivery process. You can also view delivery methods and keep track of all the specs, contacts, emails, and due dates for each deliverable type.

1:18 Deliverables are very calendar-heavy too, so let’s open the calendar view. Here we can plan and visually see when deliverables are due — whether they need to go to the studio, QC, or production.

1:33 Let’s head back to the “All” view and click into one of these deliverables.

1:39 Let’s look at the one that’s late or in progress — we can see all of our tech specs listed on the left.

1:45 This is called the detail view. Here’s where our activity feed lives — we can drop notes, mention team members, and upload attachments if needed.

1:52 For example, if you get a dead pixel report during QC, you can upload that here so everyone stays on track.

1:59 Let’s say the next step is marking this as delivered. Once we get a file path from the digital lab, we’re ready to upload.

2:12 The operator can mark it as complete, and we can build notifications to keep you informed when things happen to your material.

2:27 Once complete, let’s kick it over to Data I/O by creating a Data I/O task.

2:32 This automation grabs all the detailed info from the deliverable and sends it over.

2:39 Inside the Data I/O app, you can see we already had one completed, and now that “Ladybird DCP” deliverable is part of the Data I/O to-do list.

2:50 They can view it in the all-view setup or in a Kanban-style view that mimics a task management system.

2:55 As a Data I/O operator, you can monitor each deliverable, its specs, and its priority.

3:11 You’ll also see the delivery method and upload contact email — crucial details when it’s time to deliver.

3:20 You can open the record to see progress and updates.

3:26 Let’s say this upload is in progress — we can drop a note to our producer, Christine, saying “Upload in progress.”

3:39 Notifications will go out automatically, and I’ll get one as well.

3:46 I’ve even set up a custom notification that says, “Your upload is in progress.”

3:52 You’ll receive push, Chrome, or email notifications — all based on user preferences. Then we can add an ETA, say one hour, since things are moving quickly.

4:05 We can even track those ETAs with a number field to monitor average upload times.

4:13 Now let’s say this upload is complete and Data I/O marks it as done.

4:20 As an operator, you’ll want to notify the client — in this case, me — that the upload is on the way.

4:30 Usually that’s a manual email process, but here you can just click the email button and add a subject — or use our automated data feature.

4:43 This automatically fills in the email subject based on the deliverable title and project.

4:53 It’s an email template using merge tags to include the deliverable name and ETA. We can create custom templates for any team, so Data I/O operators can easily notify everyone when things are on the way.

5:10 This one-click email notification process is quick, efficient, and standardized.

5:22 Come check it out — book a demo! We’d love to hear from you. Cheers.