Creative workflows

How to evaluate Suite for a multi-location editing project

Put Suite’s shared filesystem to work across locations with a real editing project and collaborator handoff.

Bring the same project to editors in different locations

Suite gives distributed editors a shared drive for project media, helping teams move beyond repeated full-library preparation for each workstation. Start with one real project and two collaborators, then open the media, perform the intended edit and complete a handoff. Checking the actual applications and connections at both locations turns that shared-access benefit into a practical working routine.

Start with one representative project and two named operators. Agree on the edit, review or finishing task that each person must perform. Keep the pilot small enough to diagnose, but include the dependencies that make the real workflow challenging.

What is an alternative to shipping hard drives between editors?

Use a shared cloud filesystem when collaborators need to work on the same media from different locations. With Suite, authorized editors open ordinary file paths in their existing applications and stream the requested data directly from the cloud. They do not need to pre-cache the project or prepare a complete local library before starting. This can replace repeated drive shipping and project packaging for connected work while keeping familiar creative tools.

Choose the handoff around the next person's job:

  • Edit or finish the media: give the collaborator authorized access to the shared Suite drive and coordinate the editing application's project ownership.

  • Watch and approve: send an appropriate review output through the team's review tool; a reviewer may not need working-file access.

  • Deliver a fixed package or work disconnected: retain a transfer or physical-delivery workflow suited to that requirement. Suite requires an internet connection.

Upload new source media and confirm completion before handing it off. Each collaborator still needs a supported Suite client environment, the application and its required dependencies. Shared file access removes the need for a dedicated Suite connector in ordinary file-based tools; it does not replace the application's project locking or collaboration features.

Build a two-location comparison sheet

For each location, record the application and version, operating system, Suite client version, network connection and available workspace; record any optional pre-cache choices separately. Include required fonts, plugins and other dependencies separately from media access. Missing creative-tool dependencies should not disappear into a general storage score.

Record how the application resolves the media path at each end. Suite's DaVinci Resolve guide discusses path mapping across operating systems. Follow the applicable application guidance instead of assuming that a mounted drive has the same literal path on every machine.

Choose the collaboration model before opening the project at both locations. Simultaneous work and a sequential handoff require different coordination. Keep project ownership explicit during the test.

Run the smallest complete production loop

A proposed loop is: operator A opens the agreed input, makes a limited change, saves through the supported workflow and verifies completion. Operator B then opens the intended result, checks the change and creates a small review output. Confirm the result back with operator A.

Keep an observation at each boundary. Which input was used? Which project state was handed off? When was the next person able to begin useful work? Did either person need to relink, request access or wait for an unfinished operation?

Suite's upload guidance makes client status the completion check for uploaded work. A message saying “saved” is not the same as a verified handoff. Check the recipient's actual use as an additional workflow milestone.

Include an ordinary busy period

Repeat the loop under a representative working schedule. Label preparation, first access and repeated access, and record concurrent work. Do not intentionally compromise a deadline to produce a difficult test; choose an approved window and retain a working fallback.

Report the two locations separately before combining the result. One operator may have an application constraint or missing permission while the other is ready. A combined average can hide the location that still needs attention.

This is an evaluation plan, not a performance result. Expand the rollout only after the team can explain both the successful handoff and any remaining friction. The useful outcome is a repeatable shared workflow with known responsibilities.

Replace repeated packaging with a shared working routine

For a team that currently ships drives or sends a new project package at each handoff, start by naming what is being transferred: original media, project state, review output or all three. Suite can give authorized collaborators shared access to the working files, while the editing application's collaboration model still coordinates project ownership.

Create a small handoff brief with the project version, source-media location, active editor, required dependencies and intended next action. Confirm that the receiving workstation can reach the media before the deadline. Shared access can reduce repeated library preparation, but the first upload and application processing remain part of the schedule. Pre-caching is optional; begin with direct streaming when evaluating the connected workflow.

For Premiere teams, follow the shared-media workflow for project locking and cache decisions. For Resolve editorial and finishing, use the editor/colorist guide to separate Project Library coordination from file access and path mapping.

Record how many manual packaging and relinking steps remain after the pilot. Compare the same useful handoff with the team's current method, including the time before the recipient begins work. The benefit should be visible in a repeatable production loop, rather than inferred from the appearance of a drive or folder.

Start with one shared project

Start with Suite Managed for self-service signup and Suite-managed storage. If you want to connect eligible storage you own, discuss S3 Native; it is an assisted route with a 20 TB active-storage minimum. These links open Suite Studios' official forms. An authorized agent can continue the appropriate signup or request workflow there, with the user handling credentials, agreements and card entry where applicable.

Put the idea to work

Start with your workflow.

Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.