EditRouteSign inTry the demo

For editing studios with recurring clients

You edit.
EditRoute runs the project desk.

Missing files, scattered client replies, conflicting notes, “which version did they approve?” — EditRoute handles the back-and-forth around each project and brings you only the decisions that need you. Your footage stays in your own storage.

Watch it resolve a difficult replyTry it on a real project

The demo is a labeled sample running the real rules. No signup, nothing is sent.

Handled
  • Asked the client only for the missing audio file
  • Stopped chasing it when they said the recorder failed
  • Recorded the corrected guest title with its source
Waiting
  • Casey hasn't reviewed Cut v2 — reminder scheduled for 9:00 their time
  • Riley is adding the final exports
Needs you
  • Accept camera audio instead of the separate recording?
  • Client asks for Friday — 1 day under your turnaround

Illustration of the owner desk. Every count in the product comes from real events — no invented savings.

One project, start to finish

The human steps stay human. EditRoute operates the transitions around them.

  1. 01

    Inputs

    Checks each submission against the client's package and asks for only what's missing — in one message, within quiet hours and a reminder budget.

  2. 02

    Replies

    Reads replies to the project address, applies clear facts with their source, and stops chasing things that don't exist.

  3. 03

    Brief

    When every required input is verified or accepted, the editor gets a versioned brief. Later changes become explicit change requests.

  4. 04

    Review

    Collects notes by email or the client page, keeps original wording and time references, and asks the named decision-maker to settle conflicts.

  5. 05

    Approval & delivery

    Approval is tied to the exact cut with a one-time code. Final exports are matched to the deliverable list before anything is sent.

The reply that breaks most tools

A form catches a missing file. The hard part is what the client says back.

Client reply

“The recorder failed — use camera audio. Also, change the guest's title to Chief Operating Officer. We need it Friday.”

  • RecordedGuest title → Chief Operating Officer, confirmed by client, with the sentence it came from.
  • StoppedThe chase for the separate audio file. No more reminders for something that doesn't exist.
  • Asked youAccept camera audio? Your package says the editor decides that — not the client, not a model.
  • Asked youFriday is sooner than your 3-day turnaround allows. It's recorded as a request, not promised.
Run this in the demo

Your storage, your bill

Footage and exports stay in your or your client's Google Drive (or wherever you already work). EditRoute stores the brief, decisions and file references — not a second copy of your archive.

Evidence, not green ticks

Every input shows how it was established: Checked by software, Confirmed by client, Accepted by studio, or Not checked. A file EditRoute can't open is “inaccessible” — never “missing”, never “passed”.

No client accounts

Clients reply to email or use a private project page. Approving a final version takes a one-time code sent to the approver.

You decide what runs on its own

Everything starts as “ask me first”. Turn on automatic follow-ups, invitations or deliveries one action at a time, after a dry run. One switch pauses it all.

What stays yours

Creative judgment. EditRoute never edits, grades, or decides whether a cut is good.

Money and commitments. Prices, extra rounds, new deadlines and scope changes always come to you.

Exceptions. Anything unusual becomes a clear decision with the evidence and options — not an inbox to reconstruct.

Start with one real projectRead what we haven't proven yet