preroll.io docs
Features

Deliverables

Upload files for client review with a structured approval workflow.

Open with AI:ClaudeChatGPT

Deliverables are the files you produce for your clients — edited episodes, video cuts, show notes, transcripts, or any other asset that requires client approval before publication. preroll.io provides a structured workflow for submitting, reviewing, and approving deliverables.

Creating a Deliverable

  1. Open an episode's detail view
  2. Navigate to the Deliverables tab
  3. Click Add Deliverable
  4. Upload your file (or link an external file)
  5. Add a title and optional description
  6. Click Submit for Review

Supported File Types

Deliverables support any file type. Common uploads include:

TypeExamples
Audio.mp3, .wav, .m4a, .flac
Video.mp4, .mov, .mkv
Documents.pdf, .docx, .txt
Images.png, .jpg, .svg

Files are uploaded to Cloudflare R2 and served via signed URLs for security.

Uploads

There is no per-file size limit. Files over 100 MB automatically use multipart upload (chunked at 64 MB) for reliable delivery of large video files. Total upload capacity is limited by your plan's storage quota (Free: 10 GB, Pro: 500 GB, Studio: 2 TB).

Approval Workflow

Deliverables follow a clear approval lifecycle:

Draft → Submitted → Approved
                  ↘ Revision Requested → Resubmitted → Approved
                                                      ↘ Revision Requested → ...

Statuses

StatusMeaningWho sets it
draftUploaded but not yet shared with clientProducer
submittedSent to client for reviewProducer
approvedClient has approved this deliverableClient
revision_requestedClient wants changesClient
resubmittedProducer uploaded a revisionProducer

Submitting for Review

When you submit a deliverable:

  1. The status changes to submitted
  2. The client receives a notification (if portal access is configured)
  3. The deliverable appears in the client's portal
  4. A note is added to the episode's activity feed

Client Review

Clients review deliverables through the Client Portal or the Review Player:

  • Approve — Marks the deliverable as approved, triggers a notification to the producer
  • Request Revision — Client adds a comment explaining what needs to change

Handling Revisions

When a client requests a revision:

  1. You receive a notification with their feedback
  2. The deliverable status changes to revision_requested
  3. Make your changes and upload a new version
  4. Click Resubmit — the status moves to resubmitted
  5. The client is notified of the new version

Previous versions are preserved in the deliverable's history.

Version History

Each deliverable maintains a version history:

  • Every resubmission creates a new version
  • Previous versions remain accessible
  • Clients can compare versions in the review player
  • Version notes document what changed

Client Notifications

The approval workflow triggers notifications at key points:

EventNotification to
Deliverable submittedClient (via portal + email)
Revision requestedProducer (in-app + email)
Deliverable resubmittedClient (via portal + email)
Deliverable approvedProducer (in-app)

Email notifications include a magic link that takes the client directly to the deliverable in their portal.

Deliverable Organization

Per-Episode View

Each episode shows its deliverables with status indicators:

  • Green checkmark — Approved
  • Orange clock — Awaiting review
  • Red exclamation — Revision requested
  • Gray circle — Draft (not yet submitted)

Bulk Submission

Submit multiple deliverables at once:

  1. Upload all files to the episode
  2. Select the deliverables you want to submit
  3. Click Submit Selected

Linking External Files

For files too large to upload or stored in external systems, create a deliverable with an external link:

  • Frame.io review links
  • Google Drive share URLs
  • Vimeo private links
  • Dropbox share links

The approval workflow works the same way regardless of where the file lives.

Deliverable Metadata

Each deliverable tracks:

FieldDescription
TitleName of the deliverable
DescriptionWhat this file is / context for the client
TypeAudio, video, document, image, other
Submitted atWhen it was sent to the client
Reviewed atWhen the client took action
Turnaround timeCalculated time between submission and approval

Tips

  • Name deliverables clearly — "Episode 47 Final Mix v2" is better than "export_final2.mp3"
  • Add context in the description — Tell clients what to listen/look for
  • Use draft status — Upload work-in-progress files without notifying the client
  • Review the activity feed — See the full approval history at a glance

On this page