Production management · 16 October 2026

Freelancers in and out: how to run a job with a changing crew

To run a job with a changing crew, treat every freelancer’s time on it as three moments: a clean start with access to only the projects they work on, a hand-over when they leave, and an exit on the day they finish when their access is closed. Keep their work in the job’s own structure rather than on their own drive or in direct messages, so the next person can pick it up without a phone call. Most small CGI, animation and post studios run on freelancers, so this is less an HR question than a production one.

What goes wrong when the crew changes mid-job?

Work and knowledge leave with the person, while their access stays behind.

The usual problems are predictable. The latest version of a shot sits on a freelancer’s own drive. The client’s notes on that shot were forwarded in a chat thread nobody else can see. The file naming made sense to the person who invented it. And when they leave, their access to the shared drive and the review tool stays open for months, because nobody remembered to close it.

Access is easy to underestimate. Google’s admin documentation for Workspace, for example, notes that transferring Drive files to a new owner does not change who has access to them, that the previous owner can still edit transferred files unless their account is deleted or their permissions are changed, and that ownership can only be transferred between users in your own organization. A freelancer working from their own outside account is not in your organization, so the files they created and shared stay theirs unless you plan for that at the start.

What should day one look like?

Access to exactly what they need, in your structure, under their own name.

On day oneWhy
Their own login, invited to the specific projectsYou can see who did what, and close access for one person
No access to other clients’ projectsThey see the job, not the studio’s whole client list
Files saved in the job’s folders, not their own driveThe next person finds the latest version
The naming and versioning rules for the jobVersions stay readable after they leave
Client notes for their shots, in the client’s wordsNo interpretation lost in a forward
An end date for their access, written downThe exit is planned, not remembered
The hand-over note format, shared up frontThey know what you will ask for at the end

The end date is the line most studios skip. Writing it down on day one, even if it changes, turns “close their access” into a scheduled task instead of a good intention.

How do you hand over work when someone leaves mid-job?

Ask for a short, written hand-over note per shot or task, on their last full day.

A hand-over note does not need to be long. It needs to answer the questions the next person would otherwise ask by phone:

  • Status per shot or task: done, in progress, waiting on the client, blocked.
  • Latest version: the exact file or version number, and where it lives.
  • Open client notes: which notes are addressed, which are not, and any the freelancer disagreed with. This is much easier when notes arrive as one list per round, as described in how to give video feedback an editor can act on.
  • Known problems: a simulation that breaks at frame 140, a texture that needs replacing, a plugin version.
  • Setup details: anything unusual in the scene file or project settings.

The studio’s job is to make the note easy. If tasks and versions already live in one place per project, the note can point at them instead of describing them. If they live in four tools and a chat history, the note becomes a treasure map, and the first day of the next freelancer goes to reading it.

How do you close access properly?

Go through every tool the freelancer touched, on their last day, and check links they created as well as their logins.

  1. Review and task tools: remove them from the project, or end their seat.
  2. Shared drives and file storage: remove their access, and move files they own into a studio-owned location first.
  3. Share links they created: check which links to client or studio material they sent out, and withdraw the ones that are no longer needed.
  4. Chat and email lists: remove them from project channels.
  5. Software licenses: take back any floating or studio-paid licenses.
  6. The job file: note the date access was closed.

This takes 15 minutes if it is a habit, and hours if it is done six months later from memory.

What do tools charge for a temporary crew?

Check whether a temporary person costs a full seat, and whether the plan caps the number of members.

Per-member pricing makes a changing crew expensive in ways that only show up on the invoice. As of October 2026, Frame.io’s pricing page lists Pro at $15 per member per month on monthly billing with up to 5 members, and Team at $25 per member per month with up to 15 members, with a discount for annual billing. External reviewers on share links do not take a paid seat. A studio that brings in three extra freelancers for a busy month can run into the member cap rather than the price.

Where Frame.io is stronger: its homepage highlights notes that reach the editor inside Adobe Premiere Pro and Camera to Cloud uploads from set, and its features pages describe native apps for iOS and iPad. If your freelancers live inside Premiere all day, that integration may matter more than the seat model. For a wider comparison, see Frame.io alternatives for small studios.

Other tools take a different approach to crew who come and go. In Kadrenta, made by the same team behind The Production Brief, a freelancer with their own Kadrenta account can be added to just the projects you invite them to, and that costs your studio no seat. A freelancer on a free account gets two weeks of this, once, and after that needs a plan of their own or one of your seats. Clients and reviewers on a link never cost a seat. Paid seats for your own team can be handed back, moved to someone else the same minute, or given an end date, and being added to a project asks for the person’s consent.

And what does this look like from the freelancer’s side?

The same three moments, seen from the other end, protect the freelancer too.

A clear start tells you which projects you are on and what is expected. A written hand-over shows exactly what you delivered, which helps if questions come up later. A clean exit means nobody can blame a later change on your access. Ask for the end date and the hand-over format at the start, keep your own short record of what you delivered and when, and confirm in writing when your access has been closed.

For studios that track all of this in a spreadsheet, the signs that a crew has outgrown it are described in when a video studio outgrows spreadsheets.

Frequently asked questions

Should freelancers use their own accounts or studio accounts?

Their own, where the tool allows it, invited to the projects they work on. Shared studio logins make it impossible to see who did what, and you cannot close access for one person without changing it for everyone.

How long before a freelancer leaves should the hand-over start?

Ask for the hand-over note on their last full day, not their last hour. That leaves time for questions while they are still on the job.

Do freelancers need access to client feedback?

They need the notes that apply to their work, in full and in the client's words. They rarely need the whole client thread, the budget or the contract.

What should a freelancer keep after the job?

Whatever your agreement allows, often a portfolio copy once the work is public. Agree it at the start so nobody has to ask afterwards.

Sources