Editing for Three Studios at Once? One Inbox for All Your Assigned Projects

If you’re a wedding video editor, color grader, or retoucher who works with more than one studio, your Monday morning probably looks like this:

• Open Slack for Studio A. Scroll. Find two new messages with Frame.io links.
• Switch to Studio B’s HoneyBook. Log in again because the cookie expired. Find the project you’re supposed to cut this week.
• Open Studio C’s Notion. Their client had feedback on v2. It’s in a comment on row 14 of a database. Why is it always row 14.
• Switch back to Studio A because you forgot to check a deadline.
• Realise you’ve now opened eight tabs and can’t remember which cut you were supposed to export first.

This is the editor’s tax. Every working editor pays it. Nobody talks about it because “that’s just how it is.”

The real shape of the problem

Editors aren’t exclusive employees. The going rate for skilled wedding and event editors sits around $40–$90/hour, and almost everyone at that level works with 3–8 studios at a time. The math makes sense for both sides. The editor gets steady income even when one studio has a slow month. The studio doesn’t pay benefits, a desk, or a salary — they pay per project.

What doesn’t scale is the ops layer. If each studio has its own tool, its own project tracker, its own Slack, its own delivery system, you end up doing 30% admin and 70% editing — when it should be the other way around.

The specific failure modes I hear from editors over and over:

1. Missed deadlines — because you tracked a Studio B deadline in your head while logged into Studio A, and forgot.
2. Version confusion — because v3 from Studio A and v3 from Studio B are both in your Downloads folder, both named Final.mp4.
3. Payment limbo — because you finished the cut but forgot to invoice Studio C, and they don’t chase you, so 45 days later you notice.
4. Context cost — every tab switch costs roughly 90 seconds of reorientation. At 20 switches per day that’s half an hour of pure friction.

Each is small. Cumulatively, it’s a full morning a week.

What the fix looks like

The fix isn’t “a better tool per studio.” You don’t control which tool your studios use, and lobbying three clients to change their workflow is a losing battle.

The fix is one workspace where your assignments from every studio show up in one list, regardless of which organisation owns the project. That means: you log into one tool, you see every project you’re assigned to, sorted by deadline across all employers. Click one to open it and you’re editing that studio’s project inside that studio’s Kanban — but you didn’t have to remember which studio it belonged to.

The studio tool still belongs to each studio. The editor just gets a cross-cutting view on top.

How FlowShot’s “My Tasks” works

FlowShot is built multi-tenant — every studio is its own organisation, with its own projects, clients, and templates. When a studio invites you as a team member (editor, photographer, videographer, etc.), you get access to that org’s workspace.

If three studios invite you, you’re a member of three orgs.

The default flow is: pick an org from a dropdown, work inside it. That’s fine for an owner who runs one studio.

For editors with multiple employers, there’s a dedicated route: /my-assignments — the cross-organisation inbox.

Here’s what that page actually shows. One table. Every project you’re assigned to, across every organisation you belong to, in a single row list. Columns:

• Project name
• Studio (which organisation)
• Status (based on that studio’s Kanban columns)
• Your role on the project (Video Editor, Photographer, etc.)
• Most urgent deadline — date, coloured red when under 3 days out
• Payment status — unpaid count with a badge

Sortable by any column. The default sort is by deadline, so the most urgent thing for you (not for any one studio) sits at the top.

The part that actually matters: click-through

This is what makes it more than a dashboard. When you click a project, the project drawer opens inline — you don’t have to manually switch orgs.

You can read the brief, see the shot list, check the notes, view the timeline with client feedback, download RAW footage links, update the project status. All of it. Without ever changing which organisation you “are” in. From the studio’s side it looks like you’re inside their org doing the work; from your side, you never left the unified inbox.

When you’re done, click X. You’re back in the list. Next assignment.

This is the one thing most studio tools get wrong — they assume “I am always working for one employer at a time.” For solo studio owners, sure. For editors and freelancers, not even close.

The view-mode toggle

A subtle detail worth mentioning. The list has two modes:

• Assigned (default) — only projects where you are listed in the assigned crew, editor, or photographer role
• All — every project in every org you belong to, whether assigned to you or not

Most editors want Assigned. But if you’re a senior editor who also helps with scheduling or QA across projects, the All mode shows everything your studios are working on.

Switch between the two with a toggle at the top of the table.

Hiding completed projects

Wedding-season editors often have 40+ completed projects they don’t want to see anymore. There’s a per-project “Hide” action that moves a project out of your list (per-user — it doesn’t affect the studio’s Kanban). The hidden ones go into a “Hidden” modal, reversible. When a studio archives a project that you’d already hidden in your list, it cleans itself up.

This keeps the inbox focused on what you actually need to look at today.

Multi-format workflow (photo + video editor)

If you’re a photo editor at Studio A and a video editor at Studio B, both kinds of projects show up in the same list. FlowShot is unified around a project with primaryFormat: 'photo' | 'video' and a formats array — so “video project” and “photo project” aren’t different entities you have to reason about separately. Both are projects, both in your list, both clickable.

The role shown in the “Your role” column clarifies which hat you’re wearing for each one.

Payment: the other half of the story

Once you’ve finished a cut or delivered retouched photos, the next question is always “how do I invoice this studio?”

Most editors solve this with Google Sheets, QuickBooks, Bonsai, or a free-form email. All of them work, none of them are integrated with the project you just finished.

FlowShot includes a “Request payment” button inside the My Assignments view — select the project, fill in line items, pick PayPal / Zelle / Venmo / Cash App / bank transfer / custom link, send. The studio owner sees it in their Financial Inbox and pays you out of band.

I wrote a separate article on this flow because it’s deep enough to warrant it: How to Send an Invoice to Your Studio Employer Without Another Tool. Read that if you’re about to spend another hour on a Bonsai trial.

The setup for an editor

Three studios invite you → you accept three invitations → you bookmark /my-assignments → you stop using any of the three studios’ tools as your primary view.

Every Monday morning becomes one page. Not eight tabs. The context cost disappears.

One caveat

This only works if your studios are on FlowShot. If Studio A is on FlowShot and Studios B and C are on HoneyBook and Notion, you still have to check those separately.

What I’ve seen work in practice: an editor who adopts FlowShot for their own workflow (even just for the assignments inbox and the invoicing) gradually gets the studios they work with onto it, because the editor becomes the shared thread. When your best editors move to a tool, their studios follow.

The weekend test

If you’re an editor juggling 3+ studios right now, do this experiment.

1. Count the tabs you have open on Monday at 9am. Write it down.
2. Count the times you check Slack for a studio-specific question between 9am and noon.
3. Count the hours between when you finish a project and when you send the invoice for it.

If any of those numbers is “too many to count”, the single-inbox workflow is worth trying. If all three are low, you’ve already got a system and don’t need this.

---

My Tasks is included on every paid FlowShot plan — Starter ($25/mo), Pro ($49/mo), and Business ($89/mo). To be invited as a team member you’ll need the inviting studio to be on Starter or above (Free has no team-member seats). Once invited, you see the unified inbox at no extra cost — there’s no separate “editor seat” you have to pay for as a freelancer.

See FlowShot’s project management module — Kanban, multi-org, linked photo+video projects, assigned crew management.