Animation production tracking software: what a small studio needs and what it can skip

A production tracker answers one question all day: what state is every shot in? Big studios need a database for that. A small studio often needs a smaller thing, and should pick on that basis.

7 min read

By · Updated

The short answer

Animation production tracking software records every shot and asset, its pipeline step, its versions and its review notes. A studio of 3 to 10 people with one or two productions at a time can often do this with a lighter tool: one ticket per shot, a status, a version history, client review and a budget line. A full tracker such as ShotGrid or ftrack pays off when you have a pipeline team, many departments and software integrations to wire up.

The test is simple. If nobody at the studio would write or maintain pipeline scripts, you will not use most of what a full tracker sells.

What a production tracker does

Every tracker, big or small, has the same core.

  • Entities: project, sequence, shot, asset. A 90 second spot might have 3 sequences, 28 shots and 11 assets.
  • Tasks per entity: layout, animation, lighting, comp. Each has an assignee, a status and a due date.
  • Versions: each upload of a shot is a numbered version, such as `SQ010_SH020_anim_v004.mov`.
  • Review: someone watches the version, writes notes and approves or sends it back.
  • Reports: how many shots are final, how many are late, who is overloaded.

A production coordinator at a 40-person studio lives in this database. A founder at a 6-person studio mostly wants the last line, the reports, without the data entry that feeds it.

Why small studios find the big trackers heavy

ShotGrid (renamed Flow Production Tracking by Autodesk) and ftrack Studio are built for pipelines. They connect to Maya, Nuke, Houdini and other software, and they assume somebody configures statuses, task templates and permissions for each show. That is a good trade at scale.

For a small animation studio the cost shows up in three places.

  1. Setup. Someone has to define the pipeline steps and templates before the first shot goes in. That someone is usually the director or the producer, in the evening.
  2. Seats. Freelance animators come and go. A tool priced per user means you are adding and removing seats every month.
  3. The client. The client is not in the tracker. They get a Vimeo link and send notes by email, so the tracker records what happened inside the studio only.

None of this makes the tools bad. They are right for the studio they were built for. See ShotGrid alternatives for small studios for the comparison, and ShotGrid pricing and cost if cost is the question.

The four jobs a small studio needs it to do

1. Show the state of every shot

A grid or board: shot number, task, artist, status, due date. For a 28-shot spot you want to see in one glance that 9 are in layout, 12 in animation, 4 with the client and 3 final. A spreadsheet can do this for one project, but it falls apart at the second one, and nobody updates it.

2. Keep versions in order

Each upload is a new version of the same shot. The old ones stay, with their notes. When the director says "go back to v002," it is one click. Version names should follow a pattern the whole team uses: sequence, shot, task, version. If artists name files by hand, the tracker will not save you.

3. Get client notes on the right frame

This is where most small studios lose a week per production. Client notes arrive as "the walk cycle feels slow near the end." Which shot? Which frame? A review tool where the client comments at the second or frame on a specific version turns that into a list you can work through. See how to get client approval on video and video feedback tool for clients.

4. Compare budget to hours

An animation job is priced by the second, by the shot or as a fixed fee. In every case you need to know, before the last third of the job, whether you are on track. If the budget allows 6 days for a 10-second shot and the artist has used 9, you want to know on day 6, not at the invoice. See how to price animation per second and project budget vs hours.

Options for a small studio

OptionFits whenWatch out for
ShotGrid (Flow Production Tracking)You have pipeline tools and a TD to maintain themSetup time, seat management, client review sits outside
ftrack StudioSame profile, with a review and scheduling focusSame: configuration and seats
KitsuYou want an animation-focused tracker, and you can self-host it (it is open source) or use the hosted versionSomeone has to run it if you self-host; invoicing and client quotes are not its job
A general project tool (Asana, monday.com, ClickUp)You are happy to build a shot board yourselfNo version review by frame, so you add a second tool
A spreadsheetOne production, one person coordinatingBreaks when two productions overlap
OIOClient work with freelancers, shots as tickets, quote and invoice on the jobNo pipeline step tracking, no Maya or Houdini integration, no colour-managed player

Check each vendor's pricing page for current prices. For a side by side with the two most common rivals, see OIO vs Kitsu and OIO vs ftrack.

A light shot-tracking setup

You can run a small production without a database. This is a structure that works for a 20 to 40 shot job.

  1. Make one project per production. Put the quote, the animatic and the schedule in it.
  2. Make one ticket per shot. Name it with the shot code, such as `SQ010_SH020`.
  3. Use the same statuses on every shot: layout, blocking, polish, lighting, with client, final. Six is plenty.
  4. Assign each shot to one artist. If you use freelancers, give them the link to their tickets, not to the whole project.
  5. Upload each version to the ticket. Never replace a file.
  6. Send the client the review link per sequence, with a deadline for notes.
  7. Once a week, count the statuses and compare them to the schedule. See animation production schedule template.

If you run this for two productions and the weekly count is the only report you read, you do not need a tracker with 40 report types.

Managing the budget as you go

Revisions are where animation budgets go. A client who sees a blocking pass and asks for a different camera move costs half a day. The same note at the polish stage costs two days. So the order of approvals matters more than any report.

  • Get sign-off on the animatic before any animation starts.
  • Get sign-off on blocking before polish.
  • Limit rounds per stage: two on blocking, one on polish.
  • Write the price of an extra round into the quote.

See how to reduce revision rounds and how to run a small animation studio for the studio-level view.

What to ask before you choose

  • Can the client comment without making an account?
  • Can I give a freelancer access to one shot, not the whole show?
  • Are versions kept in order, with their notes attached to each?
  • Can I see budget used against budget quoted on the same page as the shots?
  • What happens to our data if we leave? Can we export the shot list and the notes?
  • Who sets it up, and how long will that take?

If the answer to the last question is "a pipeline TD for two weeks," and you do not have one, that is your answer.

Doing this in OIO

OIO is project management for studios of 2 to 10 people. A production is a project, each shot is a ticket with a status, and each upload is a version on the ticket. On a video the client comments at the second or frame without an account and presses Approve this version. Freelance animators work from a ticket link with no seat. The quote, the schedule and the invoice sit on the same project.

OIO does not track pipeline steps per asset, has no Maya, Nuke or Houdini integration, and has no colour-managed review player. A free Blender add-on can post a line to a ticket when a render finishes. If your studio lives in those tools, a dedicated tracker is the better fit. For 3D and animation work at studio scale, see project management for 3D and animation studios.

Plans as of November 2026: Free for 1 project, Solo at $19 a month, Studio at $99 a month for 5 seats, with a 7-day trial.

Questions

What is animation production tracking software?

It is software that records every shot and asset in a production with its task, status, versions and review notes. ShotGrid, ftrack and Kitsu are the best-known examples.

Do I need ShotGrid for a small animation studio?

Usually not. ShotGrid is built for studios with pipeline developers and many departments. A studio of 3 to 10 people with one or two jobs at a time can track shots as tickets in a lighter tool.

Is Kitsu free for animation production tracking?

Kitsu is open source, so you can self-host it at no licence cost. A hosted version is also sold. Check its pricing page for the current plans.

How do you track animation shots without a tracker?

Make one ticket or row per shot with the same statuses on every shot, upload each version to it, and count the statuses once a week against the schedule.

How do you keep an animation project on budget?

Get sign-off on the animatic and on blocking before polish, limit revision rounds per stage, and compare hours used against hours quoted on each shot while the job is still running.

Free tools for this

OIO for agencies and studios

More guides