How PublicTide works

Your whole show in one place, from the first idea to the version you send out. Your team makes the calls. PublicTide carries the work between them.

One connected workspace

Keep the next person working from the same episode, notes and assets.

Why we built it

Making a show usually means nine tabs. Research in one doc, the rundown in another, the script somewhere else, the recording in a shared drive, the edit on one person's laptop and the approval in a group chat. Every handoff drops something. PublicTide keeps the episode in one place and lets the work travel with it, so your best people spend their time on the show, not on finding things.

— Jeremy

  1. Plan

    • ResearchGathered once and kept with the episode it serves.
    • RundownArrange the ideas you pick into timed segments, with research beside them.
  2. Record

    • ScriptDraft a full script or an outline around the rundown.
    • RecordingHosts, guests and notes kept together with the episode.
  3. Edit

    • EditTranscripts, chapters and suggested cuts, ready for review.
    • ClipsKeep each clip linked to its original episode.
  4. Publish

    • ApprovalsEach one bound to the exact version someone saw.
    • PublishingPublish to the episode's own page, or download the finished file.
  1. Plan

    RundownProduct preview
    1. Cold open1:30
    2. WelcomeIntro2:00
    3. Why the 14 was cutSegment15:00
    4. Break1:00
    5. 1:30 gap before With Dev
    6. With DevInterview · starts at 21:0025:00
    7. Sign-offOutro1:30

    46:00 planned of a 60:00 target

    Sample data from Street Level, a fictional show.

    Start with the idea. Pull in research, lay out a timed rundown and draft the script around it. What you find stays next to the segment it's for, so nobody goes looking for it on record day.

    Connected
    Research, then RundownKeep research beside the segments it informs.
  2. Record

    A host in headphones at a studio microphone

    Send your guests a link. They join from a browser, nothing to install. The script runs on the prompter, each segment shows the time it has left, and anyone can drop a mark when a moment's worth keeping. Every person records on their own track, on their own machine, so a bad connection doesn't ruin the take.

    Connected
    Script, then RecordingKeep the script, hosts, guests and session notes with the episode.
  3. Edit

    Sample data from Street Level, a fictional show.

    The transcript, chapters and clip ideas are ready when you open the episode. Describe the cut you want, see what comes back and keep what works, or cut by hand. Clips stay linked to the episode they came from.

    Connected
    Edit, then ClipsTrace each clip back to its original episode.
  4. Publish

    A drawn street scene from a fictional show

    Recorded once

    • Full video
    • Vertical clip
    • Audio episode
    • Written recap
    Sample data: drawn stills from Street Level, a fictional show.

    Nothing goes out until someone on your team approves that exact version. Change it and it needs approving again. Publish the episode to its own public page with playback, or download the finished file and upload it wherever your audience is.

    Connected
    Approvals, then PublishingApprove the exact version before anything goes out.

Edit, step by step

Describe the cut you want. Review the suggestions, apply the changes, or edit by hand.

  1. The Plan tab of the editor's Inspector. Under What is this video for, the brief reads: A 60-second vertical for Shorts. Lead with the courier van and the bakery truck. Keep it tight. Under Where is it going, Shorts is chosen from Episode, YouTube, Shorts, X, Trailer and Audiogram.The Plan tab of the editor's Inspector. Under What is this video for, the brief reads: A 60-second vertical for Shorts. Lead with the courier van and the bakery truck. Keep it tight. Under Where is it going, Shorts is chosen from Episode, YouTube, Shorts, X, Trailer and Audiogram.
    Say what the video is for and where it's going.
  2. Two parts of a planned cut in the editor's Inspector, each with Keep, Trim and Cut. The forty-one day wait, a tangent, is set to Cut: too long for a minute. A slow list is a choice, a quote of 9 seconds, is set to Keep: the line people repeat.Two parts of a planned cut in the editor's Inspector, each with Keep, Trim and Cut. The forty-one day wait, a tangent, is set to Cut: too long for a minute. A slow list is a choice, a quote of 9 seconds, is set to Keep: the line people repeat.
    Each part of the plan waits for an editor to keep, trim or cut it.
  3. The editor's Inspector after Apply: Applied 5 changes. This is revision 2.The editor's Inspector after Apply: Applied 5 changes. This is revision 2.
    Apply keeps the changes as a new revision, and Undo takes them back.
  4. A line of the transcript in the editor with a 2.5 second pause and the false start There is a, sorry, let me start again, both struck through, leaving: It's a little more than an argument. There's a sort of routine to it.A line of the transcript in the editor with a 2.5 second pause and the false start There is a, sorry, let me start again, both struck through, leaving: It's a little more than an argument. There's a sort of routine to it.
    Or cut by hand: strike the false start where it was said.

Screens of the Studio editor, with sample data from Street Level, a fictional show.

Approvals

Four rules hold for every send, post and upload.

  • Nothing is sent or posted without an approvalSomeone on the team approves that exact version for that destination, or a rule your team wrote and can stop covers it.
  • Editing voids the approvalChange a version after it is approved and it needs approving again.
  • Nothing sends on its ownResearch, drafts and preparation never send or post anything by themselves.
  • Check uncertain sends before trying againIf a platform doesn't confirm a post, check its status before sending another copy.
The top of the Distribute page in the Studio for a fictional video studio: sending is on, with a Stop all sending button, and under Needs you, three items: a connection needs you to sign in again, an approval is about to expire, and a post is waiting for you to post it.The top of the Distribute page in the Studio for a fictional video studio: sending is on, with a Stop all sending button, and under Needs you, three items: a connection needs you to sign in again, an approval is about to expire, and a post is waiting for you to post it.
All sending stops from one place, and whatever needs a person waits in one list. Sample data.

Start with one show.

Sign up, make your first show and bring your team in.