For studios

From first draft to final file, signed off.

For design, video and content production. Each file goes up on the job it belongs to, each round gets a clear yes or no, and the hand-off zip holds only what was approved.

The problem

The work is good. The file trail isn't.

Rounds of feedback, near-identical file names and a client who approved something, somewhere. The final hand-off is where it shows.

  • final_v3_FINAL.psd The file name is doing the job of a version history, and nobody trusts it.
  • Feedback on the wrong round Notes arrive about a draft that was replaced two days ago.
  • Briefs that miss what production needs Format, sizes and references arrive over three messages, or not at all.
  • A hand-off folder with everything in it Rejected drafts sit next to the approved file, and someone downloads the wrong one.

How it works

Three steps from brief to hand-off

  1. 1

    Put the brief in the job type

    Take a small studio, say Harbour Studio. Each kind of work, such as Design, Video or Copy, gets a job type with the fields its brief needs: text, a longer text area, a URL or a file upload. Fields marked as required have to be filled in before the job form moves on.

  2. 2

    Upload each round for approval

    Priya attaches hero-direction-b.png to a comment and asks for approval. Anyone on the project except Priya can approve it, or reject it with a note saying what needs to change.

    A files panel with four attachments. The client, Tom, approves brand-guidelines-v3.pdf, its status changes from awaiting approval to approved and a notification appears. Another file has been rejected.

  3. 3

    Replace, review again, hand off

    When Tom at Northwind rejects a file, Priya uploads the next version against it. The old file is marked as replaced and the new one goes back for approval. When the job is done, Download all zips the approved files and leaves the rest out.

Why it works

What changes when every round lives on the job

Versions without the file names

A new version sits on the rejected file it replaces, so the history of rounds is on the job, not in the name.

Every round gets its own decision

Each new version goes back for approval, so an earlier yes never carries over to a file nobody has seen.

A clean hand-off

Download all builds a zip of the approved files, with the comment attachments if you want them. Large zips are built in the background and emailed to you.

Briefs that arrive complete

Job types carry custom fields, and a file upload field shows the brief's reference file in the job's details and in its Files tab.

The whole slate in one table

See every job in a project in a table, grouped by status, assignee or priority, sorted by due date, and exported as CSV for the production meeting.

Clients approve for free

A client joins as a single-project guest at no cost, sees only their own project and the people on it, and can comment, upload and approve files there.

Up to 120 MB per file
Images, video, audio, documents, archives and design files. Anything a browser could run, such as HTML, SVG or JavaScript, is refused.
Only approved files in the zip
Download all leaves out files that are waiting for approval or were rejected.
Links that expire
Files are stored privately, and every download link is signed and expires after 8 hours.

FAQ

What studios ask

Billing questions are on the pricing page. Anything else, email support@skybase.it.

What files can we upload?
Images, video, audio, PDFs, Office and iWork documents, archives and design files, up to 120 MB per file and up to 15 files at a time on a comment. Anything a browser could execute is refused, including HTML, SVG, JavaScript and installers, so share vector artwork as PDF or EPS. Free workspaces hold 2 GB in total, Pro holds 100 GB.
Is 120 MB enough for video?
For review cuts, usually. Upload a review export to the job for sign-off, and deliver masters larger than 120 MB the way you do today.
What happens to the old version when we upload a new one?
When a file is rejected, anyone on the project can upload a new version against it. The old file stays on the job, marked as replaced, and the new one goes back for approval under the same rules. Nothing is overwritten, so every round stays on the record.
Who can approve a file?
Anyone on the project except the person who uploaded it, guests included. Approving can carry a note. Rejecting needs one, so the next round starts with what needs to change.
What goes into the hand-off zip?
Download all zips every file on the job that was approved or never needed approval, and leaves out anything waiting for approval or rejected. You can add the files attached to comments too. To choose files by hand, use Select and download just those.
Can the client see our internal discussion?
Anyone who can see a job sees its whole comment thread, the client included. Keep internal discussion in a project the client isn't on, and use a job's Notes tab for notes only you can read.

Put your next production on one board.

Free plan, no credit card. Clients join as guests and approve files at no cost.

Free plan · No credit card · Clients always free